I've had a bit of look at this. As an Axis2 release using the new commons transports hasn't been done yet its not so trivial to use this from the Tuscany Axis binding. It would be much easier to wait for the Axis2 1.5 release but given recent progress on that its not likely to be out in the timeframes being talked about for the Tuscany 1.5 release. The options I can see are:
1) Defer TUSCANY-2916 from the Tuscany 1.5 release and fix it in a later Tuscany release after Axis2 has been released. 2) Delay the Tuscany 1.5 release till the Axis2 release is done 3) Copy the Axis2 commons JMS transport to the Tuscany SVN and do the changes to get it to work with Axis2 1.4.1 and the Tuscany WS binding Option (3) is quite a lot of work and it would be thrown away when Axis2 1.5 does come out so (1) or (2) would be better from that perspective, but if TUSCANY-2916 is an urgent requirement we might just have to do (3). ...ant
