[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1096) Make SLSB and SFSB hot deployable for RAD
Fernando Montaño (JIRA)
jira-events at lists.jboss.org
Sun May 11 18:38:28 EDT 2008
[ http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=comments#action_12412427 ]
Fernando Montaño commented on EJBTHREE-1096:
--------------------------------------------
I posted the following comment in Ken Saks' blog (Ken is the EJB 3.1 Spec Lead) when the EJB 3.1 Early Draft was announced:
"
Hi Ken.
Thanks for the resume.
I was working with EJB since 2.0 (limitations fixed by our own), then EJB 3. I really like the Java EE platform and I'm looking forward for the new features.
What I would really like is the possibility to hot deploy EJB. This would be a very big advantage for EJB, specially for the developers. Currently the development process for EJB applications is a bit cumbersome, we need to redeploy application server every time an EJB is added or changed.
Do you know about the hot deployment (for development process) support for EJB? Was it mentioned on JCP? Was it considered? Will it be?
Thanks in advance!"
His answer was:
"
Hi Fernando,
Thanks for your feedback. Hot deployment has typically been left as a value-add for products as opposed to a spec requirement, so it's unlikely we'll address this specifically within EJB 3.1. There's a basic issue with the way classloaders are used in the EE platform that makes supporting hot deployment for any single component challenging. Typically most or all of the classes in an application are loaded by a single classloader, which means everything has to be reloaded when a single thing changes.
>From a glassfish perspective we have a couple things to ease redeployment. The first is directory-based deployment. That saves you having to re-issue an asadmin command and transfer the application to the server. We've also significantly reduced the overhead of deployment itself. In the case of EJB deployment we've eliminated all statically generated code from the deployment stage (except for legacy CMP 2.x apps).
"
So, as you can read, seems like the EJB (3 or 3.1) hot deployment is reserved to be a "value-add" for JBoss AS.
I'm really sure this would be a really big advantage for JBoss AS.
The post I mentioned is here: http://blogs.sun.com/kensaks/entry/ejb_3_1_early_draft
Regards,
> Make SLSB and SFSB hot deployable for RAD
> -----------------------------------------
>
> Key: EJBTHREE-1096
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-1096
> Project: EJB 3.0
> Issue Type: Feature Request
> Affects Versions: AS 4.2.2.GA
> Reporter: Jason Long
>
> Seam POJO components are hot deployable for RAD. It would be great if SFSB and SLSB could be used in the same manner.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list