April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3831) [DMN Designer] Included Models - Create a service for providing information from external DMN files `ExternalDMNModelsService`

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-3831: --------------------------------------- Summary: [DMN Designer] Included Models - Create a service for providing information from external DMN files `ExternalDMNModelsService` Key: DROOLS-3831 URL: https://issues.jboss.org/browse/DROOLS-3831 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Daniel José dos Santos Create the {{ExternalDMNModelsService}} service for providing information about external DMN files. This service class will be responsible for returning all information from a given node from another DMN file. This API will be something like this: {{ExternalDMNFileService.getNode(final String dmnElementRef)}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3798) [DMN Designer] Included Models - When users open a DMN file with imported nodes, they must be able to see those nodes in the graph on read-only mode

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3798?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-3798: ------------------------------------ Story Points: 5 (was: 8) > [DMN Designer] Included Models - When users open a DMN file with imported nodes, they must be able to see those nodes in the graph on read-only mode > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3798 > URL: https://issues.jboss.org/browse/DROOLS-3798 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: daniel1.dmn, daniel2.dmn > > > When users open the DMN editor with an imported file+ imported nodes, they must be able to see these nodes on read-only mode. > --- > Assets: > - [^daniel1.dmn] > - [^daniel2.dmn] > --- > This task comprehends: > - Read imported nodes in the "daniel2.dmn", and put them into the canvas by consuming a *mocked service class* [1] to fill the node information; > - Create the new imported nodes in the canvas; > - Persist imported nodes info properly in the DMN file (when users save it); > - Keep these imported nodes on read-only mode; > - -Keep the properties panel correctly updated- (This JIRA https://issues.jboss.org/browse/DROOLS-3830 will address this item) > --- > Acceptance criteria: > - Open the "daniel2.dmn" > - See the imported nodes from the "daniel1.dmn" > - Try to change the name of the node (this should not be allowed, since the node must be on read only mode) > - Check the properties panel properties > --- > [1] This service class will be responsible for returning all information from a given node from another DMN file. This API will be something like this: {{ExternalDMNFileService.getNode(final String dmnElementRef)}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3798) [DMN Designer] Included Models - When users open a DMN file with imported nodes, they must be able to see those nodes in the graph on read-only mode

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3798?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-3798: ------------------------------------ Description: When users open the DMN editor with an imported file+ imported nodes, they must be able to see these nodes on read-only mode. --- Assets: - [^daniel1.dmn] - [^daniel2.dmn] --- This task comprehends: - Read imported nodes in the "daniel2.dmn", and put them into the canvas by consuming a *mocked service class* [1] to fill the node information; - Create the new imported nodes in the canvas; - Persist imported nodes info properly in the DMN file (when users save it); - Keep these imported nodes on read-only mode; - -Keep the properties panel correctly updated- (This JIRA https://issues.jboss.org/browse/DROOLS-3830 will address this item) --- Acceptance criteria: - Open the "daniel2.dmn" - See the imported nodes from the "daniel1.dmn" - Try to change the name of the node (this should not be allowed, since the node must be on read only mode) - Check the properties panel properties --- [1] This service class will be responsible for returning all information from a given node from another DMN file. This API will be something like this: {{ExternalDMNFileService.getNode(final String dmnElementRef)}} was: When users open the DMN editor with an imported file+ imported nodes, they must be able to see these nodes on read-only mode. --- Assets: - [^daniel1.dmn] - [^daniel2.dmn] --- This task comprehends: - Read imported nodes in the "daniel2.dmn", and put them into the canvas by consuming a *mocked service class* [1] to fill the node information; - Create the new imported nodes in the canvas; - Persist imported nodes info properly in the DMN file (when users save it); - Keep these imported nodes on read-only mode; - Keep the properties panel correctly updated. --- Acceptance criteria: - Open the "daniel2.dmn" - See the imported nodes from the "daniel1.dmn" - Try to change the name of the node (this should not be allowed, since the node must be on read only mode) - Check the properties panel properties --- [1] This service class will be responsible for returning all information from a given node from another DMN file. This API will be something like this: {{ExternalDMNFileService.getNode(final String dmnElementRef)}} > [DMN Designer] Included Models - When users open a DMN file with imported nodes, they must be able to see those nodes in the graph on read-only mode > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3798 > URL: https://issues.jboss.org/browse/DROOLS-3798 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: daniel1.dmn, daniel2.dmn > > > When users open the DMN editor with an imported file+ imported nodes, they must be able to see these nodes on read-only mode. > --- > Assets: > - [^daniel1.dmn] > - [^daniel2.dmn] > --- > This task comprehends: > - Read imported nodes in the "daniel2.dmn", and put them into the canvas by consuming a *mocked service class* [1] to fill the node information; > - Create the new imported nodes in the canvas; > - Persist imported nodes info properly in the DMN file (when users save it); > - Keep these imported nodes on read-only mode; > - -Keep the properties panel correctly updated- (This JIRA https://issues.jboss.org/browse/DROOLS-3830 will address this item) > --- > Acceptance criteria: > - Open the "daniel2.dmn" > - See the imported nodes from the "daniel1.dmn" > - Try to change the name of the node (this should not be allowed, since the node must be on read only mode) > - Check the properties panel properties > --- > [1] This service class will be responsible for returning all information from a given node from another DMN file. This API will be something like this: {{ExternalDMNFileService.getNode(final String dmnElementRef)}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2242) Narrow set of thrown exceptions in Streamable and Marshaller method signatures

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2242?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2242: --------------------------- Fix Version/s: 4.1.0 (was: 5.0) > Narrow set of thrown exceptions in Streamable and Marshaller method signatures > ------------------------------------------------------------------------------ > > Key: JGRP-2242 > URL: https://issues.jboss.org/browse/JGRP-2242 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 4.0 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Fix For: 4.1.0 > > > These methods all throw a generic Exception. Write methods should only need to throw IOException, while read methods should only need to throw IOException and ClassNotFoundException. > Original PR, deferred to 5.0, is here: > https://github.com/belaban/JGroups/pull/372 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3830) [DMN Designer] Included Models - When users open a DMN file with imported nodes, they must be able to see the properties panel updated with those nodes information

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3830?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-3830: ------------------------------------ Description: When users open the DMN editor with an imported file with imported nodes, they must be able to see properties from the nodes in the properties panel. > [DMN Designer] Included Models - When users open a DMN file with imported nodes, they must be able to see the properties panel updated with those nodes information > ------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3830 > URL: https://issues.jboss.org/browse/DROOLS-3830 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > When users open the DMN editor with an imported file with imported nodes, they must be able to see properties from the nodes in the properties panel. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3830) [DMN Designer] Included Models - When users open a DMN file with imported nodes, they must be able to see the properties panel updated with those nodes information

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-3830: --------------------------------------- Summary: [DMN Designer] Included Models - When users open a DMN file with imported nodes, they must be able to see the properties panel updated with those nodes information Key: DROOLS-3830 URL: https://issues.jboss.org/browse/DROOLS-3830 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Daniel José dos Santos -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3384) [DMN Designer] DMN Editor Index

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3384?page=com.atlassian.jira.plugi... ] Guilherme Gomes closed DROOLS-3384. ----------------------------------- Resolution: Done > [DMN Designer] DMN Editor Index > ------------------------------- > > Key: DROOLS-3384 > URL: https://issues.jboss.org/browse/DROOLS-3384 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Affects Versions: 7.15.0.Final > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > > This JIRA aims to cover all tasks related to interactions between DMN files. > The Import Feature introduces scenarios that couples DMN files to each other. See these two DMN files: > {quote}*file1.dmn* > - Person (Structure) > -- name (Text) > -- age (Number){quote} > {quote}*file2.dmn* > - Order (Structure) > -- price (Number) > -- product (Text) > -- salesman (file1.Person) > -- buyer (file1.Person){quote} > Notice that the user cannot delete the "file1.dmn", because it is referenced by the "file2.dmn". > Other scenarios: > - How to handle DMN files from {{kjars}}? > - Is the user allowed to rename the Data Type "Person"? > - Is the user allowed to remove the Data Type "Person"? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3384) [DMN Designer] DMN Editor Index

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3384?page=com.atlassian.jira.plugi... ] Guilherme Gomes commented on DROOLS-3384: ----------------------------------------- Closing it since this we won't address these scenarios for now. > [DMN Designer] DMN Editor Index > ------------------------------- > > Key: DROOLS-3384 > URL: https://issues.jboss.org/browse/DROOLS-3384 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Affects Versions: 7.15.0.Final > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > > This JIRA aims to cover all tasks related to interactions between DMN files. > The Import Feature introduces scenarios that couples DMN files to each other. See these two DMN files: > {quote}*file1.dmn* > - Person (Structure) > -- name (Text) > -- age (Number){quote} > {quote}*file2.dmn* > - Order (Structure) > -- price (Number) > -- product (Text) > -- salesman (file1.Person) > -- buyer (file1.Person){quote} > Notice that the user cannot delete the "file1.dmn", because it is referenced by the "file2.dmn". > Other scenarios: > - How to handle DMN files from {{kjars}}? > - Is the user allowed to rename the Data Type "Person"? > - Is the user allowed to remove the Data Type "Person"? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11679) Remove org.jboss.metadata module

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11679?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFLY-11679: ------------------------------ Fix Version/s: (was: 17.0.0.Beta1) > Remove org.jboss.metadata module > -------------------------------- > > Key: WFLY-11679 > URL: https://issues.jboss.org/browse/WFLY-11679 > Project: WildFly > Issue Type: Sub-task > Components: Class Loading, Clustering > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Minor > > Not urgent, just something I noticed when looking at https://github.com/wildfly/wildfly/pull/12014/. > The org.jboss.metadata module just depends on and exports a bunch of other ones. It's jboss-api=private and It's only use within Wildfly is org.wildfly.extension.clustering.singleton which could presumably depend directly on what it needs. > We'd want to check some with dependent projects in case they use it and do any removal fairly early in a release cycle. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11679) Remove org.jboss.metadata module

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11679?page=com.atlassian.jira.plugin... ] Kabir Khan reopened WFLY-11679: ------------------------------- [~yersan] I am reopening this as I have merged the revert > Remove org.jboss.metadata module > -------------------------------- > > Key: WFLY-11679 > URL: https://issues.jboss.org/browse/WFLY-11679 > Project: WildFly > Issue Type: Sub-task > Components: Class Loading, Clustering > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Minor > > Not urgent, just something I noticed when looking at https://github.com/wildfly/wildfly/pull/12014/. > The org.jboss.metadata module just depends on and exports a bunch of other ones. It's jboss-api=private and It's only use within Wildfly is org.wildfly.extension.clustering.singleton which could presumably depend directly on what it needs. > We'd want to check some with dependent projects in case they use it and do any removal fairly early in a release cycle. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019