You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Swavek Skret <sw...@appliedbroadband.com> on 2007/06/15 17:15:07 UTC

wsdl2java.bat code generation rules

When wsdl2java.bat runs it does not always override all of the generated
java classes. What are the rules and practices when generating the code?

Thanks,

Swavek




---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: wsdl2java.bat code generation rules

Posted by Glen Mazza <gr...@verizon.net>.
I don't believe they are documented. But when you run the Ant task
instead of command-line, at least, you will get a list of files that
were *not* updated:

http://ws.apache.org/axis2/tools/1_2/CodegenToolReference.html

Note this is to protect people who have already placed complex business
logic in the client stubs and server skeletons from accidental erasure.

If you switch to the Ant task, you can have a "depends" attribute that
first deletes and then recreates the output directories prior to
regenerating the code, which would accomplish what you want here.

Glen

Am Freitag, den 15.06.2007, 09:15 -0600 schrieb Swavek Skret:
> When wsdl2java.bat runs it does not always override all of the generated
> java classes. What are the rules and practices when generating the code?
> 
> Thanks,
> 
> Swavek
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org