Perhaps something like this:
//Session scoped backing bean
public class MyPojoManager{
private MyPojo pojo;
public MyPojo getPojo(){
if(pojo == null){
//initialize the MyPojo object
}
return pojo;
}
}
This way it would only be initialized once.
- micke
2008/7/21 Guy Bashan [EMAIL
I don't know if it's the best solution, but in a past project I did it
like this:
I had one request-scoped bean per screen, and I had a
setSelectedObject(Object object) method on each of those beans.
The original page was responsible for calling setSelectedObject() on
the target bean page. If
Hi,
You will to excuse me for this question, I have always worked with request
scope beans:
I have a screen in which details are being edited. Now, I have to add a
button near one of the drop downs that will take me to a new screen,
allowing me to create a new object and get back to the
3 matches
Mail list logo
