Done.
Josh Lucas wrote:
>
> Brett McLaughlin wrote:
> >
> > Joshua Lucas wrote:
> > >
> > > First off, let me say that Turbine is very cool and I'm glad that I finally
> > > have a 'break' at work where I can delve more deeply into it and hopefully
> > > contribute if possible.
> > >
> > > Second, I was able to get the initial splash screen using Tomcat and Turbine
> > > on Solaris 2.6. The process was quite simple which I think is great!
> > >
> > > Here is a quick blast of what I did,
> > >
> > > 1) Put all necessary Turbine jars(Turbine, ECS, JNDI, and Village) in
> > > $TOMCAT_HOME/lib.
> > > 2) Add the path to the jars to the other Tomcat classes in
> > > $TOMCAT_HOME/tomcat.sh
> > > 3) Put the TurbineResources.properties file into $TOMCAT_HOME/etc.
> > > 4) Add the following xml to $TOMCAT_HOME/webpages/WEB_INF/web.xml between
> > > the <web-app> element.
> > > <servlet>
> > > <servlet-name>Turbine</servlet-name>
> > > <servlet-class>Turbine</servlet-class>
> > > <init-param>
> > > <param-name>properties</param-name>
> > >
> > > <param-value>/path/to/tomcat/etc/TurbineResources.properties</param-value>
> > > </init-param>
> > > </servlet>
> > > 5) Restarted Tomcat
> > > 6) Tested it at http://mydomain.com/servlet/Turbine
> > >
> > > Nice and easy!
> >
> > Great. Why don't you submit a diff of the install instructions with
> > this information?
>
> Here is the diff as well as more comments. I hope I did this correct as
> I am defintely a CVS-newbie though I did read the book. :)
>
> diff -u install.txt
> Index: install.txt
> ===================================================================
> RCS file: /products/cvs/turbine/turbine/docs/install.txt,v
> retrieving revision 1.7
> diff -u -r1.7 install.txt
> --- install.txt 1999/11/04 23:13:24 1.7
> +++ install.txt 2000/01/08 08:35:36
> @@ -84,7 +84,7 @@
>
> #4. Edit TurbineResources.properties file (in the conf directory),
> define your
> database types and make sure that the database adaptor for your
> database is
> -uncommentd, and place this file in a directory accessible to your servlet
> +uncommented, and place this file in a directory accessible to your servlet
> engine.
>
> #5. Using whatever method is applicable for your servlet engine,
> specify an
> @@ -94,6 +94,35 @@
>
> servlet.Turbine.initArgs=properties=/path/to/TurbineResources.properties
>
> +-------------------------------------------------------------------------------
> +INSTALLATION WITH TOMCAT
> +-------------------------------------------------------------------------------
> +The following instructions assume that you have followed the above
> instructions for either source compilation or release distribution. It
> also assumes that you have working Tomcat installation which can be
> found at http://jakarta.apache.org.
> +
> +TOMCAT_HOME=/path/to/tomcat
> +
> +#1. Put all necessary Turbine-related jars (Turbine, ECS, Village,
> JNDI) into $TOMCAT_HOME/lib.
> +
> +#2. Add the path to the jars to the existing Tomcat CLASSPATH found in
> +$TOMCAT_HOME/tomcat.sh.
> +
> +#3. Make necessary adjustments to TurbineResources.properties and copy into
> +$TOMCAT_HOME/etc.
> +
> +#4. Add the following xml to $TOMCAT_HOME/webpages/WEB-INF/web.xml. It
> +will be a child of the <web-app> element.
> +
> +<servlet>
> + <servlet-name>Turbine</servlet-name>
> + <servlet-class>Turbine</servlet-class>
> + <init-param>
> + <param-name>properties</param-name>
> +
><param-value>/path/to/$TOMCAT_HOME/etc/TurbineResources.properties</param-value>
> +</servlet>
> +
> +#5. Restart Tomcat
> +
> +#6. Follow the instructions below for testing Turbine.
>
>
> >
> > >
> > > After all of this, I now have a question. The current architecture that I'm
> > > working with has user information in XML files as opposed to a database and
> > > authentication against a server instead of a database. I realize that the
> > > out-of-the-box Turbine does not support this but I was wondering if anyone
> > > had any suggestions as to where to start looking to modify the necessary
> > > code in order to work with this architecture.
> >
> > Are you wanting to use the XML as a data store? If so, you will want to
> > use Xerces (and possibly Xalan) to get at your data. You should look to
> > create a "warpper" for these (and if you're good ;-) any SAX compliant
> > parser/DOM compliant parser/processor) and build these to interface with
> > the current DBBroker architecture (org.apache.turbine.utils). Then it
> > can be used just like any other data store.
>
> XML would definitely be the data store and I would need 'accessor' to
> the data. That would definitely be the wrapper for Xerces that you are
> talking about. I will look closely at the current broker architecture
> and go from there. Thanks for the pointer.
>
> >
> > >
> > > Any help would be greatly appreciated.
> >
> > I'd love to - I just have about 8 other things on the list at this point
> > ;-) I can help out conceptually, I know what you need to do to make it
> > work...
>
> Only 8?!? That doesn't sound too bad. Seriously, thanks for the help
> and I will try and hash this out on the list as much as is appropiate.
> I think once it works, it could be a nice addition to Turbine.
>
> josh
>
> >
> > -Brett
> >
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
