Affects Version/s: 2.0.0-M2
Fix Version/s: 2.0.0-M3
A more general question re: plugins ... what is it about them that means that they can't be implemented as regular services, with Spring finding the implementation using classpat scanning?
Is it that we need to load them before Spring?
ie using ServiceLoader or similar?
Not challenging the design, just want to be able to write some sensible docs about it
Let me check this first ...
I think we have these, that use ServiceLoader mechanics:
Its likely we could convert 2-7 to service beans, with 1. I need to check the rational ...
I think we should do that, then.
I believe with (1) its also possible now to convert it to a service. It was not possible when the ServiceLoader introspection was run during the post-construct phase, but I changed that to now run after the post-construc pahse, when all the services are discovered and initialized.
OK, that would then be a very nice place to get to... the whole framework is just a bunch of Spring-loaded beans.
yep I agree
I think it also means that there isn't really any concept of plugins ... or at least, any of these service beans could be replaced by a different implementation with a higher @Order( if required.