[JBoss OSGi Development] - JBoss OSGi logging policy
by thomas.diesler@jboss.com
Logging in JBoss OSGi is done through multiple logging frameworks. There are bundles that use commons-logging, slf4j and of course jboss-logging. Ultimately all logging is routed to log4j.
For surefire tests this is the same.
Every (reactor) module contains a log4j configuration in
| src/test/resources/log4j.xml
|
All surefire tests MUST write their their test log to
| target/test.log
|
This file is processed by hudson jobs after the surefire test run.
The log4.xml files contain these settings
| <appender name="FILE" class="org.apache.log4j.FileAppender">
| <param name="File" value="${log4j.output.dir}/test.log"/>
| ...
| </appender>
|
| <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
| <param name="Target" value="System.out" />
| <param name="Threshold" value="INFO" />
| ...
| </appender>
|
| <root>
| <!--appender-ref ref="CONSOLE"/-->
| <appender-ref ref="FILE"/>
| </root>
|
There are many projects under the JBoss OSGi umbrella. For log file consistency and meaningful hudson console output, please respect this policy and do not change the log configuration light heartedly.
cheers
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264426#4264426
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264426
14 years, 6 months
[JBoss Microcontainer Development] - Re: Testing Deployers with new Reflect + ClassPool
by alesj
"flavia.rainone(a)jboss.com" wrote : "alesj" wrote : I guess this calls for a test that would create a CL from -beans.xml,
| | and see if the Classpools still work.
| | Flavia, will you create one or should I, and you just fix the issues if they are present?
| |
| You can go ahead and create one, as I think this will be faster.
This is done now - see TypeInfoTest and ClassPoolTestCase.
I've left a TODO in ClassPoolTestCase for you:
| try
| {
| Object anys = assertBean("AnyServlet", Object.class);
| Class<?> anysClass = anys.getClass();
| ClassLoader anysCL = anysClass.getClassLoader();
|
| DeploymentUnit du = getMainDeployerStructure().getDeploymentUnit(deployment.getName(), true);
| ClassLoader cl = getClassLoader(du);
|
| assertNotSame(cl, anysCL);
|
| // TODO - Flavia, apply ClassPool tests
| }
|
And once you delete assert(Not)Equals in JavassistTypeInfoTestCase,
we'll see how this works with your patch.
Currently both types - introspection and javassist - work for this test.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264359#4264359
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264359
14 years, 7 months