AW: AW: jca adapter for (MySQL)DB

SAP doesn`t support 2Pc, so it is also not possible that the SAP-JCA adapter support XA transactions. Some companies are going the way to build an "virtual transaction". I think that the log all operations and if one goes wrong they have a opposite-operation which will be run. They also say, that the virtual transactions cannot achieve all operations....

Juraj



-----Ursprüngliche Nachricht-----
Von: Ramakrishna Srinivasa [mailto:[email protected]]
Gesendet: Freitag, 8. August 2003 21:14
An: [email protected]
Betreff: Re: AW: jca adapter for (MySQL)DB


I wonder if it possible to do like this. When the underlying Database/EIS System doesnt support XA , how is possible to achieve it with a JCA Adapter. For example SAP by itself doesnt support 2PC. Do you mean to say that a JCA Adapter for SAP can support 2PC ? In that case who will store the data which is uncommitted , should the Adapter take care of this?
 
I am sorry, if I misinterpreted your answer.
 
//Ramki.

        -----Original Message----- 
        From: A public list for J2EE Connector architecture interest. on behalf of Johan Eltes 
        Sent: Fri 8/8/2003 10:05 PM 
        To: [email protected] 
        Cc: 
        Subject: Re: AW: jca adapter for (MySQL)DB
	
	

        To some applications, it could be of value to wrap a none-XA JDBC driver
        with an XA connector to mimic XA by deferring the commit/rollback call to
        the wrapped JDBC driver until the end of the jta transaction. It is far from
        XA but may be sufficient for the application at hand. I guess MySQL doesn't
        support XA?
	
        /Johan
	
	
        Den 03-08-08 20.38, skrev "Ram Jeyaraman" <[email protected]>:
	
        > It is important to separate out SPIs and APIs to understand the relationship
        > between JDBC and Connectors.
        >
        > JDBC is primarily an API, and Connectors is primarily an SPI. CCI is just only
        > type of an API a Connector can expose, JMS is another, and so on.
        >
        > At the system level, the JDBC driver contracts and the Connector contracts are
        > very similar. That is the reason why some vendors choose to implement JDBC
        > driver as a Connector and expose JDBC as an API to the application.
        >
        > Really from the application perspective, it does not matter, whether the JDBC
        > API is exposed via a JDBC driver or a Connector. thanks.
        >
        > ===========================================================================
        > To unsubscribe, send email to [email protected] and include in the body
        > of the message "signoff CONNECTOR-INTEREST".  For general help, send email to
        > [email protected] and include in the body of the message "help".
	
        ===========================================================================
        To unsubscribe, send email to [email protected] and include in the body
        of the message "signoff CONNECTOR-INTEREST".  For general help, send email to
        [email protected] and include in the body of the message "help".
	

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff CONNECTOR-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".