I'm still struggling to find a solution for interactive portlets,
specifically using xsl (CocoonPortlet would be great, but it seems dead?).
It appears that Velocity does work pretty well (e.g. the User Browser is
a very nice example). However, I'm looking for a solution that would use
XSL. Velocity requires access to objects in the .vm files. There are
many times I don't even have objects, just an xml data file. The data can
be very complex and it would be a bit too much work (I admit I'm lazy) to
try and objectize it. XSL works great in these situations.
For example: I'm trying to build an interactive bulletin board. The data
is stored in a single xml file. I want to give certain users an admin
type role to go in and edit the xml file. I created on XSLPortlet entry
that simply displays the data (e.g displayBulletinBoard.xsl), and another
that creates a form (e.g. editBulletinBoard.xsl).
This works fine accept once I create a form I have no way to submit it
anywhere (do I?). In Cocoon I submit it to a producer, and then I'm able
to strip out the data I need, do any processing, and submit a new document
to the browser. It seems VelocityPortlet is the only Portlet setup to do
this.
It would be great if the XSLPortlet could work more like a servlet and
accept request objects.
Has anyone figured this one out? Any help is greatly appreciated.
-Jim
Vinay Peddapuram <[EMAIL PROTECTED]>
10/17/01 02:11 PM
Please respond to jetspeed-user
To: [EMAIL PROTECTED]
cc:
Subject: Re: Writing Portlets that support "User Preferences"
When is new portlet api is due to come out? Is it gona be the same lines
of IBM
webspear portal Server API ?
thanks
Vinay
David Sean Taylor wrote:
> > Take the simple example of the Stock Quote Portlet. I would
> > like for a
>
> Im working on now that now, hopefully I can get it checked in by the end
of
> the week.
> Had a minor setback, decided to use Torque + Cloudscape in my web
service
> implementation to store preferences in the web service.
> Its mostly worked out, except for inserts still don't work. If anyone
has
> experience writing Torque db impls I'd appreciate a little help...
>
> > Similar examples would include MyFavoriteWebLinks or
>
> I wrote a bookmark portlet a while back for a client, still need to
decouple
> it from their specific code.
> Don't want to bother with it until the new portlet api comes out (its
going
> to be the old portlet api at this rate ;-)
>
> > 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?
>
> Usually you have to write specific portlet customizers for specific
> portlets, although you can choose to inherit the default.
>
> JetspeedPersistenceService stores back to the PSML file.
> In the case of the StockQuotePortlet, I chose to store everything back
to
> the web 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
