There is no such code right now, I guess, but the Jakarta Slide
implements the XA interfaces for the file store in a specific way. If
you would want to contribute something more general it would certainly
be well accepted.

Oliver

On Mon, 21 Mar 2005 09:17:35 +1100, Mason, Ross <[EMAIL PROTECTED]> wrote:
> In the same way that you have XA support for VM transactions you could do 
> something similar for File-based transactions.  These transactions could then 
> be managed by a Jca container or programmatically.
> 
> Ross
> -----Original Message-----
> From: Oliver Zeigermann [mailto:[EMAIL PROTECTED]
> Sent: Sun 20/03/2005 9:51 PM
> To: Jakarta Commons Users List
> Cc:
> Subject: Re: [transaction] XA File transaction support
> 
>         Not quite sure what you are planning. Are you talking about a JCA
>         connector for files?
> 
>         Oliver
> 
>         On Sun, 20 Mar 2005 10:12:50 +1100, Mason, Ross <[EMAIL PROTECTED]> 
> wrote:
>         > Hi,
>         >
>         > I have been looking at using commons-transaction for the Mule 
> project (http://mule.codehaus.org) for managing file and vm transactions. I 
> wanted to know if you have any plans for supporting XA transactions for 
> files? Our usage scenario almost always combines file reading/writing with 
> reading/writing of other sources such as jdbc and Jms.  Having File IO 
> included in an XA transaction would be really useful for us and probably 
> other people as well.
>         >
>         > Cheers,
>         >
>         > Ross
>         >
> 
>         ---------------------------------------------------------------------
>         To unsubscribe, e-mail: [EMAIL PROTECTED]
>         For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to