|Tomcat has a similar problem, though, it seems it is even worse. The |invocation of javac to compile the jsps sets up the path to the WAR and |standard java classes and does not use the classloader, so you would have |to do something that David Jencks proposes, namely, get the URLs from the |classloader. This is not ideal, imho. It would be best if javac that |compiles the jsps just use the context classloader. Has anyone looked into |if this is possible?
Sounds like a great idea, you need to call the getResourceAsStream on it, why don't you look into it? marcf | |Anatoly. | |On Sun, 25 Nov 2001, Julian Gosnell wrote: | |> |> Is this available to the Jetty integration anywhere. |> |> It is not enough simply to be passed the classloader because I |need to make up a classpath for the java compiler so I can |> compile JSPs on the fly. |> |> Currently Jetty only knows about classes/jars stored in the war |module. If classes/jars are deployed in the ear above, I |> have no way of knowing (without navigating the filesystem) what they are. |> |> I would rather not have to repeat what someone else has already |worked out. |> |> Is there anyway for me to get hold of this information ? |> |> Who should I talk to about agreeing how I might get hold of it ? |> |> Thanks, |> |> |> Jules |> |> |> |> _________________________________________________________ |> 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
