Chris,

When using reloadable=false  I'm not able to hot deploy java code, so
this doesnt solve the problem. As far as I see there is no way to
prevent tomcat from reinit the context. The myeclipse guys wrote an own
tomcat server handleing plugin with managers and all that stuff, so they
made some tricks there I guess...

Any other idea?

Thanks,
Remo



Remo Liechti
Application Developer
Swisslog Warehouse and Distribution Solutions

Direct: +41 (0)62 837 4345
Mobile: +41 (0)76 329 8660
CH Fax: +41 (0)62 837 4197
Internet: www.swisslog.com
----------------------------------------------------------------
About Swisslog
Swisslog is a global provider of logistic solutions for warehouses,
distribution centers and hospitals. Swisslog's solutions increase their
customers' flexibility, responsiveness, and quality of service, while
minimizing logistics costs. 


-----Original Message-----
From: Christopher Schultz [mailto:[EMAIL PROTECTED] 
Sent: Montag, 7. April 2008 17:07
To: Tomcat Users List
Subject: Re: How to prevent tomcat from restarting after hot code
replacement?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Remo,

Remo Liechti wrote:
| |The best you can do is to turn off auto-reload.
|
| Where do I turn of auto reload? Will class files still be published to

| tomcat after they changed?

Set reloadable="false" in your <Context>.

| || I just want my code to be hot deployed and not restarting tomcat.
| |You cannot do this unless you hack Tomcat or your webapp to re-load 
| |class files when they change.
|
| Well, using the MyEclipse bundle it works! But not using WTP standard?

This is because Eclipse performs some trickery to replace classes during
runtime.

- -chris

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkf6OJAACgkQ9CaO5/Lv0PBPkACfXJrWJ7nRbp+6N7uigB0F7G20
wvkAn36WuQtgb0p60ZyF9HhtCxUvivFo
=vkgu
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe,
e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


This message may contain legally privileged or confidential information and is 
therefore addressed to the named persons only. The recipient should inform the 
sender and delete this message, if he/she is not named as addressee.
The sender disclaims any and all liability for the integrity and punctuality of 
this message. The sender has activated an automatic virus scanning, but does 
not guarantee the virus free transmission of this message.


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to