[
https://issues.apache.org/jira/browse/JCR-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488939#comment-16488939
]
Greg Wilkins commented on JCR-4308:
-----------------------------------
So the issue here appears to be that you have a jar inside a jar, which is not
supported by the JVM's JarURLConnection, so it is barfing when it tries to open
`jar:file:///C:/projects/apache/jackrabbit/trunk/jackrabbit-standalone/target/jackrabbit-standalone-2.17.4-SNAPSHOT.jar!/WEB-INF/lib/aopalliance-1.0.jar`,
which we want to do in order to scan for TLDs
So first question, why hasn't the webapp been extracted into a temporary
directory. Your diff indicates you have `webapp.setExtractWAR(true);`, but I
see no extracting happening? So can you confirm you have that setting.
Now, extracting the jar will probably fix the problem.... but it's probably not
the best way to go, as you appear to want to run embedded from the jar. So
instead you might like to look at setting up your webapp to be quickstarted.
This will avoid all the discovery scanning for TLDs and annotations, which can
give you a much faster start time and it should allow you to run without
expanding the jar as well. You have a little bit of a chicken vs egg
problem to generate the quickstart-web.xml file for the unextracted webapp...
but you should be able to generate it for the extracted and then perhaps edit
it before baking it into your jar.... anyway, let's fix the first problem
before optimising.
> update Jetty to 9.4.*
> ---------------------
>
> Key: JCR-4308
> URL: https://issues.apache.org/jira/browse/JCR-4308
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: parent
> Reporter: Julian Reschke
> Priority: Major
> Attachments: JCR-4308.diff, jetty.log
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
