[Converter] Flexible Adpater Rule convert A to X and vice versa

2016-08-19 Thread Stefan Seifert
we want to use the converter service as part of the sling context-aware configuration, and started with a first implementation. [1] in sling we have a special form of map (a ValueMap) which supports additional features like typed access (with a resource provider-specific conversion magic under

Re: [Converter] Flexible Adpater Rule convert A to X and vice versa

2016-08-22 Thread David Bosschaert
Hi Stefan, I see the use-case and in a different context I also came across a use-case for 'wildcards' in the rules. I think this would be a good feature. I'll try to prototype something for that over the coming few days and ping back here once I have something to try out. Cheers, David On 19 A

Re: [Converter] Flexible Adpater Rule convert A to X and vice versa

2016-08-23 Thread David Bosschaert
Hi Stefan, I have prototyped more flexible adapter rules a little bit and committed the current state to the Converter codebase. The adapter now tries to find the most specific adaptation rule available for a given conversion, but it walks up the class hierarchy. So you could specify that you wan

RE: [Converter] Flexible Adpater Rule convert A to X and vice versa

2016-08-23 Thread Stefan Seifert
ay, August 23, 2016 5:12 PM >To: dev@felix.apache.org >Subject: Re: [Converter] Flexible Adpater Rule convert A to X and vice >versa > >Hi Stefan, > >I have prototyped more flexible adapter rules a little bit and committed >the current state to the Converter codebase.