3 Replies Latest reply on Sep 23, 2009 9:02 PM by pmuir

    Problems with beans that have been passivated

    meetoblivion

      I think I saw this before, but just wrote it off as not too much of an issue.  Basically, I have a web bean and an enterprise web bean.  The web bean is located within my web app (war file) and the EWB is in an EJB jar; both are in the EAR file.


      After about 15 minutes, the stateful EWB passivates, but the webbean stays active, since it's session scoped.  The EWB is also session scoped. They have different binding types.  When the EWB passivates, the webbean cannot reference it anymore, and there doesn't seem to be a mechanism the reload it.

        • 1. Re: Problems with beans that have been passivated
          pmuir

          John, please file a JIRA for this, I understand (I think) what you are saying, and can see how it might happen. We can certainly fix it (whether it is an easy fix tho ;-).


          If possible please attach a test case showing this. If not, a simple example packaged for JBoss AS would suffice :-)


          Thanks!

          • 2. Re: Problems with beans that have been passivated
            meetoblivion

            Ok, just created WBRI-389.


            I have to ask, any idea when a patch/commit could be available for this?  I have an app that I want to release public on top of webbeans but this causes an issue with it.  Internal apps it's not as much of a problem because a) business users are faster b) business users are more patient.  Also, what does the compatibility look like from the old AS 5.1 version and current? Would an app work there without requiring a partial rewrite?


            • 3. Re: Problems with beans that have been passivated
              pmuir

              I scheduled it for CR2, so you are looking at around 4-6w.


              Web Beans should still work with AS 5.1, we moved to a snapshot of 5.2 as we needed some of the new features there - if you can live with out those, you are safe.