-----Original Message-----
From: Santiago Urrizola [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 21, 2005 03:07 PM
To: Jetspeed Users List
Subject: Re: Clearing render parameters?
> This may be another one.
> There can be many reasons why you see previous state in your links:
> - you may have encoded the menu URLs with the render parameters thus
> keeping your state
This is how my menus is painting, they not add nothing to the url
<a href="$jetspeed.getAbsoluteUrl($node.url)?init=true"
title="$node.getTitle($preferedLocale)">
• $node.getShortTitle($preferedLocale)
</a>
> - there may be a bug in the cache manager
I debug the struts bridges, and i see that not remove the last url of
the portlet.
> - the struts bridge may keep some state in session (I would need to
> check).
is posible, they keep the last url in the request, so when
try to render
the portlet, the render with the last url but i link the menu so its
imposible this situation.
>
> I guess what you experience is #1. You can easily check if your menu
> URLs encode the render parameters or not. Instead of using tour menu
> links, simply type your "basic" URL in the browser and see if state
> is as expected.
>
> --
> Raphaël Luta - [EMAIL PROTECTED]
> Apache Portals - Enterprise Portal in Java
> http://portals.apache.org/
>
> Santiago Urrizola wrote:
>> Hi i use the M3 version and still happend this bug ?? its posible ??
>>
>> ----- Original Message ----- From: "Frank Villarreal"
>> <[EMAIL PROTECTED]>
>> To: "Jetspeed Users List" <[email protected]>
>> Sent: Tuesday, June 21, 2005 4:18 PM
>> Subject: RE: Clearing render parameters?
>>
>>
>>> Answered my own question. See bug JS2-231. This has been fixed in
>>> Jetspeed2 M3 I believe. Now for the painful task of updating
my site to
>>> this new version. Yikes.
>>>
>>> - Frank
>>>
>>>> -----Original Message-----
>>>> From: Frank Villarreal [mailto:[EMAIL PROTECTED]
>>>> Sent: Tuesday, June 21, 2005 02:13 PM
>>>> To: Jetspeed Users List
>>>> Subject: RE: Clearing render parameters?
>>>>
>>>>
>>>> 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:[EMAIL PROTECTED]
>>>> > 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
>>>> > ;)
>>>> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
___________________________________________________________
1GB gratis, Antivirus y Antispam
Correo Yahoo!, el mejor correo web del mundo
http://correo.yahoo.com.ar
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
