> Ok, for one thing, I would like to put configuration information
> in a separate .properties file, and not have to touch Turbine's.
I think the 'include' directive in the TR.properties will read the
properties from another file. This way you could read all your business
properties from a seperate file, and not muck up the TR.properties.
> 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...)
Unless they are looking at code, they wouldn't see anything. You wouldn't
be changing any behavior of the servlet, just the name? mod_rewrite...
jb
------------------------------------------------------------------------
This message has been scanned for viruses with Trend Micro's Interscan VirusWall.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
