Hi

  I am currently having issue with some of the services I have
implemented with REST enabled.  With SOAP, all the operations are
working fine, but with REST there are couples of operations that do not
work.

As I understand, axis2 converts the REST/HTTP request to a SOAP message.

 

I have RawXMLINOutMessageReceiver as the message receiver.

 

Requests that work fine have the following xml structure defined in the
WSDL.

<a>

  <b/>

</a>

In this case I am able to access the OMElement node b within the saop
body.

The URL provided in the browser looks like

http://domain/service/MyService/a

 

 

Requests that have issues are of the following structure

<a>

  <b>

     <c/>

     <d/>

  </b>

</a>

In this case, the soap message is created with only "a" and "b" as the
OMElement node. The "c" and "d" nodes are not created during the
conversion.

The URL provided in the browser looks like

http://domain/service/MyService/a?c=sample&d=free

 

I would like to understand the REST architecture within axis2 and how
the request parameters are mapped to the actual xml structure defined in
WSDL.

 

Any help will be appreciated.

 

Thanks

Shantaram

Reply via email to