Jon Stevens wrote:
>
> on 9/13/2000 9:40 AM, "Rafal Krzewski" <[EMAIL PROTECTED]> wrote:
>
> > OK, I took some time and read Servlets 2.2 spec. You can define some
> > 'application
> > environment' items that your application is expecting to find in the
> > appserver's
> > naming service. You can provide the entry name name, expected type (String,int
> > etc.)
> > and optional default value.
> > This is the proper way of dealing with deployment time settings. Nice, but we
> > would
> > have to depend on naming service being available. How does this sound like?
> > Are
> > there free (APL) implementations of naming servers that we could start
> > alongside
> > with Tomcat to emulate industry-grade application server? Or maybe I'm going
> > in
> > the worong direction? Tell me what you think.
> gag. sounds like it is overkill like most of the rest of the crap that went
> into 2.2. :-(
I guess so... But having db properties inside an compressed war makes little
sense either. We must decide if we go with editable properties file, or try
to be standard compliant.
Maybe we should give JNDI settings precedence over config file properties.
This would probably work in boths scenarios. What do you think?
> > Oh, there is a directory where a webapp is waranteed to have write rights. It
> > can be determined with:
> > File tempDir =
> > (File)servletContext.getAttribute("javax.servlets.context.tempdir");
> > (works under Tomcat)
> > I think it may prove useful.
>
> We can't be servlet engine dependent. I guess you could try to get that
> directory and then if you can't, report an error making people do manual
> configuration steps.
I got the property name form the standard, and tested with Tomcat. We could
try using this, as it's quite convinient.
Rafal
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
