Im trying to get an example working where I define
message structures within my schema element in wsdl
for both header and body messages.
Im using JIBX as a data binding tool between my domain
types and the message being passed as request/response
data structures. My question is the following:
by declaring my binding type as follows:
<wsdl:operation name="authenticate">
<soap:operation soapAction="mynamespace/myaction"
/>
<wsdl:input>
<soap:header
part="request_header"message="tns:authHeaders"
use="literal"/>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
It seems like since Im referencing another element on
my schema to define what is in my SOAPHeader block,
that jibx needs to find a mapping in my binding file
to match.
The thing thats confusing is that this element
theoretically shouldnt necessarily get to my skeleton,
and more likely handled within a Handler that I define
in, say, an "authentication" phase within the axis2
stack.
Can someone give me any advice as to how they did it?
Do I just leave my header definition out of my schema
and messages and compile my skeleton/stub code with
what only SOAPBody elements? I included my wsdl and
binding in an earlier post just in case it helps
explain it any better.
On a side note, if I dont actually choose JIBX as my
binding mechanism and leave it to default to ADB, the
wsdl2java compiles fine but gives me methods where
both my header and body are passed to my skeleton.
Sean
Im ok with the fact
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
