Hide Forgot
project_key: SOA Main LOG4J config file - jboss-log4j.xml - uses <category> elements for logger definition, Teiid comes with newer <logger> elements for particular logger definition. If customer installs Teiid into SOA-P then he gets two different logger definitions in jboss-log4j.xml - LOG4J config file contains both <category> and <logger> elements.
Candidate, not committed for 5.2
Link: Added: This issue Cloned to SOA-3268
Release Notes Docs Status: Added: Documented as Resolved Issue Writer: Added: dlesage Release Notes Text: Added: https://issues.jboss.org/browse/SOA-3202 The main LOG4J configuration file, jboss-log4j.xml, used category elements for the logger definition. EDS cames with newer logger elements for particular logger definitions. Thus, if the customer installed EDS on the SOA-P he or she would have two different logger definitions in the jboss-log4j.xml file. These settings have now been unified so there is no longer any conflict between them.
This issue has been verified in ER4 build. EDS components (Teiid and Modeshape) now use 'category' elements for logger definitions.