May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2549) [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2549?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2549: ----------------------------------- Description: {{DMNModelInstrumentedBase}} needs to support {{parent}} (like {{org.kie.dmn.model.v1_1.DMNModelInstrumentedBase}}) in order to correctly implement {{getPrefixForNamespaceURI(..)}} that is needed to set the {{QName}} prefix when setting data-types on nodes. At the moment the {{QName}} for data-types in the UI is using the {{namespaceURI}} instead of the {{prefix}} as it is currently impossible to lookup a {{prefix}} from the {{namespaceURI}} (of the nodes' parents up to {{Definitions}}). Changes required for this JIRA (split into sub-tasks when work starts):- * Update XML->(kie)DMN->(ui)DMN model mapping in the marshaller * Update the UI to set {{parent}} when adding nodes to the {{DRGElement}} and children * Update code relating to "setting data-type" to lookup {{prefix}} for {{QName}} (/) * When creating a new Diagram we need to set up the basic default NameSpace contexts on the {{DMNDiagram}}'s {{Defintions}} (/) was: {{DMNModelInstrumentedBase}} needs to support {{parent}} (like {{org.kie.dmn.model.v1_1.DMNModelInstrumentedBase}}) in order to correctly implement {{getPrefixForNamespaceURI(..)}} that is needed to set the {{QName}} prefix when setting data-types on nodes. At the moment the {{QName}} for data-types in the UI is using the {{namespaceURI}} instead of the {{prefix}} as it is currently impossible to lookup a {{prefix}} from the {{namespaceURI}} (of the nodes' parents up to {{Definitions}}). Changes required for this JIRA (split into sub-tasks when work starts):- * Update XML->(kie)DMN->(ui)DMN model mapping in the marshaller * Update the UI to set {{parent}} when adding nodes to the {{DRGElement}} and children * Update code relating to "setting data-type" to lookup {{prefix}} for {{QName}} (/) * When creating a new Diagram we need to set up the basic default NameSpace contexts on the {{DMNDiagram}}'s {{Defintions}}. > [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase > ------------------------------------------------------------------- > > Key: DROOLS-2549 > URL: https://issues.jboss.org/browse/DROOLS-2549 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > {{DMNModelInstrumentedBase}} needs to support {{parent}} (like {{org.kie.dmn.model.v1_1.DMNModelInstrumentedBase}}) in order to correctly implement {{getPrefixForNamespaceURI(..)}} that is needed to set the {{QName}} prefix when setting data-types on nodes. > At the moment the {{QName}} for data-types in the UI is using the {{namespaceURI}} instead of the {{prefix}} as it is currently impossible to lookup a {{prefix}} from the {{namespaceURI}} (of the nodes' parents up to {{Definitions}}). > Changes required for this JIRA (split into sub-tasks when work starts):- > * Update XML->(kie)DMN->(ui)DMN model mapping in the marshaller > * Update the UI to set {{parent}} when adding nodes to the {{DRGElement}} and children > * Update code relating to "setting data-type" to lookup {{prefix}} for {{QName}} (/) > * When creating a new Diagram we need to set up the basic default NameSpace contexts on the {{DMNDiagram}}'s {{Defintions}} (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2579) [DMN Designer] Add support for setting 'DMNModelInstrumentedBase.setParent(..)' to the UI model as and when Users create new elements

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2579?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2579: ----------------------------------- Tester: Jozef Marko > [DMN Designer] Add support for setting 'DMNModelInstrumentedBase.setParent(..)' to the UI model as and when Users create new elements > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2579 > URL: https://issues.jboss.org/browse/DROOLS-2579 > Project: Drools > Issue Type: Sub-task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > When the User authors a DMN file they can add new elements. These elements need to have their parent correctly set. {{QNameFieldConverter.toWidgetValue(..)}} can have the fallback removed once this is complete. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2579) [DMN Designer] Add support for setting 'DMNModelInstrumentedBase.setParent(..)' to the UI model as and when Users create new elements

by Michael Anstis (JIRA)

Michael Anstis created DROOLS-2579: -------------------------------------- Summary: [DMN Designer] Add support for setting 'DMNModelInstrumentedBase.setParent(..)' to the UI model as and when Users create new elements Key: DROOLS-2579 URL: https://issues.jboss.org/browse/DROOLS-2579 Project: Drools Issue Type: Sub-task Components: DMN Editor Reporter: Michael Anstis Assignee: Michael Anstis When the User authors a DMN file they can add new elements. These elements need to have their parent correctly set. {{QNameFieldConverter.toWidgetValue(..)}} can have the fallback removed once this is complete. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

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

by Michael Anstis (JIRA)

Michael Anstis created DROOLS-2578: -------------------------------------- Summary: [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 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)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1589) elytron-client-1_1.xsd is invalid

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1589?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1589: ---------------------------- Description: XSD validation of test-wildfly-config.xml in tests fails because of invalid XSD: {noformat}Src-resolve: Cannot Resolve The Name 'resource-type' To A(n) 'simpleType Definition' Component.{noformat} Problem is, "resource-type" (which is complexType) is used as type of an attribute (not of an element) in certificate-revocation-list-type. was: XSD validation of test-wildfly-config.xml in tests fails because of invalid XSD: {noformat}Src-resolve: Cannot Resolve The Name 'resource-type' To A(n) 'simpleType Definition' Component.{noformat} > elytron-client-1_1.xsd is invalid > --------------------------------- > > Key: ELY-1589 > URL: https://issues.jboss.org/browse/ELY-1589 > Project: WildFly Elytron > Issue Type: Bug > Components: XML > Affects Versions: 1.3.2.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > > XSD validation of test-wildfly-config.xml in tests fails because of invalid XSD: > {noformat}Src-resolve: Cannot Resolve The Name 'resource-type' To A(n) 'simpleType Definition' Component.{noformat} > Problem is, "resource-type" (which is complexType) is used as type of an attribute (not of an element) in certificate-revocation-list-type. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10421) Validate the content of the thin server-build

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-10421: --------------------------------------- Summary: Validate the content of the thin server-build Key: WFLY-10421 URL: https://issues.jboss.org/browse/WFLY-10421 Project: WildFly Issue Type: Bug Components: Build System Reporter: Brian Stansberry Assignee: Yeray Borges Follow up to WFLY-10409, but focused on server-build vs server-dist. This is probably kind of a 3 phase thing: 1) Make sure servlet-dist is correct. Possible approach: remove modules/system and then compare the content of dist and servlet-dist, largely focusing on missing files. No need to spend energy on comparing files that exist but would reasonably differ in details, like config files, license files, .galleon dir content. This validates servlet-dist itself. 2) Compare servlet-build to servlet-dist after removing modules/system and correct issues. 3) Look at servlet-[build|dist]-legacy which now may differ from the galleon equivalents. Adjust legacy to bring in things that were missing. Goal is to make sure we can still do diffs of galleon vs legacy to spot other issues without having to sort through too many known diffs. This isn't particularly high priority, as it's arguable that we should drop these servlet-xxx maven modules altogether as users will be able to create equivalents using the galleon tool. Arguable, but certainly not a for sure thing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-200) B12 OpenShift Cluster is flaky

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-200?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-200. -------------------------------- Resolution: Done > B12 OpenShift Cluster is flaky > ------------------------------ > > Key: SWSQE-200 > URL: https://issues.jboss.org/browse/SWSQE-200 > Project: Kiali QE > Issue Type: QE Task > Reporter: Kevin Earls > Assignee: Guilherme Baufaker Rêgo > Priority: Minor > > I'm opening this mostly as a placeholder, and will update it as I get more information on the problems I've been experiencing. Since I've been using B12 I've been experiencing more frequent failures than on other clusters, including minishift on my laptop and the CNCF CI Jenkins. Here are a couple of instances: > 1. Deploying ElasticSearch along with the Jaeger Production templates requires allocating 2G or memory, even though the default 512M works fine elsewhere. This can be seen in the Jaeger Standalone Performance tests job here: https://jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com/job/J... . If you run the job without changing the ES_MEMORY parameter to 2Gi it will fail. > 2. I have a set of smoke tests for Red Hat productized artifacts for the Jaeger Java client which are run using the Jaeger all-in-one template. It's fairly simple, but on B12 deployment of the Jaeger all-in-one images fails on every other build. I've made a copy of the job here: https://jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com/job/F... and its history should be clear. > So far I have not been able to get any useful information about why this is failing. In the OpenShift console it looks like Jaeger has started correctly. There are no errors in the logs, nor any to be found under monitoring. But if you click on the Jaeger link, you get the message "Application is not available . The application is currently not serving requests at this endpoint. It may not have been started or is still starting." -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2564) [DMN Editor] Add support to use data-types on applicable Expression types

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2564?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2564: ----------------------------------- Summary: [DMN Editor] Add support to use data-types on applicable Expression types (was: [DMN Editor] Add to use data-types on applicable Expression types) > [DMN Editor] Add support to use data-types on applicable Expression types > ------------------------------------------------------------------------- > > Key: DROOLS-2564 > URL: https://issues.jboss.org/browse/DROOLS-2564 > Project: Drools > Issue Type: Sub-task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2577) drools-core depends on mvel 2.3.2 and mvel 2.4.0

by Jan Hrcek (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2577?page=com.atlassian.jira.plugi... ] Jan Hrcek edited comment on DROOLS-2577 at 5/22/18 8:07 AM: ------------------------------------------------------------ Please take this report with a grain of salt for now, it's work in progress. These data come from merging dependency trees of all maven modules of kiegroup projects. I'll check later today which dependency trees this info comes from.. was (Author: jhrcek): Please take this report with a grand of salt for now, it's work in progress. These data come from merging dependency trees of all maven modules of kiegroup projects. I'll check later today which dependency trees this info comes from.. > drools-core depends on mvel 2.3.2 and mvel 2.4.0 > ------------------------------------------------ > > Key: DROOLS-2577 > URL: https://issues.jboss.org/browse/DROOLS-2577 > Project: Drools > Issue Type: Enhancement > Components: build, core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Attachments: Selection_762.png > > > http://janhrcek.cz/kiegroup-dependencies/ > See screenshot > !Selection_762.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2577) drools-core depends on mvel 2.3.2 and mvel 2.4.0

by Jan Hrcek (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2577?page=com.atlassian.jira.plugi... ] Jan Hrcek commented on DROOLS-2577: ----------------------------------- Please take this report with a grand of salt for now, it's work in progress. These data come from merging dependency trees of all maven modules of kiegroup projects. I'll check later today which dependency trees this info comes from.. > drools-core depends on mvel 2.3.2 and mvel 2.4.0 > ------------------------------------------------ > > Key: DROOLS-2577 > URL: https://issues.jboss.org/browse/DROOLS-2577 > Project: Drools > Issue Type: Enhancement > Components: build, core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Attachments: Selection_762.png > > > http://janhrcek.cz/kiegroup-dependencies/ > See screenshot > !Selection_762.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 May 2018