]
Paul Ferraro updated WFCORE-692:
--------------------------------
Summary: read-children-names(include-aliases=true) can return phantom results (was:
read-children-names(include-aliases=true) can return phantom results if another resource
exists with the same key)
read-children-names(include-aliases=true) can return phantom results
--------------------------------------------------------------------
Key: WFCORE-692
URL:
https://issues.jboss.org/browse/WFCORE-692
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 1.0.0.CR3
Reporter: Paul Ferraro
Assignee: Brian Stansberry
If a resource exists with the same key as the target address of a resource alias,
read-children-names can return incorrect results.
Here's an example:
I have a alias registered that translates:
{noformat}/subsystem=infinispan/cache-container=*/local-cache=*/file-store=FILE_STORE{noformat}
to:
{noformat}/subsystem=infinispan/cache-container=*/local-cache=*/store=file{noformat}
Additionally, I have a resource named:
{noformat}/subsystem=infinispan/cache-container=*/local-cache=*/store=none{noformat}
If I create a cache that uses store=none, the corresponding
read-children-names(child-type=file-store, include-aliases=true) operation returns the
name of the FILE_STORE resource, even though the target resource (i.e. file=store) does
not exist.
This additionally causes the /subsystem=infinispan:read-resource(include-aliases=true,
recursive=true) operation to fail.