On Thu, Jan 21, 2010 at 2:54 AM, Pascal Kesseli
<[email protected]>wrote:

> Well, that's good to hear, but as I stated before, generating Stubs using a
> WSDL including messages without any parts using Eclipse and Axis 2 creates
> invalid code.
>
> In fact, the generated code raises the following runtime exception, as
> stated before:
> org.apache.axis2.AxisFault: No XML element tag
>        at
>
> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:435
> )
>        at
>
> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAx
> isOperation.java:371)
>        at
>
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperatio
> n.java:417)
>        at
>
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisO
> peration.java:229)
>        at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
>        at
>
> org.example.www.emc_remote.EmcRemoteStub.getMeteringPoints(EmcRemoteStub.jav
> a:309)
>        at org.example.Runner.main(Runner.java:13)
>
> This is probably due to the fact that the generated SOAP message contains
> an
> empty body:
> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Body
> /></soapenv:Envelope>
>
> Clearly, this is a bug. Either in Axis 2 or in the Eclipse Web Service
> Client generation wizard. So who should I approach to fix this?
>

No this is correct. If there are not input xml it should send an empty soap
boady.

thanks,
Amila.


>
> Thanks and best regards
> Pascal
>
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Reply via email to