Re: [jetty-user] JSP implementation confusion

Philippe Marschall <[email protected]> Tue, 06 Aug 2013 11:14:13 +0200
Newsgroups gmane.comp.java.jetty.support
Message-ID <[email protected]>
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.html

I see, I need to configure the server classes. Is this an area where you 
would accept a patch?

Cheers
Philippe