Well, it took a little longer than I thought it would, but we announced
support for XA on Immutant today:
http://immutant.org/news/2012/06/26/transactions/
Enjoy!
Jim
On Saturday, December 31, 2011 7:59:27 PM UTC-5, Jim Crossley wrote:
>
>
>
> On Dec 31, 7:33 pm, Stuart Halloway wrote:
> > >
On Dec 31, 7:33 pm, Stuart Halloway wrote:
> > On Dec 31, 1:16 pm, Jeff Heon wrote:
> >> Immutant is going to have distributed (XA) transactions.
> >> The're "furiously" working on it 8)
>
> >>http://immutant.org/
>
> > "Furiously" is probably not the right word, but XA is definitely on
> > the
> On Dec 31, 1:16 pm, Jeff Heon wrote:
>> Immutant is going to have distributed (XA) transactions.
>> The're "furiously" working on it 8)
>>
>> http://immutant.org/
>
> "Furiously" is probably not the right word, but XA is definitely on
> the roadmap. It's just a matter of wiring up the Transact
On Dec 31, 12:39 pm, Leonardo Borges
wrote:
> Distributed transactions slow u down Why the hell would you want that?
> I'm yet to see a valid use case! They require sticky sessions *whi*ch suck
> for scalability! Keep in mind it's 4am on the 31st of December :-)
It's a surprisingly common req
On Dec 31, 1:16 pm, Jeff Heon wrote:
> Immutant is going to have distributed (XA) transactions.
> The're "furiously" working on it 8)
>
> http://immutant.org/
"Furiously" is probably not the right word, but XA is definitely on
the roadmap. It's just a matter of wiring up the TransactionManager
pr
On Dec 31 2011, 9:26 pm, Michael Jaaka
wrote:
> Is there any attempt to make distributed transactions?
> The usage scenario is the same like in JEE apps.
> I mean, there is a web service call, the transaction is started, there
> are some changes to db, some jms sends and when there is no failure
Immutant is going to have distributed (XA) transactions.
The're "furiously" working on it 8)
http://immutant.org/
On Dec 31, 11:26 am, Michael Jaaka
wrote:
> Is there any attempt to make distributed transactions?
> The usage scenario is the same like in JEE apps.
> I mean, there is a web service
Well, I can't speak for Michael, but we want them because we need to
update the database *and* send events notifying other parts of the
distributed system about the change. We really don't want to do only
one *or* the other, because that requires that we get into the fun
world where distributed to
Distributed transactions slow u down Why the hell would you want that?
I'm yet to see a valid use case! They require sticky sessions *whi*ch suck
for scalability! Keep in mind it's 4am on the 31st of December :-)
Leonardo Borges
www.leonardoborges.com
Sent from my Galaxy Nexus(IceCreamSandwhic
maybe avout is what you're looking for?
https://github.com/liebke/avout
2011/12/31 Michael Jaaka
> Is there any attempt to make distributed transactions?
> The usage scenario is the same like in JEE apps.
> I mean, there is a web service call, the transaction is started, there
> are some changes
10 matches
Mail list logo
