[JBoss JIRA] (WFLY-7076) Elytron introduces SSL/TLS protocol constraints
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7076?page=com.atlassian.jira.plugin.... ]
Jan Kalina edited comment on WFLY-7076 at 9/10/16 11:19 AM:
------------------------------------------------------------
bq. I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
This is defined in *org.wildfly.security.ssl.Protocol* enum (wildfly-elytron)
Reason for restriction is using this enum in our *ProtocolSelector*.
To remove this restriction should be sufficient replace all Protocol occurences by String.
Is it what we want, [~dlofthouse]?
was (Author: honza889):
bq. I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
This is defined in *org.wildfly.security.ssl.Protocol* enum (wildfly-elytron)
Reason for restriction is using this enum in our *ProtocolSelector*.
To remove this restriction should be sufficient replace all Protocol occurences by String. Is it what we want?
> Elytron introduces SSL/TLS protocol constraints
> -----------------------------------------------
>
> Key: WFLY-7076
> URL: https://issues.jboss.org/browse/WFLY-7076
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Jan Kalina
>
> {noformat}
> "protocols" => {
> "type" => LIST,
> "description" => "The enabled protocols.",
> "expressions-allowed" => true,
> "nillable" => false,
> "allowed" => [
> "SSLv2",
> "SSLv3",
> "TLSv1",
> "TLSv1_1",
> "TLSv1_2",
> "TLSv1_3"
> ],
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> {noformat}
> Why elytron on this place is going to validate user input and map standard java values [1] into proprietary values?
> Whereas on other similar places (KeyManager algorithm, TrustManager algorithm, Keystore types) it leaves up to user to set proper value.
> IMO, with such mapping another place, where bugs can raise was introduced. EAP will be here always one step back compared to java.
> Note, IBM java already today defines little bit different protocols set [2]
> I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
> [1] https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardN...
> [2] http://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.secu...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7076) Elytron introduces SSL/TLS protocol constraints
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7076?page=com.atlassian.jira.plugin.... ]
Jan Kalina edited comment on WFLY-7076 at 9/10/16 10:22 AM:
------------------------------------------------------------
bq. I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
This is defined in *org.wildfly.security.ssl.Protocol* enum (wildfly-elytron)
Reason for restriction is using this enum in our *ProtocolSelector*.
To remove this restriction should be sufficient replace all Protocol occurences by String. Is it what we want?
was (Author: honza889):
bq. I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
This is defined in *org.wildfly.security.ssl.Protocol* enum (wildfly-elytron)
Reason for restriction is using this enum in our *ProtocolSelector*.
To remove this restriction, I can replace all Protocol occurences by String.
> Elytron introduces SSL/TLS protocol constraints
> -----------------------------------------------
>
> Key: WFLY-7076
> URL: https://issues.jboss.org/browse/WFLY-7076
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Jan Kalina
>
> {noformat}
> "protocols" => {
> "type" => LIST,
> "description" => "The enabled protocols.",
> "expressions-allowed" => true,
> "nillable" => false,
> "allowed" => [
> "SSLv2",
> "SSLv3",
> "TLSv1",
> "TLSv1_1",
> "TLSv1_2",
> "TLSv1_3"
> ],
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> {noformat}
> Why elytron on this place is going to validate user input and map standard java values [1] into proprietary values?
> Whereas on other similar places (KeyManager algorithm, TrustManager algorithm, Keystore types) it leaves up to user to set proper value.
> IMO, with such mapping another place, where bugs can raise was introduced. EAP will be here always one step back compared to java.
> Note, IBM java already today defines little bit different protocols set [2]
> I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
> [1] https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardN...
> [2] http://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.secu...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7076) Elytron introduces SSL/TLS protocol constraints
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7076?page=com.atlassian.jira.plugin.... ]
Jan Kalina edited comment on WFLY-7076 at 9/10/16 10:20 AM:
------------------------------------------------------------
bq. I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
This is defined in *org.wildfly.security.ssl.Protocol* enum (wildfly-elytron)
Reason for restriction is using this enum in our *ProtocolSelector*.
To remove this restriction, I can replace all Protocol occurences by String.
was (Author: honza889):
bq. I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
This is defined in *org.wildfly.security.ssl.Protocol* enum (wildfly-elytron)
Reason for restriction is using this enum in our *ProtocolSelector*.
> Elytron introduces SSL/TLS protocol constraints
> -----------------------------------------------
>
> Key: WFLY-7076
> URL: https://issues.jboss.org/browse/WFLY-7076
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Jan Kalina
>
> {noformat}
> "protocols" => {
> "type" => LIST,
> "description" => "The enabled protocols.",
> "expressions-allowed" => true,
> "nillable" => false,
> "allowed" => [
> "SSLv2",
> "SSLv3",
> "TLSv1",
> "TLSv1_1",
> "TLSv1_2",
> "TLSv1_3"
> ],
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> {noformat}
> Why elytron on this place is going to validate user input and map standard java values [1] into proprietary values?
> Whereas on other similar places (KeyManager algorithm, TrustManager algorithm, Keystore types) it leaves up to user to set proper value.
> IMO, with such mapping another place, where bugs can raise was introduced. EAP will be here always one step back compared to java.
> Note, IBM java already today defines little bit different protocols set [2]
> I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
> [1] https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardN...
> [2] http://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.secu...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7076) Elytron introduces SSL/TLS protocol constraints
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7076?page=com.atlassian.jira.plugin.... ]
Jan Kalina edited comment on WFLY-7076 at 9/10/16 10:09 AM:
------------------------------------------------------------
bq. I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
This is defined in *org.wildfly.security.ssl.Protocol* enum (wildfly-elytron)
Reason for restriction is using this enum in our *ProtocolSelector*.
was (Author: honza889):
bq. I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
This is defined in *org.wildfly.security.ssl.Protocol* enum (wildfly-elytron)
> Elytron introduces SSL/TLS protocol constraints
> -----------------------------------------------
>
> Key: WFLY-7076
> URL: https://issues.jboss.org/browse/WFLY-7076
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Jan Kalina
>
> {noformat}
> "protocols" => {
> "type" => LIST,
> "description" => "The enabled protocols.",
> "expressions-allowed" => true,
> "nillable" => false,
> "allowed" => [
> "SSLv2",
> "SSLv3",
> "TLSv1",
> "TLSv1_1",
> "TLSv1_2",
> "TLSv1_3"
> ],
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> {noformat}
> Why elytron on this place is going to validate user input and map standard java values [1] into proprietary values?
> Whereas on other similar places (KeyManager algorithm, TrustManager algorithm, Keystore types) it leaves up to user to set proper value.
> IMO, with such mapping another place, where bugs can raise was introduced. EAP will be here always one step back compared to java.
> Note, IBM java already today defines little bit different protocols set [2]
> I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
> [1] https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardN...
> [2] http://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.secu...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7076) Elytron introduces SSL/TLS protocol constraints
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7076?page=com.atlassian.jira.plugin.... ]
Jan Kalina commented on WFLY-7076:
----------------------------------
bq. I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
This is defined in *org.wildfly.security.ssl.Protocol* enum (wildfly-elytron)
> Elytron introduces SSL/TLS protocol constraints
> -----------------------------------------------
>
> Key: WFLY-7076
> URL: https://issues.jboss.org/browse/WFLY-7076
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Jan Kalina
>
> {noformat}
> "protocols" => {
> "type" => LIST,
> "description" => "The enabled protocols.",
> "expressions-allowed" => true,
> "nillable" => false,
> "allowed" => [
> "SSLv2",
> "SSLv3",
> "TLSv1",
> "TLSv1_1",
> "TLSv1_2",
> "TLSv1_3"
> ],
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> },
> {noformat}
> Why elytron on this place is going to validate user input and map standard java values [1] into proprietary values?
> Whereas on other similar places (KeyManager algorithm, TrustManager algorithm, Keystore types) it leaves up to user to set proper value.
> IMO, with such mapping another place, where bugs can raise was introduced. EAP will be here always one step back compared to java.
> Note, IBM java already today defines little bit different protocols set [2]
> I wonder, where is that mapping "TLSv1_2 -> TLSv1.2" acually performed? I couldn't find that place.
> [1] https://docs.oracle.com/javase/8/docs/technotes/guides/security/StandardN...
> [2] http://www.ibm.com/support/knowledgecenter/SSYKE2_8.0.0/com.ibm.java.secu...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7080) Creating ssl context with only required attribute cause NPE
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7080?page=com.atlassian.jira.plugin.... ]
Jan Kalina edited comment on WFLY-7080 at 9/10/16 7:40 AM:
-----------------------------------------------------------
Sent pull request to wildfly master. (added to pull request with "SSLContext - client side", which is strongly related and may be required too)
was (Author: honza889):
Sent pull request to wildfly master.
> Creating ssl context with only required attribute cause NPE
> -----------------------------------------------------------
>
> Key: WFLY-7080
> URL: https://issues.jboss.org/browse/WFLY-7080
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Critical
> Fix For: 11.0.0.Alpha1
>
>
> {noformat}
> [standalone@localhost:9990 /] /subsystem=elytron/server-ssl-context=server2:add(protocols=[TLSv1_2])
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.server2" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.server2: Failed to start service
> Caused by: java.lang.NullPointerException"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.server2"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> },
> "rolled-back" => true
> }
> {noformat}
> In log of server there is exception:
> {noformat}
> 07:12:21,014 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.security.ssl-context.server2: org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.server2: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:275)
> at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:45)
> at org.wildfly.extension.elytron.SSLDefinitions$3.lambda$getValueSupplier$1(SSLDefinitions.java:411)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ... 3 more
> 07:12:21,016 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 6) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("server-ssl-context" => "server2")
> ]) - failure description: {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.server2" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.server2: Failed to start service
> Caused by: java.lang.NullPointerException"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.server2"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7080) Creating ssl context with only required attribute cause NPE
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7080?page=com.atlassian.jira.plugin.... ]
Jan Kalina edited comment on WFLY-7080 at 9/10/16 7:32 AM:
-----------------------------------------------------------
* *SSLContextBuilder:* "key-managers" was made optional in SSLContextBuilder because client-ssl-context (client doesnt need keystore when client auth is not used, only truststore)
* *model validation:* I will change "protocols" to optional in model.
was (Author: honza889):
* "key-managers" was made optional in SSLContextBuilder because client-ssl-context (client doesnt need keystore when client auth is not used, only truststore)
* I will change "protocols" to optional in model.
> Creating ssl context with only required attribute cause NPE
> -----------------------------------------------------------
>
> Key: WFLY-7080
> URL: https://issues.jboss.org/browse/WFLY-7080
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Critical
> Fix For: 11.0.0.Alpha1
>
>
> {noformat}
> [standalone@localhost:9990 /] /subsystem=elytron/server-ssl-context=server2:add(protocols=[TLSv1_2])
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.server2" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.server2: Failed to start service
> Caused by: java.lang.NullPointerException"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.server2"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> },
> "rolled-back" => true
> }
> {noformat}
> In log of server there is exception:
> {noformat}
> 07:12:21,014 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.security.ssl-context.server2: org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.server2: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:275)
> at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:45)
> at org.wildfly.extension.elytron.SSLDefinitions$3.lambda$getValueSupplier$1(SSLDefinitions.java:411)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ... 3 more
> 07:12:21,016 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 6) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("server-ssl-context" => "server2")
> ]) - failure description: {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.server2" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.server2: Failed to start service
> Caused by: java.lang.NullPointerException"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.server2"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7080) Creating ssl context with only required attribute cause NPE
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7080?page=com.atlassian.jira.plugin.... ]
Jan Kalina commented on WFLY-7080:
----------------------------------
* "key-managers" was made optional in SSLContextBuilder because client-ssl-context (client doesnt need keystore when client auth is not used, only truststore)
* I will change "protocols" to optional in model.
> Creating ssl context with only required attribute cause NPE
> -----------------------------------------------------------
>
> Key: WFLY-7080
> URL: https://issues.jboss.org/browse/WFLY-7080
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Critical
> Fix For: 11.0.0.Alpha1
>
>
> {noformat}
> [standalone@localhost:9990 /] /subsystem=elytron/server-ssl-context=server2:add(protocols=[TLSv1_2])
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.server2" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.server2: Failed to start service
> Caused by: java.lang.NullPointerException"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.server2"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> },
> "rolled-back" => true
> }
> {noformat}
> In log of server there is exception:
> {noformat}
> 07:12:21,014 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service org.wildfly.security.ssl-context.server2: org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.server2: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:275)
> at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:45)
> at org.wildfly.extension.elytron.SSLDefinitions$3.lambda$getValueSupplier$1(SSLDefinitions.java:411)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ... 3 more
> 07:12:21,016 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 6) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("server-ssl-context" => "server2")
> ]) - failure description: {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.server2" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.server2: Failed to start service
> Caused by: java.lang.NullPointerException"},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.server2"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (WFLY-7089) Undertow appears to require explicit keywords implements WebApplicationInitializer
by Darryl Miles (JIRA)
Darryl Miles created WFLY-7089:
----------------------------------
Summary: Undertow appears to require explicit keywords implements WebApplicationInitializer
Key: WFLY-7089
URL: https://issues.jboss.org/browse/WFLY-7089
Project: WildFly
Issue Type: Feature Request
Components: Web (Undertow)
Affects Versions: 10.1.0.Final
Reporter: Darryl Miles
Assignee: Stuart Douglas
Undertow appears to require explicit keywords implements WebApplicationInitializer set on WEB-INF/classes when the class is using an "extends AbstractBaseClassThatImplementWebApplicationInitializer".
It does not appear to see the annotation set on the base class AbstractBaseClassThatImplementWebApplicationInitializer.
More over in my particular scenario this base class is provided in a JAR that is inside the EAR (not the WAR).
Maybe what Wildfly is doing is completely specification compliant and other Servlet implementations work differently.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months