13 Replies Latest reply on Nov 17, 2006 12:37 PM by Dave Whittaker

    Application Startup Actions

    Dave Whittaker Novice

      Is anyone using seam components to perform actions on the database when their application starts? With Seam 1.0 I had a few SFSB that were application scoped and used the @Startup and @Create methods to check if certain necessary data was available and create it if it wasn't. These are actions like determining if there is at least one administrative account and creating a default one if not, or defining static categories. These stopped working in 1.1 and rather than figuring out why, I'm looking for a better way to perform these types of actions. My two chief problems were/are:

      1) These don't need to be SFSB because they only exists to fire off their create methods, yet I can't do that on application startup without scoping them to the application, and I can't place an SLSB in application scope.

      2) I have no conversation available when the application starts up and this wreaks havoc with my DAOs which expect to be able to inject an SMPC.

      Any ideas?

        • 1. Re: Application Startup Actions
          Gavin King Master

          I would really rather prefer if you figured out what changed in 1.1 that broke your code, and let me know...

          • 2. Re: Application Startup Actions
            Dave Whittaker Novice

            Fair enough. I'll look into it some more when I'm testing the page parameter converter change in a little bit. Either way though, I'm curious if you or anyone else has a better solution? Creating an SFSB only to have it remove itself from the application context in it's own @Create method doesn't exactly strike me as the most readable code :)

            • 3. Re: Application Startup Actions
              Dave Whittaker Novice

              Ok Gavin, it looks to me like the problem stems from the SeamListener trying to instantiate the application scoped SFSB before Jboss is initialized. Adding depends="org.jboss.seam.core.Ejb" doesn't seem to help. Stack trace follows

              -Exception sending context initialized event to listener instance of class org.j
              org.jboss.seam.InstantiationException: Could not instantiate Seam component: sta
               at org.jboss.seam.Component.newInstance(Component.java:1662)
               at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:153)
               at org.jboss.seam.contexts.Lifecycle.endInitialization(Lifecycle.java:12
               at org.jboss.seam.init.Initialization.init(Initialization.java:323)
               at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.j
               at org.apache.catalina.core.StandardContext.listenerStart(StandardContex
               at org.apache.catalina.core.StandardContext.start(StandardContext.java:4
               at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
               at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:73
               at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
               at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.ja
               at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.j
               at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:471
               at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1102)
               at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
               at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
               at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020)
               at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
               at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
               at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442
               at org.apache.catalina.core.StandardService.start(StandardService.java:4
               at org.apache.catalina.core.StandardServer.start(StandardServer.java:683
               at org.apache.catalina.startup.Catalina.start(Catalina.java:537)
               at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
               at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
               at java.lang.reflect.Method.invoke(Method.java:585)
               at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
               at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
              Caused by: javax.naming.NamingException: Local server is not initialized
               at org.jnp.interfaces.LocalOnlyContextFactory.getInitialContext(LocalOnl
               at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
               at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247
               at javax.naming.InitialContext.init(InitialContext.java:223)
               at javax.naming.InitialContext.<init>(InitialContext.java:197)
               at org.jboss.seam.util.Naming.getInitialContext(Naming.java:35)
               at org.jboss.seam.util.Naming.getInitialContext(Naming.java:47)
               at org.jboss.seam.Component.instantiateSessionBean(Component.java:992)
               at org.jboss.seam.Component.instantiate(Component.java:979)
               at org.jboss.seam.Component.newInstance(Component.java:1658)
               ... 28 more

              • 4. Re: Application Startup Actions
                Richard Leherpeur Novice

                I have a couple of components accessing the database and caching data for the application. I didn't get any trouble moving from Seam 1.0 to Seam 1.1

                They are defined as follow:

                public class SomeComponent {
                 public void startup() throws Exception {

                • 5. Re: Application Startup Actions
                  Dave Whittaker Novice

                  I think the problem here has to do with the @Startup annotation. I take it you're not using that?

                  • 6. Re: Application Startup Actions
                    Richard Leherpeur Novice

                    That's right, I'm not using the @Startup annotation.

                    • 7. Re: Application Startup Actions
                      Richard Leherpeur Novice

                      Actually I do.
                      I think the previous code is not the one I intended to copy. Here is what I use:

                      @Startup(depends = {"pojoCache"})
                      public class ResourcesManager {
                       private static final Log log = LogFactory.getLog(ResourcesManager.class);
                       private transient PojoCache pojoCache = org.jboss.seam.core.PojoCache.instance();
                       private EntityManager entityManager;
                       public void startup() throws Exception {

                      • 8. Re: Application Startup Actions
                        Dave Whittaker Novice

                        Ok. Well that's making it look increasingly like my problem is with when JBoss initializes since you are using a POJO rather than a session bean. Has this changed between versions?

                        • 9. Re: Application Startup Actions
                          Gavin King Master

                          Is this on JBoss AS? Or E-EJB3?

                          • 11. Re: Application Startup Actions
                            Gavin King Master

                            Well, that makes more sense, since Seam is responsible for starting the Ejb component during its startup phase.



                            on your component (no caps!)

                            • 12. Re: Application Startup Actions
                              Dave Whittaker Novice

                              Huh, don't know where I got the capital E from, I thought I just cut and pasted from the @Name. I'll give it a shot and let you know if it fixes the problem.