[
http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=comments#action_1241... ]
asookazian commented on EJBTHREE-1096:
--------------------------------------
I would appreciate a response to Jason Long's questions directly above. This issue is
not even assigned yet.
This problem is a total disaster in terms of productivity. I've recently been
restarting JBoss dozens of times a day during dev/test cycles for my Seam app.
I use ant explode as default build for Seam apps. When you use ant deploy, it's
faster for session bean dev/test cycles b/c the new version of the EAR will be re-deployed
by JBoss (restart not required - which takes longer than re-deploy) but eventually you
will have to restart Jboss/Eclipse due to strange problems and perm-gen memory issues even
if you use -XX:PermSize=256M
-XX:MaxPermSize=512M on a 2GB machine.
Either way sucks. I've also seen seemingly invalid duplicate id errors when I save a
change to a facelet and do an ant explode and refresh browser.
These comments refer to Seam 2.0.0.GA, RF3.1.3.GA and JBoss 4.2.1.GA.
Is this a EJB spec issue or JBoss EJB implementation issue or both?
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