July 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1631) Duplicated message ids in web, undertow, jsf and osgi subsystems

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1631?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-1631: ----------------------------------- Ok, I will talk to Stuart as it will be me that will probably be fixing undertow subsystem. > Duplicated message ids in web, undertow, jsf and osgi subsystems > ----------------------------------------------------------------- > > Key: WFLY-1631 > URL: https://issues.jboss.org/browse/WFLY-1631 > Project: WildFly > Issue Type: Bug > Components: JSF, OSGi, Web (Undertow) > Affects Versions: 8.0.0.Alpha2 > Reporter: Ivo Studensky > Assignee: Stuart Douglas > > There is a lot of duplicated or different messages in JBossWeb and Undertow subsystems which has the same ids. > different messages: > {noformat} > jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12604, value = "JSF version slot '%s' is missing from module %s") > jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12604, value = "WildFlyConversationAwareViewHandler was improperly initialized. Expected ViewHandler parent.") > {noformat} > duplicated messages with the same content: > {noformat} > jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12600, value = "Could not load JSF managed bean class: %s") > jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12600, value = "Could not load JSF managed bean class: %s") > jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12601, value = "JSF managed bean class %s has no default constructor") > jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12601, value = "JSF managed bean class %s has no default constructor") > jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12602, value = "Failed to parse %s, managed beans defined in this file will not be available") > jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12602, value = "Failed to parse %s, managed beans defined in this file will not be available") > jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12603, value = "Unknown JSF version '%s'. Default version '%s' will be used instead.") > jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12603, value = "Unknown JSF version %s %s will be used instead") > jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12650, value = "Failed to load annotated class: %s") > jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12650, value = "Failed to load annotated class: %s") > jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12651, value = "Annotation %s in class %s is only allowed on classes") > jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12651, value = "Annotation %s in class %s is only allowed on classes") > jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12652, value = "Instance creation failed") > jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12652, value = "Instance creation failed") > jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12653, value = "Instance destruction failed") > jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12653, value = "Instance destruction failed") > jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12654, value = "Thread local injection container not set") > jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12654, value = "Thread local injection container not set") > jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12655, value = "@ManagedBean is only allowed at class level %s") > jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12655, value = "@ManagedBean is only allowed at class level %s") > web/src/main/java/org/jboss/as/web/WebMessages.java: @Message(id = 18039, value = "Failed to create context") > osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18039, value = "Failed to create context") > web/src/main/java/org/jboss/as/web/WebMessages.java: @Message(id = 18040, value = "Failed to start context") > osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18040, value = "Failed to start context") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18200, value = "Failed to start welcome context") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18200, value = "Failed to start welcome context") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18201, value = "Failed to destroy welcome context") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18201, value = "Failed to destroy welcome context") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18202, value = "Error calling onStartup for servlet container initializer: %s") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18202, value = "Error calling onStartup for servlet container initializer: %s") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18203, value = "Error instantiating container component: %s") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18203, value = "Error instantiating container component: %s") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18204, value = "Clustering not supported, falling back to non-clustered session manager") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18204, value = "Clustering not supported, falling back to non-clustered session manager") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18205, value = "Cannot setup overlays for [%s] due to custom resources") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18205, value = "Cannot setup overlays for [%s] due to custom resources") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18206, value = "Webapp [%s] is unavailable due to startup errors") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18206, value = "Webapp [%s] is unavailable due to startup errors") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18208, value = "Failed to start context") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18208, value = "Failed to start context") > osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18208, value = "Failed to start context") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18208, value = "Failed to start context") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18208, value = "Failed to start context") > osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18208, value = "Failed to start context") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18209, value = "Failed to destroy context") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18209, value = "Failed to destroy context") > osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18209, value = "Failed to destroy context") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18209, value = "Failed to destroy context") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18209, value = "Failed to destroy context") > osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18209, value = "Failed to destroy context") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18210, value = "Register web context: %s") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18210, value = "Register web context: %s") > osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18210, value = "Register web context: %s") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18210, value = "Register web context: %s") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18210, value = "Register web context: %s") > osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18210, value = "Register web context: %s") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18214, value = "Error during login/password authenticate") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18214, value = "Error during login/password authenticate") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18215, value = "Error during certificate authenticate") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18215, value = "Error during certificate authenticate") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18216, value = "Error during digest authenticate") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18216, value = "Error during digest authenticate") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18217, value = "Error obtaining authorization helper") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18217, value = "Error obtaining authorization helper") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18218, value = "Exception in obtaining server authentication manager") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18218, value = "Exception in obtaining server authentication manager") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18219, value = "JASPI validation for unprotected request context %s failed") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18219, value = "JASPI validation for unprotected request context %s failed") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18220, value = "Caught Exception: %s") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18220, value = "Caught Exception: %s") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18221, value = "Error forwarding to login page: %s") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18221, value = "Error forwarding to login page: %s") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18222, value = "Error forwarding to error page: %s") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18222, value = "Error forwarding to error page: %s") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18224, value = "Unregister web context: %s") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18224, value = "Unregister web context: %s") > undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18226, value = "Skipped SCI for jar: %s.") > web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18226, value = "Skipped SCI for jar: %s.") > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1302) Upgrade log4-jboss-logmanager

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1302?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1302: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 958311|https://bugzilla.redhat.com/show_bug.cgi?id=958311] from ON_QA to VERIFIED > Upgrade log4-jboss-logmanager > ----------------------------- > > Key: WFLY-1302 > URL: https://issues.jboss.org/browse/WFLY-1302 > Project: WildFly > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > Upstream of log4j-jboss-logmanager contains a bug fix for serializing the {{ThrowableInformation}} correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1302) Upgrade log4-jboss-logmanager

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1302?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1302: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> made a comment on [bug 958311|https://bugzilla.redhat.com/show_bug.cgi?id=958311] Verified with 6.1.1.ER2: [jmartisk@dhcp-4-155 jboss-eap-6.1.1.ER2]$ pwd /home/jmartisk/EAP6/builds/jboss-eap-6.1.1.ER2 [jmartisk@dhcp-4-155 jboss-eap-6.1.1.ER2]$ ls modules/system/layers/base/org/jboss/log4j/logmanager/main/ log4j-jboss-logmanager-1.0.2.Final-redhat-1.jar module.xml > Upgrade log4-jboss-logmanager > ----------------------------- > > Key: WFLY-1302 > URL: https://issues.jboss.org/browse/WFLY-1302 > Project: WildFly > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > Upstream of log4j-jboss-logmanager contains a bug fix for serializing the {{ThrowableInformation}} correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-474) Update the add-user.sh images to reflect the latest guided workflow

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-474?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved WFLY-474. ----------------------------------- Fix Version/s: 8.0.0.Alpha3 (was: 9.0.0.CR1) Resolution: Out of Date Images already updated during WildFly re-branding. > Update the add-user.sh images to reflect the latest guided workflow > ------------------------------------------------------------------- > > Key: WFLY-474 > URL: https://issues.jboss.org/browse/WFLY-474 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha3 > > > No point updating 7.1.x as EAP users don't get an image to guide them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-65) EjbUtilities is used without regard for dependencies

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-65?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-65: --------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 950864|https://bugzilla.redhat.com/show_bug.cgi?id=950864] from ON_QA to VERIFIED > EjbUtilities is used without regard for dependencies > ---------------------------------------------------- > > Key: WFLY-65 > URL: https://issues.jboss.org/browse/WFLY-65 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Stuart Douglas > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha1 > > > org.jboss.as.ejb3.component.EJBUtilities is used to get services in the EJB subsystem, without setting up proper dependencies (e.g. in org.jboss.as.ejb3.component.EJBComponentCreateService#getEJBUtilities). Occasionally this can cause problems at startup as EJBUtilities can end up being null for some EJB's. > We should probably just remove this class, or at the very least make sure it is injected properly and not looked up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-65) EjbUtilities is used without regard for dependencies

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-65?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-65: --------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> made a comment on [bug 950864|https://bugzilla.redhat.com/show_bug.cgi?id=950864] Verified in 6.1.1.ER2 > EjbUtilities is used without regard for dependencies > ---------------------------------------------------- > > Key: WFLY-65 > URL: https://issues.jboss.org/browse/WFLY-65 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Stuart Douglas > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha1 > > > org.jboss.as.ejb3.component.EJBUtilities is used to get services in the EJB subsystem, without setting up proper dependencies (e.g. in org.jboss.as.ejb3.component.EJBComponentCreateService#getEJBUtilities). Occasionally this can cause problems at startup as EJBUtilities can end up being null for some EJB's. > We should probably just remove this class, or at the very least make sure it is injected properly and not looked up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-336) Wrong value of "runtime-name" property for unmanaged deployments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-336?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-336: ---------------------------------------------- Jakub Cechacek <jcechace(a)redhat.com> made a comment on [bug 910675|https://bugzilla.redhat.com/show_bug.cgi?id=910675] Verified 6.1.1.ER2 > Wrong value of "runtime-name" property for unmanaged deployments > ----------------------------------------------------------------- > > Key: WFLY-336 > URL: https://issues.jboss.org/browse/WFLY-336 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: console_1.5.2, console_1.5.3, merged > Fix For: 8.0.0.Alpha2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-14) Remove deprecated attributes of messaging subsystem in console

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-14?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-14: --------------------------------------------- Jakub Cechacek <jcechace(a)redhat.com> made a comment on [bug 948900|https://bugzilla.redhat.com/show_bug.cgi?id=948900] This seems to be OK. Status will be appropriately changed once verified by console test-suite (run currently in progress). > Remove deprecated attributes of messaging subsystem in console > -------------------------------------------------------------- > > Key: WFLY-14 > URL: https://issues.jboss.org/browse/WFLY-14 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Minor > Labels: console_1.5.3, merged > Fix For: 8.0.0.CR1 > > > The attribute {{failover-on-server-shutdown}} in > * {{/subsystem=messaging/hornetq-server=default/connection-factory=*}} and > * {{/subsystem=messaging/hornetq-server=default/bridge=*}} > is deprecated and should be removed from the UI. The relevant classes in the UI are > * {{org.jboss.as.console.client.shared.subsys.messaging.model.ConnectionFactory}} > * {{org.jboss.as.console.client.shared.subsys.messaging.model.Bridge}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (WFLY-336) Wrong value of "runtime-name" property for unmanaged deployments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-336?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-336: ---------------------------------------------- Jakub Cechacek <jcechace(a)redhat.com> changed the Status of [bug 910675|https://bugzilla.redhat.com/show_bug.cgi?id=910675] from ON_QA to VERIFIED > Wrong value of "runtime-name" property for unmanaged deployments > ----------------------------------------------------------------- > > Key: WFLY-336 > URL: https://issues.jboss.org/browse/WFLY-336 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: console_1.5.2, console_1.5.3, merged > Fix For: 8.0.0.Alpha2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (AS7-6759) Console should react properly to loss of connection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6759?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6759: ---------------------------------------------- Jakub Cechacek <jcechace(a)redhat.com> made a comment on [bug 910718|https://bugzilla.redhat.com/show_bug.cgi?id=910718] Verified 6.1.1.ER2 > Console should react properly to loss of connection > --------------------------------------------------- > > Key: AS7-6759 > URL: https://issues.jboss.org/browse/AS7-6759 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Labels: console_1.5.3, merged > > Codesplit error handling leads to freeze -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

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 July 2013