Raphael Luta wrote:
> > I would also like to add something to Turbine where the initialization
> > of the app can be done via a web browser. Drop the WAR file in
> > the container. When the app runs for the first time, it will
> > "know" that it's not configured. Present a form to the administrator:
> > let them pick the target database, initial passwords and whatever
> > else then create the database and all the SQL required for the
> > app to run. I can already create a database app in 5 seconds
> > using a Linux/MySQL combination and adding support for other
> > platform/database combinations should be easy.
> >
>
> I like that ! This can be implemented as by using my
> VariableTurbineResources implementation: by default, Turbine knows
> the value of a few variables (webapp root, etc...) because they're
> servlet container dependant. The resources service may gather at startup
> any referenced variable in the config file and if they are some variables
> which it doesn't know how fill, it throws an exception with the list
> of variables to fill in.
> The Turbine sevlet can then chose to intercept this exception and provide
> a form screen for the user to fill them in...
J2EE platform has a mechanism for building configuration information in
component creation/application assembly/application deployment phases
(the latter using a GUI). It's done using JNDI, and it's clean and
simple.
Too bad that there are many app servers that don't support
(Tomcat/JServ)
or don't support it fully (WebLogic - no WAR/EAR support).
Never the less, we should have TurbineResourceService based on J2EE.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
