On Sun, 26 Nov 2000, Raphael Luta wrote:
> Jon Stevens wrote:
> >
> > on 11/25/2000 2:44 PM, "Raphael Luta" <[EMAIL PROTECTED]>
> > wrote:
> >
> > > Issue:
> > > ======
> > > I'm currently tryng to package Jetspeed as a distributable WAR file
> > > with a complete set of functionalities (most notably an embedded
> > > Hypersonic DBMS).
> >
> > Uh. Why are you not using the TDK as your basis? You really should be using
> > that.
> >
>
> Never found the time to download it and move jetspeed on a TDK base :(
> It's in my TODO list...
I would be happy to work with you on this! All I've been working
on lately is the TDK in preparation for making a new version
of the sandbox for Scarab. Torque is now fully integrated: every
last bit of SQL required by Turbine is automatically generated
by Torque, the target database is created, and the SQL is inserted.
All the Peers for your project (as defined in an XML schema) are
auto generated and compiled.
> >
> > If you do this based on TOMCAT_HOME or some other variable to the webapp
> > directory it isn't an issue because you can use Ant to do the substitutions
> > for you during new application creation time in the TDK. We could add
> > something like this to the TDK very easily if it doesn't already exist.
> >
>
> Ant substitution occurs at building time so it's only useful if you
> deploy on the same computer that you build on (you have to build as many
> times as there are different target architectures).
> TOMCAT_HOME is not a good solution either because:
> - it's only used in 1 possible servlet container
> - there's no fixed relation between TOMCAT_HOME and the webapps deployment
> directory.
> My goal is to be able to distribute a "binary" fully-built WAR of Jetspeed
> off the web site, which can be dropped in any servlet 2.2 container and tried
> out without any configuration tweaking. No more installation questions ! :)
> I think it's something that can be of interest for most other Turbine based
> project (Jyve, etc...)
I will get rid of every last hard-wired path, so deploying TDK apps
will be seemless. I am almost there, the TDK will produce apps that
can be dropped in any contain on any path. I am in full agreement
with you that any changes that are required in Turbine to make this
happen are ultimately required to make deployment simple.
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 would like to make deploying turbine apps dead simple
to deploy! For me the TDK is about easy development and
easy deployment. I'm not far from this being a reality and
I would love to see Jyve and Jetspeed use the TDK.
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
