Issue 203 in flyway: JTA & XA DataSource support

[fly...@googlecode.com]

Status: New
Owner: axel.fontai...@gmail.com
Labels: Type-Enhancement Priority-Medium

New issue 203 by axel.fontai...@gmail.com: JTA & XA DataSource
support
http://code.google.com/p/flyway/issues/detail?id=203

Previously JTA & XA DataSources were supported by specifying a JTA
transaction manager using the setTransactionManager method.

As part of the removal of the Spring dependency, this method will be going
away in the next release.

An alternative could be JTA & XA DataSource autodetection, fetching the
UserTransaction object from JNDI and starting a new transaction that way.

If you do require this, please star this issue and add a comment with the
specific runtime environment (AppServer + Version) you use.

[fly...@googlecode.com]

Comment #1 on issue 203 by sebastia...@gmail.com: JTA & XA DataSource
support
http://code.google.com/p/flyway/issues/detail?id=203

These types of "autodetecting" are likely to fail and have the danger of
blocking certain environments.

Proposal: let the application set the UserTransaction object in Flyway. You
don't need any spring to control it and it is part of the standard.

[fly...@googlecode.com]

Comment #2 on issue 203 by axel.fontai...@gmail.com: JTA & XA
DataSource support
http://code.google.com/p/flyway/issues/detail?id=203

Hi Sebastian,

Thanks for your feedback. I still lean in favor of autodetecting though.
Spring seems to have no problem doing this successfully for almost any JEE
environment under the sun, so it must be possible.

This was also the reason why I asked for details about environments people
require. This way it can be made sure they are supported. And if one is
missing, it can always be added in the next release.

The reason I favor autodetection is that it allows the JTA dependency
(UserTransaction class) to be optional. Adding a setUserTransaction method
would force everyone to pull it in. This would of course defeat the purpose
of the effort of making Flyway a zero required-dependency library.

Cheers
Axel

[fly...@googlecode.com]

Comment #3 on issue 203 by boldo...@gmail.com: JTA & XA DataSource support
http://code.google.com/p/flyway/issues/detail?id=203

We are using Jboss 7.1.1

[fly...@googlecode.com]

Comment #4 on issue 203 by pjpi...@gmail.com: JTA & XA DataSource support
http://code.google.com/p/flyway/issues/detail?id=203

I use Glassfish 3.1.1 and 3.1.2 in a couple of big (200k LOC, 60% coverage,
4+ million queries minute) projects.

[fly...@googlecode.com]

Updates:
Status: Migrated

Comment #5 on issue 203 by axel.fontai...@gmail.com: JTA & XA
DataSource support
http://code.google.com/p/flyway/issues/detail?id=203

Migrated to GitHub: https://github.com/flyway/flyway/issues/86

To everyone who starred this issue: please leave a +1 comment on the linked
GitHub issue

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings