• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Transaction

 
Ranch Hand
Posts: 1309
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
How can a transaction be coordinated with legacy systems or Java systems outside the container/server?
 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes, J2EE uses JTA for transactions and since JTA supports distributed transactions, legacy apps, application servers, etc can involved in a single transaction.
 
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by JiaPei Jen:
How can a transaction be coordinated with legacy systems or Java systems outside the container/server?


in order to access a legacy system you need some sort of connector. If you want your connector to enlist with ongoing transactions in your app-server, the connector must be JTA complient, meaning that the classes that represent resources (like a jdbc connection) in your legacy system must implement javax.transaction.xa.XAResource and the manager / factory that allow you to obtain those resources must ba capable to detect ongoing transactions and enlist your resource with it.
Most commercial connectors are JTA complient but you can find situations (like when connecting to an AS400 queue using JTOpen) when you'll have to implement transaction aware access classes yourself.
Of course if you use a JCA compliant connector all becomes much more simple.
Cheers,
e.
 
Ranch Hand
Posts: 925
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
search on google for transaction monitor
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic