cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: User of WebParam.Mode.INOUT with Document Style Header
Date Thu, 01 Sep 2011 01:13:05 GMT
On Wednesday, August 31, 2011 4:34:43 PM jaybytez wrote:
> I was reading the specification section on WebParam.Mode.INOUT
> /The direction in which the parameter is flowing.
> Valid values are:
>     WebParam.Mode.IN
>     WebParam.Mode.OUT
>     WebParam.Mode.INOUT
> Default value is WebParam.Mode.IN.
> If you specify WebParam.Mode.OUT or WebParam.Mode.INOUT, then the data type
> of the parameter must be Holder, or extend Holder. For details, see the
> JAX-RPC specification.
> WebParam.Mode.OUT and *WebParam.Mode.INOUT modes are only supported for
> RPC-style Web Services or for parameters that map to headers.* /
> And the question is, can I use WebParam.Mode.INOUT within a Document style
> service if it is header parameter?

Actually, with CXF, you should be able to use if for Document style non-
headers as well.

> The reason I ask is that I have a WebParam with header=true and
> mode=WebParam.Mode.INOUT and I get an IllegalArgumentException claiming that
> my request doesn't match the request parameters.  But when I remove the
> mode altogether, the service invocation works.

Any chance you can create a testcase and attach it to a JIRA?


> Thanks for the help...jay
> --
> View this message in context:
> tyle-Header-tp4756426p4756426.html Sent from the cxf-user mailing list
> archive at
Daniel Kulp
Talend -

View raw message