What sort of timeframe do you need it in? The Axis2 1.5 release looks like it could start being voted on this week but that often can take some time and then the JMS transport would be released separately after that and then we'd need some time to polish a Tuscany release including those. So all that would likley take some weeks. There are alternatives like trying to port the new JMS transport to our existing ws binding, but thats likely a bit more work.
...ant On Mon, Apr 20, 2009 at 8:35 PM, Dave Sowerby <[email protected]>wrote: > Great, thanks Ant. > > Just FYI the highest priority issue for us is TUSCANY-2916 - it's > really causing us some pain. > > If there's anything I can do to help find a solution, then please let me > know! > > Cheers, > > Dave. > > On Tue, Apr 14, 2009 at 9:37 AM, ant elder <[email protected]> wrote: > > > > > > On Tue, Apr 14, 2009 at 9:25 AM, Dave Sowerby <[email protected]> > > wrote: > >> > >> Hey guys, > >> > >> Would it be possible to get fixes for Tuscany issues 2861, 2900 and > >> 2916 included the 1.5 release - these three issues are currently > >> causing us problems with 1.4, so if a 1.5 release could resolve them > >> then that'd be great. > >> > >> Cheers, > >> > >> Dave. > >> > > > > Sure we can try, i've added those three to the 1.5 release JIRA category. > > > > ...ant > > > > > > >
