[
http://jira.jboss.com/jira/browse/JBSEAM-992?page=comments#action_12367608 ]
Michael Youngstrom commented on JBSEAM-992:
-------------------------------------------
Well, that's why I wanted to record it here, so that I can show
you this page in 2 years when there is more
"legacy" ;)
:) Perhaps legacy was not the correct term...but I knew it would be the term you would
like the most. :) It will be interesting to see how things look 2 years from now.
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.
Ah, the age old question. Why do people use Spring?
I guess it would be easy to teach the Seam/JavaBean container the same
proprietary tricks - it's just not
right.)
Java is all about choice. You have every right to choose to wait for JTA standard support
for nested transactions if you wish. :)
Use Spring configured EntityManagerFactory in spring example
------------------------------------------------------------
Key: JBSEAM-992
URL:
http://jira.jboss.com/jira/browse/JBSEAM-992
Project: JBoss Seam
Issue Type: Feature Request
Components: Spring
Affects Versions: 1.2.0.GA
Reporter: Michael Youngstrom
Assigned To: Michael Youngstrom
Fix For: 2.0.0.GA
Since most Spring project will be using a Spring configured EntityManagerFactory we
should use one in the Spring example as well and inject this EntityManagerFactory into the
Seam Managed PersistenceContext component with an expression.
--
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