|
|
|
|
|
|
|
Re: impossible to generate a soap:header part [message #148157 is a reply to message #147951] |
Mon, 21 November 2005 10:42   |
Eclipse User |
|
|
|
Christophe,
the story for generated Java skeletons and clients is different than for the
Web Services Explorer. In WSDL, a SOAP header declared in a SOAP binding
references the message/part that defines the type of the header message. The
referenced message/part may, or may not, also be referenced by the portType:
1. If the message/part used by a SOAP header is referenced by an operation in
the portType, then per JAX-RPC sections 11.1 and 11.2.2 "Explicit Service
Context", the header message will be mapped to a Java parameter on the
operation's corresponding business method on the Java SEI. This is "explicit"
header processing.
2. If the message/part used by a SOAP header is not referenced by an operation
in the portType, then the header message will not be mapped, or exposed in any
way, on the SEI, and - from a JAX-RPC perspective - can only be manipulated by
using Handlers. This is "implicit" header processing.
For an example of the explicit mapping which maps headers in the WSDL to
parameters on the business methods of your Java service endpoint interface,
have a look in axis-1_2_1/samples/ws-i/scm/source/ at these files:
1. wsdl/partial/Warehouse.wsdl
2.
java/implemented/org/apache/axis/wsi/scm/warehouse/Warehouse SoapBindingImplC.java
Cheers - CB.
[1] http://www.jcp.org/en/jsr/detail?id=101
Christophe LEFLOCH wrote:
> according to web services-axis documentation, i had to use 'public void
> method(SOAPEnvelope req, SOAPEnvelope resp)' in order to look at or modify
> headers;
>
> i try this
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04008 seconds