[jboss-jira] [JBoss JIRA] (WFCORE-1836) Rejection-style transformer tests assume each operation generated by parser has distinct PathAddress

[Radoslav Husar (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13310999#comment-13310999 ] 

Radoslav Husar commented on WFCORE-1836:
----------------------------------------

Actually, the issue still holds. What we need is different set of attribute checkers for the same path but different operations since there is and add and write-attribute ops at the same address. What I am doing in  WFLY-7362 still a workaround.

> Rejection-style transformer tests assume each operation generated by parser has distinct PathAddress
> ----------------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-1836
>                 URL: https://issues.jboss.org/browse/WFCORE-1836
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Test Suite
>            Reporter: Paul Ferraro
>            Assignee: Brian Stansberry
>
> For rejection-style transformer tests, the subsystem test framework stores expected rejected operations in a map keyed by PathAddress.  This is fine when the subsystem's parser only generates add operations.  However, if the parser generates an add operation as well as a a write-attribute operation, these 2 operations will have the same path address.  If we expect one of these operations to be rejected, but not the other, we end up with an unexpected rejection - and the test fails.
> This is a little hard to explain in the abstract, so let me know if any of the above doesn't make sense.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)