Hi Glen,
Excellent catch!
The reason tools ignore the service class implement the java.rmi.Remote
is that we don't support it in the runtime.
And the reason that we throw exceptions, is that in other project
(especially the Eclipse STP) would like to catch such exception.
I know in tools we should have a concept of warnings and errors, but
that will be another story.
James
Am Mittwoch, den 27.06.2007, 09:57 +0000 schrieb [EMAIL PROTECTED]:
Author: mmao
Date: Wed Jun 27 02:57:53 2007
New Revision: 551110
URL: http://svn.apache.org/viewvc?view=rev&rev=551110
Log:
Java2Wsdl validate the service class before generating the artifacts
* In jaxws case, it will fail if the srevice class extends/implement from the
java.rmi.Remote
I wonder if a warning "this interface is ignored by JAXWS" instead of an
exception would be preferable. While I understand the java.rmi.Remote
interface is not used by JAXWS, I'm unsure why forbidding it is
necessary (or even encouraged by the spec), it's just a marker interface
that is ignored in JAXWS. That service class might also be implementing
15 other things that CXF will ignore--why worry about java.rmi.Remote in
particular?
- throw new ToolException("Can not find the ServiceBulider
for style: " + s, e);
+ throw new ToolException("Can not find or initialize the ServiceBulider
for style: " + s
+ + " Reason: \n" + e.getMessage(),
+ e);
"ServiceBuilder"
Glen
