IMO, it seems like a bad idea to me to tie your bean
code to a servlet context unless you REALLY need to.
To me, a better way would be to put the file in a
directory under classes, and use the classloader of
the current thread to get to the file.
This way, you do not need servlet.jar to use your bean
if you every decide to use it outside of a servlet.
This is a very simple process. Here is an example:
private InputStream getFile(String name){
return Thread.
currentThread().
getContextClassLoader().
getResourceAsStream(name);
}
To read a properties file classes/myprops.properties
for instance, you just do this:
Properties p = new Properties();
p.load(getFile("myprops.properties"));
Larry
>>> [EMAIL PROTECTED] 08/14/02 08:42 AM >>>
It will work in a bean if you pass a reference
to the servlet context to it...
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
