In most cases perhaps not. But what about config required for JBoss and XA/2PC datasources? Isn't that config manually required in foo-xa-ds.xml as well as configuring default tx isolation?<br><br><a href="http://www.jboss.org/community/wiki/ConfigDataSources">http://www.jboss.org/community/wiki/ConfigDataSources</a><br>
<p><transaction-isolation> - the default transaction isolation of
the connection (unspecified means use the default provided by the
database):</p><ul><li type="ul"><p>TRANSACTION_READ_UNCOMMITTED</p></li><li type="ul"><p>TRANSACTION_READ_COMMITTED</p></li><li type="ul"><p>TRANSACTION_REPEATABLE_READ</p></li><li type="ul"><p>TRANSACTION_SERIALIZABLE</p>
</li><li type="ul"><p>TRANSACTION_NONE</p></li></ul><br><br><div class="gmail_quote">On Tue, Nov 24, 2009 at 3:53 PM, Reza Rahman <span dir="ltr"><<a href="mailto:reza_rahman@lycos.com">reza_rahman@lycos.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Steven,<br>
<br>
The difference is that in a Java EE centric environment, there is *no<br>
configuration needed period*, inside or outside the WAR to get<br>
transactional functionality.<br>
<br>
Cheers,<br>
<font color="#888888">Reza<br>
</font><div><div></div><div class="h5"><br>
<br>
Boscarine, Steven wrote:<br>
> How is the UserTransaction you're mentioning different than the one Spring provides? <a href="http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/ch10.html" target="_blank">http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/ch10.html</a><br>
><br>
> There's no configuration needed outside the war.<br>
> ________________________________<br>
> From: <a href="mailto:weld-dev-bounces@lists.jboss.org">weld-dev-bounces@lists.jboss.org</a> [<a href="mailto:weld-dev-bounces@lists.jboss.org">weld-dev-bounces@lists.jboss.org</a>] On Behalf Of Dan Allen [<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>]<br>
> Sent: Tuesday, November 24, 2009 3:22 PM<br>
> To: Gurkan Erdogdu<br>
> Cc: Weld-Dev<br>
> Subject: Re: [weld-dev] persistence and transactions outside Java EE<br>
><br>
> On Tue, Nov 24, 2009 at 3:17 PM, Gurkan Erdogdu <<a href="mailto:gurkanerdogdu@yahoo.com">gurkanerdogdu@yahoo.com</a><mailto:<a href="mailto:gurkanerdogdu@yahoo.com">gurkanerdogdu@yahoo.com</a>>> wrote:<br>
><br>
>>>> the main concern is that JTA transactions simply aren't available in a servlet environment (without extra configuration).<br>
>>>><br>
> AFAIK, you can use UserTransaction object<br>
><br>
> If I download Tomcat or Jetty right now (unless I didn't get the memo) I won't have a UserTransaction.<br>
><br>
> 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.<br>
><br>
> If you can tell me that placing a single JAR file in the container so that EJB lite works, then we have something.<br>
><br>
> -Dan<br>
><br>
> --<br>
> Dan Allen<br>
> Senior Software Engineer, Red Hat | Author of Seam in Action<br>
> Registered Linux User #231597<br>
><br>
> <a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>
> <a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
> <a href="http://www.google.com/profiles/dan.j.allen" target="_blank">http://www.google.com/profiles/dan.j.allen</a><br>
><br>
> _______________________________________________<br>
> weld-dev mailing list<br>
> <a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/weld-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br>
><br>
><br>
><br>
<br>
_______________________________________________<br>
weld-dev mailing list<br>
<a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/weld-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a><br>
</div></div></blockquote></div><br>