[ http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=comments#action_1238... ] Emmanuel Bernard commented on EJBTHREE-1096: -------------------------------------------- +1 -- 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

[ http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=comments#action_1238... ] Pete Muir commented on EJBTHREE-1096: ------------------------------------- +1, would really promote EJB3 use in Seam (currently the fact you can do this for Seam managed POJOs but not for Seam managed EJB3s means people will use POJOs for development and then not change for production). -- 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

[ http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=comments#action_1239... ] Andrew Lee Rubinger commented on EJBTHREE-1096: ----------------------------------------------- Pete's provided some more context: [quoth] We are talking incremental hot deploy as in "change the class including signature without restarting the ear" (i.e. redetect ejbs, rebuild hibernate). http://docs.jboss.org/seam/2.0.1.CR1/reference/en/html/gettingstarted.htm... [/quoth] ...exploded WAR format used per example in Seam. -- 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

[ http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=comments#action_1239... ] asookazian commented on EJBTHREE-1096: -------------------------------------- +10 and +1 for JPA entity classes as well although the session beans are more critical to get working first... -- 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

[ 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? -- 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

[ http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=comments#action_1241... ] Jason Long commented on EJBTHREE-1096: -------------------------------------- And look at all the votes. Is there a way to search for issues by the number of votes? I would bet this it one of the top ones. -- 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

[ http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=comments#action_1241... ] asookazian commented on EJBTHREE-1096: -------------------------------------- I just did a quick search in http://forums.atlassian.com on "search by vote" and no hits. This would be a very good functionality to have. Or list the top X most popular (or most voted for) issues for a particular project. Unfortunately, JIRA is not open-source. I would say that since 5.0.0.Beta4 is currently available for download on jboss.org, it will not make it into the first official GA release of JBoss 5 AS. AFAIK it has not been identified yet what the actual root cause and fix/enhancement for this will be. If it requires a mod to the EJB spec that has not been done, then we may be screwed (for a while). I'd like to know if Websphere, Weblogic, Glassfish users are having this problem as well. "JBoss has been famous for being the first Java EE-based application server to support hot deployment and redeployment of appilcations" --Bill Burke, EJB3 O'Reilly Hot incremental deployment of xhtml, xml, POJO, SFSB/SLSB, and entities is very important during development/testing as JBoss shops around the world are wasting dozens of hours a year either constantly waiting for server restarts (ant explode) or dealing with the perm-gen/slowness/memory-leak JVM/container issues (ant deploy). -- 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

[ http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=comments#action_1241... ] 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. " 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, -- 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

[ https://jira.jboss.org/jira/browse/EJBTHREE-1096?page=com.atlassian.jira.... ] Julien Kronegg commented on EJBTHREE-1096: ------------------------------------------ I found a good overview of hot deploy problems and solution in http://impalablog.blogspot.com/2007/09/rationale-of-micro-hot-deployment.... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/EJBTHREE-1096?page=com.atlassian.jira.... ] Demetrio Filocamo commented on EJBTHREE-1096: --------------------------------------------- I agree with Jason, this is a very important feature, currently I'm only using Seam managed POJOs and SFSB and SLSB only when I really need them because of this problem. I also would like to know if there is any news... Demetrio -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/EJBTHREE-1096?page=com.atlassian.jira.... ] asookazian commented on EJBTHREE-1096: -------------------------------------- Jevgeni Kabanov: "The big things to look for in the next release are integration with EJB containers supporting changes to EJB interfaces, full Struts 1.x and 2.x support, better support for enums and static values plus some stuff we'd like to keep secret for the moment :)" source: http://java.dzone.com/articles/saving-time-java-development Note "integration with EJB containers supporting changes to EJB interfaces". That is a very critical enhancement for the upcoming release of JRebel. What does it mean exactly? Will Weblogic, Glassfish or JBoss support this behavior in an upcoming release, for example? Pretty decent tool, we're using 2.1a currently... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/EJBTHREE-1096?page=com.atlassian.jira.plu... ] Enterprise Developer commented on EJBTHREE-1096: ------------------------------------------------ Any work planned on this in jboss 7? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/EJBTHREE-1096?page=com.atlassian.jira.plu... ] Karsten Wutzke edited comment on EJBTHREE-1096 at 5/17/11 7:20 AM: ------------------------------------------------------------------- +1 We could really use this. Using Tomcat when working with application classes (JPQL etc) and using JBoss AS when writing the views is kinds strange. was (Author: kwutzke): +1 We could really use this. Using Tomcat when working with application classes (JPQL etc) and using Tomcat when writing the views is kinds strange. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/EJBTHREE-1096?page=com.atlassian.jira.plu... ] Karsten Wutzke edited comment on EJBTHREE-1096 at 5/17/11 7:20 AM: ------------------------------------------------------------------- +1 We could really use this. Using Tomcat when working with application classes (JPQL etc) and using JBoss AS when writing the XHTML views is kind of strange. was (Author: kwutzke): +1 We could really use this. Using Tomcat when working with application classes (JPQL etc) and using JBoss AS when writing the views is kinds strange. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira