Sharing backing beans across sessions

HI,
After doing some simple investigations I could see that different sessions were using the same backing bean instance.
I was wondering is there any way you can configure in the JSF framework to use their own instance of the backing bean?
Thanks.

Declare them as session- scoped, e.g.@SessionScoped.

Similar Messages

How-to remove a jsf backing bean from session?

How can I find the reference to a backing bean (with session scope) and then remove the bean?
I may have painted myself into a corner. When most of my pages are navigated to, they get key info from session and then initially populate the page fields. I populate the fields in the constructor with values from the database based on the keys found in session. So the second time a particular page is called the values may be stale or completely unrelated to the page navigated from because the bean already exists and, naturally, the constructor is never called.
I'm thinking if I could remove the backing bean, jsf wouldn't find it so it would be recreated on subsequent navigations. Since the constructor would be called with every navigation to the page, the values would not be stale or unrelated.
Any help would be greatly appreciated.
TIA,
Al Malin

//To reset session bean
FacesContext
     .getCurrentInstance()
     .getApplication()
     .createValueBinding( "#{yourBeanName}").setValue(FacesContext.getCurrentInstance(), null );
//To get session bean reference
Object obj = FacesContext
          .getCurrentInstance()
          .getApplication()
          .createValueBinding("#{yourBeanName}")
          .getValue(FacesContext.getCurrentInstance());
YourSessionBean bean = (YourSessionBean)obj;

Backing Beans as session beans

All the beans on our web application are session scoped beans. Will there ever be any problems due to this? I do not have time to rewrite the beans in request scope.
Thanks.

I am sorry for not being clear. We use backing beans only to retreive and provide form data. I have noticed that all the developers on the team have used session as the scope for these beans. The reason seems to be usage of features such as partial page submits which work better if the bean is in session scope.
However I agree with you that this may cause uneccesary memory footprints. I am currently working on creating a request scoped backing bean that will get data for an Edit page. On submit, the Edit page needs to be re rendered. I need to figure out how to achieve this when the bean is in request scope.

Have a backing bean in request scope; need to access parameters sent to it

I have a request scope backing bean in my app, 'projectBean'. This has a property called 'id'.
/** in request scope in faces-config.xml */
projectBean {
    id               // set by the param from the previous page
    downloadAction() // activated by commandlink, depends on id
}There is another backing bean in session scope called 'projectListingBean', which has a dataTable that lists a bunch of projectBeans. In this 'projectListingBean', I can click on any row. That row, when clicked initializes a 'id' parameter, which is then passed to the new 'projectBean'. 'projectBean' then initializes itself based on the id.
In the jsp page backed by 'projectBean', I also have a link to download something specific to that 'projectBean'. Naturally enough, I have a commandlink with actionBinding to a method in my 'projectBean', downloadXXXAction().
The problem arises because the downloadXXX() method relies on a 'id'. Remember, this id was orinigally set 2 requests back from the datatable. Since the page backed by 'projectBean' is in request scope, the id is lost, and my method call doesn't work. I tried changing the scope of 'projectBean' to session, but JSF complains that I already setting the 'id' property as a param, I can't set the whole managed bean to something 'higher' like session.
Of course, the ideal fix to this probelm would be the ability to have beans in page scope, but what other ways (hacks??) are there to get around this?

Hi, I'm posting some code snippets if it helps with understanding the problem.
faces-config.xml:

<managed-bean>
     <managed-bean-name>projectListingBean</managed-bean-name>
     <managed-bean-scope>session</managed-bean-scope>
     <managed-property>
          <property-name>projectBeans</property-name>
          <property-class>java.util.List</property-class>
          <list-entries>
               <value-class>
                    com.sun.sleuth.omcmweb.view.bean.ProjectBean
               </value-class>
          </list-entries>
     </managed-property>
</managed-bean>

<managed-bean>
     <managed-bean-name>projectBean</managed-bean-name>
     <managed-bean-class>
     </managed-bean-class>
     <managed-bean-scope>request</managed-bean-scope>
     <managed-property>
          <property-name>projectId</property-name>
          <property-class>java.lang.String</property-class>
          <value>#{param.projectId}</value>
     </managed-property>
</managed-bean>projectlsting.jsp (page backed by projectListingBean)
<h:dataTable value="#{projectListingBean.projectBeans}"
     var="projectBean" ...>
     <h:column>
          <f:facet name="header">
          </f:facet>
          <h:commandLink action="#{projectListingBean.viewProjectSUmmary}">
               <h:outputText value="#{projectBean.projectId}" />
               <f:param name="projectId" value="#{projectBean.projectId}" />
          </h:commandLink>
     </h:column>
</h:dataTable>projectsummary.jsp (page backed by request scoped projectBean)
<h:commandLink action="#{projectBean.assessmentAction}" value="..." />
...Flow:
projectlisting.jsp (projectListingBean - session) -param id passed->
projectsummary.jsp (projectBean - request) -commandLink clicked and id lost-->
projectSummary.jsp (projectBean - request)

WebSphere Custering and JSF Backing Beans

Hello All,
Can anyone enlighten me on exactly how backing bean state is maintained by JSF?
In what scope does JSF store the backing beans? (session perhaps)
Does it make sense to use JSF without stateful backing beans?
What would happen if a client post did not find its corresponding backing bean on the application server calling it?
Background:
In a clustered WebSphere Server environment, a client post may be directed to any one of the machines in the cluster. If the client post gets directed to a machine other then the machine that originally sent the client a response, the page will not find the corresponding page beans.
It is possible to serialize session beans in WebSphere and have each machine share its memory with all the boxes in the cluster. However, this practice is not permitted in some environments.
Any thoughts? Thanks in advance.

I am probably not an expert on the subject. But here are some thoughts:
1. A backing bean can have (application, session, request or None) as a scope.
Less app or session scope beans the better (from server perspective). But
There are practical reasons why you would want to use them in many cases.
2. JSF supports Client State Saving mode. But keep in mind the overhead
Involved (serialization, de-serialization, bandwidth,...).
3. You probably need to read about WebSphere load balancing capability. From
what I know it is somehow sophisticated. People typically use session affinity
to force requests initiated by same session to be served by the same app
server (enforced by network, hardware/software tools available to do so,...). Of
course with failover mechanism to ensure high availability.
Hope that helps!

Session backing beans and multiple navigator windows sharing session

Hi let's suppose i have a web and page1, page2 and page3 that should share the backingbean. Normal navigation goes from page 1 to page 2 to page 3.
I do not want a backing bean per page because i need to share data between my pages. The immediate solution is to put this bean in session context and use it in each page. But this has severe drawbacks:
- The backing bean is the same each time I access any page, and I want a new bb to be used each time the user requests for page 1
- When a user has more than one navigator window sharing session, and on each window he is navigating through pages 1 to 3, there can be a big mess because he is accessing to the same bb from both windows.
So I would like to find a solution that permit the user to navigate from both windows as if the windows had its own session.
Any hint?
Thnx

I have a similar problem as described .
I hava one window with enterable fields and when you click on a button it opens another window .Both forms are backed by the same bean .since both forms are nearly the same .
The bean is a managed bean in request scope .
when I fill in the first window with values and click on the link it opens the second but the first windows elements and now empty .
Even though it is in Request scope when the second window is being loaded the bean is re-initialized . I would expect a new intance of this bean to be created for the second window .
This is how I am calling the second window .
<h:commandButton id="newRequestItem" action="#{requestItem.createNewRequestItem}" rendered="#{createActivationRequest.displayCreateLinks}" onclick="openNewPage('NewRequestItem.jsp');"
image="images/show_all.gif" title="new request">
<h:outputText value="new request" styleClass="toolbar-command"></h:outputText>
</h:commandButton>
function openNewPage(url)
aqcbwin= window.open(url, "newRequestItem","toolbar=no, scrollbars=1");
aqcbwin.moveTo(50, 50);
target="_new";
//target="_blank";
aqcbwin.focus();
any ideas to what is wrong and how I can correct this .
Thanks for your help .
Mark

How do i get back my stateful session bean after it has been passivated

hi ,
How do i get back my stateful session bean after it has been passivated by container.
i'm confused that is it possible or not .......give me answer
i've one stateful sessionbean which i'm accessing throgh my normal java client . now what i'm doing is when i first time call a method it is running ......then i'm shutting down the server jboss .......it is calling my ejbPassivate() method ... at this particular time client program doesn't do anything.....
now after i restart my server i'm again calling back that business method with that last object reference.......it gives me the exception given below.....
java.rmi.NoSuchObjectException: no such object in table
java.rmi.NoSuchObjectException: no such object in table
     at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
     at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
     at sun.rmi.server.UnicastRef.invoke(Unknown Source)
     at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
     at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118)
     at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227)
     at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167)
     at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
     at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
     at org.jboss.proxy.ejb.StatefulSessionInterceptor.invoke(StatefulSessionInterceptor.java:106)
     at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
     at $Proxy1.makeNewAcc(Unknown Source)
     at client.GanJavaClient.main(GanJavaClient.java:46)so pls tell me that is it possible to get back that session besn or not

Stateful session beans are not persisted across restart of the EJB server instance(s) hosting them. You can't treat a Session bean as one would an entity bean.
Chuck

How can I set the value to a session bean from backing bean

Hi Experts,
How can I set the value to a session bean from backing bean where I have created getter and setter
methods for that variable.
Basically I am using ADFUtils class where I am able to get the value from session bean
using following expression
String claimType =
(String)ADFUtil.invokeEL("#{ClaimValueObj.getClaimType}");
Thanks
Gayaz

Gayaz,
Wrong Post !!
Post in JDeveloper and ADF
Thanks
--Anil

ADF BC how to access session backing bean value in servlet

Hi everyone,
How do I access session backing bean value in a servlet?

Frank, thanks for your reply.
I'm not sure how I can incorporate this example into my situation. Let me explain more detail about my problem.
"servlet" in my post here actually means a custom servlet I wrote for rendering an image that is stored in db as ordimage. In this servlet, I get hold of my appmodule by using Configuation.createRootApplicationModule(). By doing so (If I'm not wrong) a new database session/connection is created. What I'm going to achieve is set application context for this new session/connection in db with the data stored in a session backing bean in the view layer.
I can pass the required data to the servlet thru url parameter, but I don't want to do it this way for the reason that the data may contains sensitive information.
I hope I have explained myself well.
Message was edited by:
bsmt

How to decide when to keep backing bean in request and session.Pros/cons

How to decide when to keep backing bean in request and session.Pros/cons

Depends on where the bean data must be available. Start with request scope. If you need the data in session scope, then think twice about impacts (memory usage, multiple browser tabs, etc) unless the data is obviously targeted on the session scope (loggedin user, user settings, dropdown data, etc).

Calling init() method from "session scope" backing beans (AbstractPageBean)

hi,
i prepared a jsp/jsf page named DBmanage, its backing bean's scope is set to "session"
the page contains - among other components - one radiobuttongroup, the buttons of which i would like to rename at the first time when the user visits the page... (default names are "item 1", "item 2", "item 3")
i thought that the overridden init() method does the work for me with this simple code:
import com.sun.webui.jsf.model.Option
@override
init() {
rbg_default_options.setOption( new Option[]{new Option("it1", "RB1"), new Option("it2", "RB2")}
so, let see how this code works when DBmanage backing bean's scope is "request"
great! i see a radiobuttongroup with two buttons, named RB1 and RB2
ok, now i change the scope to "session"
sh&#@t!!! now i'm gazing at a page with buttons named "item 1", "item 2", "item 3"
let's place a breakpoint inside the init() method and DEBUG... and my init() code has not run(??), how can this happen? init() method is valid only for request beans?
pls! could anyone help me?
ps.: i work with netbeans6.0 & glassfish
thanks
Gabor

it's ok. i found out why it wasn't working.
my scope was set to "session", but had to be "request" so that i could use the params syntax.
thanks anyway.

How to get and set a session variable from backing bean?

Hi im using Jdev 11.1.1.2.0 and i need to set and get a session variable from backing Bean.
Any idea?

the class :
package arq.resources;
import javax.faces.context.FacesContext;
import javax.servlet.http.HttpSession;
public class SesionSigef {
public FacesContext context;
public HttpSession session;
public SesionSigef() {
super();
context = FacesContext.getCurrentInstance();
session = (HttpSession)(context.getExternalContext().getSession(true));
public Object getVariableSesion(String atributo){
return session.getAttribute(atributo);
public void setVariableSesion(String atributo,Object valor){
session.setAttribute(atributo, valor);
the example of use :
SesionSigef se = new SesionSigef();
DatosRec da = new DatosRec();
da.setDocumentoCip("Aprobar");
se.setVariableSesion("DatosRec", da);
thanks
Joaquin

We should NEVER use the session back bean?

Because the user can open a new window by right click the link, and the session scope back bean is not thread-safe.
So we should forget it?

Your concern makes really no sense, or you must be storing request scoped data in a session scoped bean instead of a request scoped bean, which can indeed lead to undesireable behaviour in multiple requests on the same session.

Calling from an EJB into a JSF Backing Bean

Hello all,
I'm looking for some help in making calls from an EJB into a Backing Bean (the converse is fairly straightforward). My basic question is: what is regarded as the best way to do this?
However, for anybody who's interested, I'll describe what I've been trying...
Here's my situation (I'm working with OC4J 10.1.3.2). I have a simple application-scoped backing bean:
   public class BackingBean implements SimpleInterface, Serializable {
       private String greeting = "Hello, World";
       private SessionEJBRemote blBeanRemote = null;
       public BackingBean() {
           // get hold of EJB
           // [ ... code to obtain EJB's remote interface snipped ... ]
           // set the callback with the EJB
           try {
               blBeanRemote.setCallback(this);
           } catch (Exception ex) {
               ex.printStackTrace();
       // methods to manipulate the greeting string
       public String getGreeting() {
           return greeting;
       public void setGreeting(String greeting) {
           this.greeting = greeting;
   }SimpleInterface, which my Backing Bean implements is, well, a simple interface:
   public interface SimpleInterface {
       public void setGreeting(String greeting);
   }And my EJB is also pretty straightforward:
   @Stateful(name="SessionEJB")
   public class SessionEJBBean implements SessionEJBRemote, SessionEJBLocal {
       private SimpleInterface callback = null;
       public void setCallback(SimpleInterface callback) {
           this.callback = callback;
           callback.setGreeting("Goodbye, World");
   }Now, by using SimpleInterface, my intention was to ensure a one-way dependency: i.e. the JSF-level code would depend on the EJB-level code, but not vice versa.
However, my experimentation has shown that when I make the call to blBeanRemote.setCallback, the parameter appears to be passed by value rather than by reference. This means firstly that, at runtime, by EJB needs to have access to my backing bean class and secondly, that the call to callback.setGreeting has no effect.
Can anybody suggest how to work around this? Is it possible to pass the backing bean by reference? Is there a better way to achieve this callback? I appreciate that these questions might be more general Java/AppServer queries rather than JSF-specific ones - but hopefully this is something that all you JSF experts have encountered before.
(Incidentally, I realise that what I'm doing in this example is pointless - what I'm building towards is using the ICEFaces framework to have the EJBs prod a backing bean which will in turn cause a user's browser to rerender.)
Many thanks - any help very much appreciated!
Alistair.

Hi Raymond - yes, you've pretty much got that spot on: an event occurs (say receipt of a JMS message - which is spontaneous, as far as the users are concerned). As a result of that event, the client's view (in their browser) needs to be re-rendered.
ICEFaces uses the AJAX technique to allow server-pushes, and rather than refreshing the whole page it uses "Direct-to-DOM" rendering to maninpulate the page components. If you've not come across it, and you're interested, then there are some pretty interesting demos here: http://www.icefaces.org/main/demos/ - the "chat" feature of the Auction Monitor demo (if you open it up in two browsers) is the nearest to the effect I'm looking for.
The Auction Monitor demo uses a number of session-scoped beans, each implementing the ICEFaces "Renderable" interface, and each of which registers itself with an application-scoped bean. The application-scoped bean can thus iterate through each of the session-scoped beans and cause the corresponding browser to refresh.
Unfortunately, in the Auction Monitor demo, the entry point is always from a browser - albeit the result is then mirrored across all connected browsers. I haven't found any examples of this processing being driven by an external event, hence my experimentation in this area!

Moving Scriptlet Code to backing bean when converting from JSP - Facelets

Hello!
We are converting our application from jsf1.2 to 2.0 and all jsps are being converted to XHTML. Some are trivial while others had very complex scriptlets.
I would like to know what are some of the recommended ways of moving Scriptlet Code to backing bean when converting from JSP -> Facelets.
I have thought about listeners, actionListeners, putting code getXXXX() of the backing bean and then calling #{bean.XXXX} but not sure whats the best way.
I do appreciate the response!
Eg of a jsp page:
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="/WEB-INF/xxx-jsf.tld" prefix="l" %>
<%@ taglib uri="/WEB-INF/yyy-pp.tld" prefix="p" %>
<%@ page import="com.ttyy.search.beans.jsf.AdvancedSearchFormManagedBean" %>
<%@ page import="com.kkee.util.*"%>
<%
    AdvancedSearchFormManagedBean advancedSearchFormManagedBean = (AdvancedSearchFormManagedBean) request.getSession().getAttribute("AdvancedSearchFormManagedBean");
    if (advancedSearchFormManagedBean == null) {
       advancedSearchFormManagedBean = new AdvancedSearchFormManagedBean();
       request.getSession().setAttribute("AdvancedSearchFormManagedBean", advancedSearchFormManagedBean);
    advancedSearchFormManagedBean.initializeForAdvancedSearchOptions();
    advancedSearchFormManagedBean.setQuickSearch();
     request.setAttribute("portletHeader", "Hello " + advancedSearchFormManagedBean.getPerson().getFirstname() + ", check out the latest programs in your practice areas and jurisdictions");
%>
<h:form id="MYCenterForm">
     <p:portletRenderer portletSetName="test of portlet"
          portletContainer="#{PortletContainerManagedBean}"
          id="MYCenter"
          portletScope = "TEST_SCOPE"
          suppressIfNoData="true"
          portletSkinName="SOME_SKIN">
          <f:facet name="persistenceToolkit">
               <h:commandLink id="persistenceToolkitLink"
                    actionListener="#{PortletContainerManagedBean.persistPortletSetStateListener}">
                    <h:outputText value="Save State Of Portlet Set" id="persistenceToolkitLinkText"/>
               </h:commandLink>
          </f:facet>
     </p:pagePortletSetRenderer>
</h:form>
<%
     String flag = PropertyItems.getInstance().getPropertyItem("response.time.flag");
     if("1".equals(flag)){
          ResponseTime rt = (ResponseTime) session.getAttribute("responseTime");
        if(rt!=null){
            rt.setDesc("my cle loaded");
            long now = System.currentTimeMillis();
            long start = rt.getStart() + rt.getTotal();
            rt.setInterval(now-start);
            rt.setTotal(rt.getTotal()+rt.getInterval());
            LogUtil.log(rt.toString(), LogUtil.DEBUG_LEVEL);
            session.setAttribute("responseTime", rt);
%>

That helps.
This could be another topic question but itst kind of related to what i am doing right now. while converting JSP to facelet (in jsf2) I came across another issue.
<h:commandLink id="Save" rendered="#{RegistrationBean.isNOTInOrigionalRegistrationMode}" action="#{RegistrationBean.updateProfile2Submit}" styleClass="#{portalSkinManagedBean.contentPortletSkin.strongTextStyle}">
          <l:htmlSkinnedImage id="SaveImage" style="border:0;" url="save.gif" alt="Save Information"/>
</h:commandLink>When I click on the generated link, I get this. And this is happening for all the h:commandLink in the application.
http://localhost:9080/registration/updateProfile2.jsf[request.getQueryString()=null][request.getRequestedSessionId()=F1CCE237DD81D301F1C4DBA6910FFD8A][request.isRequestedSessionIdFromCookie()=true][request.isRequestedSessionIdFromURL()=false][request.isRequestedSessionIdValid()=true]Parameters:[rolePracticeAreasForm:title=rolePracticeAreasForm:primaryPracticeArea=10002javax.faces.ViewState=-2943345291093118815:-4400303399130292206rolePracticeAreasForm:practiceAreasMod2=10148.1rolePracticeAreasForm:practiceAreasMod1=10002.1rolePracticeAreasForm:Save=rolePracticeAreasForm:SaverolePracticeAreasForm=rolePracticeAreasFormrolePracticeAreasForm:otherField=rolePracticeAreasForm:fromMyAccount=1]||
javax.servlet.ServletException: Index: 0, Size: 0
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:325)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at com.legaledcenter.util.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:250)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198)
     at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at com.jscape.framework.galileo.support.upload.UploadFilter.doFilter(UploadFilter.java:71)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
     at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
     at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
     at java.util.ArrayList.RangeCheck(ArrayList.java:547)
     at java.util.ArrayList.get(ArrayList.java:322)
     at javax.faces.component.AttachedObjectListHolder.restoreState(AttachedObjectListHolder.java:161)
     at javax.faces.component.UIComponentBase.restoreState(UIComponentBase.java:1427)
     at com.sun.faces.application.view.StateHolderSaver.restore(StateHolderSaver.java:121)
     at com.sun.faces.application.view.StateManagementStrategyImpl$4.invokeContextCallback(StateManagementStrategyImpl.java:289)
     at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:1253)
     at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:672)
     at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:1262)
     at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:672)
     at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:1262)
     at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:672)
     at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:1262)
     at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:672)
     at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:1262)
     at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:672)
     at com.sun.faces.application.view.StateManagementStrategyImpl.restoreView(StateManagementStrategyImpl.java:284)
     at com.sun.faces.application.StateManagerImpl.restoreView(StateManagerImpl.java:177)
     at com.sun.faces.application.view.ViewHandlingStrategy.restoreView(ViewHandlingStrategy.java:119)
     at com.sun.faces.application.view.FaceletViewHandlingStrategy.restoreView(FaceletViewHandlingStrategy.java:434)
     at com.sun.faces.application.view.MultiViewHandler.restoreView(MultiViewHandler.java:143)
     at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:199)
     at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
     at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:110)
     at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:312)
     ... 22 more
********** Message End *************Thanks

Sharing backing beans across sessions

Similar Messages

Maybe you are looking for