June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13572) Upgrade Mojarra to 2.3.9.SP11

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13572?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-13572: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13366, https://github.com/wildfly/wildfly/pull/13367 (was: https://github.com/wildfly/wildfly/pull/13366) > Upgrade Mojarra to 2.3.9.SP11 > ----------------------------- > > Key: WFLY-13572 > URL: https://issues.redhat.com/browse/WFLY-13572 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Chao Wang > Assignee: Farah Juma > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13573) Upgrade JBoss JSF API from 3.0.0.SP03 to 3.0.0.SP04

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13573?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-13573: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13366, https://github.com/wildfly/wildfly/pull/13367 (was: https://github.com/wildfly/wildfly/pull/13366) > Upgrade JBoss JSF API from 3.0.0.SP03 to 3.0.0.SP04 > --------------------------------------------------- > > Key: WFLY-13573 > URL: https://issues.redhat.com/browse/WFLY-13573 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Affects Versions: 20.0.0.Beta1 > Reporter: Chao Wang > Assignee: Farah Juma > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13573) Upgrade JBoss JSF API from 3.0.0.SP03 to 3.0.0.SP04

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13573?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-13573: ------------------------------ Fix Version/s: (was: 20.0.0.Final) > Upgrade JBoss JSF API from 3.0.0.SP03 to 3.0.0.SP04 > --------------------------------------------------- > > Key: WFLY-13573 > URL: https://issues.redhat.com/browse/WFLY-13573 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Affects Versions: 20.0.0.Beta1 > Reporter: Chao Wang > Assignee: Farah Juma > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13572) Upgrade Mojarra to 2.3.9.SP11

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13572?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-13572: ------------------------------ Fix Version/s: (was: 20.0.0.Final) > Upgrade Mojarra to 2.3.9.SP11 > ----------------------------- > > Key: WFLY-13572 > URL: https://issues.redhat.com/browse/WFLY-13572 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Chao Wang > Assignee: Farah Juma > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13571) JSF: selectOneMenu required+disabled true

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13571?page=com.atlassian.jira.plugi... ] Farah Juma edited comment on WFLY-13571 at 6/16/20 11:19 AM: ------------------------------------------------------------- Just FYI, I've submitted the following PRs against the WildFly master branch and the WildFly 20.x branch that contain [~soul2zimate]'s fix: [https://github.com/wildfly/wildfly/pull/13366] [https://github.com/wildfly/wildfly/pull/13367] was (Author: fjuma): Just FYI, I've submitted the following PRs against WildFly master and WildFly 20.x that contain [~soul2zimate]'s fix: [https://github.com/wildfly/wildfly/pull/13366] [https://github.com/wildfly/wildfly/pull/13367] > JSF: selectOneMenu required+disabled true > ----------------------------------------- > > Key: WFLY-13571 > URL: https://issues.redhat.com/browse/WFLY-13571 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 20.0.0.Final > Reporter: erick leal > Assignee: Farah Juma > Priority: Major > Attachments: project.zip > > > Submitin selectOneMenu required=true+disabled=true result in validation error message. > Regression in WildFly 20, clicking button fires a message. > WildFly 19 it's ok. > Mojarra issue: https://github.com/eclipse-ee4j/mojarra/issues/4716 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13571) JSF: selectOneMenu required+disabled true

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13571?page=com.atlassian.jira.plugi... ] Farah Juma edited comment on WFLY-13571 at 6/16/20 11:19 AM: ------------------------------------------------------------- Just FYI, I've submitted the following PRs against WildFly master and WildFly 20.x that contain [~soul2zimate]'s fix: [https://github.com/wildfly/wildfly/pull/13366] [https://github.com/wildfly/wildfly/pull/13367] was (Author: fjuma): Just FYI, I've submitted the following PRs against WildFly master and WildFly 20.x that contain [~soul2zimate]'s fix: [https://github.com/wildfly/wildfly/pull/13366] [https://github.com/wildfly/wildfly/pull/13367] > JSF: selectOneMenu required+disabled true > ----------------------------------------- > > Key: WFLY-13571 > URL: https://issues.redhat.com/browse/WFLY-13571 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 20.0.0.Final > Reporter: erick leal > Assignee: Farah Juma > Priority: Major > Attachments: project.zip > > > Submitin selectOneMenu required=true+disabled=true result in validation error message. > Regression in WildFly 20, clicking button fires a message. > WildFly 19 it's ok. > Mojarra issue: https://github.com/eclipse-ee4j/mojarra/issues/4716 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13571) JSF: selectOneMenu required+disabled true

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13571?page=com.atlassian.jira.plugi... ] Farah Juma commented on WFLY-13571: ----------------------------------- Just FYI, I've submitted the following PRs against WildFly master and WildFly 20.x that contain [~soul2zimate]'s fix: [https://github.com/wildfly/wildfly/pull/13366] [https://github.com/wildfly/wildfly/pull/13367] > JSF: selectOneMenu required+disabled true > ----------------------------------------- > > Key: WFLY-13571 > URL: https://issues.redhat.com/browse/WFLY-13571 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 20.0.0.Final > Reporter: erick leal > Assignee: Farah Juma > Priority: Major > Attachments: project.zip > > > Submitin selectOneMenu required=true+disabled=true result in validation error message. > Regression in WildFly 20, clicking button fires a message. > WildFly 19 it's ok. > Mojarra issue: https://github.com/eclipse-ee4j/mojarra/issues/4716 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5427) Update Type in Traffic Violation example

by Anna Dupliak (Jira)

[ https://issues.redhat.com/browse/DROOLS-5427?page=com.atlassian.jira.plug... ] Anna Dupliak deleted DROOLS-5427: --------------------------------- > Update Type in Traffic Violation example > ---------------------------------------- > > Key: DROOLS-5427 > URL: https://issues.redhat.com/browse/DROOLS-5427 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.38.0.Final > Reporter: Anna Dupliak > Assignee: Anna Dupliak > Priority: Minor > Labels: drools-tools > > Since we changed a constraints type mechanism we the old test scenario got failing > > > So need to recreate scesim file in Traffic Violation example. > > workarounds: > if you recreate scesim > > > > if you remove that column and add it again, no error is raised -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5434) Incorrect warning about file declaring wrong package

by Magnus Larsson (Jira)

[ https://issues.redhat.com/browse/DROOLS-5434?page=com.atlassian.jira.plug... ] Magnus Larsson updated DROOLS-5434: ----------------------------------- Description: I am running Drools in a Spring-Boot jar and get the following warning statement _File 'BOOT-INF/classes/com/example/test/TEST.drl' is in folder 'BOOT-INF/classes/com/example/test' but declares package 'com.example.test'. It is advised to have a correspondance between package and folder names_. The package name in the drl file is correct, the problem is just that _BOOT-INF.classes._ isn't considered when evaluating if printing the warning or not. I have tracked it down to *KieBuilderImpl.java*, method *isFileInKieBase*. The last 2 lines in that method calls: {code:java} // packageNameForFile prints warning if package in .drl file is not same as flatted directory structure // Does not care about SUPPORTED_RESOURCES_ROOTS, thus prints the warning String pkgNameForFile = packageNameForFile( fileName, folderNameForFile, !useFolders, file ); // Does care about SUPPORTED_RESOURCES_ROOTS, so the drl file is loaded return isPackageInKieBase( kieBase, pkgNameForFile ); {code} As it is implemented right now, the warning might either be a false-positive (and still get loaded), or the package is wrong (and the file is not loaded). Voting to include the SUPPORTED_RESOURCES_ROOTS as valid prefixes when checking if the warning should be printed. was: I am running Drools in a Spring-Boot jar and get the following warning statement _File 'BOOT-INF/classes/com/example/test/TEST.drl' is in folder 'BOOT-INF/classes/com/example/test' but declares package 'com.example.test'. It is advised to have a correspondance between package and folder names_. The package name in the drl file is correct, the problem is just that _BOOT-INF.classes._ isn't considered when evaluating if printing the warning or not. I have tracked it down to *KieBuilderImpl.java*, method *isFileInKieBase*. The last 2 lines in that method calls: {code:java} // Does not care about SUPPORTED_RESOURCES_ROOTS, thus prints the warning String pkgNameForFile = packageNameForFile( fileName, folderNameForFile, !useFolders, file ); // Does care about SUPPORTED_RESOURCES_ROOTS, so the drl file is loaded return isPackageInKieBase( kieBase, pkgNameForFile ); {code} As it is implemented right now, the warning might either be a false-positive (and still get loaded), or the package is wrong (and the file is not loaded). Voting to include the SUPPORTED_RESOURCES_ROOTS as valid prefixes when checking if the warning should be printed. > Incorrect warning about file declaring wrong package > ---------------------------------------------------- > > Key: DROOLS-5434 > URL: https://issues.redhat.com/browse/DROOLS-5434 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Magnus Larsson > Assignee: Mario Fusco > Priority: Major > > I am running Drools in a Spring-Boot jar and get the following warning statement _File 'BOOT-INF/classes/com/example/test/TEST.drl' is in folder 'BOOT-INF/classes/com/example/test' but declares package 'com.example.test'. It is advised to have a correspondance between package and folder names_. The package name in the drl file is correct, the problem is just that _BOOT-INF.classes._ isn't considered when evaluating if printing the warning or not. > I have tracked it down to *KieBuilderImpl.java*, method *isFileInKieBase*. The last 2 lines in that method calls: > {code:java} > // packageNameForFile prints warning if package in .drl file is not same as flatted directory structure > // Does not care about SUPPORTED_RESOURCES_ROOTS, thus prints the warning > String pkgNameForFile = packageNameForFile( fileName, folderNameForFile, !useFolders, file ); > // Does care about SUPPORTED_RESOURCES_ROOTS, so the drl file is loaded > return isPackageInKieBase( kieBase, pkgNameForFile ); > {code} > As it is implemented right now, the warning might either be a false-positive (and still get loaded), or the package is wrong (and the file is not loaded). > Voting to include the SUPPORTED_RESOURCES_ROOTS as valid prefixes when checking if the warning should be printed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6938) Startup error messages caused by expression where expressions are not allowed are confusing

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-6938?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-6938: ---------------------------------------- This looks like two separate issues. The host.xml one would belong in WFCORE. Probably good to check it's still an issue first though. The main one, generally if an expression is not supported it's because the attribute is a model reference, and for such an attribute the wiring should be converted to use capabilities, which will result in a capability violation message. I think has been done for EE concurrency. I'm reluctant to start blanket rejecting text that looks like an expression because we think it's wrong, as perhaps it's valid text for some case. Perhaps the capability resolution handling could handle that a bit better though and provide a slightly different failure message if it finds expression text in the unresolvable capability name. That too would be something that should be tracked in WFCORE. > Startup error messages caused by expression where expressions are not allowed are confusing > ------------------------------------------------------------------------------------------- > > Key: WFLY-6938 > URL: https://issues.redhat.com/browse/WFLY-6938 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 10.1.0.CR1 > Reporter: Ondrej Chaloupka > Assignee: Lukas Vydra > Priority: Minor > > When a property expression is used at place where expression usage is not allowed then error message which is shown is quite confusing. From user point of view (especially the newcomer) it would be nice if the error message shows the real reason - usage of expression at place where is not permitted. > Maybe CLI could warn on usage of expression on place where is not allowed too. > Documentation recommends configuration with CLI, editing of XML file is common too. More of it there are some tasks which are harder to be done with CLI and editing XML is faster/easier. > Examples: > Setting > {code} > /subsystem=ee/managed-executor-service=default:write-attribute(name=context-service, value="${my.context.service}") > {code} > ends with this error message during startup > {code} > 14:13:21,076 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "ee"), > ("managed-executor-service" => "default") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.concurrent.ee.context.service.${my.context.service}"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.concurrent.ee.executor.default is missing [jboss.concurrent.ee.context.service.${my.context.service}]"]} > {code} > another confusion is setting name of host in {{host-slave.xml}} file. When set as > {code} > <host xmlns="urn:jboss:domain:4.2" host="${host.name}"> > {code} > then NullPointerException is thrown. > {code} > [Host Controller] 14:18:45,238 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0033: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131) > at org.jboss.as.host.controller.HostControllerConfigurationPersister.load(HostControllerConfigurationPersister.java:188) > at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:594) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) > at java.lang.Thread.run(Thread.java:745)[Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError > at [row,col]:[3,1][Host Controller] Message: WFLYCTL0197: Unexpected attribute 'host' encountered > at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:117) > at org.jboss.as.host.controller.parsing.HostXml_4.readHostElement(HostXml_4.java:311) > at org.jboss.as.host.controller.parsing.HostXml_4.readElement(HostXml_4.java:170) > at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:79) > at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:50) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) ... 4 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 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 June 2020