You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Baxi, Rinilkumar (TCS)" <ri...@hp.com> on 2008/04/07 09:33:23 UTC

Regarding Axis2C architecture

Hi All,

Currently I am working on the design to invoke a legacy service through axis2c, which accepts character buffer as input and giving output is also in character buffer form.

But as per my understanding on the existing Axis2c architecture is the last handler is the "Message Receiver" and its output is XML infoset.

Kindly let me know how can and where can I integrate my code to convert the XML infoset to the raw character buffer and viceversa without damaging the existing Axis2C architecture.

Thanks in advance.

Regards.
Rinil



Re: Regarding Axis2C architecture

Posted by Samisa Abeysinghe <sa...@wso2.com>.
Baxi, Rinilkumar (TCS) wrote:
>  
> Hi All,
>  
> Currently I am working on the design to invoke a legacy service 
> through axis2c, which accepts character buffer as input and giving 
> output is also in character buffer form.
>  
> But as per my understanding on the existing Axis2c architecture is the 
> last handler is the "Message Receiver" and its output is XML infoset.
>  
> Kindly let me know how can and where can I integrate my code to 
> convert the XML infoset to the raw character buffer and viceversa 
> without damaging the existing Axis2C architecture.

You can do this with a service. That is the best and easiest option.
However, if you want to write your own custom message receiver, you can 
do that as well. Just implement the message receiver interface. However, 
give that you can get the job done with a service, I do not think taking 
this path would be ideal.

Tanka,
Samisa...


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org