Hi Achim Thanks for looking into this.
Yeah I also had a hunch about class and resource loading issues as Tapestry heavily rely on doing this in a custom way. To check for updated template files / or even .java files to hot reload. Though I found some notes about this at http://tapestry.apache.org/class-reloading.html It does only explain a bit about this and how you can turn it into production mode which avoids some hot loading. I was looking for any SPI hooks to its classloading so in case we could hook in any OSGi aware way of loading. But didn't find this. We could check its user mailing list about Tapestry and OSGi as there seems to be some past conversations http://tapestry.1045711.n5.nabble.com/template/NamlServlet.jtp?macro=search_page&node=2375124&query=osgi&n=2375124 On Mon, Dec 3, 2012 at 10:41 PM, Achim Nierbeck <[email protected]> wrote: > Ok, I tried to go the way Clause drew here, and it doesn't work for me > either. > Since there aren't any log entries that show something really bad I'm back > to my first guess, the classloading mechanism isn't osgi friendly enough. > I tried to dig into this a bit but didn't find any root cause, but since > there are tml templates they need to get loaded somehow, and if this is done > with a "custom" classloader magic we are out of luck right now. > > regards, Achim > > > 2012/12/3 ymy54 <[email protected]> >> >> Hello, and thanks for your help. >> >> The war does not include servlet.jar. Folder WEB-INF/lib contains these >> jars: >> >> antlr-2.7.7.jar >> antlr-runtime-3.3.jar >> commons-codec-1.5.jar >> javassist-3.12.1.GA.jar >> javax.inject-1.jar >> js-1.6R7.jar >> log4j-1.2.14.jar >> plastic-5.3.6.jar >> slf4j-api-1.6.1.jar >> slf4j-log4j12-1.6.1.jar >> stringtemplate-3.2.1.jar >> tapestry5-annotations-5.3.6.jar >> tapestry-core-5.3.6.jar >> tapestry-func-5.3.6.jar >> tapestry-ioc-5.3.6.jar >> tapestry-json-5.3.6.jar >> tapestry-yuicompressor-5.3.6.jar >> yuicompressor-2.4.7.jar >> >> I don't know what to try next. This is the original post with some >> logging: >> http://fusesource.com/forums/thread.jspa?threadID=4422&tstart=0 >> >> >> Achim Nierbeck wrote >> > I haven't looked at Tapestry, but it might well be that it uses special >> > classloader tricks to load all it's tml files. >> > Another possibility reason of it not working might be that some >> > "forbidden" >> > jars are included in the war. >> > servlet.jar is usually filtered out, but it might be something >> > different. >> > I might be able to check later today. >> >> >> >> >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/Pax-web-and-using-Apache-Tapestry-tp4026946p4027004.html >> Sent from the Karaf - User mailing list archive at Nabble.com. > > > > > -- > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> > Commiter & Project Lead > blog <http://notizblog.nierbeck.de/> -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
