-
Bug
-
Resolution: Done
-
Major
-
4.1.0.CR2
-
Low
This is temporary, until ISPN-518 is closed. After that, lock() and deadlock detection should be allowed again.
This needs to be disallowed in 2 places:
1) Declarative, implicit eager locking, in ConfigurationValidatingVisitor
2) Programmatic, explicit eager locking using the AdvancedCache.lock() API
should throw a ConfigurationException in both cases, with a message pointing to ISPN-518.