February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMETA-385) Add overridable flag to servlet metadata

by James Livingston (JIRA)

[ https://issues.jboss.org/browse/JBMETA-385?page=com.atlassian.jira.plugin... ] James Livingston updated JBMETA-385: ------------------------------------ Git Pull Request: https://github.com/jboss/metadata/pull/79 > Add overridable flag to servlet metadata > ---------------------------------------- > > Key: JBMETA-385 > URL: https://issues.jboss.org/browse/JBMETA-385 > Project: JBoss Metadata > Issue Type: Enhancement > Components: web > Affects Versions: 7.2.1.Final > Reporter: James Livingston > Assignee: Jean-Frederic Clere > > To resolve https://bugzilla.redhat.com/show_bug.cgi?id=1094248, I believe we need an additional 'overridable' flag on the servlet metadata which indicates whether ServletContainerInitializers (and other code using servlet dynamic registration) should be allowed to override the servlet. Normally this is not allowed, however JBWeb's internal use of DefaultServlet to handle static resources should be. > This only needs to go into 7, since the Undertow subsystem in Wildfly handles this quite differently, so does not need to pass a flag between components. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-385) Add overridable flag to servlet metadata

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBMETA-385?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBMETA-385: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1094248 > Add overridable flag to servlet metadata > ---------------------------------------- > > Key: JBMETA-385 > URL: https://issues.jboss.org/browse/JBMETA-385 > Project: JBoss Metadata > Issue Type: Enhancement > Components: web > Affects Versions: 7.2.1.Final > Reporter: James Livingston > Assignee: Jean-Frederic Clere > > To resolve https://bugzilla.redhat.com/show_bug.cgi?id=1094248, I believe we need an additional 'overridable' flag on the servlet metadata which indicates whether ServletContainerInitializers (and other code using servlet dynamic registration) should be allowed to override the servlet. Normally this is not allowed, however JBWeb's internal use of DefaultServlet to handle static resources should be. > This only needs to go into 7, since the Undertow subsystem in Wildfly handles this quite differently, so does not need to pass a flag between components. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-385) Add overridable flag to servlet metadata

by James Livingston (JIRA)

James Livingston created JBMETA-385: --------------------------------------- Summary: Add overridable flag to servlet metadata Key: JBMETA-385 URL: https://issues.jboss.org/browse/JBMETA-385 Project: JBoss Metadata Issue Type: Enhancement Components: web Affects Versions: 7.2.1.Final Reporter: James Livingston Assignee: Jean-Frederic Clere To resolve https://bugzilla.redhat.com/show_bug.cgi?id=1094248, I believe we need an additional 'overridable' flag on the servlet metadata which indicates whether ServletContainerInitializers (and other code using servlet dynamic registration) should be allowed to override the servlet. Normally this is not allowed, however JBWeb's internal use of DefaultServlet to handle static resources should be. This only needs to go into 7, since the Undertow subsystem in Wildfly handles this quite differently, so does not need to pass a flag between components. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-567) Invoking shutdown command for slave HC results in CLI disconnecting

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-567: --------------------------------------- Summary: Invoking shutdown command for slave HC results in CLI disconnecting Key: WFCORE-567 URL: https://issues.jboss.org/browse/WFCORE-567 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 1.0.0.Alpha19 Reporter: Brian Stansberry Assignee: Alexey Loubyansky Connect the CLI to the master in a domain with a slave HC and shut down the slave. CLI disconnects: {code} [domain@localhost:9990 /] shutdown --host=slave [disconnected /] {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-565) StaticDiscoveryResourceDefinition allows undefined values for its attributes

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-565?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-565: ----------------------------------------- The "get" methods from DiscoveryOption can legitimately return null before the "discover()" method is invoked. The uses of DiscoveryOptionStrategy.DiscoveryOptionComparator are not properly dealing with that. We need to rethink the DiscoveryOption sorting, as there's sorting going on before discovery has taken place. > StaticDiscoveryResourceDefinition allows undefined values for its attributes > ---------------------------------------------------------------------------- > > Key: WFCORE-565 > URL: https://issues.jboss.org/browse/WFCORE-565 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > > StaticDiscoveryResourceDefinition reuses the AttributeDefinitions from RemoteDomainControllerAddHandler, but those ADs allow undefined. That's appropriate for that OSH, but not for the StaticDiscoveryResourceDefinition ADs. > Also, the RemoteDomainControllerAddHandler AD's could use some clarification and validation as well, e.g. use setRequires(...) on the builder such that each of protocol, host, port requires the other two. So none are required, but if any is set all 3 must be. > The StaticDiscovery constructor should validate inputs with assert statements and javadoc its parameters, include whether null is allowed. (A null protocol or host will result in an IAE in discover(), so the current code does not support null.) > The DiscoveryOption interface should document whether the 3 "get" methods can return null. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-565) StaticDiscoveryResourceDefinition allows undefined values for its attributes

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-565?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-565: ----------------------------------------- DiscoveryOptionStrategy.DiscoveryOptionComparator will fail if protocol or port are null for any DiscoveryOption. > StaticDiscoveryResourceDefinition allows undefined values for its attributes > ---------------------------------------------------------------------------- > > Key: WFCORE-565 > URL: https://issues.jboss.org/browse/WFCORE-565 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > > StaticDiscoveryResourceDefinition reuses the AttributeDefinitions from RemoteDomainControllerAddHandler, but those ADs allow undefined. That's appropriate for that OSH, but not for the StaticDiscoveryResourceDefinition ADs. > Also, the RemoteDomainControllerAddHandler AD's could use some clarification and validation as well, e.g. use setRequires(...) on the builder such that each of protocol, host, port requires the other two. So none are required, but if any is set all 3 must be. > The StaticDiscovery constructor should validate inputs with assert statements and javadoc its parameters, include whether null is allowed. (A null protocol or host will result in an IAE in discover(), so the current code does not support null.) > The DiscoveryOption interface should document whether the 3 "get" methods can return null. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4349) SEVERE JSF error on undeploy of WS module after Mojarra upgrade to 2.2.10

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-4349?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-4349: ----------------------------- Affects Version/s: 9.0.0.Alpha1 (was: 9.0.0.Beta1) > SEVERE JSF error on undeploy of WS module after Mojarra upgrade to 2.2.10 > ------------------------------------------------------------------------- > > Key: WFLY-4349 > URL: https://issues.jboss.org/browse/WFLY-4349 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 9.0.0.Alpha1 > Environment: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha18) > Oracle JDK 1.7.0_80-ea-b05, Solaris SPARC 10 > Reporter: Frank Langelage > Assignee: Farah Juma > Labels: mojarra, undertow > > Since latest update I get a SEVERE entry in server.log for every web-module getting undeployed. Those Web-modules contain webservices and are war files inside and ear. > 15.02. 21:31:48,151 INFO [org.wildfly.extension.undertow#unregisterDeployment] WFLYUT0022: Unregistered web context: /mbi-ws/maj2e-langfr-dev/production > 15.02. 21:31:48,151 INFO [org.wildfly.extension.undertow#unregisterDeployment] WFLYUT0022: Unregistered web context: /mbi/maj2e-langfr-dev/web > 15.02. 21:31:48,155 SEVERE [javax.enterprise.resource.webcontainer.jsf.config#contextDestroyed] Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist. > 15.02. 21:31:48,201 INFO [org.wildfly.extension.undertow#unregisterDeployment] WFLYUT0022: Unregistered web context: /mbi-ws/maj2e-langfr-dev/planning > 15.02. 21:31:48,204 SEVERE [javax.enterprise.resource.webcontainer.jsf.config#contextDestroyed] Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist. > 15.02. 21:31:48,239 SEVERE [javax.enterprise.resource.webcontainer.jsf.config#contextDestroyed] Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist. > 15.02. 21:31:48,217 INFO [org.wildfly.extension.undertow#unregisterDeployment] WFLYUT0022: Unregistered web context: /mbi-ws/maj2e-langfr-dev/core > 15.02. 21:31:48,359 INFO [org.wildfly.extension.undertow#unregisterDeployment] WFLYUT0022: Unregistered web context: /mbi-ws/maj2e-langfr-dev/sales > 15.02. 21:31:48,372 INFO [org.wildfly.extension.undertow#unregisterDeployment] WFLYUT0022: Unregistered web context: /mbi-ws/maj2e-langfr-dev/costing > 15.02. 21:31:48,379 INFO [org.wildfly.extension.undertow#unregisterDeployment] WFLYUT0022: Unregistered web context: /mbi-ws/maj2e-langfr-dev/purchase > 15.02. 21:31:48,381 SEVERE [javax.enterprise.resource.webcontainer.jsf.config#contextDestroyed] Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist. > 15.02. 21:31:48,383 INFO [org.wildfly.extension.undertow#unregisterDeployment] WFLYUT0022: Unregistered web context: /mbi-ws/maj2e-langfr-dev/external > 15.02. 21:31:48,396 SEVERE [javax.enterprise.resource.webcontainer.jsf.config#contextDestroyed] Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist. > 15.02. 21:31:48,397 SEVERE [javax.enterprise.resource.webcontainer.jsf.config#contextDestroyed] Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist. > 15.02. 21:31:48,399 SEVERE [javax.enterprise.resource.webcontainer.jsf.config#contextDestroyed] Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist. > 15.02. 21:31:48,402 INFO [org.wildfly.extension.undertow#unregisterDeployment] WFLYUT0022: Unregistered web context: /mbi-ws/maj2e-langfr-dev/inventory > 15.02. 21:31:48,444 SEVERE [javax.enterprise.resource.webcontainer.jsf.config#contextDestroyed] Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist. > 15.02. 21:31:48,404 INFO [org.wildfly.extension.undertow#unregisterDeployment] WFLYUT0022: Unregistered web context: /mbi-ws/maj2e-langfr-dev/common > 15.02. 21:31:48,407 INFO [org.wildfly.extension.undertow#unregisterDeployment] WFLYUT0022: Unregistered web context: /mbi-ws/maj2e-langfr-dev/distribution > 15.02. 21:31:48,408 SEVERE [javax.enterprise.resource.webcontainer.jsf.config#contextDestroyed] Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist. > 15.02. 21:31:48,480 SEVERE [javax.enterprise.resource.webcontainer.jsf.config#contextDestroyed] Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist. > 15.02. 21:31:48,481 SEVERE [javax.enterprise.resource.webcontainer.jsf.config#contextDestroyed] Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist. > Undeploy of my war file does not generate this SEVERE error. > 15.02. 21:43:24,243 INFO [org.wildfly.extension.undertow#unregisterDeployment] WFLYUT0022: Unregistered web context: /web-maj2e-langfr-dev > When I go back to the previous Mojarra 2.2.9-jbossorg-2 the error message disappears. > There are also a lot of theses SEVERE error messages in the testsuite output files (*.txt). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-566) space- and comma-separated attribute marshaller are broken

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFCORE-566: ---------------------------------- Summary: space- and comma-separated attribute marshaller are broken Key: WFCORE-566 URL: https://issues.jboss.org/browse/WFCORE-566 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 1.0.0.Alpha19 Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 1.0.0.Beta1 The AttributeMarshaller's STRING_LIST and COMMA_STRING_LIST are broken as they override marshallAsElement while it's their marshallAsAttribute method (inherited from DefaultAttributeMarshaller) that is called. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-565) StaticDiscoveryResourceDefinition allows undefined values for its attributes

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-565: --------------------------------------- Summary: StaticDiscoveryResourceDefinition allows undefined values for its attributes Key: WFCORE-565 URL: https://issues.jboss.org/browse/WFCORE-565 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry StaticDiscoveryResourceDefinition reuses the AttributeDefinitions from RemoteDomainControllerAddHandler, but those ADs allow undefined. That's appropriate for that OSH, but not for the StaticDiscoveryResourceDefinition ADs. Also, the RemoteDomainControllerAddHandler AD's could use some clarification and validation as well, e.g. use setRequires(...) on the builder such that each of protocol, host, port requires the other two. So none are required, but if any is set all 3 must be. The StaticDiscovery constructor should validate inputs with assert statements and javadoc its parameters, include whether null is allowed. (A null protocol or host will result in an IAE in discover(), so the current code does not support null.) The DiscoveryOption interface should document whether the 3 "get" methods can return null. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-66) Investigate warning messages about annotations and properties on JDK 7

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGTOOL-66?page=com.atlassian.jira.plugin... ] James Perkins updated LOGTOOL-66: --------------------------------- Git Pull Request: (was: https://github.com/jboss-logging/jboss-logging-tools/pull/19) > Investigate warning messages about annotations and properties on JDK 7 > ---------------------------------------------------------------------- > > Key: LOGTOOL-66 > URL: https://issues.jboss.org/browse/LOGTOOL-66 > Project: Log Tool > Issue Type: Task > Reporter: James Perkins > Assignee: James Perkins > > Seeing odd messages like: > {code} > [javac] warning: No processor claimed any of these annotations: org.jboss.logging.annotations.Cause,org.jboss.logging.annotations.LogMessage,org.jboss.logging.annotations.Message > [WARNING] The following options were not recognized by any processor: '[generatedTranslationFilesPath]' > {code} > There were some changes in APT in JDK 7. Some information here http://docs.oracle.com/javase/7/docs/technotes/tools/solaris/javac.html. This could be a mix of using the annotations and returning different values in the methods for the annotation processor. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 February 2015