on 9/11/2000 1:13 PM, "Diethelm Guallar, Gonzalo"
<[EMAIL PROTECTED]> wrote:
> Ok, for one thing, I would like to put configuration information
> in a separate .properties file, and not have to touch Turbine's.
Just put this in the file:
include=/path/to/properties/file.txt
> Also, I guess it could become important at some point to show
> a "corporate" face by providing a corporate servlet as the entry
> point to the app architecture... We would still be telling our
> customers we use Turbine, and we would still give them the full
> source code for Turbine, of course, but they might feel more
> comfortable thinking they are using a "company-supported" servlet
> as the basis for their app (not that this means much in reality,
> but I've seen corporate minds working this way...)
Huh? You want a different URL? that is easily accomplished without having to
subclass turbine.
Again, both of these are solutions that work perfectly well without having
to modify Turbine.java or subclass it. My point here is that you should not
think that the first way out is sublcassing Turbine.java.
thanks,
-jon
--
http://scarab.tigris.org/ | http://noodle.tigris.org/
http://java.apache.org/ | http://java.apache.org/turbine/
http://www.working-dogs.com/ | http://jakarta.apache.org/velocity/
http://www.collab.net/ | http://www.sourcexchange.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
