*Disclaimer* I am very much a Turbine newbie (trying to rectify that)
Many moons ago I developed a set of classes to make it extremely
easy to add a "telnet" based administration interface for admistering
a server (i.e., you telnet into the server, authenticate yourself, and
begin performing configuration commands on the server). We have
developed 6 java servers that utilize this interface for their
configuration tasks and it works like a champ.
To make things a little friendlier (for some reason Windows users
don't seem to like command line interfaces...go figure), I am
currently on a mission to replace this "telnet" framework with
an embedded web based interface, and I have the following
requirements that I would like to try to meet.
1. Light weight (memory)
2. Easy to implement (simple security framework, simple to slap
together commands ("actions") and screens)
3. No external configuration files required
4. Minimal external file requirements (understandible log files
may need to be generated).
JSP wasn't an option becase of #3, so that led to Velocity. Velocity's
documentation lead me to Turbine, which I am currently looking at to
leverage the security framework and screen management facilities. I
am planning on using Jetty for the servlet container as it is easily
embedded (and can be programmatically configured without the
need for a webapps directory).
Does anyone out there have an example of using Turbine in this
fashion?
Currently my thoughts (haven't started implementing yet as I would
like some feedback on the feasibility):
o Create my own SecurityService that will be either programmatically
configured (or, optionally, be configured via a properties file).
o Load a standard properties file that is bundled with my server's
jar file using a class loader. This class file will configure
VelocityService to use classpath resource loader before the
file loader, and to use my security service.
o Configure Turbine using TurbineConfig and the properties that I
loaded above.
o Instantiate a Jetty server object, and progromatically configure
a servlet handler that will manage the Turbine servlet. The
base directory will be configured with the location where error
logs will go....all other resources should be managed by the
Velocity classpath resource loader.
o Start the jetty server.
In the end, I hope to have *all* content served from the .jar file that
my server is contained in and the only external file required be the
log file.
Does this look like it will work (e.g. will TurbineConfig and the
Turbine servlet work together?)? Any better ideas or suggestions?
Any examples?
Sorry for the length of this message!
Thanks,
-scott
--
Scott C. Gray <[EMAIL PROTECTED]>|Quidquid latine dictum sit, altum videtur.
Senior Engineer, MWS |Whatever is said in Latin sounds profound.
(O) 856-914-5212 (F) 856-608-7970| -Unknown
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
