So I now have JSP using Turbine as a user authentication like we talked
about.
There is one problem. TurbineResources.properties.
Turbine.java sets this as an init parameter during (init).
Anything that circumvents this servlet will break. There are a couple
ways around this.
1. Define this for the JSP Servlet:
- doesn't work for non Servlet applications: Swing, console, etc.
- will conflict with any other object that needs a "properties" param
- doesn't play well with Jakarta/Servlet 2.2. Each servlet zone has to
define init params. WAR's really shouldn't *have* to be
messed with
2. Have the default be {java.home}/TurbineResources.properties with
this value overriden in Turbine.java.
- works for all applications from Servlets, to Swing, console, etc.
- won't conflict with a JSP that needs "properties"
- works for all WARS.
- Works across servlet zones
There are some problems with this. You wouldn't be able to provide
multiple TurbineResources.properties. I am not sure if there is a
decent way around this. If someone *really* wants it we could provide a
custom property that would be specific per VM.
Thoughts?
--
Kevin A Burton
Senior Software Engineer
Kendara Inc
http://www.kendara.com
Mobile: 408-910-6145
Linux - You *will* be assimilated.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
