Hello Joshua,
Sorry, I never used the ant task nor the skeletons.
I did not see the need for a skeleton, and since they are not generated
by default, I suspect few people use them, meaning more unfixed bugs and
no help in the mailing list. I think you experienced the latter :)
The Wsdl2Java command has an option to specify the impl class name. I
suppose you checked the ant task and it did not have it..
-c, --implementationClassName <argument>
custom name of web service implementation
Regards,
Dies
[EMAIL PROTECTED] wrote:
Dies,
Again, thanks for the reply. I am running the *axis-java2wsdl *ant task
followed by the* axis-wsdl2java *ant task to generate my wsdd file. When I set
bindingname="JaxRpcMyService" in the axis-java2wsdl ant task, the wsdl:binding
appears correctly in the wsdl file ("JaxRpcMyService"). When I run the
axis-wsdl2java task and skeletondeploy="true" it applies a "Skeleton" suffix to
this name. Running the same task with skeletondeploy="false" it applies a
"Impl" suffix to this name. Whats the difference? Is there a way to avoid
adding a suffix all together?
Regards,
Joshua
*Dies Koper <[EMAIL PROTECTED]>*
05/08/2006 08:03 PM
Please respond to axis-user
To: axis-user@ws.apache.org
cc:
Subject: Re: Can you specify your own implementation class when
using the axis-wsdl2java ant task?
Hello Joshua,
The generated file name for the implementation class in the WSDD is
generated from the binding name in your WSDL:
<wsdl:binding name="YourSoapBinding" type="impl:YourPortType">
->
generated impl class name: YourSoapBindingImpl
If you can accept an implementation class name ending with "Impl",
change the binding name.
Regards,
Dies
[EMAIL PROTECTED] wrote:
> I use the axis-java2wsdl ant task to generate the wsdl file and then use the
> axis-wsdl2java class to generate the wsdd file. Is there a way to specify
the
> service implementation class when using the axis-wsdl2java ant task? I would
> prefer not to have to change the wsdd file after I generate it.
>
> Regards,
>
> Joshua
