September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3022) [DMN Designer] Data Types - Validations - Validate the uniqueness of a Data Type name

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3022?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3022: --------------------------------------- Sprint: 2018 Week 39-41 > [DMN Designer] Data Types - Validations - Validate the uniqueness of a Data Type name > ------------------------------------------------------------------------------------- > > Key: DROOLS-3022 > URL: https://issues.jboss.org/browse/DROOLS-3022 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Labels: drools-tools > Attachments: validation.png > > > The Data Type name must be unique at the level that it's defined; e.g. > - tPerson > -- uuid > -- name > -- city (Structure) > --- uuid > --- name > The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels. > ---- > Prototype: > !validation.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3025) [DMN Designer] Data Types - Set a Data Type as a collection Data Type

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3025?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3025: --------------------------------------- Sprint: 2018 Week 39-41 > [DMN Designer] Data Types - Set a Data Type as a collection Data Type > --------------------------------------------------------------------- > > Key: DROOLS-3025 > URL: https://issues.jboss.org/browse/DROOLS-3025 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Labels: drools-tools > Attachments: edit-mode-closed.png, interaction.gif > > > - A Data Type must be set as a collection data type; > - Interaction: > !interaction.gif|thumbnail! > - When edit mode is closed, it should show "✔ Yes" for a collection data type and none for a non-collection data type: > !edit-mode-closed.png|thumbnail! > - PatternFly base element for the switch button https://www.patternfly.org/pattern-library/widgets/#bootstrap-switch -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3025) [DMN Designer] Data Types - Set a Data Type as a collection Data Type

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3025?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3025: --------------------------------------- Sprint: (was: 2018 Week 39-41) > [DMN Designer] Data Types - Set a Data Type as a collection Data Type > --------------------------------------------------------------------- > > Key: DROOLS-3025 > URL: https://issues.jboss.org/browse/DROOLS-3025 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Labels: drools-tools > Attachments: edit-mode-closed.png, interaction.gif > > > - A Data Type must be set as a collection data type; > - Interaction: > !interaction.gif|thumbnail! > - When edit mode is closed, it should show "✔ Yes" for a collection data type and none for a non-collection data type: > !edit-mode-closed.png|thumbnail! > - PatternFly base element for the switch button https://www.patternfly.org/pattern-library/widgets/#bootstrap-switch -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3023) [DMN Designer] Data Types - Warnings - User must be warned when some operations affect other Data Types

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3023?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3023: --------------------------------------- Sprint: 2018 Week 39-41 > [DMN Designer] Data Types - Warnings - User must be warned when some operations affect other Data Types > ------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3023 > URL: https://issues.jboss.org/browse/DROOLS-3023 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Labels: drools-tools > > 1) When a Structure Data Type (with fields) is updated to a simple type (e.g. String, Number, Date, etc), a warn message must appear informing the user that the fields will be lost. > - tPerson > -- uuid > -- name > -- city (Structure) <-- If this data type is updated to "String", the "uuid" and "name" fields will be lost. > --- uuid > --- name > ---- > 2) When a Data Type is removed, a warn message must appear informing the user that data types with the removed type will be removed too. > - tCity <-- If the user removes this Data Type > -- uuid > -- name > - tPerson > -- uuid > -- name > -- city (tCity) <-- This field will be removed too.. > --- uuid <-- ..and consequently.. > --- name <-- ..these two will be removed too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-395) jboss-app:moduleType should use jee:moduleType as a base

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/JBMETA-395?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet resolved JBMETA-395. -------------------------------------- Resolution: Done > jboss-app:moduleType should use jee:moduleType as a base > -------------------------------------------------------- > > Key: JBMETA-395 > URL: https://issues.jboss.org/browse/JBMETA-395 > Project: JBoss Metadata > Issue Type: Bug > Components: ear > Reporter: Rob Stryker > Fix For: 12.0.0.Final > > > While attempting to make a simple ear with a war and a service inside, we run into several validation errors continuously. The following xml, for example, fails to validate: > {code} > <?xml version="1.1" encoding="UTF-8"?> > <jboss-app version="6" xmlns="http://www.jboss.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:jbee="http://www.jboss.com/xml/ns/javaee" > xmlns:jee="http://java.sun.com/xml/ns/javaee" > xsi:schemaLocation=" > http://www.jboss.com/xml/ns/javaee > http://www.jboss.org/schema/jbossas/jboss-app_7_0.xsd"> > <jee:display-name>Test</jee:display-name> > <jee:module> > <jee:web> > <jee:web-uri>myweb.war</jee:web-uri> > <jee:context-root>SomeRoot</jee:context-root> > </jee:web> > <jbee:service>bundled.sar</jbee:service> > </jee:module> > <jbee:distinct-name>MyDistinct</jbee:distinct-name> > </jboss-app> > {code} > The error is: cvc-complex-type.2.4.a: Invalid content was found starting with element 'jbee:service'. One of '{"http:// java.sun.com/xml/ns/javaee":alt-dd}' is expected. > Basically, a jbee:service does not belong inside a jee:module. However, trying to declare jbee:module rather than jee:module fails because: cvc-complex-type.2.4.a: Invalid content was found starting with element 'jbee:module'. One of '{"http:// > java.sun.com/xml/ns/javaee":display-name, "http://java.sun.com/xml/ns/javaee":icon, "http://java.sun.com/ > xml/ns/javaee":initialize-in-order, "http://java.sun.com/xml/ns/javaee":module}' is expected. > In short, jbee:moduleType should probably be using jee:moduleType as a base. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-411) Typo in jboss-common_7_1.xsd

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/JBMETA-411?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet resolved JBMETA-411. -------------------------------------- Fix Version/s: 12.0.0.Final Resolution: Done > Typo in jboss-common_7_1.xsd > ---------------------------- > > Key: JBMETA-411 > URL: https://issues.jboss.org/browse/JBMETA-411 > Project: JBoss Metadata > Issue Type: Bug > Components: common > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Fix For: 12.0.0.Final > > > There is a space in the namespace declaration -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-408) security-domainType defined twice

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/JBMETA-408?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet resolved JBMETA-408. -------------------------------------- Fix Version/s: 12.0.0.Final Resolution: Done > security-domainType defined twice > --------------------------------- > > Key: JBMETA-408 > URL: https://issues.jboss.org/browse/JBMETA-408 > Project: JBoss Metadata > Issue Type: Bug > Components: common, web > Reporter: Kaz Nishimura > Assignee: Jean-Frederic Clere > Labels: schema > Fix For: 12.0.0.Final > > > The files jboss-web_11_0.xsd and jboss-web_12_0.xsd redefines {{security-domainType}} that has already been defined in jboss-common_7_0.xsd. It might cause validation errors. > If a new attribute is added to {{security-domainType}} in WildFly 11, we should have jboss-common_11_0.xsd, shouldn't we? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-393) Missing jboss-web_10_0.xsd on jboss.org

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/JBMETA-393?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet closed JBMETA-393. ------------------------------------ Fix Version/s: 10.0.2.Final Resolution: Done > Missing jboss-web_10_0.xsd on jboss.org > --------------------------------------- > > Key: JBMETA-393 > URL: https://issues.jboss.org/browse/JBMETA-393 > Project: JBoss Metadata > Issue Type: Bug > Components: web > Reporter: Ladislav Thon > Assignee: Jean-Frederic Clere > Priority: Critical > Fix For: 10.0.2.Final > > > The {{jboss-web_10_0.xsd}} file we ship with WildFly 10 says at the beginning: > {code:xml} > <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_10_0.xsd" > version="10.0"> > ... > </jboss-web> > Instance documents may indicate the published version of > the schema using the xsi:schemaLocation attribute for the > Java EE namespace with the following location: > http://www.jboss.org/j2ee/schema/jboss-web_10_0.xsd > {code} > So we're pointing people to http://www.jboss.org/j2ee/schema/, which is a seemingly arbitrary collection of fairly old files that definitely doesn't contain {{jboss-web_10_0.xsd}}. > This seems to also be the case for XSDs in previously shipped products, e.g. all {{jboss-web_7_*.xsd}} files in EAP 6.4 point to the same location. > I found that http://www.jboss.org/schema/jbossas/ contains a more modern set of XSDs, but: > - we don't point to it, at least not from {{jboss-web_*.xsd}} files > - it doesn't contain {{jboss-web_10_0.xsd}} > I think the second point should be fairly easy to fix. Hope this is not the wrong place to report this :-) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2788: -------------------------------- Sprint: 2018 Week 33-35, 2018 Week 36-38, 2018 Week 39-41 (was: 2018 Week 33-35, 2018 Week 36-38) > UX to support selection of multiple data/domain object instances > ---------------------------------------------------------------- > > Key: DROOLS-2788 > URL: https://issues.jboss.org/browse/DROOLS-2788 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png, Screen Shot 2018-09-19 at 11.44.07 AM.png, now-headers.png > > > As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3496) Upgrade WildFly Elytron to 1.2.0.Beta13

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3496?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved WFCORE-3496. -------------------------------------- Resolution: Out of Date > Upgrade WildFly Elytron to 1.2.0.Beta13 > --------------------------------------- > > Key: WFCORE-3496 > URL: https://issues.jboss.org/browse/WFCORE-3496 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Ivo Studensky > Labels: downstream_dependency > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 September 2018