yeah, The unbound header may not by very portable, but what if I provide a
schema reference in the types section. Use types to create a header message in
message and then use soap:header for input in bindings. To do this I need to
explicitly import the schema in wsdl types. Something like
<wsdl:definitions somenamespace>
<wsdl:types>
<xsd:import
namespace="http://webservice.jboss.com/ws4ee schema"
schemaLocation=".some.xsd" id="jbws"/>
some more types
</wsdl:types>
<wsdl:message name="my-header">
<wsdl:part name="my-header" element="jbws:username ">
</wsdl:message>
.........
<wsdl:porttype>.............
.............
<soap:operation="somename" soapAction="somevalue"/>
<wsdl:input>
<soap:header message="my-header" use="literal">
</wsdl:input>
<wsdl:service>
</wsdl:service>
</wsdl:definitions>
here I define a type, create a message and use this message as a soap:header in
bindings.
after this I suppose client soap stack should be able to set the header
correctly.
Is something like this make sense or its impossible??
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869700#3869700
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869700
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
