----- Original Message -----
From: Kevin A. Burton <[EMAIL PROTECTED]>
To: JetSpeed <[EMAIL PROTECTED]>
Sent: Monday, May 01, 2000 9:50 PM
Subject: Re: Debugging Jetspeed
> Julian Coombes wrote:
> >
> > I'm relatively new to jetspeed, and one of my goals is to understand how
> > everything hangs together, so that I can learn and eventually help build
the
> > thing. The problem is that when I understand something I have to
understand
> > every minute detail, and with Jetspeed
>
> Cool!
>
> > that's quite difficult for a
> > number of reasons, primarily because its still fairly embryonic, there
aren't
> > stacks of documentation, and getting it working correctly is still
something of
> > a balancing act.
>
> Well. I keep hearing that. I tried to fix things with Jetspeed 1.1
> but haven't received any feedback since then. Point out any areas that
> need to be improved so that we can fix them :)
<snip>
I've bee following Jetspeed since it was a web-based email system. I would
like to point out that with the latest release, the installation docs are
the best they have ever been. But you asked (and I got a big mouth) so here
are some documents I thought would be useful:
In my experience - i've managed to help a few Windows people (like myself)
who were too embarased to post on the list - the most difficult piece is
setting up the .properties files. The documents say "follow the directions
in the .properties files" (or something like that), but these are hard to
understand if you do not know what they do, and are intimidating. I was
quickly overwhelmed by the number of options in these files; I got lost
among terms like portlet, portletControl, PortletController... But it turns
out that I only had to change about 3 lines in each property file to get the
system running! A little summary on setting up these files would sure help.
(I've seen most answers are in the FAQ-O-MATIC, but when there is a
different FAQ link on the Jetspeed web pages, who realizes there is a better
one available?)
I also believe that Jetspeed seekers are also hindered by a lack of
documentation from the Tomcat team. I admit I have not looked in a while,
but I have not seen a "here's what all these config files do, and here is
how you set them up". Adding the web.xml snippet was one of the best
additions to the installation documents.
Also, there is no documentation that I could find on setting up the
database. While the web pages say you can use a database, there is no
mention as to what features are added by using one.
Another missing piece of documentation - and the one I am currently trying
to piece out of the mailing lists - is how do I add my own .RSS file to the
mix. I understand .XML/XSL/Cocoon/RSS/... files, but I don't see how they
all link together? Is there a "main" xml which calls the other XML's?
And how about "user" documents? Supposing I have the system setup and ready
to go, there is no online help to tell users how they can login, design a
home page, etc. I know, you can't create user documents until the logic and
design are settled, I only mention it so it gets on the list somewhere. :)
I think much confusion is that not only is Jetspeed quickly changing and
growing, but so are the many .jar files used in its libraries. Then they
change Tomcat's directy structure on me, and...argh...d%*@...rassafrassan...
:b
Just kidding! Actually, it is this "challenge" that I enjoy. And the mailing
list is almost as enjoyable as my morning, radio talk-show. (Yeah, my wife
says I need to get a life, too) But I must admit that sometimes it gets
frustrating when everyone is talking about something added in CVS, and I
cannot get things to compile. And once it does compile, there's no doc on
how to use/see the new feature. But such is life on the bleeding edge. Like
they say, "If you can't take the heat, get out of the CVS!" (well, they
should say it ;) )
Thanks for tollerating this ranting. Keep up the great work!
Steve B.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
