-
1. Re: Question re Hot deployment of JSPs
"clewis@virgin" wrote:
If I hot deploy a JSP by dropping it into the right location in an exploded war, does this cause the Unified Class Loader associated with the war to be dropped and recreated?
I guess you mean, if you change an existent jsp or add a new jsp to a exploded war, does it redeploy the war. If that's what your question meant, then no - hot deploying jsps will not re-deploy the application.
Let us know if you meant something else :-) -
2. Re: Question re Hot deployment of JSPs
You're right that is what I meant.
Some background: I have a .war and a .ear whose classloaders aren't scoped (so they're share the same repository).
Questions:
Can I safely hot deploy jsps to the war (if it's deployed exploded).
If the war isn't re-deployed how is the jsp relinked?
What happens to references made by that jsp to shared classes? -
3. Re: Question re Hot deployment of JSPs
"clewis@virgin" wrote:
Can I safely hot deploy jsps to the war (if it's deployed exploded).
Yes."clewis@virgin" wrote:
If the war isn't re-deployed how is the jsp relinked?
The last modified timestamp indicates a change to the jsp. Any modified jsps will be recompiled and will go through the JSP lifecycle."clewis@virgin" wrote:
What happens to references made by that jsp to shared classes?
The jsp will be recompiled and will go through the jsp lifecycle.