tests for ws-rm, I thought
initially the problem after a successful response retransmission from the
server (hence my question about how the client was configured) but the
problem is occurring before. I'll look into it today.
regards, aki
2013/6/3 Juan Alberto Lopez Cavallotti juan.cavallo
Hi Aki,
That answers my questions, thanks a lot for your help.
Regards,
Juan
MuleSoft
On Wed, Jun 5, 2013 at 9:48 AM, Aki Yoshida elak...@gmail.com wrote:
Hi Juan,
2013/6/4 Juan Alberto Lopez Cavallotti juan.cavallo...@mulesoft.com
Hello Aki,
Thanks for your response and for taking
was configured) but the
problem is occurring before. I'll look into it today.
regards, aki
2013/6/3 Juan Alberto Lopez Cavallotti juan.cavallo...@mulesoft.com
Hi Aki,
Please find the log here: http://pastebin.com/B0TtSduG
About the client, it works correctly all the time when I
the decoupled endpoint and persistence at the client?
regards, aki
2013/5/31 Juan Alberto Lopez Cavallotti juan.cavallo...@mulesoft.com
Hi Aki,
Thank you for your reponse.
Yes, I have a decoupled endpoint, I have a standalone client based on
cxf's sample projects (nothing fancy
or to 2.6.8?
2013/5/29 Juan Alberto Lopez Cavallotti juan.cavallo...@mulesoft.com
Hi Aki,
Thanks for getting back to me, if you wish to see the implementation of
the
conduit, here is a github link for it:
https://github.com/mulesoft/mule/blob/mule-3.3.2/modules/cxf/src/main/java
Hello,
I have a custom conduit implementation which takes care of the integration
of CXF and MuleESB. I am able to use the WS-RM functionality on the happy
path over this conduit but when something goes wrong on the backchannel I
get the message stuck on the redelivery queue and constantly
, req/resp or oneway, etc). And i don't know what your
conduit is doing. So it's really hard what to say based on the info you
provided so far.
2013/5/29 Juan Alberto Lopez Cavallotti juan.cavallo...@mulesoft.com
Hello,
I have a custom conduit implementation which takes care
