On Jun 24, 2004, at 7:22 AM, Oliver Pfau wrote:
Hi,
I have a general JSR-168 question:
is it possible to share a attribute between two portlets which are not in
the same portlet application in a JSR-168 portlet ?
The portlet session, application scope, but its limited to per portlet application
-- or --
PLT 11.1.1:
The portlet-container must not propagate parameters received in an action request to subsequent render requests of the portlet.
If a portlet wants to do that, it can use Render URLs or must use the setRenderParameter or setRenderParameters method of the ActionResponse
object within the processAction call.
The second approach is limited to strings
I want to write two portlets:
one displays the TreeNode data structure from javax.swing.tree.* and
stores a navigation status (String) in the context (with the application
context it should work), the other portlet retrieves the navigation status
and shows the chosen contents.
This sounds interesting. Is it an HTML-based tree view? With JavaScript?
I am looking for something like this to use in the Jetspeed Portlet Application Manager portlets
Problem: I plan a generic navigation portlet which can switch its TreeNode
content in run time. I mean one navigation portlet for many content
portlets. I don't found a way to realize this communication. I think I
have to pack the navigation portlet with each content portlet together as
portlet application....I am not very happy with this solution....any ideas
?
I think the render parameters could work
You could also write a jetspeed service to share common data (see the PAM portlet application for an example of accessing the Registry Service)
-- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
