The suggested fix worked and I now I have JBoss MQ providing XA transactions
for WebSphere! I've placed the patch under Jira, as requested:
http://jira.jboss.com/jira/browse/JBMQ-17.
Thanks for the support!
Daniel.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtop
Access to cvs is described here:
http://sourceforge.net/cvs/?group_id=22866
Patches are context diffs of the source files changes. They should be submitted
to:
http://jira.jboss.com/jira/browse/JBAS
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859945#385994
Thanks for the reply Adrian!
I would like to do this simple fix myself and contribute it back to the
project. How should I go about doing this? You mentioned submitting a patch
but what does this mean exactly (is there an open CVS server, for instance)?
Sorry, but I'm new on JBoss and still
Report it is a bug. http://jira.jboss.com/jira/browse/JBMQ
Even if the IBM Xid implementation were serializable, it would fail to
deserialize
on the server unless you put that class inside JBossMQ.
The fix is trivial if you want to attempt it yourself and post the patch:
In org.jboss.mq.Transac
Oops, forgive the incorrect account name on the previous post. "marcfleury" is
an account generated from bugmenot.com. I think my browser must have picked up
a cookie on this machine from some other visit. This is my real account.
Thanks,
Daniel.
View the original post :
http://www.jboss.o
