Ed Knutson wrote:
>
> This is pretty critical to how customized settings will be stored in the
> database.
>
> If all the parameters necessary to render any given portlet according to a
> certain user's tastes can be stored as portlet markup, then for each user, a
> fully customized version of defaultPortlets.xml can be stored. When the user
> logs in or reloads after log in:
> -the existence of an unexpired entry in the cache is checked for
> -if not, the existence of a row in the db for this user is checked for
> -if either exists, the PortletController uses it to generate the custom screen
> (otherwise, defaultPortlets.xml)
> -if a row was read from the db, it should be cached
> -any action which updates the row in the db also expires the cache entry
+1. The only problem, and this is just a general technical problem not
really Jetspeed related. Current DB absctraction/implementation APIs
don't lend themselves to using XML that well. I would love to see a way
to hide the DB persistence through an Avalon Block interface. We can
them provide this back to the API
Portlet API
|
Factory
|
Data Snap-in Framework ( Avalon )
|
| |
XML Database (OPL, Castor JDO, Expresso DB impl, etc)
> Being able to store custom settings as portlet markup would also give site
> administrators greater control over the presentation of the defaultPortlets; it
> would be more like a home page.
>
> I'm all +1.
<snip>
I really want this to happen. It would be great! :)
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
"For evil to win is for good men to do nothing."
--
--------------------------------------------------------------
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]
