Has anybody got any good ideas for a way to disable ECAS from triggering
without commenting them out from the core code?

Like overriding the service definitions in hot-deploy it would be handy to
be able to clear any ECAs that are listening on a particular service call
or entity update from within the custom code.

Any thoughts?

-- 
Rupert Howell

Provolve Ltd
Front Office, Deale House, 16 Lavant Street, Petersfield, GU32 3EW, UK

t: 01730 267868 / m: 079 0968 5308
e:  [email protected]
w: http://www.provolve.com

Reply via email to