Interviews World
 .Net (166)
 
  .Net Framework(43)
  .Net Memory Management(2)
  .Net Web Service(6)
  .Net Remoting(30)
  .Net Security(2)
  .Net Threading(8)
  .Net Architecture(2)
  Basic C#(33)
  VB.Net(2)
  .Net Window Service(3)
  .Net Window Forms(14)
  Advanced C#(25)
  Visual Studio 2003(2)
  Visual Studio 2005(2)
  Visual Studio 2008(2)
  Visual Studio 2010(2)
 
 ASP.Net (49)
 
  ASP.NET General(7)
  ASP.NET Caching(9)
  ASP.NET Ajax(13)
  ASP.NET Session(7)
  ASP.NET Localisation(2)
  ASP.NET 1.1(2)
  ASP.NET 2.0(2)
  ASP.NET 3.5(11)
  ASP.NET 4.0(2)
 
 Database (88)
 
  SQL Server 2000(20)
  SQL Server 2005(24)
  SQL Server 2008(42)
 
 ADO.Net (7)
 
  General ADO.NET(7)
 
 Object Oriented (27)
 
  Basic Object Oriented(19)
  Advanced Object Oriented(8)
 
 XML (24)
 
  Basic XML(24)
 
 MS Dynamics (1)
 
  MS Dynamics GP 9(2)
  MS Dynamics GP 10(1)
  MS Dynamics Soloman(2)
  MS Dynamics CRM 3.0(2)
  MS Dynamics CRM 4.0(2)
  MS Dynamics CRM 5.0(2)
 
 Sharepoint (65)
 
  Basic SharePoint(35)
  SharePoint Server 2003(4)
  SharePoint Server 2007(25)
  SharePoint Server 2010(2)
 
 HR (2)
 
  Basic HR(2)
 
 Java (1)
 
  Basic Java(1)
 
 PHP (2)
 
  Basic PHP(2)
 
 Testing (15)
 
  Automation Testing(15)
 
 
  Welcome to Interviews World
 

$5 .COM Black Friday Sale!


Question : What is the relationship between XAML and JTS/JTA?

Answer :

J2EE includes support for distributed transactions through two specifications, Java Transaction API (JTA) and Java Transaction Service (JTS). JTA is a high level, implementation independent, protocol independent API that allows applications to access transactions. JTS specifies the implementation of a Transaction Manager which supports JTA and implements the Java mapping of the OMG Object Transaction Service (OTS) 1.1 specification using the IIOP protocol. The JTA API allows you to demarcate transactions in a manner that is independent of the transaction manager service or JTS.

While JTA provides an API for demarcating transactions in Java-based application logic, XAML provides an agreed upon protocol or a coordinated process of interaction among transactionally-aware web services over a defined transport. Given this, a web service internally implementing JTA could expose these transactional capabilities using XAML.

 
 
  Website Highlights
 




















 
 
 
  Newsleter
 
Enter your Email:
Newsletter