Thanks Matt! I have indeed spotted the following line: // TODO: 2.2+ use this annotation for all @Plugin classes
Right now I am sitting on the fence whether I shall address my issue with extending the plugin system or rather implement a MySingletonBeanFactory interface extending from Comparable<MySingletonBeanFactory> and @Plugin-annotate those factories. Food for thought... It is 22:50 here, time to sleep. On Mon, Mar 8, 2021 at 10:42 PM Matt Sicker <boa...@gmail.com> wrote: > There's an @Order annotation that's only supported for > ConfigurationFactory plugins that you could extend for arbitrary > plugins perhaps? > > On Mon, 8 Mar 2021 at 15:24, Volkan Yazıcı <volkan.yaz...@gmail.com> > wrote: > > > > I am working on migrating statically bound JsonTemplateLayout resolvers > to > > plugins. There certain types of resolvers need to have a single > > implementation. When a user provides a custom plugin which implements the > > same footprint as the singleton one, I need a way to prefer one over > > another. I am not sure if this is the right way of thinking, but... if > I'd > > be doing this in Spring, I'd probably use @Primary or @Order. I can > > introduce my own @PluginOrder annotation, but I had the impression that > > this might have a wider audience. What do you think? >
