The configurer I'm working on as today are only supposed to post-process our spring-boot auto magics so there's not side effects for a end user but yes it could be extended later on to any component/language/dataformat in the registry. And yes I'm also taking into account an option to enable/disable configurer on different level (always in spring boot), i.e. disable all configurer for a component/language/dataformat or just disable a single one.
Let me see what we can have and how it works in this first round then we can discuss the next steps. --- Luca Burgazzoli On Thu, May 18, 2017 at 9:31 AM, Zoran Regvart <zo...@regvart.com> wrote: > 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
