[JBoss JIRA] (DROOLS-3468) [DMN Editor] Support Decision Service invocation
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3468?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3468:
--------------------------------
Attachment: server-error.log
> [DMN Editor] Support Decision Service invocation
> ------------------------------------------------
>
> Key: DROOLS-3468
> URL: https://issues.jboss.org/browse/DROOLS-3468
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.16.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: a1 (1).dmn, error.log, server-error.log
>
>
> User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
> h2. Acceptance criteria
> - Import attached model *a1*
> - Connect *mood* decision service and *Decision-1* decision node
> - Deploy the model
> - Try to evaluate model via a rest call
> - Check the output json doesn't contain [^error.log]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3468) [DMN Editor] Support Decision Service invocation
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3468?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3468:
--------------------------------
Description:
User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
h2. Acceptance criteria
- Import attached model *a1*
- Connect *mood* decision service and *Decision-1* decision node
- Deploy the model
- Try to evaluate model via a rest call
- Check the output json doesn't contain [^error.log]
- Check the server log doesn't contain [^server-error.log]
was:
User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
h2. Acceptance criteria
- Import attached model *a1*
- Connect *mood* decision service and *Decision-1* decision node
- Deploy the model
- Try to evaluate model via a rest call
- Check the output json doesn't contain [^error.log]
> [DMN Editor] Support Decision Service invocation
> ------------------------------------------------
>
> Key: DROOLS-3468
> URL: https://issues.jboss.org/browse/DROOLS-3468
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.16.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: a1 (1).dmn, error.log, server-error.log
>
>
> User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
> h2. Acceptance criteria
> - Import attached model *a1*
> - Connect *mood* decision service and *Decision-1* decision node
> - Deploy the model
> - Try to evaluate model via a rest call
> - Check the output json doesn't contain [^error.log]
> - Check the server log doesn't contain [^server-error.log]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3468) [DMN Editor] Support Decision Service invocation
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3468?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3468:
--------------------------------
Description:
User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
h2. Acceptance criteria
- Import attached model *a1*
- Connect *mood* decision service and *Decision-1* decision node
- Deploy the model
- Try to evaluate model via a rest call
- Check the output json doesn't contain [^error.log]
was:
User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
h2. Acceptance criteria
- Import attached model *a1*
- Connect *mood* decision service and *Decision-1* decision node
- Deploy the model
- Try to evaluate model via a rest call
- Check the output json doesn't contain
> [DMN Editor] Support Decision Service invocation
> ------------------------------------------------
>
> Key: DROOLS-3468
> URL: https://issues.jboss.org/browse/DROOLS-3468
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.16.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: a1 (1).dmn, error.log
>
>
> User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
> h2. Acceptance criteria
> - Import attached model *a1*
> - Connect *mood* decision service and *Decision-1* decision node
> - Deploy the model
> - Try to evaluate model via a rest call
> - Check the output json doesn't contain [^error.log]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3468) [DMN Editor] Support Decision Service invocation
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3468?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3468:
--------------------------------
Description:
User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
h2. Acceptance criteria
- Import attached model *a1*
- Connect *mood* decision service and *Decision-1* decision node
- Deploy the model
- Try to evaluate model via a rest call
- Check the output json doesn't contain
was:
User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
h2. Acceptance criteria
- Import attached model *a1*
- Connect *mood* decision service and *Decision-1* decision node
- Deploy the model
- Try to evaluate model via a rest call
- Check the output json doesn't contain [1]
[1]
```
{"dmn-message-severity" : "ERROR",
"message" : "Function 'mood' not found. Invocation failed on node 'Decision-1'",
"message-type" : "REQ_NOT_FOUND"}
```
> [DMN Editor] Support Decision Service invocation
> ------------------------------------------------
>
> Key: DROOLS-3468
> URL: https://issues.jboss.org/browse/DROOLS-3468
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.16.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: a1 (1).dmn, error.log
>
>
> User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
> h2. Acceptance criteria
> - Import attached model *a1*
> - Connect *mood* decision service and *Decision-1* decision node
> - Deploy the model
> - Try to evaluate model via a rest call
> - Check the output json doesn't contain
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3468) [DMN Editor] Support Decision Service invocation
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3468?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3468:
--------------------------------
Attachment: error.log
> [DMN Editor] Support Decision Service invocation
> ------------------------------------------------
>
> Key: DROOLS-3468
> URL: https://issues.jboss.org/browse/DROOLS-3468
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.16.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: a1 (1).dmn, error.log
>
>
> User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
> h2. Acceptance criteria
> - Import attached model *a1*
> - Connect *mood* decision service and *Decision-1* decision node
> - Deploy the model
> - Try to evaluate model via a rest call
> - Check the output json doesn't contain
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3468) [DMN Editor] Support Decision Service invocation
by Jozef Marko (Jira)
Jozef Marko created DROOLS-3468:
-----------------------------------
Summary: [DMN Editor] Support Decision Service invocation
Key: DROOLS-3468
URL: https://issues.jboss.org/browse/DROOLS-3468
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.16.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
Attachments: a1 (1).dmn
User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
h2. Acceptance criteria
- Import attached model *a1*
- Connect *mood* decision service and *Decision-1* decision node
- Deploy the model
- Try to evaluate model via a rest call
- Check the output json doesn't contain [1]
[1]
```json
{"dmn-message-severity" : "ERROR",
"message" : "Function 'mood' not found. Invocation failed on node 'Decision-1'",
"message-type" : "REQ_NOT_FOUND"}
```
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3468) [DMN Editor] Support Decision Service invocation
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3468?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3468:
--------------------------------
Description:
User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
h2. Acceptance criteria
- Import attached model *a1*
- Connect *mood* decision service and *Decision-1* decision node
- Deploy the model
- Try to evaluate model via a rest call
- Check the output json doesn't contain [1]
[1]
```
{"dmn-message-severity" : "ERROR",
"message" : "Function 'mood' not found. Invocation failed on node 'Decision-1'",
"message-type" : "REQ_NOT_FOUND"}
```
was:
User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
h2. Acceptance criteria
- Import attached model *a1*
- Connect *mood* decision service and *Decision-1* decision node
- Deploy the model
- Try to evaluate model via a rest call
- Check the output json doesn't contain [1]
[1]
```json
{"dmn-message-severity" : "ERROR",
"message" : "Function 'mood' not found. Invocation failed on node 'Decision-1'",
"message-type" : "REQ_NOT_FOUND"}
```
> [DMN Editor] Support Decision Service invocation
> ------------------------------------------------
>
> Key: DROOLS-3468
> URL: https://issues.jboss.org/browse/DROOLS-3468
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.16.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Attachments: a1 (1).dmn
>
>
> User is not able to model a DMN model where he declare a Decision service and invoke this Decision Service from other node, because the Decision Service node doesn't allow any incoming nor outgoing connections.
> h2. Acceptance criteria
> - Import attached model *a1*
> - Connect *mood* decision service and *Decision-1* decision node
> - Deploy the model
> - Try to evaluate model via a rest call
> - Check the output json doesn't contain [1]
> [1]
> ```
> {"dmn-message-severity" : "ERROR",
> "message" : "Function 'mood' not found. Invocation failed on node 'Decision-1'",
> "message-type" : "REQ_NOT_FOUND"}
> ```
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (WFLY-11504) Some hibernate tests fail with security on IBM Java 8: HHH000142
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFLY-11504?page=com.atlassian.jira.plugin... ]
Scott Marlow reassigned WFLY-11504:
-----------------------------------
Assignee: Gail Badner (was: Scott Marlow)
> Some hibernate tests fail with security on IBM Java 8: HHH000142
> ----------------------------------------------------------------
>
> Key: WFLY-11504
> URL: https://issues.jboss.org/browse/WFLY-11504
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate, Test Suite
> Affects Versions: 16.0.0.Beta1
> Environment: IBM Java 8, build 8.0.5.25 or 8.0.5.26
> Reporter: Ondrej Kotek
> Assignee: Gail Badner
> Priority: Major
> Attachments: org.jboss.as.test.integration.jpa.hibernate.entitytest.EntityTestCase-output.txt
>
>
> Seven hibernate tests fail with security on IBM Java 8, for example:
> {noformat}
> org.hibernate.HibernateException: HHH000142: Bytecode enhancement failed: org.jboss.as.test.integration.jpa.hibernate.Employee
> {noformat}
> Affected test cases:
> * {{org.jboss.as.test.integration.jpa.hibernate.entitytest.EntityTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.basicenverstest.BasicEnversTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.basicselectiveenverstest.BasicSelectiveEnversTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.implementvalidityauditstrategytest.ImplementValidityAuditStrategyTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.envers.validityauditstrategyoninheritancetest.ValidityAuditStrategyonInheritanceTestCase}}
> * {{org.jboss.as.test.integration.jpa.hibernate.sessionfactorytest.SessionFactoryTestCase}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3442) Rename the "Name" label in DMN Definition properties panel
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3442?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3442:
-------------------------------------
Definitely +1 for this change.
> Rename the "Name" label in DMN Definition properties panel
> ----------------------------------------------------------
>
> Key: DROOLS-3442
> URL: https://issues.jboss.org/browse/DROOLS-3442
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> The field "Name" refers to name for the DMN model, rather than the file. The generic label "Name" might mislead users to believe that they are renaming the file name, when they are not. To clarify the purpose of this field, consider providing a more accurate field label - for example: "Model name" or etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3442) Rename the "Name" label in DMN Definition properties panel
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3442?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3442:
--------------------------------
Labels: UX UXTeam drools-tools (was: UX UXTeam)
> Rename the "Name" label in DMN Definition properties panel
> ----------------------------------------------------------
>
> Key: DROOLS-3442
> URL: https://issues.jboss.org/browse/DROOLS-3442
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> The field "Name" refers to name for the DMN model, rather than the file. The generic label "Name" might mislead users to believe that they are renaming the file name, when they are not. To clarify the purpose of this field, consider providing a more accurate field label - for example: "Model name" or etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months