> Should I be
> using the Jetspeed Persistence Service? Would this be a
look at the HelloVelocityPortlet as an example
For any portlet, setAttribute() method stores an attribute as a param to the
psml
see HelloAction.doUpdate():
portlet.setAttribute("text",text,data);
the setAttribute method on AbstractPortlet is calling the persistence
service
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 16, 2001 3:39 PM
> To: [EMAIL PROTECTED]
> Subject: Writing Portlets that support "User Preferences"
>
>
> I have been searching through the documentation and mailing
> lists and I
> can't seem to figure out how to do a portlet that a user can
> customize. I
> apologize for the soft question but here goes....
>
> Take the simple example of the Stock Quote Portlet. I would
> like for a
> user to click on an edit button, get a new window either inside the
> portlet window or a new window, allow the user to type in
> (validate) a
> stock ticker, and return to the portal window with the updated ticker
> list. This customization information would be saved in a
> file or in a
> database and pulled the next time the user logs in.
>
> Similar examples would include MyFavoriteWebLinks or
> MyCustomerOrders,
> etc.
>
> Do each of these require that a custom portlet be written?
> Should I be
> using the Jetspeed Persistence Service? Would this be a
> candidate for
> Velocity?
>
> We currently use ejbs, coccon, xml/xsl in our current
> architecture. I
> considered the XSLPortlet but that only uses a single xml/xsl
> combination,
> and the CocoonPortlet is not yet ready.
>
> I am currently thinking that I need to write a custom portlets with a
> small database schema to store some of this metadata.
>
> Any recommendations are welcome!
>
> Thanks.
> Jim Hughes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
