HONEYCOMB-122 Update reader registry to share similar APIs as writer

+ 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>

1 files changed, 3 insertions, 2 deletions

diff --git a/v3po/translate-utils/src/main/yang/translate-utils.yang b/v3po/translate-utils/src/main/yang/translate-utils.yang
index 2c00bb548..b543bba0d 100644
--- a/v3po/translate-utils/src/main/yang/translate-utils.yang
+++ b/v3po/translate-utils/src/main/yang/translate-utils.yang
@@ -18,6 +18,7 @@ module translate-utils {
     identity delegating-reader-registry {
         base config:module-type;
         config:provided-service tapi:honeycomb-reader-registry;
+        config:provided-service tapi:honeycomb-reader-registry-builder;
         config:java-name-prefix DelegatingReaderRegistry;
     }
 
@@ -25,11 +26,11 @@ module translate-utils {
         case delegating-reader-registry {
             when "/config:modules/config:module/config:type = 'delegating-reader-registry'";
 
-                list root-readers {
+                list reader-factory {
                     uses config:service-ref {
                         refine type {
                             mandatory true;
-                            config:required-identity tapi:honeycomb-reader;
+                            config:required-identity tapi:honeycomb-reader-factory;
                         }
                     }
                 }