Re: Axis2 isn't following document literal wrapped standard in generated code

[Michael Mattox]

I'm using xmlbeans, and I noticed that the unwrap option doesn't have
any effect.  I get the same results.

I think I tried adb with unwrap false, and since false is the default,
I think there is not a need to specify it.

-Michael

On 8/2/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Michael,
>
> Did you try the ADB binding ("-d adb") option with unwrap option ("-uw"?)
>
> thanks,
> dims
>
> On 8/2/07, Michael Mattox <[EMAIL PROTECTED]> wrote:
> > I'm trying out Axis2 after using XFire.  I have a WSDL that is
> > document literal wrapped.  My WSDL operation has a single element
> > named parameters.  This element refers to a complex type called
> > XInHolder.  This element contains a single element, called XIn which
> > is a complextype.
> >
> > As I understand the wrapped standard, my method foo should have one
> > parameter named XIn.  This is because each element of the "wrapper
> > object" is a parameter to the method.  This is the case with XFire.
> >
> > With Axis2, my method foo has a XDocument parameter (using xmlbeans
> > bindings).  This document class as a getXInHolder method.  The result
> > is Axis2 is generating the code with not only the wrapper element
> > (which shouldn't be) but also a Document object which wraps the
> > wrapper element.  This adds 2 levels to my web service.
> >
> > This isn't a major problem because my web service simply delegates to
> > a business service and we can dereference the objects and pass the
> > correct object (XIn).  But it doesn't seem like Axis2 is respecting
> > the wrapped standard.  Actually I'm not sure this is even specified in
> > the standard.
> >
> > Any ideas?
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Axis2 isn't following document literal wrapped standard in generated code

[Michael Mattox]

I'm trying out Axis2 after using XFire.  I have a WSDL that is
document literal wrapped.  My WSDL operation has a single element
named parameters.  This element refers to a complex type called
XInHolder.  This element contains a single element, called XIn which
is a complextype.

As I understand the wrapped standard, my method foo should have one
parameter named XIn.  This is because each element of the "wrapper
object" is a parameter to the method.  This is the case with XFire.

With Axis2, my method foo has a XDocument parameter (using xmlbeans
bindings).  This document class as a getXInHolder method.  The result
is Axis2 is generating the code with not only the wrapper element
(which shouldn't be) but also a Document object which wraps the
wrapper element.  This adds 2 levels to my web service.

This isn't a major problem because my web service simply delegates to
a business service and we can dereference the objects and pass the
correct object (XIn).  But it doesn't seem like Axis2 is respecting
the wrapped standard.  Actually I'm not sure this is even specified in
the standard.

Any ideas?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How to exclude interfaces with Java2WSDL?

[Michael Mattox]

I'm generating a WSDL with Java2WSDL.  All my classes implement an
interface and have a method getCategory.  When I run Java2WSDL I pass
-x "getCategory" to exclude this method but it doesn't work.  The WSDL
generated has an object for the class with an attribute "category" of
type "anyType".  I can't figure out if the -x parameter is not working
or if I'm doing something wrong.  A search of the mailing list
archives & JIRA turn up nothing.  Any ideas?

-Michael