Here are some snippets from previous postings that may be of help (I
think b is what you want):
[snip from Ate Douma]
To summarize: Jetspeed currently provides three implementations for
encoding and storing portletwindow
state and parameters:
a) fully encoded on the url (like for instance Pluto does):
use class org.apache.jetspeed.container.state.impl.PathNavigationalState
b) only portletwindow state (window state and portlet mode) are saved
in the session, parameters
are encoded on the url:
use class org.apache.jetspeed.container.state.impl.SessionNavigationalState
c) state and parameters are saved in the session (the default):
use class
org.apache.jetspeed.container.state.impl.SessionFullNavigationalState
[snip from David Sean Taylor]
See portal-url-generation.xml.
<!-- Navigation state we are currently using -->
<bean id="NavigationalState"
class="org.apache.jetspeed.container.state.impl.SessionFullNavigationalState"
singleton="false"
>
<constructor-arg><ref
bean="NavigationalStateCodec"/></constructor-arg>
</bean>
If you don't want to make render parameters stateful, use
SessionNavigationalState instead:
<!-- Navigation state we are currently using -->
<bean id="NavigationalState"
class="org.apache.jetspeed.container.state.impl.SessionNavigationalState"
singleton="false"
>
<constructor-arg><ref
bean="NavigationalStateCodec"/></constructor-arg>
</bean>
IF you want to store navigational state in the URL, change your spring
configuration to:
<!-- Navigation state we are currently using -->
<bean id="NavigationalState"
class="org.apache.jetspeed.container.state.impl.PathNavigationalState"
singleton="false"
>
<constructor-arg><ref
bean="NavigationalStateCodec"/></constructor-arg>
</bean>
finally, another Nav state impl available:
PortletWindowRequestNavigationalState which also stores state in the
server side and allows for optionally render parameters when
synchronizes state
/**
* true if for a targeted PortletWindow using StateFullParameters
the saved (in the session) render parameters
* must be cleared when synchronizing the states.
* Prevents the default behavior when using StateFullParameters to
copy the parameters from the session
* when no parameters are specified in the PortletURL.
* Used if for the targeted PortletWindow no render parameters are
specified.
*/
private boolean clearParameters;
public void setClearParameters(boolean ignoreParameters)
{
this.clearParameters = ignoreParameters;
}
On 8/13/06, Prashant <[EMAIL PROTECTED]> wrote:
Hello,
My requirement is as follows.
There are say 3 portlets on A.psml . and on clicking some link in any of
three portlet page redirected to B.psml. Now when i return from B.psml
to A.psml , normally all the portlets on A.psml will display as they
were when page was redirected to B.psml(as request parmaters doesnot get
cleared) .I want to intialize the portlets on A.psml ie. i want to clear
the render parameters for all portlets on A.psml when page is redirected
to from B.psml to A.psml.
Can anyone tell me how i can achieve this . In jetspeed is it possible
for a portlet to know its psml and the portlets there in that psml.
thanks and regards
prashant
--
Prashant <[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
