OK, I fixed the nillable issue at r1384251
Locally I could use the ping service but got a (actually reassuring) "unable to find valid certification path to requested target"
which is caused by a self signed local certificat (or no valid certificat at all, anyway)
So I tried on a remote server and got this
<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
<soapenv:Body>
<pingResponse xmlns="http://ofbiz.apache.org/service/";>
<map-Map>
<map-Entry>
<map-Key>
<std-String value="responseMessage"/>
</map-Key>
<map-Value>
<std-String value="success"/>
</map-Value>
</map-Entry>
<map-Entry>
<map-Key>
<std-String value="message"/>
</map-Key>
<map-Value>
<std-String value="PONG"/>
</map-Value>
</map-Entry>
</map-Map>
</pingResponse>
</soapenv:Body>
</soapenv:Envelope>
with your request
<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >
<SOAP-ENV:Body>
<jsx1:ping xmlns:jsx1="http://ofbiz.apache.org/service/"; >
<map-Map>
<jsx1:map-Entry>
<jsx1:map-Key>
<jsx1:std-String value="message" />
</jsx1:map-Key>
<jsx1:map-Value>
<jsx1:null />
<jsx1:std-String value="PING_TEST_BOOYAH" />
</jsx1:map-Value>
</jsx1:map-Entry>
</map-Map>
</jsx1:ping>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Could you confirm it works for you for other services with these changes?
Thanks
Jacques
From: "Jacques Le Roux" <[email protected]>
There is an error in generated WSDL related to nillable, I will have a look...
Thanks for report
Jacques
From: "Parm Lehal" <[email protected]>
I am trying use web-service using netbeans. The JAX-WS SOAP service fails
with this error :
javax.xml.ws.WebServiceException: Unexpected response element Response
expected: {http://ofbiz.apache.org/service/}createProductResponse
at
com.sun.xml.internal.ws.client.sei.ResponseBuilder$RpcLit.readResponse(ResponseBuilder.java:603)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:110)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107)
at $Proxy28.createProduct(Unknown Source)
However, if I use xmlrpc, it works fine. Is there any trick in making
JAX-WS web service work or am I missing something? Please, advise.
Regards,
Parminder Lehal
