4 Replies Latest reply on Jun 15, 2008 7:03 PM by dan.j.allen

    Seam initializes multiple times when starting application

    thomas.googli.medeltiden.org

      When the seam ServletContextListener is called multiple times it scans and starts all seam components multiple times as well, is this the intended behaviour?
      After the first start seam gives an WARN message on each subsequent seam init.
      Were using multiple vhosts, that is what might to trig this
      behaviour, these are the .toString()s of the context each time seam starts.


      StandardEngine[jboss.web].StandardHost[localhost].StandardContext[/foo]
      StandardEngine[jboss.web].StandardHost[foo.com].StandardContext[/foo]
      StandardEngine[jboss.web].StandardHost[test.foo.com].StandardContext[/foo]
      



      First start up (jboss as 4.2.2)


      23:59:32,091 INFO  [ServletContextListener] Welcome to Seam 2.0.1.GA
      23:59:37,466 INFO  [Initialization] Namespace: http://jboss.com/products/seam/async, package: org.jboss.seam.async, prefix: org.jboss.seam.async
      23:59:37,466 INFO  [Initialization] Namespace: http://jboss.com/products/seam/framework, package: org.jboss.seam.framework, prefix: org.jboss.seam.core.framework
      23:59:37,466 INFO  [Initialization] Namespace: http://jboss.com/products/seam/theme, package: org.jboss.seam.theme, prefix: org.jboss.seam.theme
      ...



      Second start up with WARN


      WARN  [SeamPhaseListener] There should only be one Seam phase listener per application
      00:01:07,591 INFO  [ServletContextListener] Welcome to Seam 2.0.1.GA
      ...