|
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() {
if(condition1)
return
ComplexTypeBean;
else if(condition2)
return
ComplextypeBean2;
}
I added the beanMapping tag for both complex type
beans in the soap service. I generate WSDL and I don't see the bean definition
in the WSDL. It used work fine in Axis 1.1. Should I change anything in order
for the WSDL to define the complextype. Even though method signature doesn't
have complex type bean, I am referring it in wsdd file. I don't understand why
Axis doesn't define that bean in the WSDL.
My requirement is to return a complex type bean
based on the condition. So I have to return Object and leave it to the client
for casting to the right complex type bean. .NET client fails since the
definition of the complex type beans are missing.
How do I add a complex type bean to a service even
if the service is 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" |
