In a webapp, there is a hierarchy of classloaders with the "web" classloader inheriting from the "application" classloader which in turn inherits from the "bootstrap" classloader. Tapestry adds another classloader to the mix to confuse things further. I think something is going on with your classloader hierarchy that is slightly different to most people's setups.
Can you provide exact details of how you are running your app and how you define your classpath(s)? -- View this message in context: http://tapestry.1045711.n5.nabble.com/Cannot-get-component-library-to-load-tp5713444p5713501.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
