Anyone aware of an outstanding bug report on this?

-----Original Message-----
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2003 5:36 PM
To: [EMAIL PROTECTED]
Subject: Re: wrapped services && soapenc:Array


Sounds like a bug. For doc/lit, Axis should generate an element with
unbounded content.

Anne

----- Original Message -----
From: "Cory Wilkerson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 31, 2003 6:06 PM
Subject: RE: wrapped services && soapenc:Array


> Well, this is what Axis is generating by default -- and I've told it it's
a wrapped service --- it's interpreting everything else as doc/lit...just
not this.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 31, 2003 5:05 PM
> To: [EMAIL PROTECTED]
> Subject: Re: wrapped services && soapenc:Array
>
>
>
> Java2WSDL has options to produce doc/lit wsdl files, but I believe the
> default is rpc.
>
>
>
>
>                       "Cory Wilkerson"
>                       <[EMAIL PROTECTED]        To:
<[EMAIL PROTECTED]>
>                       lnow.com>                cc:
>                                                Subject:  wrapped services
&& soapenc:Array
>                       07/31/2003 03:59
>                       PM
>                       Please respond to
>                       axis-user
>
>
>
>
>
> Why does my wrapped service (doc/literal) define extensions of
> soapenc:Array?  Shouldn't Axis generate wsdl that just describes an
element
> with unbounded content of a given type?  .Net won't swallow this sort of
> declaration.
>
> So, given a class "FooService" with method "fooMethod(String[] args)"....
>
> I'd expect to see wsdl that looks something like:
>
> <schema>
>              <element name="args">
>                          <complexType>
>                                      <element name="foo" type="xsd:string"
> minOccurs="0" maxOccurs="unbounded"/>
>                          </complexType>
>              </element>
> </schema>
>
> I've seen some stuff moving across the mailing list in regards to this as
> well as a few bug reports -- is the issue stagnant?
>
> Thanks,
> Cory
>
>
>
>
>
>
>

Reply via email to