[jboss-jira] [JBoss JIRA] (WFLY-5283) [Migration operation] [Web to Undertow] Connector's protocol names via FQCN are not recognized as migratable
Kabir Khan (JIRA)
issues at jboss.org
Wed Dec 6 11:20:44 EST 2017
[ https://issues.jboss.org/browse/WFLY-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kabir Khan closed WFLY-5283.
----------------------------
> [Migration operation] [Web to Undertow] Connector's protocol names via FQCN are not recognized as migratable
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5283
> URL: https://issues.jboss.org/browse/WFLY-5283
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Beta2
> Reporter: Radim Hatlapatka
> Assignee: Stuart Douglas
> Priority: Critical
> Fix For: 10.0.0.CR1
>
>
> In Web subsystem there is possible to define protocol either via its API name (e.g. {{HTTP/1.1}}, where it is taken default implementation of given API) or via FQCN.
> In case of {{HTTP/1.1}} there are several implementations:
> JIO => {{org.apache.coyote.http11.Http11Protocol}} - default protocol
> NIO2 => {{org.apache.coyote.http11.Http11NioProtocol}} - required to be used to be able to use WebSockets
> APR (default with natives) => {{org.apache.coyote.http11.Http11AprProtocol}}
> The {{:migrate}} operation should also recognize these FQCN as valid HTTP/HTTPS protocols and migrate them correctly.
> Note: in case of AJP there are these FQCN:
> {{org.apache.coyote.ajp.AjpAprProtocol}} - AJP with natives enabled
> {{org.apache.coyote.ajp.AjpProtocol}} AJP without natives
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list