Similar issue with applications like Velocity. These apps depend (somewhat misguidedly) on an unpacked deployment of web apps. This is because they need to read "web pages" in order to parse them for tag substitution. AFAIK, they do not delegate a class to do the reading for them.
jim > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On > Behalf Of Jan Bartel > Sent: Sunday, March 10, 2002 9:24 AM > To: Jules Gosnell; Jboss-Development > ([EMAIL PROTECTED]) > Subject: JSP classpath (Was: Re: [JBoss-dev] Re: What's going ON??) > > > 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? > > *However* there still seems to me to be a problem with JSPs > in general: > ie, any JSP that has to be compiled that refers to a class > (such as an > ejb) that is found by an njar:file:....^/blah.jar URL won't > be able to be compiled?! > > Jan > > > > Jules, > > > > 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
