yes, we could definitly think about this. one is already exposed as part of the management API https://github.com/apache/sling/blob/trunk/bundles/extensions/caconfig/impl/src/main/java/org/apache/sling/caconfig/management/ContextPathStrategyMultiplexer.java
if we you think we should expose others (or all) as well please open a JIRA ticket. stefan >-----Original Message----- >From: Nicolas Peltier [mailto:npelt...@adobe.com] >Sent: Friday, January 6, 2017 11:57 AM >To: users@sling.apache.org >Subject: [caconfig] shouldn't multiplexers be exposed? > >Hi, > >right now ContextPathStrategyMultiplexer (and other multiplexers) are in >impl package, and thus only accessible within the bundle. > >However iiuc those multiplexers are the ones you call to use the interface >API regardless of which the implementation is. > >If in an application i want to implement let say a custom >ConfigurationResourceResolvingStrategy, i might need the >ContextPathStrategyMultiplexer API to >use findContextResources, but i (think) i can’t right now? > >Nicolas
