JSF ConversationScoped bean not elevating scope between POSTs

Question

I have a bean with an action method called view() and a field of type MyObject:

@ManagedBean
@ConversationScoped
public class MyBean implements Serializable{
    private @Inject Conversation conversation; //has getter and setter
    private MyObject object; //has getter and setter
    ... other fields follow

    public String view(MyObject selectedObj){
        conversation.begin();
        return "success";
    }

    public String getSomeProperty(){
            return object.getProperty();
    }

    ...other methods follow
}

On screen1.xhtml I am using primefaces p:dataTable with var="obj" to output rows with a commandButton to view the object of the row the user clicks on. The button on each row looks like the following.

<p:commandButton action="#{myBean.view(obj)}"
ajax="false" title="View Clone" image="ui-icon ui-icon-locked"/>

When the user clicks on a commandButton in one of the rows, they are taken to page2.xhtml where more detailed info about the obj is displayed. This works correctly and displays the details. When I am inside of the view(MyObject selectedObj) action method, I immediately call conversation.begin(), assign this.obj = selectedObj, and user gets page2.xhtml.

However, when the user clicks a commandButton on page2 it should redisplay with different information from the obj that was assigned from the view() action call that happened when they came from page1 because the scope was elevated to conversation. This is not happening. The obj field is null in the bean when the scope should have prevented it from being lost. So when they clicked a commandButton on page2, it gives null pointer exception when the page tries to resolve #{myBean.someProperty}.

What am I missing? Thank you for any help.

I must be really good at stumping people. I always get Tumbleweed awards b/c no one can answer my questions. Too hard? — Adam, Aug 14 '11 at 23:35
This might help - http://stackoverflow.com/questions/5250311/cdi-conversationscoped-long-running-bean-not-working/5489558#5489558 — Bhesh Gurung, Aug 15 '11 at 01:22

Lars Bohl · Answer 1 · 2012-07-25T06:21:17.743

@ConversationScoped is a feature of CDI, not JSF itself. That means that in order for it to work properly, you must use @ConversationScoped in combination with @javax.inject.Named, not @ManagedBean.

CDI is not by default included in JSF 2.0 or 2.1, so you would also need to add a CDI implementation like Weld (see http://seamframework.org/Weld) and an "empty beans.xml", as described in the weld documentation.

score 2 · Answer 2 · edited Dec 06 '12 at 05:06

2

@ConversationScoped is an annotation of CDI. If you use it you must never use @ManagedBean which is a JSF annotation. instead you must annotate the bean with @Named.

edited Dec 06 '12 at 05:06

vgoff

10,980
3
38
56

answered Dec 06 '12 at 04:43

Mohd Kose Avase

21
2

This is already answered by Lars Bohl. Why are you repeating an already given answer? This is a Q&A site where one can upvote other's answer if you agree, not an old fashioned discussion forum where one would repeat other's post in a primitive manner. – BalusC Dec 06 '12 at 11:15

JSF ConversationScoped bean not elevating scope between POSTs

2 Answers2