[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 908664|https://bugzilla.redhat.com/show_bug.cgi?id=908664]
This seems to be OK. Status will be appropriately change 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
[JBoss JIRA] (WFLY-256) Remove direct connections parameter
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-256?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on WFLY-256:
----------------------------------------------
Jakub Cechacek <jcechace(a)redhat.com> made a comment on [bug 908720|https://bugzilla.redhat.com/show_bug.cgi?id=908720]
This seems to be OK. Status will be appropriately changed once verified by console test-suite (run currently in progress).
> Remove direct connections parameter
> -----------------------------------
>
> Key: WFLY-256
> URL: https://issues.jboss.org/browse/WFLY-256
> Project: WildFly
> Issue Type: Feature Request
> Components: Web Console
> Reporter: Bartosz Baranowski
> Assignee: Bartosz Baranowski
> Priority: Minor
> Labels: console_1.5.3, merged
> Fix For: 8.0.0.Alpha2
>
>
> The direct connection parameter makes no sense. Currently console allows to create cluster connection only with broadcast group( which, if present, renders direct connection mute)
> One could define cluster connection like that(to have static connectors), but from console POV, there is no way to tell the difference. Hence this parameter makes no sense.
--
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
[JBoss JIRA] (DROOLS-186) Enforce maven 3.0.5+ to build droolsjbpm
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-186?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer reassigned DROOLS-186:
---------------------------------------------
Assignee: Michael Biarnes Kiefer
> Enforce maven 3.0.5+ to build droolsjbpm
> ----------------------------------------
>
> Key: DROOLS-186
> URL: https://issues.jboss.org/browse/DROOLS-186
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
> Fix For: 6.0.0.CR1
>
>
> Reasons:
> - To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
> - Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
> TODO list:
> - The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
> {code}
> <requireMavenVersion>
> <version>[3.0.5,)</version>
> </requireMavenVersion>
> {code}
> Notify porcelli to do the same for uberfire.
> - Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice before pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
> - Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
--
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
[JBoss JIRA] (DROOLS-186) Enforce maven 3.0.5+ to build droolsjbpm
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-186?page=com.atlassian.jira.plugin... ]
Geoffrey De Smet updated DROOLS-186:
------------------------------------
Description:
Reasons:
- To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
- Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
TODO list:
- The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
{code}
<requireMavenVersion>
<version>[3.0.5,)</version>
</requireMavenVersion>
{code}
Notice porcelli to do the same for uberfire.
- Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice for pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
- Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
was:
Reasons:
- To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
- Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
TODO list:
- The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
{code}
<requireMavenVersion>
<version>[3.0.5,)</version>
</requireMavenVersion>
{code}
- Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice for pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
- Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
> Enforce maven 3.0.5+ to build droolsjbpm
> ----------------------------------------
>
> Key: DROOLS-186
> URL: https://issues.jboss.org/browse/DROOLS-186
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Geoffrey De Smet
> Fix For: 6.0.0.CR1
>
>
> Reasons:
> - To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
> - Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
> TODO list:
> - The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
> {code}
> <requireMavenVersion>
> <version>[3.0.5,)</version>
> </requireMavenVersion>
> {code}
> Notice porcelli to do the same for uberfire.
> - Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice for pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
> - Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
--
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
[JBoss JIRA] (DROOLS-186) Enforce maven 3.0.5+ to build droolsjbpm
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-186?page=com.atlassian.jira.plugin... ]
Geoffrey De Smet updated DROOLS-186:
------------------------------------
Description:
Reasons:
- To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
- Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
TODO list:
- The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
{code}
<requireMavenVersion>
<version>[3.0.5,)</version>
</requireMavenVersion>
{code}
Notify porcelli to do the same for uberfire.
- Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice for pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
- Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
was:
Reasons:
- To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
- Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
TODO list:
- The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
{code}
<requireMavenVersion>
<version>[3.0.5,)</version>
</requireMavenVersion>
{code}
Notice porcelli to do the same for uberfire.
- Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice for pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
- Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
> Enforce maven 3.0.5+ to build droolsjbpm
> ----------------------------------------
>
> Key: DROOLS-186
> URL: https://issues.jboss.org/browse/DROOLS-186
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Geoffrey De Smet
> Fix For: 6.0.0.CR1
>
>
> Reasons:
> - To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
> - Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
> TODO list:
> - The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
> {code}
> <requireMavenVersion>
> <version>[3.0.5,)</version>
> </requireMavenVersion>
> {code}
> Notify porcelli to do the same for uberfire.
> - Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice for pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
> - Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
--
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
[JBoss JIRA] (DROOLS-186) Enforce maven 3.0.5+ to build droolsjbpm
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-186?page=com.atlassian.jira.plugin... ]
Geoffrey De Smet updated DROOLS-186:
------------------------------------
Description:
Reasons:
- To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
- Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
TODO list:
- The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
{code}
<requireMavenVersion>
<version>[3.0.5,)</version>
</requireMavenVersion>
{code}
Notify porcelli to do the same for uberfire.
- Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice before pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
- Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
was:
Reasons:
- To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
- Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
TODO list:
- The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
{code}
<requireMavenVersion>
<version>[3.0.5,)</version>
</requireMavenVersion>
{code}
Notify porcelli to do the same for uberfire.
- Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice for pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
- Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
> Enforce maven 3.0.5+ to build droolsjbpm
> ----------------------------------------
>
> Key: DROOLS-186
> URL: https://issues.jboss.org/browse/DROOLS-186
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Geoffrey De Smet
> Fix For: 6.0.0.CR1
>
>
> Reasons:
> - To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
> - Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
> TODO list:
> - The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
> {code}
> <requireMavenVersion>
> <version>[3.0.5,)</version>
> </requireMavenVersion>
> {code}
> Notify porcelli to do the same for uberfire.
> - Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice before pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
> - Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
--
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
[JBoss JIRA] (DROOLS-186) Enforce maven 3.0.5+ to build droolsjbpm
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created DROOLS-186:
---------------------------------------
Summary: Enforce maven 3.0.5+ to build droolsjbpm
Key: DROOLS-186
URL: https://issues.jboss.org/browse/DROOLS-186
Project: Drools
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Geoffrey De Smet
Fix For: 6.0.0.CR1
Reasons:
- To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
- Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
TODO list:
- The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
{code}
<requireMavenVersion>
<version>[3.0.3,)</version>
</requireMavenVersion>
{code}
- Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice for pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
- Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
--
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
[JBoss JIRA] (DROOLS-186) Enforce maven 3.0.5+ to build droolsjbpm
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-186?page=com.atlassian.jira.plugin... ]
Geoffrey De Smet updated DROOLS-186:
------------------------------------
Description:
Reasons:
- To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
- Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
TODO list:
- The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
{code}
<requireMavenVersion>
<version>[3.0.5,)</version>
</requireMavenVersion>
{code}
- Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice for pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
- Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
was:
Reasons:
- To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
- Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
TODO list:
- The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
{code}
<requireMavenVersion>
<version>[3.0.3,)</version>
</requireMavenVersion>
{code}
- Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice for pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
- Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
> Enforce maven 3.0.5+ to build droolsjbpm
> ----------------------------------------
>
> Key: DROOLS-186
> URL: https://issues.jboss.org/browse/DROOLS-186
> Project: Drools
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Geoffrey De Smet
> Fix For: 6.0.0.CR1
>
>
> Reasons:
> - To have stable, reproducible builds, it's important that no one is building this our project with bugs that already fixed in a newer maven version (while others don't see those bugs because they build with the latest).
> - Also see the dangerous issue described on thecore list: "mvn 3.0.4+ vs 3.0.3 - different dependency resolution ?!"
> TODO list:
> - The change itself in the sources is simple. Open droolsjbpm-parent and change the enforcer-plugin like this
> {code}
> <requireMavenVersion>
> <version>[3.0.5,)</version>
> </requireMavenVersion>
> {code}
> - Bigger issue is communicating this change to the team. Expect that many people still to use 3.0.3 and 3.0.4 and suddenly "won't be able to build". Send them an advance notice for pushing the change. Expect some people not to read that and to complain anyway - so push early in the morning and watch the IRC so you can help them :)
> - Last, but not least: configure all jenkins jobs for droolsjbpm master to use maven 3.0.5 or they 'll start failing.
--
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
[JBoss JIRA] (WFLY-1631) Duplicated message ids in web, undertow, jsf and osgi subsystems
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1631?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1631:
-----------------------------------------------
Ivo Studensky <istudens(a)redhat.com> made a comment on [bug 980823|https://bugzilla.redhat.com/show_bug.cgi?id=980823]
Description of problem:
There are duplicated messages in JSF susbsystem in EAP which has the same ids. At the moment they also have the same content. But at general, there should not be any duplicated messages.
This bug is a part of WFLY-1631.
> 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