Hi thanks, For the whole lot of help you guys have given me. I'm sorry I did not reply earlier///since I was bogged down by deadlines.
But just as an update for this problem: It was figured out that by modifying the struts webapp a little bit the request issue could be worked around. Since I'm not the owner of that webapp I do not know the nature of the fix but I plan to find out and update this post for others who may have issues. Regards, Archana -----Original Message----- From: Archana Turaga [mailto:[EMAIL PROTECTED] Sent: Sunday, October 23, 2005 7:16 PM To: Jetspeed Users List Subject: RE: REQUEST PROBLEM in JSR 168 portlets Hi jonathan, Another request: Is it possible to give me some info about how you did this: "Just used this myself to set the source of an iFrame in one portlet from the struts action within another ortlet." By the way thanks for pointing me to this really informative site. You should post this link on the Jetspeed website somewhere. Has some interesting pointers which can give some clues to desperate people like me ;-) Thanks a lot,Regards, Archana -----Original Message----- From: Jonathan Hawkins [mailto:[EMAIL PROTECTED] Sent: Saturday, October 22, 2005 2:08 AM To: Jetspeed Users List Subject: Re: REQUEST PROBLEM in JSR 168 portlets Take a look at http://www.doc.ic.ac.uk/~mo197/portlets/portlet_messaging/ Just used this myself to set the source of an iFrame in one portlet from the struts action within another ortlet. Hope that helps Jon Jacek Wiślicki wrote: > Wiadomosc od Archana Turaga z 2005-10-21 23:55 brzmiala: > >> 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. > > As far as I understand, the only problem is passing some attribute > between different web aplications (within the same container), right? > I don't know much about other servlet containers, but with Tomcat you > could set the "crossContext" attribute for either application context > to "true" and then setup the parameter (identified e.g. by the HTTP > session id) in the other servlet context (another webapp), like this: > //your application context: > <HTTPServlet>.getServletContext().getContext(<String:other app context > name>).setAttribute(<String>, <Object>); > //other application context > <HTTPServlet>.getServletContext().getAttribute(<String>); > > The above code can be applied from within a servlet, you should modify > it to execute from a portlet, i.e. get a servlet context from a > portlet context. I am not sure if a PortletContext object could by > fully functional as a ServletContext object, however if such a > solution fails, use an intermediate redirection servlet for setting > the other context attributes. > > I do hope that it's what you meant. > > --------------------------------------------------------------------- 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] 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]
