Andreas, Thanks for the pointers, this will help me to get this resolved. I don't want to do a transports release with any synapse scenario broken. Will try my best to get this fixed.
Thanks, Ruwan On Tue, Sep 22, 2009 at 6:03 PM, Andreas Veithen <andreas.veit...@gmail.com>wrote: > Ruwan, > > I think there is a mail thread somewhere that shows an example of the > issue in Synapse, but I'm unable for the moment to find this thread > again. If I remember well, the problem shows up with an HTTP to JMS > proxy (in-out). I think (to be confirmed) that the root cause is as > follows: > - serverSide = true means that Axis2 expects a MessageReceiver and > will attempt to invoke it when the message context is injected into > the engine. Thus, serverSide should be set to true only for incoming > requests (i.e. in the TransportReceiver). > - Synapse seems to expect Axis2 to call the MessageReceiver also for > incoming responses. The version of the JMS transport in Synapse > therefore did set serverSide to true in the TransportSender code that > handles the response. This however doesn't work with Axis2's > ServiceClient API. > > As a conclusion (and if my analysis is correct), Synapse and Axis2 (or > at least the ServiceClient API) have two different ideas about the > meaning of serverSide. This is probably also the reason why the NIO > HTTP transport doesn't work with ServiceClient. > > One potential solution to explore is to make sure that Synapse creates > the response message context itself (with serverSide=true) before > sending the outgoing request. Indeed the transports first check if > there is already an existing message context for the response. If we > modify the transport (senders) so that they leave serverSide alone, it > could be possible to make them work properly with both Synapse and > ServiceClient. > > Andreas > > On Tue, Sep 22, 2009 at 03:00, Ruwan Linton <ruwan.lin...@gmail.com> > wrote: > > Hi Andreas, > > > > Where exactly is Synapse not using the axis2 API correctly?? Can you give > me > > a one pointer related to this issue?? Also does this means that synapse > is > > not working properly with the current trunk of transports?? If so what > will > > be the failure? > > > > Thanks, > > Ruwan > > > > On Tue, Sep 22, 2009 at 12:17 AM, Andreas Veithen < > andreas.veit...@gmail.com > >> wrote: > > > >> The problem behind WSCOMMONS-444 is probably more related to Synapse > >> not using the Axis2 APIs in the correct way. The code currently in > >> trunk works well with Axis2 and could be released. They will however > >> not work correctly with Synapse. > >> > >> The other missing thing is documentation, in particular for the JMS > >> transport. I noticed that somebody at WSO2 has documented [1] the > >> various options for the JMS transport. Maybe they can contribute this > >> back to the transports project? > >> > >> Andreas > >> > >> [1] > >> > https://www.wso2.org/repos/wso2/trunk/carbon/docs/xdoc/transports/transports-catalog.xml > >> > >> On Mon, Sep 21, 2009 at 20:07, Ruwan Linton <ruwan.lin...@gmail.com> > >> wrote: > >> > I had a look at this issue and it seems it requires a set of axis2 > >> changes, > >> > and probably we will not be able to fix it for the 1.0 release of the > >> > transports. > >> > > >> > So my proposal is to do the 1.0 release with marking it as a known > issue > >> and > >> > do a 1.1 release of the transports later, after fixing the related > issue > >> in > >> > axis2. > >> > > >> > Thanks, > >> > Ruwan > >> > > >> > On Mon, Sep 21, 2009 at 11:13 PM, Ruwan Linton < > ruwan.lin...@gmail.com > >> >wrote: > >> > > >> >> Hi Glen/Raymond and all, > >> >> > >> >> I had a look at the dependencies and the open JIRAs, and there are no > >> >> SNAPSHOT dependencies and there is only one open blocker [1] which I > am > >> not > >> >> too sure what the right fix is. I will find some background on the > issue > >> and > >> >> will see what we can do for that. At the same time I would like to > get > >> >> started with the release soon, by branching off for the 1.0 release > of > >> the > >> >> transports. > >> >> > >> >> [1] - https://issues.apache.org/jira/browse/WSCOMMONS-444 > >> >> > >> >> Thanks, > >> >> Ruwan > >> >> > >> >> > >> >> On Mon, Sep 21, 2009 at 10:18 PM, Raymond Feng <enjoyj...@gmail.com > >> >wrote: > >> >> > >> >>> +1. The lack of compatible transport releases prevents us (Apache > >> Tuscany) > >> >>> from upgrading to Axis2 1.5 for Web Service binding. > >> >>> > >> >>> Thanks, > >> >>> Raymond > >> >>> -------------------------------------------------- > >> >>> From: "Glen Daniels" <g...@thoughtcraft.com> > >> >>> Sent: Monday, September 21, 2009 8:15 AM > >> >>> To: <commons-dev@ws.apache.org> > >> >>> Subject: Re: Transports release for the axis2 1.5 family > >> >>> > >> >>> > >> >>> Hi Ruwan: > >> >>>> > >> >>>> Yes, we should release the transports. +1 to your being Release > >> Manager. > >> >>>> Unless there's anything blocking it, I'd suggest to go ahead and > put > >> them > >> >>>> out > >> >>>> ASAP. Let me know if you need any help? > >> >>>> > >> >>>> As per this mail thread [1] this should be version 1.0 of the > >> transports, > >> >>>> with each having a separately tweakable version number. > >> >>>> > >> >>>> Thanks, > >> >>>> --Glen > >> >>>> > >> >>>> [1] http://markmail.org/message/dyliuvtfl76r2qod > >> >>>> > >> >>>> Ruwan Linton wrote: > >> >>>> > >> >>>>> Guys, > >> >>>>> > >> >>>>> I didn't hear back from anyone. Don't we need to do a release of > the > >> >>>>> transports to go with axis2 1.5.x???? > >> >>>>> > >> >>>>> Thanks, > >> >>>>> Ruwan > >> >>>>> > >> >>>>> On Wed, Sep 9, 2009 at 8:30 AM, Ruwan Linton < > ruwan.lin...@gmail.com > >> > > >> >>>>> wrote: > >> >>>>> > >> >>>>> Folks, > >> >>>>>> > >> >>>>>> It is a shame that we do not have a release of the transports > even > >> >>>>>> after > >> >>>>>> few months of the axis2 1.5 release, to work with the axis2-1.5. > >> This > >> >>>>>> is > >> >>>>>> blocking the synapse-1.3 release badly together with the rampart > and > >> >>>>>> sandesha releases. > >> >>>>>> > >> >>>>>> Can we please get a transports release any time soon. If there is > no > >> >>>>>> one to > >> >>>>>> take the responsibility I would like to volunteer to get this > out, > >> >>>>>> since we > >> >>>>>> are badly in need of this for the synapse 1.3 release. > >> >>>>>> > >> >>>>>> Thanks, > >> >>>>>> Ruwan > >> >>>>>> > >> >>>>>> -- > >> >>>>>> Ruwan Linton > >> >>>>>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > >> >>>>>> WSO2 Inc.; http://wso2.org > >> >>>>>> email: ru...@wso2.com; cell: +94 77 341 3097 > >> >>>>>> blog: http://ruwansblog.blogspot.com > >> >>>>>> > >> >>>>>> > >> >>>>> > >> >>>>> > >> >>>>> > >> >> > >> >> > >> >> -- > >> >> Ruwan Linton > >> >> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > >> >> WSO2 Inc.; http://wso2.org > >> >> email: ru...@wso2.com; cell: +94 77 341 3097 > >> >> blog: http://ruwansblog.blogspot.com > >> >> > >> > > >> > > >> > > >> > -- > >> > Ruwan Linton > >> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > >> > WSO2 Inc.; http://wso2.org > >> > email: ru...@wso2.com; cell: +94 77 341 3097 > >> > blog: http://ruwansblog.blogspot.com > >> > > >> > > > > > > > > -- > > Ruwan Linton > > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > > WSO2 Inc.; http://wso2.org > > email: ru...@wso2.com; cell: +94 77 341 3097 > > blog: http://ruwansblog.blogspot.com > > > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com
