I have a service interface that itself uses interfaces. It looks like this:
{
User getUser();User[] findUserByName(String name);
... }
User is an interface implemented in two different concrete ways in my project (this is a requirement). java2wsdl warns out with:
[java] 0 [main] WARN fromJava.Types - The class citysearch.tools.sum.data.views.UserView 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.
and doesn't generate the right wsdl file. This problem can be solved if I replace User in the above API with UserImpl which is a trivial implementation of User. Why is it necessary for me to supply this trivial impl? Is there any way for me to get java2wsdl to treat these interfaces as simple beans? Can I specify a mapping from an interface to a concrete class to disambiguate wsdl generation?
I think that a java interface is isomorphic to any xml schema type and should be presentable as an xsd complex type.
Thanks everybody! Josh
