setDestinationFile imho is the implementation detail and filename is
more informative because the user finds it in the docs easily.

Ara.

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:xdoclet-devel-
> [EMAIL PROTECTED]] On Behalf Of Andrew Stevens
> Sent: Friday, June 21, 2002 3:03 AM
> To: [EMAIL PROTECTED]
> Subject: [Xdoclet-devel] <jsptaglib filename="foobar.xml"/>
> 
> From JspTaglibSubTask.java:
> 
>     public JspTaglibSubTask()
>     {
>         setTemplateURL(getClass().getResource(DEFAULT_TEMPLATE_FILE));
>         setDestinationFile(filename);
> ...
> 
>     /**
>      * Sets the Filename attribute of the JspTaglibSubTask object
>      *
>      * @param new_filename  The new Filename value
>      */
>     public void setFilename(String new_filename)
>     {
>         filename = new_filename;
>         setDestinationFile(filename);
>     }
> 
> Why do we have a separate 'filename' parameter for this subtask?  It
seems
> to me it just passes everything straight through to the
destinationFile
> parameter, so gives us nothing except an alternative name for the same
> parameter...  Is there some particular reason for it, or can I
> remove/deprecate it in favour of using destinationFile directly?
> 
> 
> Andrew.
> 
> 
> -------------------------------------------------------
> Sponsored by:
> ThinkGeek at http://www.ThinkGeek.com/
> _______________________________________________
> Xdoclet-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-devel



-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to