right now development in the middle. do not use the version
that's currently in the cvs, as it does not let manta join on
external transaction monitors.
the status right now is as follows:
MantaXAConnectionFactory (which doubles as
XATopicConnectionFactory and XAQueueConnectionFactory)
is implemented alright. I tested binding it into JNDI and
looking it up.
MantaXAConnection (which doubles as XATopicConnection
and XAQueueConnection) is implemented to a point where I
can register an XA-topic-MDB on WLS8.1sp4. The MDB
looks up the correct object, and asks for the getTopicSession
() from the connection. It seems to be deployed alright.
MantaXASession object(s) - I need to decide about letting it
double as XATopicSession or XAQueueSession as well - this
is half-way implemented. Seems like most of the methods
are on the right track, and it's probably another day or two of
coding (together with implementing XAResource and Xid
there) before real XA testing can commence. I need some
test scenarios for this. Right now I am thinking of testing it
with a simple Session EJB that creates a UserTransaction
with it. Any comments or ideas for tests will be welcome.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok.
No ideas for tests arrived.. that's cool.
I finished writing all the manta's side classes needed for XA,
which right now forces disk-writes on every change, not only
at relevant points. I only have a little corner with the 'forget'
implementation, but that's going to be closed this Monday.
I did find out, however, that the integration of an XA resource
to a TransactionManager, is regulated in J2EE1.4 by using
JCA, but there's nothing decisive in J2EE1.3, which means
that any Application Server is free to implement it as it
wishes.
This is of course not very good.
Anyway, I did manage to hook up to BEA's Weblogic8.1sp4
and make sure Manta's XA implementation works there
correctly (well, within reasonable testing efforts anyway). I will
make sure that everything is covered (e.g. forget...) and move
on to JCA.
May my strength be straightened, as Jacob says.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1038557
Nimo is taking this task under his capable hands.
thanks
Amir Shevat
Logged In: YES
user_id=990269
The implementation is finished, although it needs more
testing. It will be available in the CVS after the next update.
Logged In: YES
user_id=990269
right now development in the middle. do not use the version
that's currently in the cvs, as it does not let manta join on
external transaction monitors.
the status right now is as follows:
MantaXAConnectionFactory (which doubles as
XATopicConnectionFactory and XAQueueConnectionFactory)
is implemented alright. I tested binding it into JNDI and
looking it up.
MantaXAConnection (which doubles as XATopicConnection
and XAQueueConnection) is implemented to a point where I
can register an XA-topic-MDB on WLS8.1sp4. The MDB
looks up the correct object, and asks for the getTopicSession
() from the connection. It seems to be deployed alright.
MantaXASession object(s) - I need to decide about letting it
double as XATopicSession or XAQueueSession as well - this
is half-way implemented. Seems like most of the methods
are on the right track, and it's probably another day or two of
coding (together with implementing XAResource and Xid
there) before real XA testing can commence. I need some
test scenarios for this. Right now I am thinking of testing it
with a simple Session EJB that creates a UserTransaction
with it. Any comments or ideas for tests will be welcome.
Logged In: YES
user_id=990269
Ok.
No ideas for tests arrived.. that's cool.
I finished writing all the manta's side classes needed for XA,
which right now forces disk-writes on every change, not only
at relevant points. I only have a little corner with the 'forget'
implementation, but that's going to be closed this Monday.
I did find out, however, that the integration of an XA resource
to a TransactionManager, is regulated in J2EE1.4 by using
JCA, but there's nothing decisive in J2EE1.3, which means
that any Application Server is free to implement it as it
wishes.
This is of course not very good.
Anyway, I did manage to hook up to BEA's Weblogic8.1sp4
and make sure Manta's XA implementation works there
correctly (well, within reasonable testing efforts anyway). I will
make sure that everything is covered (e.g. forget...) and move
on to JCA.
May my strength be straightened, as Jacob says.