1. It's in the curator-client project, not curator-framework (i.e. it's low level) 2. Because of namespaces, users should call CuratorFramework.newNamespaceAwareEnsurePath() instead of directly allocating an EnsurePath object.
-JZ On Sep 16, 2013, at 1:55 PM, John Vines <[email protected]> wrote: > Is there a particular reason the EnsurePath constructor takes in > CuratorZookeeperClient instead of a CuratorFramework like a lot of the > other curator items? I thought about making a ticket, but I figured it was > better to ask first.
