Hi Hans
Changing axis2 1.4 ourselves is not really an option for us, since we
want to use vanilla components, not modified ones. We could try to
modify the JMS transport (to make it block instead of build a large
queue), but we don't know all ins and outs of this (Is this desired in
the case of publish/subscribe, for example?). Since the current JMS
classes are going to be replaced by the Synapse code base we think it
might not be worth the trouble to change it in the axis2 jms transport
code.
Yes
We have also installed Synapse and managed to get it invoking our
webservices using JMS without problems. Yet, this works differently.
Synapse translates the JMS message into a HTTP SOAP message and passes
that message to axis2. So, axis2 and synapse are going to share the
code that manages the connection factory and incoming messages. That
makes sense...
Is there a forum/repository where we can track the progress on the
merging of the code bases of the axis2 and synapse projects?
Not yet.. we have been busy lately with other defects and enhancements
and unfortunately moving transports out into another project lies with
lower priority right now.. and thus my rough estimate of a few months
before we could get things in place and sorted out clearly..
asankha
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
