On Sun, 2005-12-11 at 09:56 -0800, Wade Chandler wrote: > --- robert burrell donkin > <[EMAIL PROTECTED]> wrote:
<snip> > > if you want to understand why people complain, stick > > around and help us > > with the development ;) > > > > it's a small library but a difficult subject. we > > need more eyes and more > > hands with energy for the problem... > > > > - robert > > > > > > > So what are the biggest complaints? Is there a list > of the most complained about issues some where? Is > the only complaint that someone needs to configure a > propeties file, or is it that they have to add a few > more kilobytes to their application? I would be glad > to help where I can. Is there a page on the dev site > about current issues or the complaints? there is really but one issue: automagic configuration in complex classloaders has a tendency to throw exceptions. throwing runtime exceptions is sort-of-theoretically-the-right-thing-to-do (from a security perspective) but is also very bad thing for any deep library to do. the consensus now (however) is that the practical security gains are negligible. 1.1 is better than previous versions but there are number of configurations which the various specifications ensure that JCL cannot function. for the vast majority of these there are slight changes that can be made to the configuration which will allow JCL to run fine. what's really needed is a troubleshooting guide which tells people who get into difficulties how they can fix stuff. since there are very few even half-decent introductions to practical classloading, we added one here: http://jakarta.apache.org/commons/logging/tech.html. we also spent quite a lot of time working on a systematic approach (with code) to the various permutations possible with standard classloader configurations. a reasonable troubleshooting guide could be based on that. help with that guide would be very useful. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
