Hi Shital
Do you mean that next release of Axis2 say (Axis2_1_5) will not have
code base for JMS Transport
Yes..
and we'll have include ws-commons library to support JMS Transport?
This will be done for you, most probably automatically with the Axis2
release.. but the specifics are yet to be sorted out.. one could argue
not to ship the JMS and other transports by default with the Axis2
builds considering the size of the artifacts.. but it would be made very
simple for users who want to use these transports, to make use of them.
With the new structure, all transport code for Axis2 now comes from
ws-commons, so its almost hidden from end users.
I was thinking of extending *org.apache.axis2.transport.jms.JMSSender*
and see if I can implement request-response operation. Do you think I
should wait till next week and use your nightly builds?
Yes,.. as a user you should not be worried about this level of the
framework code. But you are more than welcome to join the dev lists and
contribute to help make things better.
asankha
--
Asankha C. Perera
http://adroitlogic.org
http://esbmagic.blogspot.com
