[ http://jira.jboss.com/jira/browse/JBSEAM-992?page=comments#action_12355133 ] Gavin King commented on JBSEAM-992: ----------------------------------- I'm not sure that this is really useful ... why not just use the Seam-managed PC, which is actually more powerful than the Spring one...? -- 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/JBSEAM-992?page=comments#action_12355138 ] Gavin King commented on JBSEAM-992: ----------------------------------- You can already do that. Look at the JPA example. Nothing platform-dependent there. -- 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/JBSEAM-992?page=comments#action_12355189 ] Ian Hlavats commented on JBSEAM-992: ------------------------------------ For unit testing, if I use a Seam-managed persistence context then I am using the embedded EJB container with TestNG. How do you test Spring integration with this approach? How do you bootstrap a Spring WebApplicationContext in a mock servlet environment? So far I have been creating the Spring application context from my EJBs and getting Spring beans directly in my Seam components (during @Create or @PostConstruct, not using @In). The other option, to use a Spring-managed persistence context, would lend itself to standalone unit testing, but the Hibernate entity manager does not work without the EJB container running. How do you get the Hibernate EntityManager in a standalone unit test? I don't think a JNDI lookup will work here. Some guidance here would be much appreciated. -- 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/JBSEAM-992?page=all ] youngm reassigned JBSEAM-992: ----------------------------- Assignee: youngm -- 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/JBSEAM-992?page=all ] Gavin King updated JBSEAM-992: ------------------------------ Fix Version/s: 1.3.1.BETA1 (was: 1.3.0.ALPHA) -- 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/JBSEAM-992?page=all ] Michael Youngstrom updated JBSEAM-992: -------------------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.BETA1) -- 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/JBSEAM-992?page=all ] Michael Youngstrom updated JBSEAM-992: -------------------------------------- Fix Version/s: 2.0.0.GA (was: 2.0.0.CR1) The example is now updated to use spring managed transactions and all dependence on microcontainer and EJB3 have been removed. In order to use a spring configured EntityManagerFactory though spring needs to fix SPR-3645. Since spring 2.0.7 isn't scheduled to be released until July 31st I'm pushing this back to 2.0.0.GA. -- 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/JBSEAM-992?page=comments#action_12367597 ] Michael Youngstrom commented on JBSEAM-992: ------------------------------------------- One advantage might be the ability to use a thirdparty JTA transaction manager since Spring configured EMFs support injections of a datasource. Another reason might be configuration. Many legacy spring apps use spring based configuration techniques configure the properties of an EMF which may be more flexible at times than depending upon the configuration properties hard coded in a persistence.xml. Using a spring configured EMF with spring transactions can provide some powerful functionality such as: transaction suspension support for propagation rules like REQURIES_NEW and NOT_SUPPORTED as well as support for things like nested transactions. Spring configured EMFs can provide quite a bit of power to spring users. And I don't think we should stop Seam-Spring users from taking advantage of them. Now my intention with this issue isn't necessarily to lead people down this path as a "best practice" but more to show and test that it is possible (my work on this so far found a bug SPR-3645). The Seam examples all walk a fine line between best practice, showing what is possible, and regression testing. Using a spring configured EMF in the spring example would be showing spring users that it is possible and would also aid in regression testing. I'm not exactly sure what you are referring to here. -- 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/JBSEAM-992?page=comments#action_12367605 ] Christian Bauer commented on JBSEAM-992: ---------------------------------------- (And except for "nested transactions" I do not see any technical argument for using a Spring/JavaBean container instead of an EJB 3.0 container or Seam container. I guess it would be easy to teach the Seam/JavaBean container the same proprietary tricks - it's just not right.) -- 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/JBSEAM-992?page=comments#action_12367609 ] Christian Bauer commented on JBSEAM-992: ---------------------------------------- One step would be to put "This feature is not supported by JTA" and "This feature is not supported by EJB" onto the source of the examples you are working on and also add the contact address of the respective expert group of any relevant JSR. This is at the same time a warning for beginners and a marker that can be removed later if a better solution is found within any standard. It also helps to support the great choices we all enjoy, through encouraging participation in standardization efforts. (I should become a Sun marketing guy.) -- 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/JBSEAM-992?page=all ] Pete Muir closed JBSEAM-992. ---------------------------- -- 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