[JBoss JIRA] (DROOLS-2932) [DMN Designer] keyboard navigation in context grid editor
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2932?page=com.atlassian.jira.plugi... ]
Jozef Marko reopened DROOLS-2932:
---------------------------------
> [DMN Designer] keyboard navigation in context grid editor
> ---------------------------------------------------------
>
> Key: DROOLS-2932
> URL: https://issues.jboss.org/browse/DROOLS-2932
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
> Fix For: 7.16.0.Final
>
>
> User should be able to navigate between context grid editor cells by keyboard. We should implement standard navigation:
> - Move up: *arrow up*
> - Move left: *arrow left*
> - Move down: *arrow down*
> - Move right: *arrow right*
> Corner cases we need to address:
> - No cell selected
> -- -Select Top left cell if any arrow pressed?- left top cell selected by default
> - Multiple cells selected
> -- -Select Top left cell of current selected if any arrow pressed?- selection adjusted, no error thrown
> - Selected cell on the corner, no other cells in demanded way
> -- Keep selected the current cell
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-3468) [DMN Editor] Support Decision Service invocation
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3468?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3468:
-----------------------------------
Sprint: 2018 Week 51-01
> [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: Screenshot from 2019-01-02 15-37-21.png, 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)
6 years, 11 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 edited comment on DROOLS-3468 at 1/2/19 9:39 AM:
-------------------------------------------------------------
[~tari_manga] I provided picture. And yes, I agree the problem is due to missing _KnowledgeRequirement_, that is why I filed an issue as our designer doesn't allow me to create such connection there.
was (Author: jomarko):
[~tari_manga] I provided picture. And yes, I agree the problem is due to missing _KnowledgeRequirement_, that is why I filed an issues as our designer doesn't allow me to create such connection there.
> [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: Screenshot from 2019-01-02 15-37-21.png, 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)
6 years, 11 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 edited comment on DROOLS-3468 at 1/2/19 9:39 AM:
-------------------------------------------------------------
[~tari_manga] I provided picture. And yes, I agree the problem is due to missing _KnowledgeRequirement_, that is why I filed an issues as our designer doesn't allow me to create such connection there.
was (Author: jomarko):
[~tari_manga] I provided picture. And yes, I agree the problem is due to missing `KnowledgeRequirement`, that is why I filed an issues as our designer doesn't allow me to create such connection there.
> [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: Screenshot from 2019-01-02 15-37-21.png, 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)
6 years, 11 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 commented on DROOLS-3468:
-------------------------------------
[~tari_manga] I provided picture. And yes, I agree the problem is due to missing `KnowledgeRequirement`, that is why I filed an issues as our designer doesn't allow me to create such connection there.
> [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: Screenshot from 2019-01-02 15-37-21.png, 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)
6 years, 11 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: Screenshot from 2019-01-02 15-37-21.png
> [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: Screenshot from 2019-01-02 15-37-21.png, 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)
6 years, 11 months
[JBoss JIRA] (WFLY-11543) EJB transactional method unable to commit when invoked from CDI bean with MariaDB
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11543?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11543:
------------------------------------
Fix Version/s: 15.0.1
> EJB transactional method unable to commit when invoked from CDI bean with MariaDB
> ---------------------------------------------------------------------------------
>
> Key: WFLY-11543
> URL: https://issues.jboss.org/browse/WFLY-11543
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 15.0.0.Final
> Environment: WildFly 15.0.0.Final
> MariaDB 10.1.19
> Reporter: Michal Jurc
> Assignee: Scott Marlow
> Priority: Blocker
> Fix For: 15.0.1.Final, 16.0.0.Beta1
>
> Attachments: logs.zip, server-trace.zip
>
>
> Issue cloned from the [community forum|https://developer.jboss.org/thread/279303] for tracking.
> {quote}Hello,
>
> We are having issues after deploying our application in the latest Wildfly 15.0.0 Final recently released with the following exception:
> java.sql.SQLException: XAER_RMFAIL: The command cannot be executed when global transaction is in the IDLE state
>
> The error occurs when our code calls a transactional EJB method that itself calls a couple more injected SessionBean that handles the database persistence through an EntityManager
> The issue only seems to affect the MariaDB port and not oracle.{quote}
> {quote}I have hit the same problem, migrated from Wildfly 10.0.0. to 15.0.0, using MySQL, same error, similar situation, cdi managed bean that invokes 2 EJBs that use different persistent units. I dont seem to have the problem in 14.0.1 either.
>
> Another error that has surfaced is this (apologies for the weird formatting but struggled to define a simple type-up without cluttering)
>
> "javax.persistence.TransactionRequiredException: no transaction is in progress"
> Managed bean with injected ejb (with datasource2) and injected entitymanager for datasource1, code is nested as follows
>
> Managed bean method save @Transactional(value = TxType.REQUIRED)
> {
> ejb save @TransactionAttribute(TransactionAttributeType.MANDATORY)
> {
> persist
> flush
> }
>
> find with lock => LockModeType.PESSIMISTIC_WRITE at this point the "no transaction is in progress" exception is fired
>
> }
>
> Did notice that error does not occur if the invocation is purely ejb rather that cdi managed bean {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months