I'm not sure if avoiding such info can do any good. I expect to have
the same types on my service and client generated from wsdl, but
without such information you couldn't do that.
On 11/21/06, Hookom, Jacob <[EMAIL PROTECTED]> wrote:
With WSDL generation from Aegis, is there a way to avoid sub-types for
collections/arrays?
If we have:
interface Company {
Employee[] getEmployees();
}
a child type of tns:ArrayOfEmployee is generated in the WSDL:
<xsd:element minOccurs="0" name="items" nillable="true"
type="ns1:ArrayOfEmployee" />
What we would like to have generated is:
<xsd:element minOccurs="0" maxOccurs="unbounded" name="Employee"
nillable="true" type="ns1:Employee" />
Any help would be appreciated!
Thanks,
Jacob
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
--
-----
When one of our products stops working, we'll blame another vendor
within 24 hours.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
