commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34185] - Requirement: Combine JCL and UGLI
Date Fri, 25 Mar 2005 21:40:54 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34185>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34185





------- Additional Comments From rdonkin@apache.org  2005-03-25 22:40 -------
FWIW issues like this have been discussed at length on the jakarta commons list.
I thought it might save a little time if I were to point out the tricky bit of
any JCL redesign.

The key design mistake made when JCL was created was not the much-malined
dynamic discovery mechanism, it was the fact that LogFactory is too tightly
coupled to the discovery mechanism. It would be possible to extract an interface
modelled as an abstract superclass containing the user-facing API from
LogFactory and retrofit a minimal implementation lookup mechanism with no
complex discovery. This would allow refitting of new binding mechanisms whilst
maintaining backwards compatibility. 

Had the storm not blown up about the current JCL implementation, this was the
direction which the JCL2 codebase would have taken. 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message