>> Well, some documentation would be helpfull, and if I ddn't have my hands full
>> with other stuff I'd start ... and yes, I know I could look at Jyve and
>> see how it works ...
>
>I agree. What documentation would you like to see other than what is already
>there? The Javadocs are fairly complete. Jyve is an excellent example code
>base. The FSD (docs/fsd.html) goes over the general scope. What more would
>you like?
Well, lets put it this way. I am very busy doing clients work so I would like
perhaps a simple HOTO, or similar intorduction document on doing some
development. Yes, I could go through the javadoc's but they don't tell you
where to start, middle and end. Yes, I could go through Jyve, and
try some variations on it ...
I guess I haven't been following the development that closely, so for someone
like you who have been deep in the development cycle, of course using Turbine
is easy, of course you can get things to work ...
>> Also, I was planning to use Turbine for a client project, but since my project
>> started in October last year I couldn't reliably use Turbine ...
>
>We started a project around last October using Turbine without any major
>issues.
Funny, I'm sure you posted a message about Dash in the middle of december
that end of January was your deadline for the client project ...
>> I'm also interested in seeing a development path to a Java2 environment
>> for Turbine and also JServ, which I know you can conjole it to work
>> but I'd prefer a stable environment.
>
>What exactly does that mean ("development path to a Java2 environment")?
>Turbine runs just fine in a Java2 environment.
Well, I suppose running JSDK 2.2 might be a start. I've seen your rant about
why you don't understand why they called the environment Java2 instead
of 1.2, and judging by your response to me and others, I'm glad you're
not in customer support. Also, not using any depreciated API's (you
might not now ... again, it's a time thing for me to check)
>> But then, I hear you say, use Tomcat and Jakarta, etc for Java2 platform,
>
>Jakarta is a project. Tomcat is a servlet engine. I never said use Tomcat
>for Java2. If it helps you any, I have never personally used Tomcat at all,
>period. I still use Apache JServ 1.1.
>> well, it is also in development stage and In don't know if Turbine will
>> work with them since there are some JServ dependent features in
>> Turbine (what what I've read anyway) ...
>
>I have no clue as to what you are talking about. There is nothing in JServ
>that Turbine is directly dependent on. We have everything that may be
>dependent already copied within the Turbine CVS tree so there are no issues
>with that since the classloader will find those classes.
I can't find the messages now, but there the was some discussion and
development earlier about the use some Jserv internals and Jserv had
to be modified to meet the need, I think it was providing an enumeration
over a dataset instead of a hash ... wich I could find the message ...
Yes, I can see that the Turbine classes have their own org/apache/jserv
directory. How does this affect using another servlet engine then with
Turbine?
>Turbine will run just fine with any JSDK 2.0 or higher (including Tomcat)
>servlet engine. Period.
>
>Tomcat also is not Java2 dependent. Neither is Turbine. Both will run just
>fine in a Java2 environment. I would use Java2 only because the JVM's are
>better than Java1.
Well, I might not know everything, that is fairly evident, but at least have
some tollerance for us idiots ...
--
A room without books is like a body without a soul - somebody.
Mr Grumpy, http://www.cyber4.org/members/grumpy/index.html
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
