Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-15319

Fix JSFDeploymentProcessorTestCase failure with SE 17 and security manager enabled

    XMLWordPrintable

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Done
    • None
    • 25.0.0.Final
    • None

    Description

      JSFDeploymentProcessorTestCase fails with the following exception with SE 17 and with the security manager enabled:

      org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy bundled-jsf.ear: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"bundled-jsf.ear\".\"bundled-jsf-webapp.war\".undertow-deployment" => "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&gt;org.apache.myfaces.webapp.StartupServletContextListener</listener-class&gt;
      </listener>
      
          Caused by: 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.
      
      Caused by: org.xml.sax.SAXParseException; systemId: file:///store/work/tc-work/b10fef355372d849/testsuite/integration/basic/META-INF/standard-faces-config.xml; lineNumber: 28; columnNumber: 87; Error at line 28 char 87: String index out of range: 2
        at deployment.bundled-jsf.ear.bundled-jsf-webapp.war//org.apache.commons.digester.Digester.createSAXException(Digester.java:3181)
        at deployment.bundled-jsf.ear.bundled-jsf-webapp.war//org.apache.commons.digester.Digester.createSAXException(Digester.java:3207)
        at deployment.bundled-jsf.ear.bundled-jsf-webapp.war//org.apache.commons.digester.Digester.endElement(Digester.java:1225)
      

       

      Attachments

        Issue Links

          Activity

            People

              fjuma1@redhat.com Farah Juma
              fjuma1@redhat.com Farah Juma
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: