cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Tremblay <henri.tremb...@gmail.com>
Subject Re: Request and Response wrapper
Date Fri, 09 Dec 2011 17:09:07 GMT
Awesome! I'll try that right away.

On 9 December 2011 16:29, Daniel Kulp <dkulp@apache.org> wrote:

>
> You need to add:
>
> @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
>
> to the SEI interface/impl to let it know that methods are in not to be
> wrapped.   That should likely fix most of the issues.
>
>
> Dan
>
>
> On Friday, December 09, 2011 11:31:36 AM Henri Tremblay wrote:
> > Hi,
> >
> > My second question of the day. To make it easy for the developers, I'm
> > requested to build my web service with the following pattern
> >
> > MyMethodResponse myMethod(MyMethodRequest request)
> >
> > This doesn't work well with cxf because it adds a wrapper object over the
> > request and response.
> >
> > Is there a way to tell it not to add this wrapper? Or what would be the
> > suggestion in my case?
> >
> > I also notice a strange side effect of that. I'm generating the client
> side
> > code using the cxf maven plugin. I have this:
> >
> > MyService {
> >    FooRes foo(FooReq r);
> > }
> >
> > MyService2 {
> >    AnotherFooRes foo(FooReq r);
> > }
> >
> > At generation, the @ResponseWrapper of MyService2.foo is giving FooRes
> for
> > the classname. The return type is correct thought. What's up? Bug?
> >
> >
> > Thanks
> > -
> > Henri
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message