Found a solution, but I'm not sure if it is optimal.
Take a look at:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056482#4056482
Near the end of the first code sample, the author has placed a dummy method
in the
code, solely to publish (expose) a subclass in the WSDL. This approach also
worked for
my implementation - the WSDL now correctly shows the subclass extending the
base class
via the XML extension base mechanism. Testing with the client works fine; I
can use
the "instanceof" operator to determine the type.
This makes we wonder whether or not the annotation processor implementation
should
be smart enough to find the @XmlType annotated subclass, rather than rely on
adding
a method to the service implementation POJO.
--
View this message in context:
http://www.nabble.com/JAXWS-inheritance-in-return-type-tf4025947.html#a11437118
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
