On 28/04/20 18:47, roccom wrote: > Upgrading to a newer version fixed this for us. We were on 2.1.2 and now are > on 2.1.5. I think this issue was reported and fixed in 2.1.3. Glad to hear this. Regards.
-- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
