also note that the forthcoming Servlet.next JSR also refers to this EG as a coordination point.
- Larrry
________________________________
From: Dhanji R. Prasanna [mailto:dhanji_at_gmail.com]
Sent: Mon 6/4/2007 4:30 PM
To: dev_at_jsr311.dev.java.net
Subject: dynamic deployment/class reloading
Hi
This may be a bit premature to discuss, but I was just looking at the JSF2.0 proposal the other day and they have listed dynamic class-reloading as one of their big features. There is also a strong nod toward us, saying that JSF will now integrate with jsr311 and be more "restful."
Tapestry 5.0 alpha releases also sport this feature (which I think is kinda neat and very relevant in a Model 2 world, just as JSP reloading is/was in Model 1 days). I think this could be useful for jsr311. Thoughts?
Changes to individual resource classes could be picked up by the runtime and redeployed without restarting it. Im not sure of the logistics (haven't thought through an appropriate classloading model--and don't like Tapestry's) but this could be very useful. And obviate some of those painful out of PermGen memory errors that some appservers give us *looks in Larry Cable's direction and ducks* =)
Of course, Im making a lot of assumptions about the deployment environment too, dont know how this would fit in with Restlet for instance. Anyway, just a thought. Also am curious as to how/what the integration with JSF will be like and if there has been any discussion around it with the spec leads? It seems they too have an aggressive release schedule.
Dhanji.
Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.