[jboss-user] [Installation, Configuration & Deployment] - Classloader bug with java2parentdelegation in JBoss 5.x?

[ops]

Hi,
I tested the following using JBoss 4.2.2.GA. I deployed some utility classes in server/default/lib and also in my application configured with java2parentdelegation=true. The application has a scoped loader repository. In fact, the classes stored in lib are only used, if they were loaded to the default UnifiedLoaderRepository before. This behaviour is exactly as described in the classloader wiki. BUT! If I test the same szenario with JBoss 5.1.0.GA, there is a strage thing happening: If the class was not loaded to the standard UnifiedLoaderRepository before, it is loaded into it now and used.
If I understood the class loading model right, this is a contradiction to the java2parentdelegation flag, wich means that classes from the standard repository are only used in scoped applications, if they were loaded to the standard repository before. In any other case the scoped application has to load the classes itself. 

What do you experts think?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4267789#4267789

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4267789