that should work,
Thanks,
Parikh, Pratik
From: Jalenak, Jerry [mailto:[EMAIL PROTECTED] Sent: Friday, November 04, 2005 11:09 AM To: axis-user@ws.apache.org Subject: RE: WSDL2Java Question I’ve done that, and I
still get skeleton classes for all of my objects. I think what is
happening is that WSDL2Java is creating an entire package for my webservice,
when I really already have all the implementation done. What I have been
thinking now is, can I simply change the deploy.wsdd to point to my implemented
class? Or will that cause other problems? Jerry
Jalenak Software
Engineer Netopia,
Inc. From:
Parikh,Pratik [mailto:[EMAIL PROTECTED] use -S option while you
generate..... Thanks, Parikh,
Pratik From: Jalenak,
Jerry [mailto:[EMAIL PROTECTED] I have a complete set of Java
classes that I am exposing through Axis 1.3. Is there a way, using
WSDL2Java, to only generate the binding classes (i.e. Service, ServiceLocator,
SoapBindingImpl, SoapBindingStub, SoapBindingSkeleton), the deploy and undeploy
WSDD files, without also generating all of the other server-side skeleton code
for my existing classes? It would be nice (and convenient) if WSDL2Java
would simply ‘hook’ into my existing classes….. Thanks! Jerry
Jalenak Software
Engineer Netopia,
Inc.
|
- RE: WSDL2Java Question Parikh,Pratik
- WSDL2Java question George Papandreou