Probably close to none. In a rare case that you might have to move the location of
the program or point to a different version of the program you have just one place
to change: classpath instead two.
But it's almost an insignificant detail. Do you see an advantage in using init
param? (Don't reply if no in which case we'll agree that both methods are ok)
d.
"Christopher K. St. John" wrote:
> David Mossakowski wrote:
> >
> > with this setup you can load the property file by calling
> > bundle = ResourceBundle.getBundle("cookieprogram");
> > because the ResourceBundle will search the classpath for that bundle
> >
> > After you do this you can put the path of the files you need to write into the
> > properties file along with other properties you might need.
> >
>
> What's the advantage of this over just setting the path
> as an init parameter?
>
> -cks
>
> ___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
--
David Mossakowski [EMAIL PROTECTED]
Programmer 212.310.7275
Instinet Corporation
"I don't sit idly by, I'm planning a big surprise"
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
