January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9708) Wildfly 11.0.0.Final JSF 1.2 configuration error

by Luis Canales (JIRA)

[ https://issues.jboss.org/browse/WFLY-9708?page=com.atlassian.jira.plugin.... ] Luis Canales edited comment on WFLY-9708 at 1/18/18 11:14 AM: -------------------------------------------------------------- Hi Martin, I have this in my jboss-all.xml (I'm not using CDI in my application): _<jboss umlns="urn:jboss:1.0"> <weld xmlns="urn:jboss:weld:1.0" require-bean-descriptor="true"/> </jboss>_ The same application runs in Wildfly 10.1.0. I've build the 3 JSF1.2 modules (jsf-api, jsf-impl and jsf-injection) for both Wildfly (10.1.0, 11.0.0) according to the tutorial. I think "WeldApplication" is bean instantiated when the module is loaded. In Wildfly 10.1.0 "WeldApplication" extends from "ForwardingApplication" and this class is included inside the module. However, in Wildfly 11.0.0 it extends from "ApplicationWrapper" (dependent from JSF2.0). was (Author: lcanales): Hi Martin, I have this in my jboss-all.xml (I'm not using CDI in my application): _<jboss umlns="urn:jboss:1.0"> <weld xmlns="urn:jboss:weld:1.0" require-bean-descriptor="true"/> </jboss>_ The same application runs in Wildfly 10.1.0. I've build the 3 JSF1.2 modules (jsf-api, jsf-impl and jsf-injection) for both Wildfly (10.1.0, 11.0.0) according to the tutorial. I think "WeldApplication" is bean instantiated when the module is loaded. In Wildfly 10.1.0 "WeldApplication" extends from "ForwardingApplication" and this class is included inside the module. However, in Wildfly 11.0.0 it extends from "ApplicationWrapper" (dependent from JSF2.0). > Wildfly 11.0.0.Final JSF 1.2 configuration error > ------------------------------------------------ > > Key: WFLY-9708 > URL: https://issues.jboss.org/browse/WFLY-9708 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JSF > Affects Versions: 11.0.0.Final > Reporter: Luis Canales > Assignee: Martin Kouba > Priority: Optional > Attachments: log.txt > > > Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF2.0, so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error: > _java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper_ > If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9708) Wildfly 11.0.0.Final JSF 1.2 configuration error

by Luis Canales (JIRA)

[ https://issues.jboss.org/browse/WFLY-9708?page=com.atlassian.jira.plugin.... ] Luis Canales commented on WFLY-9708: ------------------------------------ Hi Martin, I have this in my jboss-all.xml (I'm not using CDI in my application): _<jboss umlns="urn:jboss:1.0"> <weld xmlns="urn:jboss:weld:1.0" require-bean-descriptor="true"/> </jboss>_ The same application runs in Wildfly 10.1.0. I've build the 3 JSF1.2 modules (jsf-api, jsf-impl and jsf-injection) for both Wildfly (10.1.0, 11.0.0) according to the tutorial. I think "WeldApplication" is bean instantiated when the module is loaded. In Wildfly 10.1.0 "WeldApplication" extends from "ForwardingApplication" and this class is included inside the module. However, in Wildfly 11.0.0 it extends from "ApplicationWrapper" (dependent from JSF2.0). > Wildfly 11.0.0.Final JSF 1.2 configuration error > ------------------------------------------------ > > Key: WFLY-9708 > URL: https://issues.jboss.org/browse/WFLY-9708 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JSF > Affects Versions: 11.0.0.Final > Reporter: Luis Canales > Assignee: Martin Kouba > Priority: Optional > Attachments: log.txt > > > Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF2.0, so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error: > _java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper_ > If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-153) [QE] - INV-008 View Relationships between EAP servers and VMs that run a Linux OS and navigate across the relationships

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-153?page=com.atlassian.jira.pl... ] Vojtech Prusa closed HAWKULARQE-153. ------------------------------------ Resolution: Out of Date > [QE] - INV-008 View Relationships between EAP servers and VMs that run a Linux OS and navigate across the relationships > ----------------------------------------------------------------------------------------------------------------------- > > Key: HAWKULARQE-153 > URL: https://issues.jboss.org/browse/HAWKULARQE-153 > Project: Hawkular QE > Issue Type: Task > Environment: Need instances CFME, RHEVM, HS and EAP monitored by this HS when EAP is running on VM under RHEVM. > Reporter: Vojtech Prusa > Assignee: Vojtech Prusa > > Manually tested. > Automate https://trello.com/c/oBeMkciI/254-inv-008-view-relationships-between-eap-... > Use JON QE RHEVMs test user. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2857) Usage of wildfly.sasl.local-user.default-user in core configuration files

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2857?page=com.atlassian.jira.plugi... ] Ken Wills closed WFCORE-2857. ----------------------------- Resolution: Out of Date > Usage of wildfly.sasl.local-user.default-user in core configuration files > ------------------------------------------------------------------------- > > Key: WFCORE-2857 > URL: https://issues.jboss.org/browse/WFCORE-2857 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Test Suite > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 4.0.0.Alpha6 > > > The property wildfly.sasl.local-user.default-user is present in some, commented out on other, and absent from some default configuation files in core. (the default host-slave.xml for example has it, but it appears to have no effect if removed). There is uneven usage of it throughout the testsuite config files. > We should review and make the usage (or non-usage) consistent. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9706) Newly added InfiniteOrPositiveValidators to messaging attributes should just print warning if negative values are not -1

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9706?page=com.atlassian.jira.plugin.... ] Brian Stansberry edited comment on WFLY-9706 at 1/18/18 11:00 AM: ------------------------------------------------------------------ If a negative value other than -1 was allowed before but we don't want to allow it any more, then use a ParameterCorrector to correct it. I don't know if a WARN is worth it. We need to control our metaspace and the odds that someone is doing this wrong seems low. was (Author: brian.stansberry): If a negative value other than -1 was allowed before but we don't want to allow it any more, then use a ParameterCorrector to correct it. > Newly added InfiniteOrPositiveValidators to messaging attributes should just print warning if negative values are not -1 > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-9706 > URL: https://issues.jboss.org/browse/WFLY-9706 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 12.0.0.Alpha1 > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > > This Jira is reaction to WFLY-9433. > The WFLY-9433 makes validator rules more strict for some attributes in messaging subsystem. Although there is no reason to use these values (which are newly considered as invalid), it was possible to configure them and they worked with Wildfly 11 and previous releases. > As it is proposed in JBEAP-14110, this change should be done in 2 steps: > * only WARN the user if the parameter is not valid (a negative value other than -1) > * in next release, reject the parameter > I am setting priority as Blocker, because this fix must be included in Wildfly 12 release. It makes no sense to do it later. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1186) Isolate embedded server / host-controller module loading when starting new server(s)

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1186?page=com.atlassian.jira.plugi... ] Ken Wills closed WFCORE-1186. ----------------------------- Resolution: Out of Date > Isolate embedded server / host-controller module loading when starting new server(s) > ------------------------------------------------------------------------------------ > > Key: WFCORE-1186 > URL: https://issues.jboss.org/browse/WFCORE-1186 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Ken Wills > Assignee: Ken Wills > > Currently starting an embedded server obtains a single ModuleLoader instance, which is then statically initialized with specific pointers to certain filesystem directories & paths (server.log and module.path etc). > It would be ideal if each embedded instance could use it's own ModuleLoader, as it would allow all of these properties to be managed separately, and potentially multiple servers to be started at the same time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3409) embed-server doesn't honor "module.path" system property

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3409?page=com.atlassian.jira.plugi... ] Ken Wills reassigned WFCORE-3409: --------------------------------- Assignee: ehsavoie Hugonnet (was: Ken Wills) > embed-server doesn't honor "module.path" system property > -------------------------------------------------------- > > Key: WFCORE-3409 > URL: https://issues.jboss.org/browse/WFCORE-3409 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 4.0.0.Alpha2 > Reporter: Tomaz Cerar > Assignee: ehsavoie Hugonnet > > Every other parts of server and launchers (including embed-host-controller) honor the "module.path" system property for setting modules path. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-938) Embedded host controller doesn't support --admin-mode=false option

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-938?page=com.atlassian.jira.plugin... ] Ken Wills reassigned WFCORE-938: -------------------------------- Assignee: ehsavoie Hugonnet (was: Ken Wills) > Embedded host controller doesn't support --admin-mode=false option > ------------------------------------------------------------------ > > Key: WFCORE-938 > URL: https://issues.jboss.org/browse/WFCORE-938 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management > Affects Versions: 2.0.0.Beta4 > Reporter: Petr Kremensky > Assignee: ehsavoie Hugonnet > Labels: domain-mode > > Embedded standalone instance supports two running modes depending on a value of admin-only option (true is default). > * *true* > ** only start services related to server administration > ** do not start other services or accept end user requests. > ** embedded instance will not be visible to remote management clients > * *false* > ** all services are started > ** embedded instance is visible to remote management clients (e.g. EAP can be configured via admin console) > Embedded host controller doesn't offer such a option and is started using --admin-only=true mode by default. Option to run embedded host controller instance with --admin-only=false should be available as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1187) Embedded server start / stop / start with new --jboss-home continues to refer to previous server.log

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1187?page=com.atlassian.jira.plugi... ] Ken Wills reassigned WFCORE-1187: --------------------------------- Assignee: ehsavoie Hugonnet (was: Ken Wills) > Embedded server start / stop / start with new --jboss-home continues to refer to previous server.log > ---------------------------------------------------------------------------------------------------- > > Key: WFCORE-1187 > URL: https://issues.jboss.org/browse/WFCORE-1187 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Ken Wills > Assignee: ehsavoie Hugonnet > > - start-embedded-server --jboss-home=/foo/bar1 > - stop-embedded-server > - start-embedded-server --jboss-home=/foo/bar2 > -- server.log in /foo/bar1/standalone/logs/server.log is still written to. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3103) Embedded server doesn't close open file handles

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3103?page=com.atlassian.jira.plugi... ] Ken Wills reassigned WFCORE-3103: --------------------------------- Assignee: ehsavoie Hugonnet (was: Ken Wills) > Embedded server doesn't close open file handles > ----------------------------------------------- > > Key: WFCORE-3103 > URL: https://issues.jboss.org/browse/WFCORE-3103 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Modules > Reporter: Jan Blizňák > Assignee: ehsavoie Hugonnet > > When embedded server is started programatically (eg. via CLI wrapper) with specified jboss home, JARs from that path are opened via classloader. But these open handles are never released even after embedded server is stopped. > This causes problem in situation eg. when you want to delete that jboss home. This is exactly one of the scenarios used in EAP installer, you are not allowed to delete open files on Windows - see JBEAP-1404. > I created a simple project that reproduce the issue with arbitrary EAP/WF distribution https://github.com/jbliznak/embedded-server-filelocking > Run it with: > mvn clean test "-Dwildfly.home=C:\dev\jboss-eap-7.1" "-Denforcer.skip" -Dtest=ModulesFileLockingTestCase > Manual steps to reproduce in Java code: > * start a CLI wrapper > * start embed-server from given server path > * stop embed-server > * terminate CLI wrapper > * try to delete given server path -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2018