db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stan Bradbury (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-232) Open Invitation to add a Question and Answer to Derby FAQs
Date Thu, 26 May 2005 19:08:58 GMT
     [ http://issues.apache.org/jira/browse/DERBY-232?page=comments#action_66381 ]
Stan Bradbury commented on DERBY-232:

Proposed FAQ for addition to the website document.  This was posted on the developerWorks
forum May 23, 2005:

   ??  Question:
from what I've read (PDF docs), it seems Cloudscape is not suitable when a program wants to
execute a transaction spanning two Cloudscape databases distributed accross (remotely located)
JVMs. Did anybody try this before? If it is not possible, is there any workaround, possibly
in conjunction with other tools?

The usual scenario would be to use the EmbeddedXADataSource (probably JNDI) and to register
a XAResource obtained from the XADataSouce/XAConnection

   !! Answer:
XA support using Network Server will allow you to do this. This functionality has been added
to the current Derby codeline. You can test drive the functionality using the Derby 10.1 alpha
snapshot available at: 

There is an example of establishing an XA connection in the recent build of the Admin and
Sever Guide at: 

> Open Invitation to add a Question and Answer to Derby FAQs
> ----------------------------------------------------------
>          Key: DERBY-232
>          URL: http://issues.apache.org/jira/browse/DERBY-232
>      Project: Derby
>         Type: Task
>   Components: Web Site
>     Reporter: Jean T. Anderson
>     Assignee: Jean T. Anderson
>     Priority: Trivial

> Add a comment to this Jira issue with the FAQ entry (both the question and the answer)
you would like to be added to http://incubator.apache.org/derby/faq.html, and the assignee
will add it.
> Indicate in your comment if the FAQ belongs in the "Developing Derby" or "Using Derby"

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message