lossing of attributes in the request scope of jsf

[vadymkarpenko]

I am playing around with a simple jsf portlet and have stuck on the problem that managed bean with the scope request lose its attributes and they are not available at the result page. But when I run this application in tomcat lice web app everything is ok.
Here is some more details :

 <navigation-rule>
 <from-view-id>/inputname.jsp</from-view-id>
 <navigation-case>
 <from-action>#{PersonBean.sayHi}</from-action>
 <from-outcome>ok</from-outcome>
 <to-view-id>/greeting.jsp</to-view-id>
 </navigation-case>
 </navigation-rule>

 <managed-bean>
 <managed-bean-name>PersonBean</managed-bean-name>
 <managed-bean-class>PersonBean</managed-bean-class>
 <managed-bean-scope>request</managed-bean-scope>
 </managed-bean>

inputname.jsp main part:
 <h:form >
 <h:inputText id="userName" value="#{PersonBean.userName}"/>
 <h:commandButton id="submit" action="#{PersonBean.sayHi}" value="Say Hello" />
 </h:form>

PersonBean.sayHi :
 public String sayHi(){
 userName+=" (hello from jsf core)";
 return "ok";
 }

greetings.jsp main part:

 <h:outputText value="#{PersonBean.userName}" />!

So when the scope request it works ok like web app but id doesn't when it is working like jsf portlet.

Can anybody explain to me why ? Can this be a bug of jboss portal?

[vadymkarpenko]

in addition to my post, I use :
JBoss AP 4.0.4.GA
JBoss Portal 2.1.4.CR1

[ssilvert]

This sort of JSF portlet works fine for others. Must be something wrong with your configuration.

[vadymkarpenko]

I understand that this looks like a very simple problem.
But I still have a question on our example "HelloWorldJSFPortlet". In this portlet you are using

 <managed-bean>
 <description>Basic UserBean</description>
 <managed-bean-name>user</managed-bean-name>
<managed-bean-class>org.jboss.portlet.hello.bean.User</managed-bean-class>
 <managed-bean-scope>session</managed-bean-scope>
 </managed-bean>

and it works ok because the score is session. But if you change the scope to request it doesn't work.
I have started this example like web app in tomcat, and it works ok with the scope request.
So I think that this is some of the problem of jsf portlet.

I have examined portal-core.war on this aspect . You have there beans in the request scope but you are using them to change session scope beans. So you are not using there request scope beans at the result page.

I will appreciate if you will answer on this problem.

[theute]

Stan,
could it be because between the action phase and the render phase, there is another HTTP request (a redirection) ? So when you call an action you actually do *2* HTTP requests. (I don't know how you handled that).

I think at some point you could tell JBoss Portal to avoid the redirection. But then you trigger the action twice on a refresh.

[ssilvert]

It's a bug in MyFacesGenericPortlet. I'm going to fix it as soon as I can.

Stan

[ssilvert]

I committed a simple fix for this. It will be in the next version of MyFaces 1.1.

Handling the request attributes will also be addressed in the spec for JSR-301.

Stan

[leman_1]

Hello,

I am having the same type of problem with a Struts based application. I am using an existing application and trying to get it running as a portlet. There are a lot of cases where the actions save objects as request attributes. On the forwarded to jsp page the usebean call fails saying the bean doesn't exist in the request.

The example struts application doesn't try to do this anywhere. I don't know if I am missing something from the configuration files.

Any help would be greatly appeciated.

[domyalex]

Uh.... in which version of MyFaces will the fix be available? I recently switched to 1.1.4 but realized that the problem persisted.

Regards

Alejandro

[ssilvert]

"domyalex" wrote:
Uh.... in which version of MyFaces will the fix be available? I recently switched to 1.1.4 but realized that the problem persisted.

Regards

Alejandro

Fixed in 1.1.5. You can use a nightly build.

We are also talking about doing a patch branch for 1.1.4. If so, it will be included in that.

Stan

[theute]

Thank you Stan !