Thanks for the response. Well the difference here is that I have the same
portlet showing up for create/update/delete. So the distinction is done in the
portlet.xml (Snippet is as below). So a menu link is associated with that page
with specific parameters. The menu is rendered within the Jetspeed scope but
the link is to a JSR168 portlet which is an external webapp. Unless I do
something like when the link is clicked I somehow pass the attribute along as
to what was clicked...then based on that the jsp can show up in the relevant
mode. WELL THE BIG QUESTION IS WHERE CAN I SET THIS ATTRIBUTE? What you said is
more in the JSR168 session context Right? Do let me know if there is any
additional information that is needed? And thanks once again for the response.
Regards,
Archana
portlet.xml snippet is as follows:
<portlet id="omx_sp_create">
<portlet-name>omx_sp_create</portlet-name>
<portlet-class>org.apache.portals.bridges.struts.StrutsPortlet</portlet-class>
<init-param>
<name>ServletContextProvider</name>
<value>org.apache.jetspeed.portlet.ServletContextProviderImpl</value>
</init-param>
<init-param>
<name>ViewPage</name>
<value>/switch.do?prefix=&page=/showServiceProvider.do?INTV_weboam_mode=Create&helpid=communicator3</value>
</init-param>
<expiration-cache>-1</expiration-cache>
<supports>
<mime-type>text/html</mime-type>
<portlet-mode>VIEW</portlet-mode>
</supports>
</portlet>
<portlet id="omx_sp_update">
<!--same as above-->
<portlet-name>omx_sp_update</portlet-name>
<init-param>
<name>ViewPage</name>
<value>/switch.do?prefix=&page=/showServiceProviderList.do?INTV_weboam_mode=Update&helpid=communicator3.html</value>
</init-param>
</portlet>
<portlet id="omx_sp_delete">
<portlet-name>omx_sp_delete</portlet-name>
<init-param>
<name>ViewPage</name>
<value>/switch.do?prefix=&page=/showServiceProviderList.do?INTV_weboam_mode=Delete&helpid=communicator3.html</value>
</init-param>
</portlet>
-----Original Message-----
From: Jacek Wiślicki [mailto:[EMAIL PROTECTED]
Sent: Friday, October 21, 2005 4:51 PM
To: Jetspeed Users List
Subject: Re: REQUEST PROBLEM in JSR 168 portlets
Wiadomosc od Archana Turaga z 2005-10-21 20:51 brzmiala:
> -I have defined certain parameters as part of my view page in the
> portlet.xml.
> -I noticed that when I navigate to one link do some action go to another
> link and then come back to the previous link the request parameters seem
> to be lost (Also look at the email Amit has outlined).
> -After reading the JSR 168 spec ("PLT.11.1.1 Request Parameters")and
> struts bridges document(Readme.txt) it seems that if RenderRequest is
> used to display the page the parameters in request scope should not be
> depended upon. That is what I concluded. Is there a way to get around
> this problem.
Maybe you should try storing the parameters in the application scope, e.g.
<RenderRequest>.getPortletSession().setAttribute(<String>, <Object>,
PortletSession.APPLICATION_SCOPE);
or cast a PortletSession object to a HTTPSession object:
((HTTPSession)<RenderRequest>.getPortletSession()).setAttribute(<String>,
<Object>);
--
pozdrawiam,
Jacek Wislicki
[EMAIL PROTECTED]
tel.: +48 502 408 444
gg: 2540358
skype: jacek_wislicki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail transmission may contain information that is proprietary,
privileged and/or confidential and is intended exclusively for the person(s) to
whom it is addressed. Any use, copying, retention or disclosure by any person
other than the intended recipient or the intended recipient's designees is
strictly prohibited. If you are the intended recipient, you must treat the
information in confidence and in accordance with all laws related to the
privacy and confidentiality of such information. If you are not the intended
recipient or their designee, please notify the sender immediately by return
e-mail and delete all copies of this email, including all attachments.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
