axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug B" <>
Subject Re: More Axis & wrapped (Was: Re: No such operation)
Date Thu, 29 Jun 2006 19:11:27 GMT
Thanks, Anne.  That's how I "guessed" the ant task's syntax, but there
were a few possible ways it could have been implemented, or even not
at all, so I was glad to find it.

But I think that approach is what we're going to try to do, but at
this point my customer is still trying to use JBuilder's Axis-hiding
tools, and he hasn't found out how to do -noWrapped from them.  He's
willing to revert to command-line if necessary, but is leaving that as
a last resort.


On 6/29/06, Anne Thomas Manes <> wrote:
> Doug,
> The WSDL2Java Reference Guide documents the -W --nowrapped option. See
> My recommendation is to define your WSDLs following the wrapped convention,
> but to turn it off in your service implementation (using -W). That gives
> your client developers to use the wrapped option if they like.
> Anne
> On 6/28/06, Doug B <> wrote:
> >
>  Sigh.  I changed our WSDL & Schema to use a naming convention that I
> thought would work with Axis' current default behaviour on the server
> side, and it caused its own issues.  Namely, apparently 4 of my 5
> operation signatures now meet all Axis' criteria for "wrapped" style,
> but one does not.  So Axis generated 1 interface method the way I
> wanted, with request and response complexType beans, and 4 "wrapped"
> style methods (which would have confused the heck out of me if we
>  hadn't had this whole discussion).
> Eventually I got the ant <wsdl2java> task to not use "wrapped"
> (seemingly undocumented syntax*), so things look like they might be
> ok.  My test-generated server deploy.wsdd at least looks like the
> qnames will match now.
> I'm not sure if using a "wrapped-compatible" WSDL is better or worse
> if you're not planning on actually using wrapped mappings.  It looks
>  like, at least with Axis, either way you have to customize the
> generated artifacts, so you have to know about "wrapped" even if you
> don't want to use it.
> BTW, wrapped looks much harder to use portably than non-wrapped, from
> a business code point-of-view.  The wrapped method signatures have
> dependencies on axis packages, where the non-wrapped ones only have
> dependencies on my Schema beans, which ideally, one day, will be
> totally POJO allowing me to switch out engines easily.  But that's a
> different subject.
> *
> doesn't
> document any attribute to disable wrapped, but setting the attribute
> noWrapped="true" in the main element of the task worked.
> Doug
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message