Hi Richard, thanks for reply!
I think that it could be better (for example) if it should be possible to
insert the @XmlSeeAlso in the service endpoint class.
In this way when you defining the XXX Service endpoint class you can indicate
implicit classes that are involved in the service execution (and therefore need
to be described in the WSDL).
Ok, this will introduce a dependency between the endpoint and the implicit
subclass(es) but from my point of view is better than the inheritance issue...
So, for example....
| @WebService
| @XmlSeeAlso (value=Employee.class)
| public class XXXServiceEndpoint {
|
| @WebMethod
| public Person getPerson(){
| return new Employee(...);
| }
| }
So the Person class will be picked up automatically as part of method
signature, while the Employee subclass will be included by the @XmlSeeAlso
annotation.
The advantage is that the Person class is left untouched (without any
annotation)
But unfortunately things are not working in that way...
Regards,
Andrea
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197041#4197041
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197041
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
