So.. read the exception stack trace fully.. If down at the bottom it
talks about slf4j or some logging issue.. then it's because Jetty
purposefuly hides the slf4j libraries from tapestry (because jetty ships
with slf4j for itself ) and you have to add a particular vmarg to fix
that. At least this is what we do, you might be having the same issue,
but no guarantees.
vmargs:
-Dorg.mortbay.jetty.webapp.parentLoaderPriority=true or false
(At the moment I can't get to my eclipse, so I can't remember if have to
set to true or false)
But here are the docs for this property:
http://docs.codehaus.org/display/JETTY/Classloading
http://docs.codehaus.org/display/JETTY/SystemProperties
On 8/10/09 10:56 PM, Eldred Mullany wrote:
Hi All
I am having a strange problem with an old t5.0.13 app and jetty. When I
startup the application in Eclipse it shows that it connects to db,
starts up all services etc, however when hit a web page that contains
any component such as<t:form> throws an exception
java.lang.ClassNotFoundException: caught an exception while obtaining a
class file for org.apache.tapestry5.corelib.components. I then built a
war file and deployed it under tomcat and it worked fine.
So the problem seems to be jetty, but not sure what's causing it not to
resolve classes, does anyone have any suggestions on what the cause of
this is. I checked my tapestry-core-5.0.13.jar which doesn't seem
corrupt, all classes reside in their respective packages. It would'nt
have worked in tomcat if my libraries were corrupt.
Thanks
Eldred Mullany
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
