Preface:
We are currently authenticating using handlers.
The service uses an inHandler and the client uses an outHandler
This all works well. However, the WSDL makes no mention of the header
elements
We have now modified the WSDL to describe the soap header elements
by adding the <soap:header> element in the binding section
e.g.
<operation name="oper1">
<soap:operation
soapAction="http://www.mydomain.com/oper1"/>
<input>
<soap:header
message="tns:authenticationTokenMessage" part="header" use="literal"/>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
Using XFIRE to generate the interface now places the AuthenticationToken
element in the msg
e.g....,@WebParam(header=true) AuthenticationToken token
Question:
Does the XFIRE based client need to be modified to not use the outHandler
and instead pass the token to the message
When we do that, no soap headers are being generated
Also, now that an inHandler is not used on the service side, how can we
get hold of the xfire session available from the MessageContext
inside the service class.
Shal Jain
FoundationIP - Part of CPA Software Solutions
********************************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee; access to this
email by anyone else is unauthorized.
If you are not the intended recipient: (1) you are kindly requested
to return a copy of this message to the sender indicating that you
have received it in error, and to destroy the received copy; and (2)
any disclosure or distribution of this message, as well as any action
taken or omitted to be taken in reliance on its content, is prohibited
and may be unlawful.
********************************************************************************
