Ok, then I´ll implement a tiny adaptor for that. What would be the right default format in the tc_path_add property ... Unix or WinX?
It´s Jasper that uses the tc_path_add property to extend its classpath just for compilation purposes (calls the embedded compiler with explicit, string-based arguments :-( Before RH, the respective jars where part of the system classpath which the JSP compiler does indeed use! Now, the jars are added to a subordinate classloader of the system classloader which makes this property very important ... until someone writes a contextclassloader-aware compiler. The servlet should run in the WebApplicationContext classloader as expected. CGJ -----Ursprüngliche Nachricht----- Von: Peter Levart [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 18. Oktober 2001 13:15 An: Jung , Dr. Christoph; Jboss-Development (E-Mail) Betreff: Re: AW: [JBoss-dev] Jetty JSP-Compilation On Thursday 18 October 2001 09:57, Jung , Dr. Christoph wrote: > I fixed this in jetty.properties, although I´m not sure whether exchanging > the ":" with ";" in the > compiler-classpath specification is platform-neutral? > > CGJ > It appears that it isn't. Windows might use ";". On Linux I had to change back to ":"... Is this meant to be so? The classpath for JSP compiler is taken only from jetty.properties? It does not take into account the <classpath archives="..." /> from jboss-service.xml files in conf or jetty-plugin.sar... What about running the compiled JSPs? Which classpath is used for that? Peter _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
