Hi, On Tue, Sep 18, 2012 at 11:40 AM, Michael Dürig <[email protected]> wrote: > I think we should unify the approach and extend it to other areas where > applicable. The advantages are that there is no code duplication for > functionality required in oak-jcr and oak-core and that these classes can be > instantiated ad hoc without the need for passing instances of these around.
+1 This approach already opened up a chance to simplify some of the name validation code in .oak.plugins.name (no need for the extra Namespaces utility class), on which I'm just now working. BR, Jukka Zitting
