So it was definitely my fault.
I forgot to wrap the header parameter with a Holder<>.
Once I did this, the WebParam.Mode.INOUT worked.
Thanks a ton!
jay
--
View this message in context:
http://cxf.547215.n5.nabble.com/User-of-WebParam-Mode-INOUT-with-Document-Style-Header-tp4756426p4764622.ht
Sure...I can see if I can replicate this in a simple JUnit.
The following is a sample of the operation and a snippet of the stacktrace.
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.WRAPPED, use =
SOAPBinding.Use.LITERAL, style = SOAPBinding.Style.DOCUMENT)
@RequestWrapper(localNa
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 WebP
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 t
