-----Original Message----- From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Scott M Stark Sent: Tuesday, January 23, 2007 1:31 AM To: JBoss.org development list Subject: Re: [jboss-dev] Re: Commons-logging upgrade Its required in general to avoid java ee classes from being visible. Specificially for the jcl classes, it should not be required. I'm hesitant to say it can be dropped though since the problem is a function of the runtime class loader hierarchy that shows up for the various component creation/initial use patterns. I guess I need to reproduce the original issue to understand why its not happening now. Brian Stansberry wrote: > jboss-development-bounces(a)lists.jboss.org wrote: ... > > Yes. I didn't mean to imply the late binding patch no longer had > value; just that allowing the loading of JCL classes from the war > removes a large category of cases where it is needed. I also wanted to > hijack the thread a bit to get into whether the FilteredPackages was still needed. > :-) > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development