I think this is best solution. Imagine you have class A and class B. B
holds an instance of A. Now you force B to be reloaded. Should A be
reloaded too? What happens with the instance of A in B? Is it
duplicated? C is holding an instance of B, so must C be reloaded (and
all existing objects which
Leon Rosenberg [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
You don't need to restart the server to get your changes live, you can
force it to reload the whole application, which, in case of tomcat,
your users wouldn't even notice (as long as ALL your beans in session
are
matador wrote:
Leon Rosenberg [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
You don't need to restart the server to get your changes live, you can
force it to reload the whole application, which, in case of tomcat,
your users wouldn't even notice (as long as ALL your beans in session
On 9/23/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
given a change to class file(s), does anyone know a
hack workaround to
force tomcat to reload * just those files *. I know
about restarting the
app from the console and context.xml. but i cannot
afford to knock users
off in the middle
Leon Rosenberg [EMAIL PROTECTED] wrote in
news:[EMAIL PROTECTED]:
On 9/23/05, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
I think it's forbidden by the spec.
SRV.3.7 Reloading Considerations
Although a Container Provider implementation of a class reloading
scheme for ease
of
