[JBoss JIRA] (WFLY-10796) Warning about JSF version 'NONE' is shown in logs
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-10796?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-10796:
-----------------------------
Description:
Following warning is shown in log upon server start:
{code}
2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead.
{code}
Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening.
was:
Following warning is shown in log upon server start:
{code}
2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead.
{code}
Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present.
> Warning about JSF version 'NONE' is shown in logs
> --------------------------------------------------
>
> Key: WFLY-10796
> URL: https://issues.jboss.org/browse/WFLY-10796
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 14.0.0.Beta2
> Reporter: Jan Kašík
> Assignee: Dmitrii Tikhomirov
>
> Following warning is shown in log upon server start:
> {code}
> 2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead.
> {code}
> Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
3 days, 22 hours
[JBoss JIRA] (DROOLS-4849) SudokuExample cannot solve hard samples any more in Drools 7
by Didier Loiseau (Jira)
Didier Loiseau created DROOLS-4849:
--------------------------------------
Summary: SudokuExample cannot solve hard samples any more in Drools 7
Key: DROOLS-4849
URL: https://issues.redhat.com/browse/DROOLS-4849
Project: Drools
Issue Type: Bug
Affects Versions: 7.30.0.Final
Reporter: Didier Loiseau
Assignee: Mario Fusco
It appears {{SudokuExample}} is capable to resolve the Simple and Medium samples, but none of the Hard ones. They resolve a few cells but end with
{quote}
Sorry - can't solve this grid.
{quote}
in the console.
With explain = true, I can see that the "single" and "hidden single" rules fire (not always both, depends on the puzzle), but clearly when it stops, at least the latter should still fire for some cells.
There is also a small bug in the code, which is that the {{unsolvable}} flag is not reset during setup, so when you get the above error you also get it for any other example you solve afterwards.
I have checked with Drools 6.5.0.Final (checked out the examples from GitHub) and the solver works fine. The Sudoku example appears to be mostly the same though.
I am running the examples with Java 8 from IntelliJ or command line, if that matters. I tested this on 2 different machines.
It is a bit unfortunate because it is the first example in the GUI.
Full console output for sample Hard 1:
{code}
12:14:28.256 [main] INFO o.d.c.k.b.impl.ClasspathKieProject.notifyKieModuleFound:133 - Found kmodule: file:/C:/Users/Public/Documents/projects/drools/drools-examples/target/classes/META-INF/kmodule.xml
12:14:30.424 [main] WARN o.d.c.k.b.impl.ClasspathKieProject.getPomPropertiesFromFileSystem:322 - Unable to find pom.properties in /C:/Users/Public/Documents/projects/drools/drools-examples/target/classes
12:14:30.475 [main] INFO o.d.c.k.b.impl.ClasspathKieProject.generatePomPropertiesFromPom:354 - Recursed up folders, found and used pom.xml C:\Users\Public\Documents\projects\drools\drools-examples\pom.xml
12:14:42.619 [AWT-EventQueue-0] WARN o.d.c.k.builder.impl.KieBuilderImpl.packageNameForFile:394 - File 'org/drools/games/wumpus/server/paintCave.drl' is in folder 'org/drools/games/wumpus/server' but declares package 'org.drools.games.wumpus.server.view'. It is advised to have a correspondance between package and folder names.
12:14:42.632 [AWT-EventQueue-0] WARN o.d.c.k.builder.impl.KieBuilderImpl.packageNameForFile:394 - File 'org/drools/games/wumpus/server/paintSensor.drl' is in folder 'org/drools/games/wumpus/server' but declares package 'org.drools.games.wumpus.server.view'. It is advised to have a correspondance between package and folder names.
12:14:42.687 [AWT-EventQueue-0] WARN o.d.c.k.builder.impl.KieBuilderImpl.packageNameForFile:394 - File 'org/drools/games/wumpus/server/ui.drl' is in folder 'org/drools/games/wumpus/server' but declares package 'org.drools.games.wumpus.server.view'. It is advised to have a correspondance between package and folder names.
Validation complete.
Col: 0 Col: 1 Col: 2 Col: 3 Col: 4 Col: 5 Col: 6 Col: 7 Col: 8
Row 0: 2 4 7 9 2 4 6 4 67 9 23 6 9 --- 5 --- --- 1 --- 3 67 9 --- 8 --- 4 67
Row 1: 12 7 9 --- 8 --- 1 67 9 23 6 9 --- 4 --- 23 6 1 3 67 9 3 67 9 --- 5 ---
Row 2: 1 4 9 1 456 --- 3 --- 6 89 --- 7 --- 6 8 --- 2 --- 4 6 9 1 4 6
Row 3: 1234 1234 1 4 1 5 8 --- 6 --- 5 78 5 7 45 7 --- 9 ---
Row 4: --- 6 --- --- 7 --- --- 5 --- --- 4 --- --- 2 --- --- 9 --- --- 8 --- --- 1 --- --- 3 ---
Row 5: --- 8 --- 12 4 1 4 9 1 5 --- 3 --- 5 7 567 4567 2 4 67
Row 6: 1 3 7 1 3 6 --- 2 --- 3 56 --- 8 --- 3 56 --- 4 --- 3 567 9 1 67
Row 7: --- 5 --- 1 34 6 1 4 678 3 6 --- 9 --- 34 6 1 3 67 --- 2 --- 1 678
Row 8: 34 --- 9 --- 4 6 8 --- 7 --- --- 1 --- 23456 3 56 3 56 6 8
Sorry - can't solve this grid.
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 days, 23 hours
[JBoss JIRA] (WFLY-12461) Can't use smallrye-health without weld extension
by Florian Sailer (Jira)
Florian Sailer created WFLY-12461:
-------------------------------------
Summary: Can't use smallrye-health without weld extension
Key: WFLY-12461
URL: https://issues.jboss.org/browse/WFLY-12461
Project: WildFly
Issue Type: Bug
Components: MP Health
Affects Versions: 17.0.1.Final
Reporter: Florian Sailer
Assignee: Jeff Mesnil
Since this commit in the smallrye implementation it was possible to use smallrye without CDI.
https://github.com/smallrye/smallrye-health/commit/a6a7812877d74d2c3f5b29...
I'm trying to migrate from Wildfly 15.0.1-Final to 17.0.1-Final, where the smallrye-health extension unfortunately needs weld to startup. It's not possbible for me to activate weld on my sever, because there are some problems using the org.apache.cxf.jaxrs framework with weld.
I am getting the following exception while starting:
14:16:04,960 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-health-smallrye' are not available:
org.wildfly.weld; There are no known registration points which can provide this capability.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 months, 2 weeks
[JBoss JIRA] (DROOLS-3944) DMN Editor: Data type usability study
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3944?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-3944:
--------------------------------------
Sprint: 2019 Week 23-25
> DMN Editor: Data type usability study
> -------------------------------------
>
> Key: DROOLS-3944
> URL: https://issues.jboss.org/browse/DROOLS-3944
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Environment: Version 7.4
> Reporter: Elizabeth Clayton
> Assignee: Sarahjane Clark
> Priority: Major
> Labels: UX, UXTeam, Usability, drools-tools
>
> Lightweight usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types.
> GOALS: Access the Data Type editor in terms of productivity and usability.
> * Ease of use when creating a complex type (concern: minimizing the mouse usage.)
> * Ease of use when saving a basic data type (e.g. age: number)
> * Discoverability of actions in the kebab menu, especially, insert nested, delete.
> * Ease of use/accuracy: Type-ahead of the data type selector.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
1 year, 1 month
[JBoss JIRA] (WFLY-13630) Scattered caches should not contain a transaction resource
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-13630:
-----------------------------------
Summary: Scattered caches should not contain a transaction resource
Key: WFLY-13630
URL: https://issues.redhat.com/browse/WFLY-13630
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 20.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
This configuration throws an error at runtime. Thus we should not registered this child resource for scattered caches, nor should such a configuration be allowed by the parser.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (WFLY-13629) WildFly kitchensink quickstart doesn't run test when started by Maven
by Norbert Kawiński (Jira)
[ https://issues.redhat.com/browse/WFLY-13629?page=com.atlassian.jira.plugi... ]
Norbert Kawiński updated WFLY-13629:
------------------------------------
Description:
Problem:
When running kitchensink's tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run.
Cause:
{color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests.
Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...]
{color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color}
* {color:#505f79}_{{**/Test*.java}}_{color}
* {color:#505f79}_{{**/*Test.java}}_{color}
* {color:#505f79}_{{**/*Tests.java}}_{color}
* {color:#505f79}{{_**/*TestCase.java_}}{color}
{color:#172b4d}{{}}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention.{color}
{color:#172b4d}Solution:\{{}}{color}
{color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color}
was:
Problem:
When running tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run.
Cause:
{color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests.
Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...]
{color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color}
* {color:#505f79}_{{**/Test*.java}}_{color}
* {color:#505f79}_{{**/*Test.java}}_{color}
* {color:#505f79}_{{**/*Tests.java}}_{color}
* {color:#505f79}{{_**/*TestCase.java_}}{color}
{color:#172b4d}{{}}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention.
{color}
{color:#172b4d}Solution:{{}}{color}
{color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color}
> WildFly kitchensink quickstart doesn't run test when started by Maven
> ---------------------------------------------------------------------
>
> Key: WFLY-13629
> URL: https://issues.redhat.com/browse/WFLY-13629
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 20.0.0.Final
> Reporter: Norbert Kawiński
> Assignee: Eduardo Martins
> Priority: Major
>
> Problem:
> When running kitchensink's tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run.
>
> Cause:
> {color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests.
> Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...]
> {color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color}
> * {color:#505f79}_{{**/Test*.java}}_{color}
> * {color:#505f79}_{{**/*Test.java}}_{color}
> * {color:#505f79}_{{**/*Tests.java}}_{color}
> * {color:#505f79}{{_**/*TestCase.java_}}{color}
> {color:#172b4d}{{}}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention.{color}
>
> {color:#172b4d}Solution:\{{}}{color}
> {color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (WFLY-13629) WildFly kitchensink quickstart doesn't run test when started by Maven
by Norbert Kawiński (Jira)
[ https://issues.redhat.com/browse/WFLY-13629?page=com.atlassian.jira.plugi... ]
Norbert Kawiński updated WFLY-13629:
------------------------------------
Description:
Problem:
When running kitchensink's tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run.
Cause:
{color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests.
Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...]
??{color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color}??
* ??{color:#505f79}_{{**/Test*.java}}_{color}??
* ??{color:#505f79}_{{**/*Test.java}}_{color}??
* ??{color:#505f79}_{{**/*Tests.java}}_{color}??
* ??{color:#505f79}{{_**/*TestCase.java_}}{color}??
{color:#172b4d}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention.{color}
{color:#172b4d}Solution:{color}
{color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color}
was:
Problem:
When running kitchensink's tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run.
Cause:
{color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests.
Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...]
{color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color}
* {color:#505f79}_{{**/Test*.java}}_{color}
* {color:#505f79}_{{**/*Test.java}}_{color}
* {color:#505f79}_{{**/*Tests.java}}_{color}
* {color:#505f79}{{_**/*TestCase.java_}}{color}
{color:#172b4d}{{}}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention.{color}
{color:#172b4d}Solution:\{{}}{color}
{color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color}
> WildFly kitchensink quickstart doesn't run test when started by Maven
> ---------------------------------------------------------------------
>
> Key: WFLY-13629
> URL: https://issues.redhat.com/browse/WFLY-13629
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 20.0.0.Final
> Reporter: Norbert Kawiński
> Assignee: Eduardo Martins
> Priority: Major
>
> Problem:
> When running kitchensink's tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run.
>
> Cause:
> {color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests.
> Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...]
> ??{color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color}??
> * ??{color:#505f79}_{{**/Test*.java}}_{color}??
> * ??{color:#505f79}_{{**/*Test.java}}_{color}??
> * ??{color:#505f79}_{{**/*Tests.java}}_{color}??
> * ??{color:#505f79}{{_**/*TestCase.java_}}{color}??
> {color:#172b4d}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention.{color}
>
> {color:#172b4d}Solution:{color}
> {color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (WFLY-13627) Distributed sessions/SFSBs stored in non-transactional invalidation-cache should schedule expirations locally
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13627?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-13627:
--------------------------------
Summary: Distributed sessions/SFSBs stored in non-transactional invalidation-cache should schedule expirations locally (was: Distributed sessions stored in non-transactional invalidation-cache should schedule expirations locally)
> Distributed sessions/SFSBs stored in non-transactional invalidation-cache should schedule expirations locally
> -------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13627
> URL: https://issues.redhat.com/browse/WFLY-13627
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 20.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
>
> Currently, distributed web sessions (and SFSBs) are expired on the primary owner of the session. For non-transactional invalidation caches expiration should always be scheduled locally. This used to be the case, however, the logic for determining this has changed such that expirations happen on the owner of segment 0.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
