August 2019 - jboss-jira - Jboss List Archives

[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)

5 days, 3 hours

2
1
0 / 0

[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)

5 days, 3 hours

2
1
0 / 0

[JBoss JIRA] (JBRULES-3445) DSL expander expands lines in /* */comment block

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3445: ------------------------------------ Summary: DSL expander expands lines in /* */comment block Key: JBRULES-3445 URL: https://issues.jboss.org/browse/JBRULES-3445 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When you comment some code in dslr file, the expander still tries to expand it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

5 months

3
10
0 / 0

[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

3
2
0 / 0

[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

2
1
0 / 0

[JBoss JIRA] (WFLY-11255) EE Concurrency Utilities Managed Executors / Thread Pool runtime stats

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-11255?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-11255: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12567, https://github.com/wildfly/wildfly-proposals/pull/243 (was: https://github.com/wildfly/wildfly/pull/12567) > EE Concurrency Utilities Managed Executors / Thread Pool runtime stats > ---------------------------------------------------------------------- > > Key: WFLY-11255 > URL: https://issues.jboss.org/browse/WFLY-11255 > Project: WildFly > Issue Type: Feature Request > Components: Concurrency Utilities > Affects Versions: 14.0.0.Final > Reporter: Brad Maxwell > Assignee: Eduardo Martins > Priority: Major > > The managed executors / thread pools in the EE subsytem currently do not show any runtime information when invoked with include-runtime=true, the current thread pool size, queue length and such would be useful to check the performance and tuning. > {code} > /subsystem=ee/managed-executor-service=default:read-resource(include-runtime=true,recursive=true) > { > "outcome" => "success", > "result" => { > "context-service" => "default", > "core-threads" => undefined, > "hung-task-threshold" => 60000L, > "jndi-name" => "java:jboss/ee/concurrency/executor/default", > "keepalive-time" => 5000L, > "long-running-tasks" => false, > "max-threads" => undefined, > "queue-length" => undefined, > "reject-policy" => "ABORT", > "thread-factory" => undefined > } > } > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12467) Move EE management model version to 5.0.0

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12467?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-12467: ----------------------------------- Description: Update EE subsystem model to 5.0.0 > Move EE management model version to 5.0.0 > ----------------------------------------- > > Key: WFLY-12467 > URL: https://issues.jboss.org/browse/WFLY-12467 > Project: WildFly > Issue Type: Enhancement > Components: EE > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > Update EE subsystem model to 5.0.0 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12467) Move EE management model version to 5.0.0

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-12467: -------------------------------------- Summary: Move EE management model version to 5.0.0 Key: WFLY-12467 URL: https://issues.jboss.org/browse/WFLY-12467 Project: WildFly Issue Type: Enhancement Components: EE Reporter: Eduardo Martins Assignee: Eduardo Martins -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4642) Add ability to run chunks of the integration testsuite against Galleon-slimmed server

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4642: ---------------------------------------- Summary: Add ability to run chunks of the integration testsuite against Galleon-slimmed server Key: WFCORE-4642 URL: https://issues.jboss.org/browse/WFCORE-4642 Project: WildFly Core Issue Type: Task Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Develop a set of Galleon layers that aligns with how we expect a WildFly Core server in a cloud scenario to be provisioned. Provision such a server in some of the testsuite modules and execute as many of the tests as possible against it. Goal is to surface any weaknesses in our expected configuration and to guard against behavior regressions. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4642) Add ability to run chunks of the integration testsuite against Galleon-slimmed server

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4642?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4642: ------------------------------------- Fix Version/s: 10.0.0.Beta6 > Add ability to run chunks of the integration testsuite against Galleon-slimmed server > ------------------------------------------------------------------------------------- > > Key: WFCORE-4642 > URL: https://issues.jboss.org/browse/WFCORE-4642 > Project: WildFly Core > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 10.0.0.Beta6 > > > Develop a set of Galleon layers that aligns with how we expect a WildFly Core server in a cloud scenario to be provisioned. Provision such a server in some of the testsuite modules and execute as many of the tests as possible against it. > Goal is to surface any weaknesses in our expected configuration and to guard against behavior regressions. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years

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 August 2019