Spot on Jan, I missed that comment. It works now (-20 seconds!).
The next challenge is to feed that same configuration to jetty:run. We have this context on the server:
<Configure class="org.eclipse.jetty.webapp.WebAppContext"> <Set name="contextPath">/langur</Set> <Set name="war"><SystemProperty name="jetty.home"/>/langur</Set> <Set name="defaultsDescriptor">etc/webdefault.xml</Set> <Call name="setAttribute"> <Arg>org.eclipse.jetty.server.webapp.WebInfIncludeJarPattern</Arg> <Arg>.*/.*langur[^/]*\.jar$</Arg> </Call> </Configure>
And this in our pom.xml:
<plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>jetty-maven-plugin</artifactId> <version>${jetty.version}</version> <configuration> <jettyXml>${basedir}/../langur-distribution/src/main/resources/etc/jetty.xml</jettyXml> <webAppConfig> <contextPath>/langur</contextPath> <defaultsDescriptor>${basedir}/../langur-distribution/src/main/resources/etc/webdefault.xml</defaultsDescriptor> <extraClasspath>${basedir}/src/main/resources</extraClasspath> </webAppConfig>
I can't figure out the equivalent of the Call element here.
Gert-Jan
On Mar 29, 2012, at 12:49 AM, Jan Bartel wrote: Geert, The default behaviour (spec compliance) is to scan all jars in WEB-INF, so an empty pattern scans all jars. Here's the comment from the code: WebInfConfiguration line 118: //null is inclusive, no pattern == all jars match Jan On 29 March 2012 02:56, Gert-Jan van de Streek < g.j.streek@xxxxxxxx> wrote:
This configuration does not seem to have any effect, while from what I understand it should effectively turn classpath scanning off:
<Configure class="org.eclipse.jetty.webapp.WebAppContext">
<Set name="contextPath">/langur</Set>
<Set name="war"><SystemProperty name="jetty.home"/>/langur</Set>
<Set name="defaultsDescriptor">etc/webdefault.xml</Set>
<Call name="setAttribute">
<Arg>org.eclipse.jetty.server.webapp.WebInfIncludeJarPattern</Arg>
<Arg></Arg>
</Call>
</Configure>
On Mar 28, 2012, at 12:27 AM, Jan Bartel wrote:
You can set the context attribute
"org.eclipse.jetty.server.webapp.WebInfIncludeJarPattern" with a set
of patterns matching jar names that you want to include in the
scanning.
Here's an example of a pattern that is used to control which jars on
the container classpath are scanned:
.*/.*jsp-api-[^/]*\.jar$|.*/.*jsp-[^/]*\.jar$|.*/.*taglibs[^/]*\.jar$
regards
Jan
On 26 March 2012 23:03, Gert-Jan van de Streek <g.j.streek@xxxxxxxx> wrote:
Classpath scanning for servlets etc is currently taking up about 20 of the starting time of our webapp. This is probably due the number of included jars (about a hundred).
Is there any way to hint the scanner which jar files to include in (or what jar files to exlude from) classpath scanning?
Met vriendelijke groet, regards,
Gert-Jan van de Streek
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________ jetty-users mailing list jetty-users@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/jetty-users
|
