Re: Failed comunication between Axis server and JAX-WSclient

\avalon-util-exception-1.0.0.jar -- View this message in context: http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX-WSclient-tp4658126p4658154.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.

Re: Failed comunication between Axis server and JAX-WSclient

Hi Jacopo, I already did! See the 4th post http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX-WSclient-tp4658126p4658130.html http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX-WSclient-tp4658126p4658130.html . -- View

Re: Failed comunication between Axis server and JAX-WSclient

This is what I ended up doing: Not particurarly fond of it but works. Now I am unsure if it breaks some webservices calls -- View this message in context: http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX-WSclient-tp4658126p4658145.html Sent from the OFBiz

Re: Failed comunication between Axis server and JAX-WSclient

(xmlns, null, ModelService.TNS); -errMsg.addAttribute(defaultNS); - // log the response message if (Debug.verboseOn()) { try { -- View this message in context: http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX

Re: Failed comunication between Axis server and JAX-WSclient

message if (Debug.verboseOn()) { try { -- View this message in context: http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX-WSclient-tp4658126p4658146.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.

Re: Failed comunication between Axis server and JAX-WSclient

fixing OFBIZ-4245 would be great! Jacques -- View this message in context: http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX-WSclient-tp4658126p4658138.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.

Re: Failed comunication between Axis server and JAX-WSclient

. This solution worked for a client (I did not write the CXF patch nor I have it in hand) but I agree an integrated solution fixing OFBIZ-4245 would be great! Jacques -- View this message in context: http://ofbiz.135035.n4.nabble. com/Failed-comunication-between-Axis-server-and-JAX

Re: Failed comunication between Axis server and JAX-WSclient

Jacques Le Roux wrote Yes this happens randomly, though not recently. Do you use the trunk HEAD? Jacques Actually no, I use branch release13.07 -- View this message in context: http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX-WSclient-tp4658126p4658152

Re: Failed comunication between Axis server and JAX-WSclient

Ok. Thanks Jacopo! Oh by the way.. to whom it may concern...it seems that branch release13.07 lacks this jar: framework\base\lib\avalon-util-exception-1.0.0.jar -- View this message in context: http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX-WSclient

Failed comunication between Axis server and JAX-WSclient

Hi, I'm using ofbiz branch 13.07, and launching it from an Eclipse environment. I was trying to call a service from a jax-ws client (using websphere jax-ws library but I tried also with cxf) generating the client starting from the WSDL, but while the request is sent and executed correctly the

Re: Failed comunication between Axis server and JAX-WSclient

Hi Gianluca, I didn't play with this part of OFBiz since long but I had a look at the code and I have tried to change it in order to produce the output you need. Could you please try to apply the attached patch? I didn't test it so it may not work. Let me know how it goes. Jacopo On Wed, Nov

Re: Failed comunication between Axis server and JAX-WSclient

I think you forgot to attach the patch cos I'm not seeing it... -- View this message in context: http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX-WSclient-tp4658126p4658128.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.

Re: Failed comunication between Axis server and JAX-WSclient

createAndSendSoapResponse should produce an Axiom OMElement mapMap fully qualified without the need to build a partial DOM response and parse it back don't you think? -- View this message in context: http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX-WSclient-tp4658126p4658130

Re: Failed comunication between Axis server and JAX-WSclient

it... -- View this message in context: http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX-WSclient-tp4658126p4658128.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.

Re: Failed comunication between Axis server and JAX-WSclient

response and parse it back don't you think? -- View this message in context: http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX-WSclient-tp4658126p4658130.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.

Re: Failed comunication between Axis server and JAX-WSclient

that is possible to trasform the response xml using an interceptor to get the result that is expected. I'd prefer a more integrated solution though. -- View this message in context: http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX-WSclient-tp4658126p4658138.html

Re: Failed comunication between Axis server and JAX-WSclient

integrated solution though. -- View this message in context: http://ofbiz.135035.n4.nabble.com/Failed-comunication-between-Axis-server-and-JAX-WSclient-tp4658126p4658138.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.