Re: [jetty-user] JSP implementation confusion

Philippe,

If you raise the bug
(https://bugs.eclipse.org/bugs/enter_bug.cgi?product=3DJetty), and
attach a patch, I'll gladly apply it.

cheers
Jan

On 6 August 2013 19:14, Philippe Marschall
<[email protected]> wrote:
> On 06.08.13 00:41, Jan Bartel wrote:
>>
>> Hi Philippe,
>>
>> Yes, we use Jasper from Glassfish. It actually contains the
>> capabilities to support various different compilation types, detecting
>> at runtime what is available. For our osgi environment, we ensure that
>> we explicitly disable the jsr199 compiler as it requires a special
>> classpath that is not present in the osgi world:
>> https://java.net/jira/browse/JSP-21. For jetty-9, by default it will
>> actually use the jsr199 compiler, but you can turn that off and use
>> the JDT compiler we ship. In older versions of jetty, the JDT compiler
>> was needed (can't remember the specifics of which version, you'd have
>> to check the wiki and docs).
>
>
> Thank you for the explanation.
>
>
>> Probably a good point that we could disable access to the
>> org.apache.jasper.* classes by default. You can do it yourself using
>> the setSytemClasses() call on WebAppContext if you like:
>> http://www.eclipse.org/jetty/documentation/current/jetty-classloading.ht=
ml
>
>
> I see, I need to configure the server classes. Is this an area where you
> would accept a patch?
>
>
> Cheers
> Philippe
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>



--=20
Jan Bartel <[email protected]>
www.webtide.com =96 Developer advice, services and support
from the Jetty & CometD experts.