Yes, ideally that would be great, however JAX-WS doesn't pass the contents of the SOAP header into the endpoint.
Before using JAX-WS, we defined our WSDLs to contain a message definition with TWO parts. For example:
<wsdl:message name="OTA_HotelResRQ">
<wsdl:part name="Header" element="tch:TransactionControlHeader"/>
<wsdl:part name="Body" element="ota:OTA_HotelResRQ"/>
</wsdl:message>
JAX-WS doesn't allow this, so we had to move the "Header" part into the soap header.
Jitendra Kotamraju <Jitendra.Kotamraju_at_Sun.COM> wrote:
LeRoy Hall wrote:
> I'm having a problem "undeploying" a jax-ws web service. When I
> attempt to undeploy/redeploy the service, it fails because something
> is holding open the xml file that was generated by wsimport based on
> my custom config file that contains the handler-chains. Has anyone
> run into this problem??
>
> I have need to parse data sent in the soap header and as far as I can
> tell the only way to do this is with a handler.
Where exactly you need parse soap headers, in endpoint ?
Jitu
>
> I'm currently deploying on Tomcat 5.5.
>
> Thanks.
>
>
> Have a burning question? Go to Yahoo! Answers
>
> and get answers from real people who know.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net
For additional commands, e-mail: dev-help_at_jax-ws.dev.java.net
---------------------------------
Everyone is raving about the all-new Yahoo! Mail beta.