You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Achim Abeling <ac...@freenet-ag.de> on 2006/07/24 15:12:23 UTC

WSDL does not contain complex type corresponding to bean mapping if not explicitly used

Hi,

I am using Axis 1.3 and found out that the automatically generated WSDL 
for a webservice does not contain complex types for beans that are not 
explicitly used in a webservice even though there is a bean mapping 
defined for it.

Isn't this a problem for webservices where such beans are used 
indirectly e.g. in collections or maps?

Best regards
Achim

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: WSDL does not contain complex type corresponding to bean mapping if not explicitly used

Posted by Achim Abeling <ac...@freenet-ag.de>.
Hi Anne,

thanks for your help.

I now found out that the deployment descriptor also contains this switch.

Achim

Anne Thomas Manes wrote:
> You will need to run java2wsdl and inlcude this switch:
> 
>         -e, --extraClasses <argument>
>             A space or comma separated list of class names to be added to
>             the type section.
> 
> Anne
> 
> On 7/24/06, Achim Abeling <ac...@freenet-ag.de> wrote:
>> Hi,
>>
>> I am using Axis 1.3 and found out that the automatically generated WSDL
>> for a webservice does not contain complex types for beans that are not
>> explicitly used in a webservice even though there is a bean mapping
>> defined for it.
>>
>> Isn't this a problem for webservices where such beans are used
>> indirectly e.g. in collections or maps?
>>
>> Best regards
>> Achim
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: WSDL does not contain complex type corresponding to bean mapping if not explicitly used

Posted by Anne Thomas Manes <at...@gmail.com>.
You will need to run java2wsdl and inlcude this switch:

         -e, --extraClasses <argument>
             A space or comma separated list of class names to be added to
             the type section.

Anne

On 7/24/06, Achim Abeling <ac...@freenet-ag.de> wrote:
> Hi,
>
> I am using Axis 1.3 and found out that the automatically generated WSDL
> for a webservice does not contain complex types for beans that are not
> explicitly used in a webservice even though there is a bean mapping
> defined for it.
>
> Isn't this a problem for webservices where such beans are used
> indirectly e.g. in collections or maps?
>
> Best regards
> Achim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org