"Kevin A. Burton" <[EMAIL PROTECTED]> wrote:
> <snip> >
> > > There has been talk about using multiple URLs for some Portlets.
> > 
> > Well maybe we should not use the url as part of the handle for cacheing
but
> > use some other method for uniqueness?  For the turbine screen portlet
we're
> > working on there is no url.  Since I am passing the screen to display in
the
> > portlet as a parameter, every instance of the portlet output is the same. 
The
> > second portlet is a cache hit since the classname/url are the same (
> > TurbineScreenPortlet/null ).
> 
> Also... Turbine screens probably won't work in the long run.  I am going
> to remove RunData from the PortletConfig so that it isn't tied to the
> Servlet Engine.  Why do you want to use Turbine screens?

Well we have Turbine-based applications that we want the first screen to be in
a portal on our users jetspeed home page.  We envision all our applications
able to be 'subscribed to' or 'customized' by the user ( layout, ordering, etc
) using jetspeed.  We started writing our web applications using turbine. 
Instead of just creating a extra portlet for each applications first screen,
we just wrote a simple generic portlet that will display any turbine screen. 


If you don't have the RunData in the PortletConfig object, I don't think it
will be a problem.  We can just create one in the portal for use by the
turbine screen.  The parameters will still be in the PortletConfig so they can
still be passed to the screen.

If interested, we were going to contribute the portlet to the jetspeed
project.  We are using it to bring in admin screens from Turbine and the first
cut admin screen from Jetspeed onto our page. Let me know and I'll post what
we have tomorrow.


Jeffrey D. Brekke
mailto:[EMAIL PROTECTED]
http://sites.netscape.net/ekkerbj/homepage


____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at 
http://webmail.netscape.com.


--
--------------------------------------------------------------
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]

Reply via email to