java2wsdl interface question

[Nishant Deshpande <ni...@gmail.com>]

i have been reading various threads asking this question on the
net but not really got any definitive answers so i will try here.

so if i use java2wsdl to convert some api which either takes/returns
an interface, i get the following errors:
"""
- The class com.[protected].ReportRequestObject does not contain a
default constructor, which is a requirement for a bean class.  The
class cannot be converted into an xml schema type.  An xml schema
anyType will be used to define this class in the wsdl file.
- The class com.[protected].ReportObject does not contain a default
constructor, which is a requirement for a bean class.  The class
cannot be converted into an xml schema type.  An xml schema anyType
will be used to define this class in the wsdl file.
"""

the only way i can think of to get around this is to create an
'interface' bean (essentially an implementation of this interface with
a default constructor) and use this to create the wsdl and then edit
the wsdl and i guess it will work.

any better ways?

Re: java2wsdl interface question

[Anne Thomas Manes <at...@gmail.com>]

Nope. Create the bean.

On 2/7/06, Nishant Deshpande <ni...@gmail.com> wrote:
>
> i have been reading various threads asking this question on the
> net but not really got any definitive answers so i will try here.
>
> so if i use java2wsdl to convert some api which either takes/returns
> an interface, i get the following errors:
> """
> - The class com.[protected].ReportRequestObject does not contain a
> default constructor, which is a requirement for a bean class.  The
> class cannot be converted into an xml schema type.  An xml schema
> anyType will be used to define this class in the wsdl file.
> - The class com.[protected].ReportObject does not contain a default
> constructor, which is a requirement for a bean class.  The class
> cannot be converted into an xml schema type.  An xml schema anyType
> will be used to define this class in the wsdl file.
> """
>
> the only way i can think of to get around this is to create an
> 'interface' bean (essentially an implementation of this interface with
> a default constructor) and use this to create the wsdl and then edit
> the wsdl and i guess it will work.
>
> any better ways?
>