October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3000) Enhance data type restrictions UX (decision tables & DT dialog)

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3000: --------------------------------------- Attachment: enumration-widget.png > Enhance data type restrictions UX (decision tables & DT dialog) > --------------------------------------------------------------- > > Key: DROOLS-3000 > URL: https://issues.jboss.org/browse/DROOLS-3000 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > 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)

6 years, 3 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 closed JBMETA-395. ------------------------------------ > 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 > Priority: Major > 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.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-394) jboss-app_7_0.xsd imports jboss-common_6_0.xsd and application_6.xsd

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/JBMETA-394?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet closed JBMETA-394. ------------------------------------ > jboss-app_7_0.xsd imports jboss-common_6_0.xsd and application_6.xsd > -------------------------------------------------------------------- > > Key: JBMETA-394 > URL: https://issues.jboss.org/browse/JBMETA-394 > Project: JBoss Metadata > Issue Type: Bug > Components: ear > Reporter: Rob Stryker > Priority: Major > Fix For: 12.0.0.Final > > > The following xml code in eclipse fails the validate: > {code} > <?xml version="1.1" encoding="UTF-8"?> > <jboss-app version="7.0" xmlns="http://www.jboss.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:jee="http://www.jboss.com/xml/ns/javaee" > xsi:schemaLocation=" > http://www.jboss.com/xml/ns/javaee > http://www.jboss.org/schema/jbossas/jboss-app_7_0.xsd"> > <description>test</description> > </jboss-app> > {code} > The error is: cvc-complex-type.3.1: Value '7.0' of attribute 'version' of element 'jboss-app' is not valid with respect to > the corresponding attribute use. Attribute 'version' has a fixed value of '6'. > This is clearly caused by the intermingling of jee 7 with jee6 in the schemas. These schemas need to be cleaned up or our users will be experiencing errors all the time. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-363) Validation errors with "jboss-web_7_0.xsd

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/JBMETA-363?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet closed JBMETA-363. ------------------------------------ > Validation errors with "jboss-web_7_0.xsd > ----------------------------------------- > > Key: JBMETA-363 > URL: https://issues.jboss.org/browse/JBMETA-363 > Project: JBoss Metadata > Issue Type: Bug > Components: web > Affects Versions: 7.0.5.Final, 8.1.2.Final > Environment: Eclipse > Reporter: Wolfgang Knauf > Assignee: Jean-Frederic Clere > Priority: Major > Fix For: 12.0.0.Final > > > I tried to create a "jboss-web.xml" file based on the "jboss-web_7_1.xsd" > As this is not uploaded to the web up to now, I created it with a schema location pointing to my local JBoss 7.2.0Alpha1 snapshot: > <?xml version="1.0" encoding="UTF-8"?> > <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 file:///C:/Temp/jboss-as-7.2.0.Alpha1-SNAPSHOT/docs/schema/jboss-web_7_0.xsd" > version="7.0"> > ... > </jboss-web> > Eclipse shows validation errors in the XSD file. > The first on is: > sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two > occurences of 'http://java.sun.com/xml/ns/javaee,descriptionGroup' > (occurs in javaee_6.xsd, line 88) > And a lot more of those. > The file was created as part of https://issues.jboss.org/browse/AS7-1262 - and the one who created it found the same validation error. > It seems the fix is quite simple: > "jboss-web_7_0.xsd" contains this import: > <xsd:import namespace="http://java.sun.com/xml/ns/javaee" schemaLocation="web-app_3_0.xsd"/> > Change it to: > <xsd:import namespace="http://java.sun.com/xml/ns/javaee" schemaLocation="http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"/> > The reason seems to be: "jboss-web_7_0.xsd" imports "jboss-common_6-0.xsd", and this one imports "javaee_6.xsd" with a full schema location. > The "web-app_3_0.xsd" in "jboss-web_7_0.xsd" has a local schema location, thus the "javaee_6.xsd" import in "web-app_3_0.xsd" points also to local. > And this seems to cause a duplicate import of the file. > (might also be an Eclipse valiation bug) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-404) Validation errors with "jboss-web_11_0.xsd

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/JBMETA-404?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet closed JBMETA-404. ------------------------------------ > Validation errors with "jboss-web_11_0.xsd > ------------------------------------------ > > Key: JBMETA-404 > URL: https://issues.jboss.org/browse/JBMETA-404 > Project: JBoss Metadata > Issue Type: Bug > Affects Versions: 10.0.2.Final > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Major > Fix For: 12.0.0.Final > > > Eclipse reports some errors when validating a "jboss-web.xml" file which defines the 11.0 xsd. > First problem: "web-app_3_1.xsd" is imported. The target namespace seems to be invalid, it should be "http://xmlns.jcp.org/xml/ns/javaee" instead of "http://java.sun.com/xml/ns/javaee" > <xsd:import namespace="http://xmlns.jcp.org/xml/ns/javaee" schemaLocation="http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"/> > The validation error: *"The namespace attribute 'http://java.sun.com/xml/ns/javaee' of an import element information must be identical to the targetNamespace attribute 'http://xmlns.jcp.org/xml/ns/javaee' of the imported document".* > It would probably also make sense to include the full schemaLocation URL ;-). > After fixing the namespace, there are four more errors left: > *src-resolve: Cannot resolve the name 'jboss:jndiEnvironmentRefsGroup' to a( n ) group component > src-resolve: Cannot resolve the name 'javaee:generic-booleanType' to a( n ) 'simpleType definition' component > src-ct.2.1: Complex type definition Representation Error for type 'symbolic-link-allowedType' ... > src-resolve: Cannot resolve the name 'jboss:security-roleType' to a( n ) 'type definition' component* > The first two errors: previous versions of jboss-web.xsd imported "jboss-common_6_0.xsd" which defined a "jndiEnvironmentRefsGroup". This file also imported "javaee_6.xsd", which defines the "generic-booleanType". -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-398) The jboss-web_7_1.xsd and 7.2.xsd file cause validation errors in Eclipse

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/JBMETA-398?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet closed JBMETA-398. ------------------------------------ > The jboss-web_7_1.xsd and 7.2.xsd file cause validation errors in Eclipse > ------------------------------------------------------------------------- > > Key: JBMETA-398 > URL: https://issues.jboss.org/browse/JBMETA-398 > Project: JBoss Metadata > Issue Type: Bug > Components: web > Affects Versions: 7.2.0.Final > Reporter: Radovan Netuka > Assignee: Radovan Netuka > Priority: Major > Fix For: 12.0.0.Final > > > The jboss-web_7_2.xsd file cause validation errors in eclipse. > The following error from line 261: > src-ct.2.1: Complex Type Definition Representation Error for type 'symbolic-linked-allowedType'. When <simpleContent> is used, the base type must be a complexType whose content type is simple, or, only if restriction is specified, a complex type with mixed content and emptiable particle, or, only if extension is specified, a simple type. 'boolean' satisfies none of these conditions > This also happens in jboss-web_7_1.xsd -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-405) [JDK9+] org.jboss.metadata.merge package is exported by multiple jars

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/JBMETA-405?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet closed JBMETA-405. ------------------------------------ > [JDK9+] org.jboss.metadata.merge package is exported by multiple jars > --------------------------------------------------------------------- > > Key: JBMETA-405 > URL: https://issues.jboss.org/browse/JBMETA-405 > Project: JBoss Metadata > Issue Type: Bug > Components: common, ear > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Major > Fix For: 12.0.0.Final > > > if you have > jboss-metadata-ear-11.0.0.Final.jar and jboss-metadata-common-11.0.0.Final.jar > on your module path, jvm complains as both jars export package {{org.jboss.metadata.merge}} > which violates the modules contract where only one module (jar) can provide single package. > example error that jvm prints > {noformat} > Error: Modules jboss.metadata.ear and jboss.metadata.common export package org.jboss.metadata.merge to module wildfly.clustering.common > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-397) Typo in jboss-client_6_0.xsd - "applicetion"

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/JBMETA-397?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet closed JBMETA-397. ------------------------------------ > Typo in jboss-client_6_0.xsd - "applicetion" > -------------------------------------------- > > Key: JBMETA-397 > URL: https://issues.jboss.org/browse/JBMETA-397 > Project: JBoss Metadata > Issue Type: Bug > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Trivial > Fix For: 12.0.0.Final > > > Typo in jboss-client_6_0.xsd: > ...All the applicetion client deployment descriptors must... > should be: > ...All the application client deployment descriptors must... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-407) jboss-common_7_0.xsd should not include itself

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/JBMETA-407?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet closed JBMETA-407. ------------------------------------ > jboss-common_7_0.xsd should not include itself > ---------------------------------------------- > > Key: JBMETA-407 > URL: https://issues.jboss.org/browse/JBMETA-407 > Project: JBoss Metadata > Issue Type: Bug > Components: common > Reporter: Kaz Nishimura > Priority: Minor > Labels: schema > Fix For: 12.0.0.Final > > > The file [jboss-common_7_0.xsd|https://github.com/jboss/metadata/blob/b55f691848d9d...] contains this line: > {{<xsd:include schemaLocation="jboss-common_7_0.xsd"/>}} > It includes the file itself. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 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 closed JBMETA-408. ------------------------------------ > 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 > Priority: Major > 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.12.1#712002)

6 years, 3 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 October 2018