summaryrefslogtreecommitdiffstats
path: root/v3po/data-impl/src/main/java/io/fd/honeycomb/v3po/data/impl/ModifiableDataTreeDelegator.java
AgeCommit message (Collapse)AuthorFilesLines
2016-07-29HONEYCOMB-130: Separate v3po plugin from HC infraMaros Marsalek1-236/+0
Creating folders: - common/ - infra/ - v3po/ - vpp-common/ Change-Id: I2c39e1b17e39e7c0f0628f44aa5fe08563fa06e4 Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
2016-07-21HONEYCOMB-122 Update reader registry to share similar APIs as writerMaros Marsalek1-2/+2
+ Extract common registry builder base code (Reader registry is not flat, so there is not full control over ordering as with writers but it is sufficient) + Split CompositeReader into CompositeReader, SubtreeReader and GenericReader + No need to build composite structure in ReaderFactories (registry does that internally) + Keep only ReaderCustomizer + ListReaderCustomizer, no root reader (same for writers) Change-Id: Ic4e5bc96ad47a6cbcada4efcc2209db5c16d2a6c Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
2016-07-13HONEYCOMB-94 Reimplement writer registry with better ordering optionsMaros Marsalek1-168/+60
Now the registry is flat and allows for full control of writer execution order Change-Id: I864e1d676588ffe59b596145e0829e81b1a1ed2f Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
2016-06-23HONEYCOMB-92 Ignore empty modifications for e.g. empty presence containersMaros Marsalek1-22/+22
Change-Id: I565686dbd2474fffbfea4e8cc837861845723bda Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
2016-06-15HONEYCOMB-92: Process modifications recursivelyMaros Marsalek1-15/+185
+ Fix update subtree, child writer lookup + Change initializers operation to merge Change-Id: I6ece7eb3d17d5a0b4a413189ddd383567d7e2270 Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
2016-05-24HONEYCOMB-61: Fix outstanding issuesMaros Marsalek1-3/+3
Change-Id: I2dec6bbd8db656663029ad0f59da1b583c890565 Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
2016-05-23HONEYCOMB-61: Add BA broker for context data treeMaros Marsalek1-0/+174
With broker, context data can be accessed in a transactional manner, same as config data + Renamed data-api concepts to not include DataTree + Renamed context related concepts to better distinguish between them + Now passing full ReadContext to read customizers + Naming context is backed by context data broker Change-Id: I0b2876dd74a31a9ced7d9b5145672868e12f8b82 Signed-off-by: Maros Marsalek <mmarsale@cisco.com>