Are you planning on using the interfaces already provided in javax.transaction.xa? I noticed that your TransactionManager interface is very close to XAResource and your Xid interface is identical to the one in that package. Is this stuff working at a lower level or is it intended to be a JTA implementation that works in the standard way with java transaction managers?
The reason I ask, is I'm trying to imagine writing a JCA resource adapter to plug Qpid into an app server. To do this you have to implement XAResource in javax.transaction.xa. Also, what about the case for non-XA (local only) transactions. The transactional enqueue and dequeue methods must take Xid parameters. In the local case would you just generate some suitable values to use for these or would the local transaction methods on MessageStore be different or just like they currently are? Rupert On 26/03/07, Arnaud Simon <[EMAIL PROTECTED]> wrote:
+1 I first though about only sending bytes arrays and Uids around but it was too restrictive so we went for what we currently have. I´ll synchronize with Gordon for defining PersistableQueue and PersistableMessage interfaces. Cheers Arnaud On Mon, 2007-03-26 at 14:42 +0100, Gordon Sim wrote: > Alan Conway wrote: > > One note here - in the C++ broker, I'd like to pass a more restricted > > interface to Queue and Message to the messagestore. > > I agree; I'm going to be continuing with the dtx implementation on c++ > and will do some refactoring as part of that, including the point you > mention here (e.g. some sort of PersistableQueue and PersistableMessage > interface). >
