curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cameron McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CURATOR-68) Namespace is not stripped off events generated via a NamspaceFacade
Date Mon, 21 Oct 2013 00:47:41 GMT

     [ https://issues.apache.org/jira/browse/CURATOR-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Cameron McKenzie updated CURATOR-68:
------------------------------------

    Attachment: NamespaceTest.java

Simple test to reproduce. Just replace the ZK_CONNECT_STRING with an appropriate connect string
and run.

Depends on log4j and curator libraries.

> Namespace is not stripped off events generated via a NamspaceFacade
> -------------------------------------------------------------------
>
>                 Key: CURATOR-68
>                 URL: https://issues.apache.org/jira/browse/CURATOR-68
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 2.2.0-incubating
>         Environment: Should be reproducable in any environment. Has been reproduced running
on Windows 7 and Solaris 10.
>            Reporter: Cameron McKenzie
>            Priority: Minor
>              Labels: namespace
>             Fix For: awaiting-response
>
>         Attachments: NamespaceTest.java
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> When a namespace is defined via the CuratorFrameworkFactory.Builder methods, paths for
events generated by the CuratorFramework have the namespace stripped off them.
> When using a NamespaceFacade, the paths for generated event paths include the namespace.
> This appears to be due to the implementation of the Watcher() interface in the constructor
of the CuratorFrameworkImpl class. It attempts to remove the namespace from events before
passing them to CuratorListener instances. In the case where the namespace is defined by the
builder (and is thus part of the base CuratorFramework instance) this works fine. In the case
where a NamespaceFacade is being used then the namespace of the base CuratorFramework instance
is used instead of the namespace of the NamespaceFacade).
> I will attach a simple test case to reproduce



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message