Hi dims, I sort of agree but there's a reason for how it is now..
If WS-A is understood on a request message, the response message must also have WS-A headers. The WS-A Action is not optional for any message so we have 2 options: 1. Fault when no response action is available. 2. Put in a sensible (though wrong) default action on the response message A while back I advoctaed 1 but was rebuffed, so we have 2. I'm guessing (hoping) that keith is using a service with WSDL2 (or no WSDL) which would explain why there's no response action available. David On 06/02/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
should not be added unless specified in the wsdl/services.xml -- dims On 2/6/07, keith chapman <[EMAIL PROTECTED]> wrote: > Hi, > > I just noticed that the soap action I set on the client appears in the > response from the server. Seems like the createOutMessageContext method in > the MessageContextBuilder class does this if there is no outaction specified > on the operation. Is such an action needed? Is there a need for an action to > appear on the response? > > Thanks, > Keith. > > -- > Keith Chapman > WSO2 Inc. > Oxygen for Web Services Developers. > http://wso2.org/ -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- David Illsley - IBM Web Services Development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
