David Mossakowski wrote:
>
> 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)
>
I was thinking that servlet containers might provide
a configuration gui that would allow access to init
parameters.
Parameters stored in a custom place wouldn't be
presented, because the container wouldn't know about
them.
The move toward webapps and standardized deployment
methods makes this sort of decision somewhat more
important, but I think we would agree that the
significance of the question depends on exactly how
the servlet is intended to be deployed. A custom
servlet for local use obviously has more flexibility
than a full blown webapp designed to be deployed into
a wide variety of servlet engines.
-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
