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=37484>. 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=37484 ------- Additional Comments From [EMAIL PROTECTED] 2006-02-13 22:46 ------- Sadly, there are no silver bullets. It's very easy to complain but much more difficult to understand the problem in detail. So, I should probably thank you know for being one of the tiny minority who step up and help :) JCL is incredibly widely used. This makes things very difficult. The issue for JCL is (and has always been) that the J2EE classloading specifications are broken. Static binding has it's own limitations. It also has it's own issues. The vast majority of problems experienced by users are caused by having JCL jars in different classloaders they are not aware of. Static binding will not solve this problem. Dynamic binding addresses application isolation in well behaved containers in a fashion that is impossible for compile time static binding. Application isolation should be possible by using byte code engineering to perform static binding but that has it's own set of issues. So, no silver bullets but maybe we can make things a little less painful... -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
