Sourav,

Portals don't work like you want them too. Portlets cannot receive request parameters added to a generic portlet URL. These url's need to be encoded. You only real option here is to have your external page launch the portal and then the user would need to do navigation from within the portlet itself to get to the data they need. The JSR-168 Portlet spec does not support "GET" requests - that is they do not support modifying the parameters on a GET request after it has been encoded (or in the case of the Action, after getting the url string).

That said, my advice would be to access your JSF application stand-alone when launched from your external page. If that's not possible, you might want to make your external page a portlet and look at using JSR-286 (still under development) eventing to invoke your portlet into the mode you need. The latter suggestion is not appropriate for a short term solution because not only is JSR-286 not final, it will also require JSR-301 (also not final), and JSF 1.2.

Scott

souravm wrote:

Hi All,

I’ve a MyFaces (1.1.4) Portlet deployed in jboss portal server.

First time I need to access this portlet from a non-JSF (jsp) page which sends a http post request with some request parameters.

The solution does not work when the request does not have any request parameter (works fine when accessed by a request with no request parameter).

When I try to read the request parameter(s) in the constructor of the managed bean they come as null.

I tried extending the processAction() method of MyFacesGenericPortlet. I read the request parameters from the ActionRequest and set them in RenderRequest using setRenderParameter (This anyway one has to do for a jsp based portlet implementation). With this approach I can read the request parameters in the constructor of the managed bean.

I would like to validate whether this is a known limitation of MyFacesGenericPortlet and the solution approach mentioned above is right one (or any other approach is recommended) ?

Any help in this regard would be highly appreciated.

Sourav

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***


Reply via email to