[jboss-jira] [JBoss JIRA] Commented: (JBAS-6580) org.jboss.test.web.test.JSFIntegrationUnitTestCase

[Dimitris Andreadis (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-6580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12456486#action_12456486 ] 

Dimitris Andreadis commented on JBAS-6580:
------------------------------------------

We have applied the latest logging libs that enable the setting of JDK levels in jboss-log4j.xml

org.jboss.logging:org.jboss.logging:2.0.6.GA
org.jboss.logbridge:jboss-logbridge:1.0.0.CR3
org.jboss.logmanager:jboss-logmanager:1.0.0.CR2

The default level for JSF is INFO:
...
   <!-- Set the logging level of the JSF implementation that uses
      | java.util.logging. The jdk logging levels can be controlled
      | through the org.jboss.logging.log4j.JDKLevel class that
      | in addition to the standard log4j levels it adds support for
      | SEVERE, WARNING, CONFIG, FINE, FINER, FINEST
   -->
   <category name="javax.enterprise.resource.webcontainer.jsf">
     <priority value="INFO" class="org.jboss.logging.log4j.JDKLevel"/>
   </category>

Also I've disabled JBossJSFConfigurationListener's own log bridging:

// JBAS-6475, with the update to jboss-log-bridge this is not need
//        // If the pluginClass is not set, assume Log4J
//        if (System.getProperty("org.jboss.logging.Logger.pluginClass") == null) 
//        {
//            setLog4J();
//            setLog4JForFacelets();
//        }

And enabled the dynamic setting of JDK log levels through Log4jService.java. For those levels to be propagated to the JUL side you need to tell the service to reconfigure() itself.

Now, with all those changes in place there shouldn't be any need for JSF to bridge logging.

However, I cannot get JBCTS-903 to work, and I can verify that the log level for javax.enterprise.resource.webcontainer.jsf is set to INFO.

The testsuite JSFIntegrationUnitTestCase needs also to be changed. The Log4jService can now understand the setting of JDK log levels (again you need to reconfigure() it).

Assign back to Stan to look at.

> org.jboss.test.web.test.JSFIntegrationUnitTestCase
> --------------------------------------------------
>
>                 Key: JBAS-6580
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6580
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JSF
>            Reporter: Shelly McGowan
>            Assignee: Stan Silvert
>             Fix For: JBossAS-5.1.0.Beta1
>
>
> Stan, can you identify the root cause of these failures and impact on Beta1 release.
> Testcase: testFaceletsLogging took 0.683 sec
>         FAILED
> null
> junit.framework.AssertionFailedError
>         at org.jboss.test.web.test.JSFIntegrationUnitTestCase.testFaceletsLogging(JSFIntegrationUnitTestCase.java:134)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)
> Testcase: testJSFIntegrated took 1.288 sec
>         FAILED
> null
> junit.framework.AssertionFailedError
>         at org.jboss.test.web.test.JSFIntegrationUnitTestCase.testJSFIntegrated(JSFIntegrationUnitTestCase.java:95)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira