I haven't been following all that closely... Is the problem with the njar format that either jasper or another compiler can only deal with jar files and class files on its classpath?
(2) is easy, just requires fiddling with the build scripts a bit. If you only need one jar or file available to the compiler[s] another possibility is to extract it into a local directory. Another possibility would be to include a back door into njar that would return the path to the temp file it unpacks into. david jencks On 2002.03.10 08:57:04 -0500 Jan Bartel wrote: > The njar:file:....jetty-plugin.sar^/org.mortbay.jetty.jar is going to be > a problem for the JSP classpath. > > Either: > > (1) jars inside sars need to be extracted by the JBoss deployer > (2) we forget sar format for Jetty and put all mortbay jars into > <jboss.home>lib > > I assume that since JBoss is working hard not to have to > extract anything that option (1) won't be popular. I guess option (2) > means that we separate out the jetty jboss-service.xml file to > drop into the deploy directory and put all our jars (including > jetty-ejb.jar?) into <jboss.home>/lib, which chimes better with the > JBoss deployment philosophy. > > Jules, amongst your refactoring, are you making option (2) possible? > > Jan > > > > the Jetty JSP classpath stuff appears to be broken, for several > reasons: > > > > * to form the path, "file:" is stripped off the front of all URLs > > returned from the AbstractWebContainer getCompileClasspath(). > > On windows, you could wind up with the incorrect path /c:/blah. > > > > * to do the stripping, it is acuatally "file:".length() chars > > which get stripped from the front of each URL. That won't work > > when the url is njar:file:/blah/blah/blah, as is unfortunately > > the case with njar:file:......jetty-plugin.sar^/org.mortbay.jetty.jar > > > > I am surmising that this problem has cropped up because Jetty now > > gets handed a URLClassloader instead of an MBeanClassloader. > > > > In any case, is this one of the things that you are currently fixing, > or > > do you want me to go ahead and fix it before you commit your changes, > as > > I'm hanging out to commit the new Jetty version? > > > > > > Jan > > > > > >>> Hi Jules, > >>> > >>> I'm trying to update the version of Jetty, but everything seems > broken > >>> with JBoss/Jetty. I can't run the web integration tests nor deploy a > >>> simple war file with a JSP in it. > >>> > >>> I see from the list that you said you are working on the integration > >>> stuff, so can you please tell me what you're working on, so I know > what > >>> to concentrate on to get this update in???! > >>> > >>> ta, > >>> Jan > >>> > >> > >> > >> _________________________________________________________ > >> Do You Yahoo!? > >> Get your free @yahoo.com address at http://mail.yahoo.com > >> > >> > > > > > > > > _______________________________________________ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
