[
https://issues.jboss.org/browse/WFLY-8551?page=com.atlassian.jira.plugin....
]
Tomaz Cerar commented on WFLY-8551:
-----------------------------------
I still think that adapter shouldn't be a capability.
from outside view only thing you are interested in is "mod_cluster" capability
how it is composed to get to that you don't care.
It is similar as with what we have in web-common, you as user, you don't care about
who is providing impl for webhost, either undertow or jbossweb.
you just care that you get webhost and that its api works for you.
As such, undertow as consumer of mod_cluster capability should only care about that
capability it doesn't need to know about adapters. Which is also what I did in my
initial work on that, but you two disagreed :)
Establish proper capability contract for mod_cluster undertow
adapter
---------------------------------------------------------------------
Key: WFLY-8551
URL:
https://issues.jboss.org/browse/WFLY-8551
Project: WildFly
Issue Type: Bug
Components: mod_cluster
Affects Versions: 11.0.0.Alpha1
Reporter: Radoslav Husar
Assignee: Radoslav Husar
This was never exposed as there wasn't an expectation that somebody would depend on
this. Initial contract + workaround introduced by
https://github.com/wildfly/wildfly/pull/9897
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)