[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)
4 days, 10 hours
- 2
- 1
[JBoss JIRA] (ELY-776) Eliminate reference to "slot" from module configurations
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-776?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse reassigned ELY-776:
------------------------------------
Assignee: Darran Lofthouse
> Eliminate reference to "slot" from module configurations
> --------------------------------------------------------
>
> Key: ELY-776
> URL: https://issues.jboss.org/browse/ELY-776
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Authentication Client
> Reporter: David Lloyd
> Assignee: Darran Lofthouse
> Fix For: 1.1.0.Beta15
>
>
> The final version of our client XSD should accept a name for modules but no slot. Instead, either the new name-only APIs should be used or a ModuleIdentifier created via that class's "fromString" method. Module slots are deprecated.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
4 days, 10 hours
- 2
- 1
[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)
4 days, 11 hours
- 2
- 1
- ← Newer
- 1
- Older →