Jetspeed Best Practices

[Ramiro Rinaudo <rr...@ciudad.com.ar>]

I'm making a multiple application portal using jetspeed 1.4b3. I wonder wich is the best way to do some things in terms of design.

1- basic portlet that get data from a database. 
    I don't care about  how the connection is made or using a JDO such as castor or hibernate. Instead I'm worry about what my Action shoud do. The way it should be done in Jetspeed. 
    This is what I do: Get the data from the database, put the object created into a velocity context, and then use the         HttpSession to maintain the object, so further requests, don't access the database. I'm putting the object into session, since Portlets context is not maintained between request, and it's not shared among multiple Portlets in the same page. Is this a good approach? any suggestions.

2- Multiple Application portal.
    I need to create multiple apps into one portal, every app uses lots of portlets, and pages or panes. This apps are completely different, and different users will access them. So I must create at least one role for each app. Wich is the best approach? Create one page with mulples panes for each app, one page for all apps, or multiples pages for one app? Then... How the links between pages or panes should be done? How Jetspeed manages to grant or not access to a portlet or page? How new users get their psml copies based on their roles?

3- Extending Jetspeed users.
    I've extended succesfully jetspeed users, using MySql as database. Where should I make the user to add the new data. Change Jetspeed New User code. Change Jetspeed Edit user code, or create a new portlet to do it?

4- any other example.
    Any Idea that is in your mind. That things should be done.

Thanks for answer.....

Ramiro Rinaudo