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 this
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
Launched test-result ant target, test results:
Tests 321
Failures 1
Errors 0
Skipped 0
Success rate 99.69%
Time 1326.873
The failed one:
basetests testBasicDisk Failure is-empty
junit.framework.AssertionFailedError: is-empty
at
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:
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:
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.
Hey thanks! I've got the patch, unfortunately those are the exact
modifications I already made,
and they're not sufficient.
*The result is something like this:*
?xml version=1.0 encoding=utf-8?
soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Body
Yes, I've seen it. (that's where I got the link for the RPC-Literal
specifications that I posted)
These are the solutions suggested: (quoting)
Daniel Kulp wrote
1) Download the wsdl and edit it to match what the service really
produces.
In this case, all the part names of parameters need
