Are you saying that while WSDL2Java itself is still being debugged/improved you want it to generate new files every time? I can understand that argument, but I think that once the tool stabilizes, it should only generate new files if the WSDL has changed since the last time it generated the files.
> -----Original Message-----
> From: Russell Butek [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 07, 2002 7:38 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Revamped WSDL2Java framework
>
>
> I don't think your notion of dependency checking in the
> WSDL2Java task is a
> good idea. The builds are used in development. WSDL2Java is
> one of the
> things we're developing. When we're mucking with WSDL2Java,
> we WANT the
> generated stuff to be regenerated every time. It would be a
> nuisance to do
> 'ant clean' just so we make sure we generate fresh bindings.
> Now if we had
> something like 'ant cleanBindings' that ONLY removed the
> generated stuff,
> then I'd be OK with your suggestion.
>
> "Steve Loughran" <[EMAIL PROTECTED]> on 05/06/2002 06:51:17 PM
>
> To: <[EMAIL PROTECTED]>
> cc:
> Subject: Re: Revamped WSDL2Java framework
>
> I'd also like some form of dependency checking in the
> task...if the date of
> the generated files is later than that of the source file,
> you shouldnt
> generate the output files. It is hard to add this ina build
> file outside of
> the task, as it is only when you parse the WSDL that you know what the
> names
> of the classes will be
***********************************************************************************
WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
************************************************************************************
