keith chapman wrote:
> Let me clarify the need for multiple MR's. If we think of codegen, as
> of now Axis2 generates the serverside code based on the portType of a
> WSDL (It does not take the binding into consideration).
Well that is the idea , binding is for the client side not for the
server side, at the server side what we need to care is the porttype.
> Imaging a user has a WSDL such that the response SOAP message should
> have a custom SOAP header when the request is SOAP 1.1 or 1.2 and a
> custom http header when the request is REST.
Well , you should not forget that Axis2 is transport independent ,
meaning at the service level it does not have any idea how the request
came and how the response should be serialized. And Axis2 is a SOAP
engine and we have support for REST . We do not need to make it a REST
engine.  :) , so REST related serialization should be at the transport
level , you may have all the necessary data in the MC.
>
> Now axis2 codegen cannot handle the above scenario.
Well it can handle SOAP scenario :)
>
> Now the only way to do this as of now is to write a module and then do
> the checks within that module and add these headers, but these are
> really binding details of a service and the AxisBinding
This is exactly the right way to do , I mean REST is an extension in
Axis2 , so the idea or module is  to handle extensions.
> hierarchy contains these details and it should have been the
> responsibility of the MessageReceiver to do this. That means we have a
> MR per binding or a single MR with a lot of if conditions (I prefer
> having a MR per binding).
hmm , what happen if we start to generate JMS binding , then do we need
to have some other MR for that ? I think answer is no . And before
calling the AxisEngine everything has to be converted into a SOAP message.
>
> This is where the need for multiple MR's come in.
>
> Glen/Deepal I agree that taking parts off the path/query/body and
> binding the SOAP infoset is part of the builder but imaging this
> situation. Think of having JAX-RS support in Axis2. 
Well we do not need to talk about that since we do not have support for
JAX-RS.

Thank you!
Deepal

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to