Re: classloader issue

Hi Leonardo, Happy new year to you as well. For your issue it depends the classes, ee classes (spec jars) should almost all be filtered. That said the classloading can be controlled using openejb.classloader.forced-[load|skip] = my.package,my.other.package in conf/system.properties Romain Man

Re: Classloader issue

Hi, that's some slight optimizations pushed years ago, not sure it is still relevant today to do it. In fact it mainly depends libs, for disgester that's the real first time we have an issue because of it - i have to admit i didnt dig in your case so can't say really more. *Romain Manni-Bucau*

Re: Classloader issue

Hi, It was strange, I could not reproduce the initial issue on my computer. It turned out it was because I had TomEE 1.5.0 JAX-RS, while the other guy had 1.5.1 JAX-RS. Once I updated to 1.5.2, the issue appeared. The fix you have provided: openejb.classloader.forced-load=org.apache.commons.digeste

Re: Classloader issue

it forces to load the matching classes (that's a prefix) from the webapp first you can update the page normally if you want to contribute this doc to the site *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/*

Re: Classloader issue

What does it do? It is not present in documentation page: http://tomee.apache.org/properties-listing.html Will check that ASAP. Thanks, Witold Szczerba On 6 May 2013 14:03, Romain Manni-Bucau wrote: > Hi > > maybe try adding in conf/system.properties: > > openejb.classloader.forced-load=org.apa

Re: Classloader issue

Hi maybe try adding in conf/system.properties: openejb.classloader.forced-load=org.apache.commons.digester *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin