Sounds like a bug, so you should file a bug report. I don't know any
workaround to your problem, other than handwriting the WSDL (rather
than auto-generating it). Many people recommend writing the WSDL
manually anyway.
Praveen Peddi wrote:
This is a re-send with simplified
explaination. Just want to try my luck again.
While I am in the process of
migrating from Axis1.1 to 1.2, I have noticed something wierd in WSDL
generation.
I have a method:
public Object[] method1() {
ComplexType1 type1 = new
ComplexType1();
ComplexType2 type2 = new
ComplexType2();
Object[] objects = new
Object[]{type1, type2};
return objects;
}
The above method returns Obejct[]
that has two complex type beans. I added the beanMapping tags for for
complex types for the service (RPC style). Generated WSDL doesn't
define the complex types due to which .NET client fails to de serialize
the objects to beans.
How do I add a complex type bean to
a service even if the service methods are not directly referring to the
bean? Axis1.1 used to define the bean in WSDL if wsdd has beanMapping
for that bean (even if service is not referring to the bean).
Thanks
Praveen
**************************************************************
Praveen Peddi
Sr Software Engg, Context Media, Inc.
email:[EMAIL PROTECTED]
Tel: 401.854.3475
Fax: 401.861.3596
web: http://www.contextmedia.com
**************************************************************
Context Media- "The Leader in Enterprise Content Integration"
|