RE: cvs commit: ws-axis/java/samples/ws-i/scm build.xml

[Ias <ia...@tmax.co.kr>]

> -----Original Message-----
> From: Glen Daniels [mailto:gdaniels@sonicsoftware.com] 
> Sent: Wednesday, March 31, 2004 11:32 PM
> To: Tom Jordahl; axis-dev@ws.apache.org
> Subject: RE: cvs commit: ws-axis/java/samples/ws-i/scm build.xml
> 
> 
> Um... why?  There's some kind of issue with all the WSDL2Java 
> and Java2WSDLing going on with this test, which Ias can go 
> take a look at when he gets a chance - it's just something 
> getting put in the wrong place, or copied multiple times.  My 
> fix just cleans everything out to avoid it.

Can we specify BindingImpl instead of generating it automatically with
WSDL2Java?
For example, supposing there's an option "b"

WSDL2Java ... -s -b
org.apache.axis.wsi.scm.manufacturer.ManufacturerSoapBindingImplA
->
      <parameter name="className"
value="org.apache.axis.wsi.scm.manufacturer.ManufacturerSoapBindingImplA"/>
in the generated deploy.wsdd

In addition, is it possible to skip generating artifacts which already exist
in a specified destination directory?
For example,

[The first time] WSDL2Java test.wsdl -o d:/test
->
A, B, C are generated
->
Update test.wsdl
->
[The second time] WSDL2Java test.wsdl -o d:/test
->
A, B, C are skipped, and D is generated.

Thanks,

Ias