-
1. Re: Status of EJBTHREE-1096 Make SLSB and SFSB hot deployabl
alrubinger Feb 16, 2009 10:29 AM (in response to supernovasoftware.com)Jason:
You're right, this has been unscheduled for some time. Our development priorities have simply not lined up here.
We are, however, aware of the community interest. Basically this feature boils down to a dev-mode where we line up a new ClassLoader, ditch it when some scanner detects a new classfile has been dropped into place, and make a new CL.
S,
ALR -
2. Re: Status of EJBTHREE-1096 Make SLSB and SFSB hot deployabl
supernovasoftware.com Feb 16, 2009 1:08 PM (in response to supernovasoftware.com)Thank you very much for the response.
Any idea when this could become a reality? -
3. Re: Status of EJBTHREE-1096 Make SLSB and SFSB hot deployabl
alrubinger Feb 16, 2009 1:41 PM (in response to supernovasoftware.com)If you're volunteering to get into some dev, we'll get you in some basic stuff to start out, then point you in the right direction. ;)
S,
ALR -
4. Re: Status of EJBTHREE-1096 Make SLSB and SFSB hot deployabl
supernovasoftware.com Feb 16, 2009 2:52 PM (in response to supernovasoftware.com)I greatly appreciate all of the work by JBoss developers on all of the products I use.
My experience with this type of coding, my already overloaded work schedule, and other things will make it impossible for me to contribute.
I am interested in an estimated time frame of when your development priorities will line up with community interest on this matter. -
5. Re: Status of EJBTHREE-1096 Make SLSB and SFSB hot deployabl
alrubinger Feb 16, 2009 3:23 PM (in response to supernovasoftware.com)Ah, so we're not the only ones currently overloaded. ;)
Unfortunately, I cannot give you an estimate now. We do feature-specific planning for each EJB3 release (every 2 weeks), and we have a longer-term roadmap as well. At the moment EJBTHREE-1096 is not on the roadmap (which mostly involves spec compliance for EJB 3.1, as you can see from the dev forums), and the little tinkering I've done last weekend shows that it'll need some more attention than a couple hours to make a point release.
For now the workaround continues to be hot-deployable applications (working, though is different from incremental redeploy of classes).
S,
ALR