SQL Anywhere has a SQL command "PREPARE TO COMMIT", so obviously it is able
to participate in Two Phase Commit scenarios, what is a core demand to
participate in distributed transaction environments.

Now in times where enterprise applications more and more are getting
implemented using the Java platform, I see a need to support Two Phase
Commits in a vendor-neutral way, i. e. outside of the SQL area but inside of
the JDBC API area. The JDBC standard for this reason contains optional
support for the XADataSource interface which allows to handle the Two Phase
Commit using API calls instead of SQL commands.

I personally think it would be really useful to find support of XADataSource
in the IAnywhere JDBC driver, since our software (we are an ISV and such
cannot rely to find SQLAnyhwere at ALL of our customers but just at SOME of
them) must be able to run on any JDBC driver and DBMS, so we cannot use the
"PREPARE TO COMMIT" command inside of the connection.

What is your opinion about it? Any good reasons against XADataSource?
Anybody besides me likes to have that feature?

Regards
Markus

Any news? I mean, am I the only one that is using SQL Anyhwere 11 with
distributed transactions?

"Markus KARG" <karg (AT) quipsy (DOT) de> schrieb im Newsbeitrag
news:49dd989d (AT) forums-1-dub (DOT) ..