[
https://issues.apache.org/jira/browse/FELIX-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852851#comment-16852851
]
David Bosschaert commented on FELIX-5678:
-----------------------------------------
Hi [~dleangen] somehow I think that a merger is fundamentally different to a
converter, albeit the case that it may be easy to implement a deep merger with
the help of the converter. So to me it sounds like a separate component.
I have to admit, I have not really had the need for a deep merger myself that
often, but that doesn't mean others don't need it.
I would suggest discussing it on one of the Felix mailing lists (for increased
visibility) and maybe get an initial implementation started in Felix? Maybe we
can take it from there?
Oh, and BTW it's certainly not too early for OSGi R8 proposals :)
> Allow merging of objects
> ------------------------
>
> Key: FELIX-5678
> URL: https://issues.apache.org/jira/browse/FELIX-5678
> Project: Felix
> Issue Type: Bug
> Components: Converter
> Reporter: David Leangen
> Priority: Major
>
> Given a typed object O1 and a "partial" representation of an object O2 (for
> instance in the form of a Map), allow O2 to be merged into O1.
> Example:
> {code}
> public class Foo {
> public String a;
> public String b;
> public String c;
> }
> Foo f = new Foo();
> a = "Eh!";
> b = "Be cool.";
> c = "See you later?";
> Map<String, String> m = new Map<>();
> m.put("b", "Be there or be square");
> Foo f2 = Converter.convert(f).merge(m);
> {code}
> I am sure there are many ways to skin this cat.
> If the Converter API cannot be changed, what would be the best way to tackle
> this problem?
> (In the meantime, while awaiting comments form [~bosschaert], I'll try to run
> a few experiments to see if I can come up with something reasonable.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
