[
https://issues.jboss.org/browse/WFCORE-692?page=com.atlassian.jira.plugin...
]
Paul Ferraro commented on WFCORE-692:
-------------------------------------
[~kabirkhan] BTW, the issue turned out to be far more specific to my use case than I
initially assumed. The key difference is that I have a non-aliased resource with the same
path key, which causes the read-children-names operation to mistakenly decided that the
target resource exists.
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: Paul Ferraro
Fix For: 1.0.0.CR5, 2.0.0.Alpha1
If another resource exists with the same key as the target address of a resource alias,
the read-children-names(include-aliases=true) operation can return phantom 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 results of a
read-children-names(child-type=file-store, include-aliases=true) operation includes 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)