Skip to main content

@RequestWrapper vs @SOAPBinding

1 reply [Last post]
jortizclaver
Offline
Joined: 2006-05-18

Hi,

My WS has two different operations. Both of them receive two parameters but only one of them returns something. Using a WDSL2Java approach, I get an interface based in @RequestWrapper style for the one that has a return value. The void method is implemented using @SOAPBinding so I need to use intermediate object to get the values of my parameters.

Is there any way I can generate @RequestWrapper methods even if me method is void?

Thanks in advance
Jorge

P.S: When I say 'void' I mean that the output message of the operation is empty.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
vivekp
Offline
Joined: 2003-06-10

Generation of wrapper style operation solely depends upon the wrapper style rules defined by the jaxws 2.0 specification.

I guess your second operation might not be meeting all the wrapper style requirements so not getting generated as such. A WSDL/Schema that was used to generate this interface will help determine why its not a wrapper style operation and also the generated interface.

-vivek.

> Hi,
>
> My WS has two different operations. Both of them
> receive two parameters but only one of them returns
> something. Using a WDSL2Java approach, I get an
> interface based in @RequestWrapper style for the one
> that has a return value. The void method is
> implemented using @SOAPBinding so I need to use
> intermediate object to get the values of my
> parameters.
>
> Is there any way I can generate @RequestWrapper
> methods even if me method is void?
>
> Thanks in advance
> Jorge
>
> P.S: When I say 'void' I mean that the output message
> of the operation is empty.