Please note that this behavior change has nothing to do with eXo JCR


On Fri, May 3, 2013 at 8:42 AM, Christophe Laprun <claprun@redhat.com> wrote:
On 05/02/2013 08:28 PM, Nicolas Filotto wrote:
It is actually a configuration issue more details here
https://jira.exoplatform.org/browse/JCR-2163

Thank you for the information. Good to know. This is a little troubling, though, because that exact same configuration used to work with EAP 6, meaning that people will need to update their configurations to be able to run on EAP 6.1. Luckily, this is just a minor change but we definitely need to document it somewhere.


--
Cordialement / Best,
Chris

Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow GateIn: http://blog.gatein.org / http://twitter.com/gatein
Follow me: http://metacosm.info/metacosm / http://twitter.com/metacosm