Whitney Sorenson created CURATOR-152:
----------------------------------------
Summary: NamespaceFacade does not provide access to underyling
client
Key: CURATOR-152
URL: https://issues.apache.org/jira/browse/CURATOR-152
Project: Apache Curator
Issue Type: Improvement
Components: Framework
Reporter: Whitney Sorenson
Priority: Minor
NamespaceFacade throws UnsupportedOperationException on close() and start().
This is impractical for the case where NamespaceFacade is being used as the
only CuratorFramework available to an application. Clients are left to either:
- Make a separate binding for underlying curator framework
- Use reflection to access underlying client
- Reimplement Namespace functionality in their own code
None of these are ideal or necessary. The NamespaceFacade should allow close to
be called on the underlying client or should allow access to the underlying
client for this type of use case. Since it previously threw an exception,
proxying the close call to the underlying client would not break existing users.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
