August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2889) Research accessibility considerations for Data Type list drag-n-drop.

by Sarah Rambacher (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2889?page=com.atlassian.jira.plugi... ] Sarah Rambacher resolved DROOLS-2889. ------------------------------------- Resolution: Done > Research accessibility considerations for Data Type list drag-n-drop. > ---------------------------------------------------------------------- > > Key: DROOLS-2889 > URL: https://issues.jboss.org/browse/DROOLS-2889 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Sarah Rambacher > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2018-08-13 at 1.42.16 PM.png > > > Use Case: As a DMN user I will want to be able to reorder the list of Custom data types so that I can arrange data types in a logical order. > Notes: > * The Data Type dialog leverage the following PR list pattern: > https://www.patternfly.org/pattern-library/content-views/tree-list-view > * The list will need to be re-orderable, there is an open design jira to determine the interaction options for that feature. > * Design is currently being iterated upon, but last iteration wireframes are posted at: https://redhat.invisionapp.com/share/B7NEEUSV539 > Verification conditions: > * Research results summarized in the jira or a linked google doc., etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2578) [DMN Designer] Add use of 'DMNModelInstrumentedBase.setParent(..)' to marshaller

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2578?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-2578: ---------------------------------------- [~manstis] so to double-check, this task requires any converters which takes a kie-dmn-model anemic pojo converting to a WB DMN pojo which extends org.kie.workbench.common.dmn.api.definition.v1_1.DMNModelInstrumentedBase to set its parent. Correct? I will do it although likely there will be less of a need for this namespace scope resolution when dealing with DMN v1.2 (as the prefix: is no longer supported for xml namespaces ;) ) I will keep posted as I progress. > [DMN Designer] Add use of 'DMNModelInstrumentedBase.setParent(..)' to marshaller > -------------------------------------------------------------------------------- > > Key: DROOLS-2578 > URL: https://issues.jboss.org/browse/DROOLS-2578 > Project: Drools > Issue Type: Sub-task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Matteo Mortari > Priority: Critical > > In order to correctly handle QName prefix resolution I have added {{DMNModelInstrumentedBase.getPrefixForNamespaceURI(..)}} to the UI model. I will add support for setting it appropriately as the User authors a DMN model in the UI (i.e. to new elements as and when created) however the marshaller will need to set it accordingly when going from KIE-DMN-model to UI-DMN-model too; so existing diagrams have the parental hierarchy correctly set. > This depends on https://github.com/kiegroup/kie-wb-common/pull/1818 being merged. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10907) ServiceRegistry lookup of legacy SingletonServiceBuilderFactory throws UnsupportedOperationException

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10907?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-10907: -------------------------------- Description: Legacy code will lookup a SingletonPolicy or SingletonServiceBuilderFactory using the deprecated ServiceController.awaitValue() or getValue() methods. Services installed using the new MSC service installation API will throw an UnsupportedOperationException in this case. Consequently, the services providing the legacy implementations of these deprecated APIs need to be installed using the deprecated MSC API to prevent migrated applications from unexpected UnsupportedOperationExceptions. (was: Legacy code will lookup a SingletonPolicy or SingletonServiceBuilderFactory using the deprecated ServiceController.awaitValue() or getValue(). This service needs to be installed using the deprecated MSC API, to prevent an UnsupportedOperationException.) > ServiceRegistry lookup of legacy SingletonServiceBuilderFactory throws UnsupportedOperationException > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-10907 > URL: https://issues.jboss.org/browse/WFLY-10907 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 14.0.0.Beta2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > > Legacy code will lookup a SingletonPolicy or SingletonServiceBuilderFactory using the deprecated ServiceController.awaitValue() or getValue() methods. Services installed using the new MSC service installation API will throw an UnsupportedOperationException in this case. Consequently, the services providing the legacy implementations of these deprecated APIs need to be installed using the deprecated MSC API to prevent migrated applications from unexpected UnsupportedOperationExceptions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3620) Upgrade log4j-jboss-logmanager from 1.1.4.Final to 1.1.5.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3620?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-3620: --------------------------------------- Diff https://github.com/jboss-logging/log4j-jboss-logmanager/compare/1.1.4.Fin... > Upgrade log4j-jboss-logmanager from 1.1.4.Final to 1.1.5.Final > -------------------------------------------------------------- > > Key: WFCORE-3620 > URL: https://issues.jboss.org/browse/WFCORE-3620 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > There was a minor [bug|JBEAP-14214] found in previous versions of {{org.jboss.logmanager:log4j-jboss-logmanager}}. This is fixed in 1.1.5.Final. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2888: ------------------------------------- [~tirelli] [~karreiro] I've updated the design, and various reference materials: * Click-thru: https://cdn.rawgit.com/lclay2/bxms-uxd-sandbox/808aa447/design/dtDemoAddO... * Created a document to outline the changes made in this story: https://docs.google.com/document/d/1Vf3IemHMhwXUG4tZYSaAyVTSTEiC31lE2dFw-... * Posted a PDF of the prior design iteration. I'd like to mark this as Resolved, please let me know, thanks! > Data Type UX - dialog enhancements: Add and Reorder > ---------------------------------------------------- > > Key: DROOLS-2888 > URL: https://issues.jboss.org/browse/DROOLS-2888 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2018-08-17 at 4.29.29 PM.png, dataType4.pdf, previous.gif, viewMoreLess.gif > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > As a user I want to: > * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow. > * Reorder the list of Custom data types so that I can arrange data types in a logical order. > * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default. > Functional considerations/ pre conditions: > * Fields will be presented at the bottom of a structured list by default. > * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table > * Drag-n-drop be evaluated with regard to accessibility. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2888: -------------------------------- Attachment: dataType4.pdf > Data Type UX - dialog enhancements: Add and Reorder > ---------------------------------------------------- > > Key: DROOLS-2888 > URL: https://issues.jboss.org/browse/DROOLS-2888 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2018-08-17 at 4.29.29 PM.png, dataType4.pdf, previous.gif, viewMoreLess.gif > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > As a user I want to: > * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow. > * Reorder the list of Custom data types so that I can arrange data types in a logical order. > * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default. > Functional considerations/ pre conditions: > * Fields will be presented at the bottom of a structured list by default. > * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table > * Drag-n-drop be evaluated with regard to accessibility. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2889) Research accessibility considerations for Data Type list drag-n-drop.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2889?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2889: ------------------------------------- [~srambach] Should we mark this as Resolved? > Research accessibility considerations for Data Type list drag-n-drop. > ---------------------------------------------------------------------- > > Key: DROOLS-2889 > URL: https://issues.jboss.org/browse/DROOLS-2889 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Sarah Rambacher > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2018-08-13 at 1.42.16 PM.png > > > Use Case: As a DMN user I will want to be able to reorder the list of Custom data types so that I can arrange data types in a logical order. > Notes: > * The Data Type dialog leverage the following PR list pattern: > https://www.patternfly.org/pattern-library/content-views/tree-list-view > * The list will need to be re-orderable, there is an open design jira to determine the interaction options for that feature. > * Design is currently being iterated upon, but last iteration wireframes are posted at: https://redhat.invisionapp.com/share/B7NEEUSV539 > Verification conditions: > * Research results summarized in the jira or a linked google doc., etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10907) ServiceRegistry lookup of legacy SingletonServiceBuilderFactory throws UnsupportedOperationException

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10907?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-10907: -------------------------------- Labels: (was: regress) > ServiceRegistry lookup of legacy SingletonServiceBuilderFactory throws UnsupportedOperationException > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-10907 > URL: https://issues.jboss.org/browse/WFLY-10907 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 14.0.0.Beta2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Legacy code will lookup a SingletonPolicy or SingletonServiceBuilderFactory using the deprecated ServiceController.awaitValue() or getValue(). This service needs to be installed using the deprecated MSC API, to prevent an UnsupportedOperationException. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10907) ServiceRegistry lookup of legacy SingletonServiceBuilderFactory throws UnsupportedOperationException

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10907?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-10907: -------------------------------- Priority: Critical (was: Major) > ServiceRegistry lookup of legacy SingletonServiceBuilderFactory throws UnsupportedOperationException > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-10907 > URL: https://issues.jboss.org/browse/WFLY-10907 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 14.0.0.Beta2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > > Legacy code will lookup a SingletonPolicy or SingletonServiceBuilderFactory using the deprecated ServiceController.awaitValue() or getValue(). This service needs to be installed using the deprecated MSC API, to prevent an UnsupportedOperationException. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10907) ServiceRegistry lookup of legacy SingletonServiceBuilderFactory throws UnsupportedOperationException

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10907?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-10907: -------------------------------- Description: Legacy code will lookup a SingletonPolicy or SingletonServiceBuilderFactory using the deprecated ServiceController.awaitValue() or getValue(). This service needs to be installed using the deprecated MSC API, to prevent an UnsupportedOperationException. (was: Legacy code will lookup SingletonServiceBuilderFactory using the deprecated ServiceController.awaitValue() or getValue(). This service needs to be installed using the deprecated MSC API, to prevent an UnsupportedOperationException.) > ServiceRegistry lookup of legacy SingletonServiceBuilderFactory throws UnsupportedOperationException > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-10907 > URL: https://issues.jboss.org/browse/WFLY-10907 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 14.0.0.Beta2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Labels: regress > > Legacy code will lookup a SingletonPolicy or SingletonServiceBuilderFactory using the deprecated ServiceController.awaitValue() or getValue(). This service needs to be installed using the deprecated MSC API, to prevent an UnsupportedOperationException. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018