This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Currently there is only one method allowing to set keys replacing original keys. It implies some rather heavy computaion that is unnecessary if client knows that it want to append new keys or remove existing keys without any merging. /** * appends mentioned keys to existing key set */ protected final appendKeys(Object[] keys); and (not so important) method protected final removeKeys(Object[] keys);
It could be called addKeys() and driven by setBefore() strategy too.
Children.Keys is already bloated enough and we can't make it into 3.6 anyway, so I'd rather refuse this and suggest to use some lightweight Children subclass after issue 32708 gets finished and merged, especially in case of strict 1:1 mapping.
I though about implemeting my own children but I have not found any way how to notify about change. There is probaly some package private contract.
Yes, this is why I referred to 32708 (and issue 35833).
I agree.
I like issue #32708 approach. *** This issue has been marked as a duplicate of 32708 ***