java.lang.IllegalStateException: ApplicationAssociate ctor not called in same callstack as FacesConfigParser.contextInitialized(). The configuration for your Configure Listener or Faces Servlet definitions in your deployment descriptor may be wrong. Please check section 10 of the JSF spec for more details.

denoo.info | 4 months ago
  1. 0

    Finally JSF 1.2 and Facelets on Websphere 6.1. | devNoo

    denoo.info | 4 months ago
    java.lang.IllegalStateException: ApplicationAssociate ctor not called in same callstack as FacesConfigParser.contextInitialized(). The configuration for your Configure Listener or Faces Servlet definitions in your deployment descriptor may be wrong. Please check section 10 of the JSF spec for more details.
  2. 0

    Null pointer exception when deploying to Orion apps server

    Oracle Community | 1 decade ago | 843842
    java.lang.IllegalStateException: ApplicationAssociate ctor not called in same callstack as ConfigureListener.contextInitialized()
  3. 0

    RE: update from 1.1.6 to 1.2.8 -> IllegalStateException: No Factories configured for this Application

    myfaces-users | 7 years ago | Michael Heinen
    java.lang.IllegalStateException: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions! If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml. A typical config looks like this; <listener> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class> </listener>
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    update from 1.1.6 to 1.2.8 -> IllegalStateException: No Factories configured for this Application

    myfaces-users | 7 years ago | Michael Heinen
    java.lang.IllegalStateException: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions! If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml. A typical config looks like this; <listener> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class> </listener>
  6. 0

    RE: update from 1.1.6 to 1.2.8 -> IllegalStateException: No Factories configured for this Application

    myfaces-users | 7 years ago | Michael Heinen
    java.lang.IllegalStateException: No Factories configured for this Application. This happens if the faces-initialization does not work at all - make sure that you properly include all configuration settings necessary for a basic faces application and that all the necessary libs are included. Also check the logging output of your web application and your container for any exceptions! If you did that and find nothing, the mistake might be due to the fact that you use some special web-containers which do not support registering context-listeners via TLD files and a context listener is not setup in your web.xml. A typical config looks like this; <listener> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class> </listener>

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.IllegalStateException

      ApplicationAssociate ctor not called in same callstack as FacesConfigParser.contextInitialized(). The configuration for your Configure Listener or Faces Servlet definitions in your deployment descriptor may be wrong. Please check section 10 of the JSF spec for more details.

      at com.sun.faces.application.ApplicationAssociate.<init>()
    2. JSF
      ApplicationFactoryImpl.getApplication
      1. com.sun.faces.application.ApplicationAssociate.<init>(ApplicationAssociate.java:94)
      2. com.sun.faces.application.ApplicationImpl.<init>(ApplicationImpl.java:96)
      3. com.sun.faces.application.ApplicationFactoryImpl.getApplication(ApplicationFactoryImpl.java:76)
      3 frames
    3. JavaEE 7
      FacesServlet.init
      1. javax.faces.webapp.FacesServlet.init(FacesServlet.java:144)
      1 frame
    4. WebSphere
      ServletWrapper.init
      1. com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:191)
      1 frame
    5. com.ibm.ws
      ServletWrapper.init
      1. com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:326)
      1 frame
    6. WebSphere
      ServletWrapper.initialize
      1. com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1143)
      1 frame
    7. com.ibm.ws
      ServletWrapper.initialize
      1. com.ibm.ws.wswebcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:159)
      1 frame
    8. com.ibm.wsspi
      WebExtensionProcessor.createServletWrapper
      1. com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:99)
      1 frame
    9. WebSphere
      WebApp.commonInitializationFinish
      1. com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:790)
      2. com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:470)
      3. com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:307)
      3 frames
    10. com.ibm.ws
      WebContainer.addWebApplication
      1. com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:334)
      2. com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:90)
      3. com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157)
      4. com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:665)
      5. com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:618)
      5 frames
    11. WebSphere
      ApplicationMgrImpl$AppInitializer.run
      1. com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:395)
      2. com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:611)
      3. com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1302)
      4. com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1165)
      5. com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:587)
      6. com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:832)
      7. com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:951)
      8. com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2129)
      8 frames
    12. com.ibm.wsspi
      WsComponentImpl$_AsynchInitializer.run
      1. com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:342)
      1 frame
    13. com.ibm.ws
      ThreadPool$Worker.run
      1. com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
      1 frame