December 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3446) Data type constraints: Basic interaction/workflow

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3446?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3446: ------------------------------------- [~tirelli] [~karreiro] [~manstis] I posted proposals, for the A & B input contexts. I'm going to stop work on this until the team has had a chance to review and discuss. > Data type constraints: Basic interaction/workflow > ------------------------------------------------- > > Key: DROOLS-3446 > URL: https://issues.jboss.org/browse/DROOLS-3446 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view: > As a user, I want to be able to set data type constraints for an input value in a Decision Table, so that this constraint is valid _*only*_ in the context of this specific input in this Decision Table. > * From the Data Types tab: > As a user I want the ability to define constraints for data type definitions in use within the DMN file. > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3446) Data type constraints: Basic interaction/workflow

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3446?page=com.atlassian.jira.plugi... ] Liz Clayton edited comment on DROOLS-3446 at 12/20/18 3:48 PM: --------------------------------------------------------------- Adding wireframe proposal click-thrus: * A) Data type list/tab. https://redhat.invisionapp.com/share/D5PPHAI8PAG * B) from the DMN canvas view (Decision table.) https://redhat.invisionapp.com/share/96PQDNLMREP was (Author: uxdlc): Adding wireframe proposal click-thrus: * A) Data type list/tab. https://redhat.invisionapp.com/share/D5PPHAI8PAG * B) from the DMN canvas view (Decision table.) https://redhat.invisionapp.com/share/V8PQCPBURBY > Data type constraints: Basic interaction/workflow > ------------------------------------------------- > > Key: DROOLS-3446 > URL: https://issues.jboss.org/browse/DROOLS-3446 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view: > As a user, I want to be able to set data type constraints for an input value in a Decision Table, so that this constraint is valid _*only*_ in the context of this specific input in this Decision Table. > * From the Data Types tab: > As a user I want the ability to define constraints for data type definitions in use within the DMN file. > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3446) Data type constraints: Basic interaction/workflow

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3446?page=com.atlassian.jira.plugi... ] Liz Clayton edited comment on DROOLS-3446 at 12/20/18 3:10 PM: --------------------------------------------------------------- Adding wireframe proposal click-thrus: * A) Data type list/tab. https://redhat.invisionapp.com/share/D5PPHAI8PAG * B) from the DMN canvas view (Decision table.) https://redhat.invisionapp.com/share/V8PQCPBURBY was (Author: uxdlc): Adding wireframe proposal click-thrus: * A) Data type list/tab. https://redhat.invisionapp.com/share/D5PPHAI8PAG#/screens * B) from the DMN canvas view (Decision table.) https://redhat.invisionapp.com/share/V8PQCPBURBY > Data type constraints: Basic interaction/workflow > ------------------------------------------------- > > Key: DROOLS-3446 > URL: https://issues.jboss.org/browse/DROOLS-3446 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view: > As a user, I want to be able to set data type constraints for an input value in a Decision Table, so that this constraint is valid _*only*_ in the context of this specific input in this Decision Table. > * From the Data Types tab: > As a user I want the ability to define constraints for data type definitions in use within the DMN file. > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3446) Data type constraints: Basic interaction/workflow

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3446?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3446: ------------------------------------- Adding wireframe proposal click-thrus: * A) Data type list/tab. https://redhat.invisionapp.com/share/D5PPHAI8PAG#/screens * B) from the DMN canvas view (Decision table.) https://redhat.invisionapp.com/share/V8PQCPBURBY > Data type constraints: Basic interaction/workflow > ------------------------------------------------- > > Key: DROOLS-3446 > URL: https://issues.jboss.org/browse/DROOLS-3446 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view: > As a user, I want to be able to set data type constraints for an input value in a Decision Table, so that this constraint is valid _*only*_ in the context of this specific input in this Decision Table. > * From the Data Types tab: > As a user I want the ability to define constraints for data type definitions in use within the DMN file. > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[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 moved JBEAP-16080 to WFLY-11543: ------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11543 (was: JBEAP-16080) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JPA / Hibernate (was: Hibernate) (was: JPA / Hibernate) Affects Version/s: 15.0.0.Final (was: 7.3.0.CD15) (was: 7.2.0.GA.CR3) > 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 > > 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)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1537) PolicyContext.getContext("javax.security.auth.Subject.container")

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/ELY-1537?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev resolved ELY-1537. -------------------------------- Release Notes Text: ELY-1537 has been rejected. Resolution: Rejected > PolicyContext.getContext("javax.security.auth.Subject.container") > ----------------------------------------------------------------- > > Key: ELY-1537 > URL: https://issues.jboss.org/browse/ELY-1537 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.2.3.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > > PolicyContext.getContext("javax.security.auth.Subject.container") returns null when using elytron to protect a web application. > This should return the authenticated subject. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1537) PolicyContext.getContext("javax.security.auth.Subject.container")

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/ELY-1537?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev reassigned ELY-1537: ---------------------------------- Assignee: Ilia Vassilev > PolicyContext.getContext("javax.security.auth.Subject.container") > ----------------------------------------------------------------- > > Key: ELY-1537 > URL: https://issues.jboss.org/browse/ELY-1537 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.2.3.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > > PolicyContext.getContext("javax.security.auth.Subject.container") returns null when using elytron to protect a web application. > This should return the authenticated subject. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4261) Update Maven dependencies to reference individual Elytron modules.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4261?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-4261: ------------------------------------- Description: Additionally remove the root 'wildfly-elytron' dependency. This should also review the classes the application server users as we will likely want to start considering these public API. was:Additionally remove the root 'wildfly-elytron' dependency. > Update Maven dependencies to reference individual Elytron modules. > ------------------------------------------------------------------ > > Key: WFCORE-4261 > URL: https://issues.jboss.org/browse/WFCORE-4261 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 8.0.0.Beta2 > > > Additionally remove the root 'wildfly-elytron' dependency. > This should also review the classes the application server users as we will likely want to start considering these public API. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11540) Update Maven dependencies to reference individual Elytron modules.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11540?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFLY-11540: ------------------------------------ Description: This should also review the classes the application server users as we will likely want to start considering these public API. > Update Maven dependencies to reference individual Elytron modules. > ------------------------------------------------------------------ > > Key: WFLY-11540 > URL: https://issues.jboss.org/browse/WFLY-11540 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 16.0.0.Beta1 > > > This should also review the classes the application server users as we will likely want to start considering these public API. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2441) Inconsistency between DMR and XSD representation of Elytron simple-permission-mapper

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFCORE-2441?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFCORE-2441: ---------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/2727) > Inconsistency between DMR and XSD representation of Elytron simple-permission-mapper > ------------------------------------------------------------------------------------ > > Key: WFCORE-2441 > URL: https://issues.jboss.org/browse/WFCORE-2441 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta7 > Reporter: Ondrej Kotek > Assignee: Ilia Vassilev > Priority: Major > Labels: user_experience > > There are inconsistencies between DMR and XSD representation of {{constant-permission-mapper}}. > According to XSD {{permission}} must occur at least one times in {{constant-permission-mapper}}. According to DMR it is {{"nillable" => true}}. This should be unified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2018