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

JSFDeploymentProcessorTestCase fails with Faces 4

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 29.0.0.Final
    • None
    • JSF
    • None

      If JSFDeploymentProcessorTestCase is run against WFP or my WFLY-16432 branch, it fails:

      <testcase name="facesConfigXmlTest" classname="org.jboss.as.test.integration.jsf.version.JSFDeploymentProcessorTestCase" time="0.432">
          <error type="java.lang.NullPointerException">java.lang.NullPointerException
      	at java.base/java.lang.String.contains(String.java:2036)
      	at org.jboss.as.test.integration.jsf.version.JSFDeploymentProcessorTestCase.facesConfigXmlTest(JSFDeploymentProcessorTestCase.java:214)
      

      The NPE is because the HTTP response has no entity.

      Perhaps part of the problem is the WFLY-16527 issue, although I don't see any logging to indicate that. (I say perhaps it's relevant because I don't see anything that would enabled CDI for the test deployment.)

      I don't think this test would work anyway because it uses FacesContext.class.getPackage().getSpecificationTitle() and with Faces 4 that returns null, since the Faces 4 API MANIFEST.MF is largely empty (which seems like an API bug.) Perhaps on the server side that is part of why the response has no entity.

      Note that the test doesn't check the HTTP response code. I assume the lack of response entity is because it's not a 200.

              jaslee@redhat.com Jason Lee
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: