Great discussion :) On Thu, May 18, 2017 at 9:24 AM, Nicola Ferraro <ni.ferr...@gmail.com> wrote: > I wonder (before this goes too far and we add more stuff) if we should add > a easy way to disable a configurer (also a configurer defined by Camel).
I think that if this is all at configuration time (before component starts), then you have an option to opt-out by not including the configurer on the classpath and to provide your own configurer that rollbacks prevous configurer's changes; so perhaps just something like Ordered interface in Spring? zoran -- Zoran Regvart
