Struts bridge problem - Code fragment

[Santiago Urrizola <ch...@yahoo.com.ar>]

Hi to all, i see this fragment of code in the StrutsPorlet class of the 
struts bridge M3 Version

            String path = null;
            String pageURL = request.getParameter(StrutsPortletURL.PAGE);
            if (pageURL == null)

I think there ir the problem, becasuse when i link a psml (containing an 
struts porlet) from the menu, the variable pageURL still have data, form a 
previous call to this portlet... making that the porlet render the same 
previous context when they must have render the content for de default page, 
(ViewPage, defined in the portlet.xml)
Is this correct or is a bug ?
Is there anybody who see that ??
Thanks a lot




----- Original Message ----- 
From: "Raphaël Luta" <ra...@apache.org>
To: "Jetspeed Users List" <je...@portals.apache.org>
Sent: Tuesday, June 21, 2005 4:38 PM
Subject: Re: Clearing render parameters?


> If you access a portal by typing a straight URL and not using any
> session bound render parameters:
>  - yes, you should have a "clean" state for your portal without any
>    attached render parameters
>  - yes, there was a bug in M2 that is fixed in M3 that could cause
>    incorrect render parameters to be included.
>
> Frank Villarreal wrote:
>> Raphael,
>>
>> first off, thanks for the response.  Second, are you saying that the
>> "correct" behavior in Jetspeed2 (which is what I'm using ... M2 build)
>> should clear the render parameters if I where to for instance, navigate 
>> to
>> "http://myhost/jetspeed/portal"???  This does not happen with the M2 
>> build
>> ... the previous state (meaning the previous render parameters) are 
>> somehow
>> persisted when I try that.  Was that a bug or was that by design?  I'm 
>> now
>> confused.
>>
>> - Frank
>>
>>
>>>-----Original Message-----
>>>From: Raphaël Luta [mailto:raphael@apache.org]
>>>Sent: Thursday, June 16, 2005 04:49 AM
>>>To: Jetspeed Users List
>>>Subject: Re: Clearing render parameters?
>>>
>>>
>>>Frank Villarreal wrote:
>>> > <snip>
>>>
>>>>If you have a Menu link that reads "Home" and represents the
>>>
>>>"default" page
>>>
>>>>for portal, is it not logical that the user should be taken
>>>
>>>"back" to what
>>>
>>>>they first "saw" when they logged-in to the portal instead of
>>>
>>>the "current
>>>
>>>>state" of that default page??? Reason being: the "current
>>>
>>>state" could be
>>>
>>>>several state changes deep into a "maximized" portlet that no longer
>>>>resembles what the user first saw ... therefore they become confused and
>>>>wonder what happened to the "home" page!
>>>>
>>>>It just seems to me that the spec is lacking in this regard.
>>>
>>>Unfortunately,
>>>
>>>>I can't wait around for the spec to change (if it ever does),
>>>
>>>so I need to
>>>
>>>>customize this ASAP in order to make my site intuitive for my users.
>>>>
>>>>- Frank
>>>>
>>>
>>>First, what version of Jetspeed are you using ? There was a bug in
>>>the render parameters were handled in Jetspeed M2 that should be
>>>fixed in M3 (JS2-231). So first advice is to update the M3 or M4-dev.
>>>
>>>Second, if your portlets use URL parameters to keep their render
>>>state, as they
>>>should, simply using a default URL in the portal menu should get
>>>you where you
>>>want (ie http://myhost/myportal)
>>>
>>>Now, if your portlets also depend on session-bound parameters for
>>>your state,
>>>this is going to be trickier. AFAIK, J2 cannot access the sessions of the
>>>portlets themselves since they are in a different webapp and the
>>>Servlet API
>>>nor the Portlet API allows us to do this, so you'll need to
>>>customize J2 itself
>>>to do it.
>>>
>>>Possible strategy:
>>>- Subclass the
>>>org.apache.jetspeed.commons.JetspeedContainerServlet and modify
>>>   the doGet() to check for a CLEAR_SESSION request attribute. If
>>>this attribute
>>>   is in the request, invalidate() the current session and create
>>>it anew (or
>>>   manually clear all bound objects).
>>>   (You'll need to patch
>>>org.apache.jetspeed.tools.deploy.JetspeedWebApplicationRewriter
>>>to automatically
>>>   deploy with your new servlet and possibly manually patch the
>>>web.xml of
>>>already deployed portlet apps to use your customized container servlet)
>>>
>>>- Now, you simply need to set the CLEAR_SESSION request attribute
>>>by any mean
>>>   (like a Portal level application or any portlet) to be able to
>>>automatically
>>>   reset the sessions and thus the state of all your portlets.
>>>
>>>Let us know if this works for you and as always patches are welcome ;)
>>>
>>>--
>>>Raphaël Luta - raphael@apache.org
>>>Apache Portals - Enterprise Portal in Java
>>>http://portals.apache.org/
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
> 


	

	
		
___________________________________________________________ 
1GB gratis, Antivirus y Antispam 
Correo Yahoo!, el mejor correo web del mundo 
http://correo.yahoo.com.ar


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org