We can do it either way. Of the ones I converted to using Integrators, search
and envers both have "skip" settings defined.
search: hibernate.search.autoregister_listeners
envers: hibernate.listeners.envers.autoRegister
(should really standardize these names)
I guess it really depends on the intention here as to whether we should
disable all of them.
Max, not sure about "much more configuration" here. The whole point of
Integrator here is that the listener regsitration is automatically handled
now. The Envers one is even smart enough to not regsiter its listeners if its
not needed.
Anyway, we currently have the above 2 settings to help you with the specific
things you asked. If you want a "global, do not process any Integrators"
flag, let us know. Its easy enough either way...
On Thursday, March 31, 2011, at 03:30 pm, Emmanuel Bernard wrote:
There is one for search too. But should we have a global flag to
disable
all integrations? Does it makes sense (what about Bean Validation for
example?
On 31 mars 2011, at 20:08, Adam Warski wrote:
> On Mar 31, 2011, at 12:05 PM, Max Rydahl Andersen wrote:
>> btw. any way to disable specific discovery items ?
>> i.e. I would like to not have search and envers enabled when the tools
>> are doing query plans/executions since it then suddenly requires much
>> more configuration to have it setup and run.
>
> There's a
>
> hibernate.listeners.envers.autoRegister
>
> config property, is that what you need?
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
---
Steve Ebersole <steve(a)hibernate.org>
http://hibernate.org