10 Replies Latest reply on Feb 25, 2009 1:52 PM by Pete Muir

    Backing the Web Beans Application scope

    Pete Muir Master

      Currently we back the Web Beans Application scope with the servlet context, however this isn't sufficient as Servlet may not be available.

      The application context should available for the whole time the application is running (including *Web Beans* startup and shutdown), it doesn't need to be replicated and the objects it contains don't support serialization.

      So, my proposal is to delegate providing backing for the application context to the AS through the Web Beans bootstrap (https://svn.jboss.org/repos/webbeans/ri/trunk/webbeans-ri-spi/src/main/java/org/jboss/webbeans/bootstrap/api/Bootstrap.java).

      This would require the Web Beans bootstrap deployer to have an implementation of BeanStore (https://svn.jboss.org/repos/webbeans/ri/trunk/webbeans-ri-spi/src/main/java/org/jboss/webbeans/context/api/BeanStore.java) which it passes to Web Beans through it's (WB) Bootstrap.

      Ales and I had some ideas for how to back it:

      • non-serializable JNDI
      • EJB3.1 singleton
      • MBean server.

        Thoughts?