So the count is 2.
IONA and Inprise - both CORBA vendors - what about the other CORBA vendors?
Sun, IBM, Oracle, Sybase? (Where is Evan when you need him?) What about the
non-CORBA vendors? Rickard?
Surely as soon as an organisation strikes two or more different databases or
two or more EJB servers then this is going to be a problem? This only IONA
and Inprise can solve it? (Unless its Oracle 8i, in which case WebLogic can
as well)
This is pretty bad from a EJB perspective is it not? All Roger Session's
current arguments are vapid, this is one he could really pick up and run
with! JDBC 2.0 XA has been around since Nov 98 hasn't it?
Simon
---
Simon Blake
the esperanto Group
[EMAIL PROTECTED]
----- Original Message -----
From: "Jonathan K. Weedon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 29, 2000 5:52 AM
Subject: Re: [EJB-INT] 2 connections in a single transaction
> Simon,
>
> <vendor>
>
> Inprise AppServer 4.1 supports this feature: we provide distributed,
> two-phase commit using JDBC2/XA drivers across multiple heterogenous
> (or homogenous) DBMSs, driven by our OTS/JTS compliant transaction
> engine. All of this is done as per the OMG and Sun specifications,
> using IIOP to do the transaction propagation and XA for the
> coordination. And, yes, we had to jump through all sorts of hoops
> (read: horrendous JDBC2/XA driver bugs) to get it to work.
>
> Note that IAS 4.1 will not be generally available for a couple of
> weeks...
>
> </vendor>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
