Is JBoss 3.2.6, 3.2.7 and any version of JBoss 4.x had a solution to this "commons-logging" problem?
I needed to do a hacked version of beanutils, and put it in my EAR file, "sealing" it in the jboss-app.xml using the following configuration: <loader-repository> | beanutils.commons.apache.org:loader=ACSDeploy.ear | <loader-repository-config>java2ParentDelegation=false</loader-repository-config> | </loader-repository> This worked properly, but then I faced the problem with commons-logging, and came to this post. Is there already a solution, better than removing the jar from my EAR file ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872658#3872658 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872658 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
