Re: Navigation in a Portal

[Scott O'Bryan]

Very true Kito.  If it has a predictable format then you're golden.  One 
interesting thing if you are using this approach with 286 is that there 
are portlet filters which give you access to (and allow you to wrap) the 
various PortletRequest/response objects.  Might help a bit as well.  :)

Kito D. Mann wrote:
Sandy,
I agree with Scott here that this is most likely going to have to be
specific to your portal server. I've done something similar with eXo, and
basically I have taken the filter approach (largely because I want more
control over the URL structure than eXo gives me by default). However, if I
didn't care about the format of the URL, I would just see if WebLogic Portal
has a specific URL syntax that maps to specific desktops. So, for example,
if one desktop is called Phase1, perhaps the WebLogic URL might be
http://localhost/portal/user/desktops/Phase1. If there's a specific mapping,
it should be easy enough to output a direct link to that page through your
portlet. In the past, I have found converters useful for this.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kito D. Mann - Author, JavaServer Faces in Action
http://www.virtua.com - JSF/Java EE consulting, training, and mentoring
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info

  
-----Original Message-----
From: Scott O'Bryan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 22, 2008 1:45 PM
To: MyFaces Discussion
Subject: Re: Navigation in a Portal

The "filter" may not work either because the url's are not guaranteed
to
actually CARRY your parameters as payload.  They may be stored
internally to the portal and only a token (to represent all the
parameters) saved on the url.  I'm not sure how the weblogic portal
does it.

What you are trying to do needs to be container specific and you need
to
be able to generate a URL that refers to the workspace your trying to
reference.

One thing you may want to look at that's coming with JSR-286 is
eventing.  The reason I suggest you look at this is that, to a large
extent, your current architecture is contrary to what is being defined
in 286, yet the 286 processes may well let you accomplish your ultimate
goal.

Scott

MC PHERSON Sandy wrote:
    
Hi I have a small problem which I'm trying to figure out the best
solution to.

We have a portal (Weblogic 10) which has different desktops (portal
files) for different operational phases, as the available content
differs greatly from phase to phase. The majority of our portlets are
JSF portlets.

In the header of each portal desktop there is a JSF portlet which can
      
be
    
used to select the date to be shown and therefore the phase and
      
desktop
    
to be shown. I have a method on a managed bean which can identify
      
which
    
desktop has to be shown, but using this within the JSF context to
navigate to a different portal desktop is not going to work.

The problem is how do I forward to the new desktop from within the
portlet which is in the action part of its JSF life cycle? I can't
      
use
    
the standard JSF navigation as this would only apply to the contents
      
of
    
the portlet and not of the portal as a whole.

I have a nasty feeling I will have to put a filter in and check the
selected date before I display the desktop. This will mean rooting
around in the URL which is sent when the form containing the date
selection is submitted.

Before I do this I was just wondering if anyone else had a more
      
elegant
    
solution.

Thanks
Sandy
____

This message and any files transmitted with it are legally privileged
      
and intended for the sole use of the individual(s) or entity to whom
they are addressed. If you are not the intended recipient, please
notify the sender by reply and delete the message and any attachments
from your system. Any unauthorised use or disclosure of the content of
this message is strictly prohibited and may be unlawful.
    
Nothing in this e-mail message amounts to a contractual or legal
      
commitment on the part of EUROCONTROL, unless it is confirmed by
appropriately signed hard copy.
    
Any views expressed in this message are those of the sender.