RE: Myfaces Portlet does not work when a bean is stored in Requestscope...

Hi Scott, Thanks again for clearing some of the basic points. For the better future reference purpose here I try to summarize our discussion/debate points. 1. Issue # 1 - How to handle initial Portlet request which has request parameters. Yes I do agree with you that Portals, according to

Re: Myfaces Portlet does not work when a bean is stored in Requestscope...

souravm wrote: Hi Scott, Thanks again for clearing some of the basic points. For the better future reference purpose here I try to summarize our discussion/debate points. 1. Issue # 1 - How to handle initial Portlet request which has request parameters. Yes I do agree with you that

Re: Myfaces Portlet does not work when a bean is stored in Requestscope...

A quick list of items that will be addressed as part of 301 in JSF 1.2 over other bridges are: 1. Better thought through request scope 2. Extendible GenericFacesPortlet allowing custom behavior and mixture of portlet/jsf generated content while still being able to use the bridge 3. Much better

RE: Myfaces Portlet does not work when a bean is stored in Requestscope...

Hi Scott, Thanks for the list. Is there any good documentation available anywhere to help starting with My faces JSF 1.2 and the Portlet Bridge ? I was trying to experiment with them. But at a first step itself I'm getting problem once we put the respective jars in the jboss server. The

Re: Myfaces Portlet does not work when a bean is stored in Requestscope...

I would be surprised if JBoss didn't have JSF built in. Since the RI is under development, there is no real good documentation. On the wiki I have a page which outlines getting Pluto installed in Tomcat6, presumably you could use the RI or MyFaces with that. Scott souravm wrote: Hi Scott,

RE: Myfaces Portlet does not work when a bean is stored in Requestscope...

JBoss Portal Server works fine with JSF 1.2. The problem starts when I add the portlet-bridge-api-1.0.0-alpha-2.jar and portlet-bridge-impl-1.0.0-alpha-2.jar. It gives error while parsing the faces-config.xml file in Manifest folder of portlet-bridge-impl-1.0.0-alpha-2.jar. It says Parse Error

Re: Myfaces Portlet does not work when a bean is stored in Requestscope...

Hey Souravm, are you on the dev list? We should probably continue this there. Scott souravm wrote: JBoss Portal Server works fine with JSF 1.2. The problem starts when I add the portlet-bridge-api-1.0.0-alpha-2.jar and portlet-bridge-impl-1.0.0-alpha-2.jar. It gives error while parsing

RE: Myfaces Portlet does not work when a bean is stored in Requestscope...

Ok. I'm not currently in dev list. Let me add myself there and let you know. Regards, Sourav -Original Message- From: Scott O'Bryan [mailto:[EMAIL PROTECTED] Sent: Monday, April 21, 2008 5:05 PM To: MyFaces Discussion Subject: Re: Myfaces Portlet does not work when a bean is stored in

RE: Myfaces Portlet does not work when a bean is stored in Requestscope ...

Hi Scott, Thanks for the detailed answer/explanation. They were really helpful to verify my understanding and also enriching the same. My consolidated response to your last 2 mails are embedded below. Regards, Sourav -Original Message- From: Scott O'Bryan [mailto:[EMAIL PROTECTED]

Re: Myfaces Portlet does not work when a bean is stored in Requestscope ...

Eeks I wish these would have been seperate, this is going to be a long response and not be as easily referenceable in the archives. souravm wrote: Hi Scott, Thanks for the detailed answer/explanation. They were really helpful to verify my understanding and also enriching the same. My