Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 999668

Summary: EAP62_2010 - [RFE] Logging Unification (JBoss Modules)
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Brian Stansberry <brian.stansberry>
Component: Class LoadingAssignee: David M. Lloyd <david.lloyd>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: cdewolf, dandread, david.lloyd, nziakova, pkremens
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:45:27 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brian Stansberry 2013-08-21 19:57:27 UTC
Tracker issue for JBoss Modules portion of EAP62_2010 Logging Unification.

ANDIAMO-7 compliance.

Comment 1 David M. Lloyd 2013-09-10 13:43:08 UTC
Still working on a viable solution.

Comment 2 David M. Lloyd 2013-09-17 21:46:29 UTC
Cannot be fixed for 6.2.

Comment 3 Dimitris Andreadis 2013-09-25 15:53:30 UTC
Hey David, can you provide some justification on why this will be deferred, (or will not be done at all?). Thanks.

Comment 4 David M. Lloyd 2013-09-25 16:11:03 UTC
It's a technical problem.  Our i18n logging solution requires jboss-logging; jboss-logging is not available to jboss-modules because it is loaded *as* a module, so jboss-modules cannot link directly against it.  JBoss Modules also has an internal logging API which is designed to accommodate the logging system initializing after the module system bootstraps; this API also constrains how the logging implementation can be implemented, so to change that somehow would break compatibility, which is a consideration for any proposed solution.

So far I do not have a workable solution to this problem, so it cannot be fixed until a solution presents itself.

Comment 5 Dimitris Andreadis 2013-09-25 16:27:36 UTC
So, it's a chicken-egg problem, thanks.

Comment 6 David M. Lloyd 2013-09-25 16:29:59 UTC
Exactly.  I have a couple ideas but I don't know if they're really workable, but I do know it can't be done by 6.2 in any case.