dkulp wrote:
>
> That example is for a server side thing to get the headers that were sent
> in
> with the request (or add headers to the response).The
> WebServiceContext is
> really a server side thing.The client side has the RequestContext and
> ResponseContexts on the proxy objec
dkulp wrote:
>
> That example is for a server side thing to get the headers that were sent
> in
> with the request (or add headers to the response).The
> WebServiceContext is
> really a server side thing.The client side has the RequestContext and
> ResponseContexts on the proxy objec
dkulp wrote:
>
> In anycase, since the wsdl sucks, you would need to drop to the API's
> listed
> in the FAQ. On the client side, the context would be the request
> context:
> ((BindingProvider)proxy).getRequestContext().put(HEADER_LIST, headers);
>
Yep, I'm surprised they didn't put this i
karypid wrote:
>
> With JAX-WS, I think you can set a flag "header=true" in the web service
> interface. Like:
> public void someWebMethod(@WebParam(header=true) String myHeaderParam);
>
Unfortunately, I don't have control of the wsdl (it's Amazon's web service).
In the PortType.java file t
I'm trying to make the soap header of WS client requests look like this
(adding the aws parameters to the soap:header):
http://docs.amazonwebservices.com/AWSECommerceService/latest/DG/index.html?AuthJavaSampleSig2.html
http://security.amazonaws.com/doc/2007-01-01/";>
1D9FVRAYCP1VJS767E02EXAMPLE