The user community is trying to fix up the documentation but we are very early into the process.

There is a wiki where we are trying to get an outline of what we all would have liked to have when we started.
http://wiki.apache.org/portals/Jetspeed2
It is an old unused wiki and I have started to clean out some of the old stuff.
I have asked Hippo(Jetspeed developers) to update the roadmap on the wiki.

If you have some suggestions about what you think we should create, please let the group know.

I have some ideas about how the documentation should be organized to allow different types of users to get the information that they need. A person who is trying to run jetspeed "out of the box" with no customization(evaluator for example) needs different information than a developer who needs to modify the way that users login which is different from the info required by someone who is going to build custom portlets

I would like some discussion about this approach to see if we can build a modular documentation set that will give us as much of a custom view of the documentation as possible while minimizing the number of overlapping documents.

We also need some high level documentation that can help evaluators to understand what they are getting with Jetspeed, the underlying architecture and when this the right way to go.


Ron


Stefano Bianchi wrote:
Hi all,
fine to hear you made it (at least start it), as I tried unsuccesfully to do the same... no way to make it work on MySQL backend. I used J1.X for several projects, but the time I am spending to evaluate J2 is definitively too high... My sincere congratulations to the developer team, nevertheless consider it might be hard for "dummy" interested parties to start using J2.
My two cents, just a comment.
Be well,
Stefano

----- Original Message ----- From: "rache" <rachehernan...@yahoo.com>
To: <jetspeed-user@portals.apache.org>
Sent: Friday, May 08, 2009 10:55 AM
Subject: Jetspeed2 Installation



Hi,

I'm new to portals and I was able to install Jetspeed2 using the demo
installer jar.
I used Oracle XE as the database. The portal was fine except for some
portlets that are not working.

I have a couple of questions though.
I wanted to create my own portal following the JetExpress tutorial.
However, even if I use a different database for the 2nd portal i get an
exception
on my container name not being unique; jetspeed - actionvalve bean can't be
created due to this.
Even if I changed the name in the mvn command to use jetexpress, I wonder
why its throwing this.

So I just installed a fresh Tomcat instance and used mysql as the 2nd
database.
Custom portal was deployed but I can't login using any of the credentials
that comes along.
Its sayign that the DefaultLoginModule class can not be found.

I checked the tomcat lib folder and it has the security jar.

Any help will be greatly appreciated.

Thanks,
Rache
--
View this message in context: http://www.nabble.com/Jetspeed2-Installation-tp23442409p23442409.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org








---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org

Reply via email to