tomcat has memory issues when it comes to context loading. hence outta
memory errors it has been plaqued with. you should use jetty for development
and tomcat for production enviroments. When you deploy to production you
should create either a ant task to collect together your war and deploy it
onto tomcat.
~evan
----- Original Message -----
From: "entelechon" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, July 30, 2007 2:42 PM
Subject: [T5] Eclipse WTP - conflict between class reloading and context
reloading
I am using Eclipse WTP and Tomcat 5.5 to develop with Tapestry 5. Changes
to
page classes are supposedly picked up by Tapestry, via an inspection of
the
class path.
Now, when I change a page class, Tomcat notices the changed file and
reloads
the whole context - effectively resetting the application state and taking
ages to re-initialize everything.
I can change the context to be non-reloadable (in server.xml, specifying
reloadable="false"). However, then nothing happens: Neither does Tomcat
reload the context (expected), nor does Tapestry load the changed page
class
(unexpected).
Any help?
Thanks,
Markus
--
View this message in context:
http://www.nabble.com/-T5--Eclipse-WTP---conflict-between-class-reloading-and-context-reloading-tf4178263.html#a11880890
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
