Hi, On 5 September 2017 at 07:55, Francesco Mari <mari.france...@gmail.com> wrote:
> On Mon, Sep 4, 2017 at 6:18 PM, Ian Boston <i...@tfd.co.uk> wrote: > > Do you mean: > > keep the OakConversionService but put all the logic to convert from a > > Value to a URI inside that implementation using new Oak SPI/APIs if > > necessary and drop the AdapterManager completely ? > > Yes. I think there is no need to provide a generic adapter-like > implementation to solve this use case. > > > This would mean something the datastore implementation implements which > > oak-core can navigate to would have to implement a mix in interface with > a > > getURI() method. I am not certain what or how without trying to do it. > > > > Would that address your concern here ? > > I think it's worth trying. Thanks for bringing the conversation forward. > I will create 2 new branches. 1 with no adapter manager relying on mixin interfaces and one with a non OSGi adapter manager plugin pattern. Thanks for the input. Best Regards Ian
