[ https://issues.redhat.com/browse/WFLY-13633?page=com.atlassian.jira.plugi... ]
Thomas Jenkinson commented on WFLY-13633:
-----------------------------------------
I think it is a data integrity issue in the sense that a subsequent deploy of a resource would be treated as a CMR so the behaviour of the resource would not be as expected by the user.
> Undeployed CMR resource JNDI names are not deregisted as needing to be treated as CMR
> -------------------------------------------------------------------------------------
>
> Key: WFLY-13633
> URL: https://issues.redhat.com/browse/WFLY-13633
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Reporter: Thomas Jenkinson
> Assignee: Michael Musgrove
> Priority: Blocker
>
> https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... does not remove the JNDI name from the list of names that Narayana will treat as CMR resources as it is removed from a copy of the map: https://github.com/jbosstm/narayana/blob/48818111d12d2e51b52082a00bcb6060...
> This means that if Narayana encounters another resource with the same name at a later date it will consider it is a CMR resource.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
Thomas Jenkinson created WFLY-13633:
---------------------------------------
Summary: Undeployed CMR resource JNDI names are not deregisted as needing to be treated as CMR
Key: WFLY-13633
URL: https://issues.redhat.com/browse/WFLY-13633
Project: WildFly
Issue Type: Bug
Components: Transactions
Reporter: Thomas Jenkinson
Assignee: Michael Musgrove
https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... does not remove the JNDI name from the list of names that Narayana will treat as CMR resources as it is removed from a copy of the map: https://github.com/jbosstm/narayana/blob/48818111d12d2e51b52082a00bcb6060...
This means that if Narayana encounters another resource with the same name at a later date it will consider it is a CMR resource.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[ https://issues.redhat.com/browse/DROOLS-5203?page=com.atlassian.jira.plug... ]
Jozef Marko reopened DROOLS-5203:
---------------------------------
> Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows
> --------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5203
> URL: https://issues.redhat.com/browse/DROOLS-5203
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> Goal is to merge and reuse the existing generic validator for the issue types in the title. The user should see no difference in the workbench use, but this will help us to reduce reduncancy and improve future V&V coverage for both DMN and DRL at the same time.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[ https://issues.redhat.com/browse/DROOLS-5203?page=com.atlassian.jira.plug... ]
Jozef Marko closed DROOLS-5203.
-------------------------------
Resolution: Rejected
> Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows
> --------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5203
> URL: https://issues.redhat.com/browse/DROOLS-5203
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> Goal is to merge and reuse the existing generic validator for the issue types in the title. The user should see no difference in the workbench use, but this will help us to reduce reduncancy and improve future V&V coverage for both DMN and DRL at the same time.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)