Thanks Chris,<br><br>you&#39;re right, I found my mistake: I had a file in the classpath with the same name of the one contained in the jar, so it was loading that file instead of the one in the jar.<br>I just changed the name of the file and then I&#39;ve been able to reproduce that issue. I also checked that the fix you suggested works perfectly.<br>
<br>I pushed that fix on the master (but using my test since it is a bit easier and doesn&#39;t require a change in the pom.xml) and backported it to the 5.4.x.<br><br>Mark, should I backport it to other (older) releases?<br>
<br>Mario<br>