• 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

Query abt JTS

 
Ranch Hand
Posts: 418
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,
JTS defines interfaces used by transaction managers and resource managers behind the scenes. It defines various objs passed between these managers . So should each j2ee vendor implement / support JTS? Or it can have its own proprietary protocol similar to JTS?
:roll:
 
Ranch Hand
Posts: 157
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
rashmi
i m not sure about my answer,i think every j2ee vendor do supports JTS
but ofcourse implementations are in its own proprietary way.

Originally posted by Rashmi Tambe:
Hi All,
JTS defines interfaces used by transaction managers and resource managers behind the scenes. It defines various objs passed between these managers . So should each j2ee vendor implement / support JTS? Or it can have its own proprietary protocol similar to JTS?
:roll:

 
Rashmi Tambe
Ranch Hand
Posts: 418
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks vikasids
Anybody else to give me exact answer?
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
From the J2EE specification:

    This specification does not require the Product Provider to implement any particular
protocol for transaction interoperability across multiple J2EE products. J2EE
compatibility requires neither interoperability among identical J2EE products from
the same Product Provider, nor among heterogeneous J2EE products from multiple
Product Providers.
    We recommend that J2EE Product Providers use the IIOP transaction
propagation protocol defined by OMG and described in the OTS specification
(and implemented by the Java Transaction Service), for transaction
interoperability when using the EJB interoperability protocol based on RMI-IIOP.
We plan to require the IIOP transaction propagation protocol as the EJB server
transaction interoperability protocol in a future release of this specification.

 
Rashmi Tambe
Ranch Hand
Posts: 418
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Lasse :-)
 
reply
    Bookmark Topic Watch Topic
  • New Topic