I think this sounds reasonable, but could you be more specific about your use case, and the way it could be used inside Pivot?
Thanks, ~Roger -----Original Message----- From: Sandro Martini [mailto:sandro.mart...@gmail.com] Sent: Thursday, September 11, 2014 9:14 AM To: dev@pivot.apache.org Subject: Loading of classes via Service Provider Hi all, for some developments I'm doing in other projects I'm using the standard Java ServiceLoader to be able to automatically load multiple implementations of a given class/interface name, for a plugin-like system. In Pivot there is a similar thing: the class Service, doing all in our code without using Java ServiceLoader for better flexibility, but loading only 1 implementation (the first found in classpath) of the given class/interface name. I think it could be a good addition the ability to: - handle more than 1 file META-INF/services/ ... if possible - find/load more than 1 implementation (if found) with this we could set some basis for a plugin-like component system, or maybe for something like auto-discovery of Components and auto-registering ... and probably other n things :-) . These new features could expand existing Service class, and retrofit (update but in a compatible way) its existing behavior. Other approach would require classpath scanning (like Spring and many other frameworks) but in a complex way, probably too much for our requirements here. What do you think ? Bye, Sandro
