Steven,
The difference is that in a Java EE centric environment, there is *no
configuration needed period*, inside or outside the WAR to get
transactional functionality.
Cheers,
Reza
Boscarine, Steven wrote:
How is the UserTransaction you're mentioning different than the
one Spring provides?
http://static.springsource.org/spring/docs/3.0.x/spring-framework-referen...
There's no configuration needed outside the war.
________________________________
From: weld-dev-bounces(a)lists.jboss.org [weld-dev-bounces(a)lists.jboss.org] On Behalf Of
Dan Allen [dan.j.allen(a)gmail.com]
Sent: Tuesday, November 24, 2009 3:22 PM
To: Gurkan Erdogdu
Cc: Weld-Dev
Subject: Re: [weld-dev] persistence and transactions outside Java EE
On Tue, Nov 24, 2009 at 3:17 PM, Gurkan Erdogdu
<gurkanerdogdu@yahoo.com<mailto:gurkanerdogdu@yahoo.com>> wrote:
>>> the main concern is that JTA transactions simply aren't available in a
servlet environment (without extra configuration).
>>>
AFAIK, you can use UserTransaction object
If I download Tomcat or Jetty right now (unless I didn't get the memo) I won't
have a UserTransaction.
Yes, if I spend half the day searching the web to find a tutorial that actually works,
maybe I can "upgrade" these containers to support JTA, but that's a PITA.
If you can tell me that placing a single JAR file in the container so that EJB lite
works, then we have something.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev