[jboss-jira] [JBoss JIRA] (WFCORE-750) Capability requirement resolution for socket-bindings
Brian Stansberry (JIRA)
issues at jboss.org
Tue Jun 9 08:39:03 EDT 2015
Brian Stansberry created WFCORE-750:
---------------------------------------
Summary: Capability requirement resolution for socket-bindings
Key: WFCORE-750
URL: https://issues.jboss.org/browse/WFCORE-750
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 2.0.0.Beta1
In a managed domain the existing capability resolution mechanism will not work properly for socket binding capabilities due to the relationship between socket-binding-groups and profiles.
The same socket-binding capability name can be registered in different socket-binding-groups. The existing approach can handle this easily enough by creating a CapabilityContext for each group, a la what is down with profiles. But then the resolution of requirements from resources in profiles needs to be handled.
The particular thing is that *all* requirements for socket bindings within a given profile must be resolvable against at least one socket binding group. Otherwise, no server group can map that profile and a socket binding group and end up with a combination that will work on a server.
So, the capability requirement validation stuff will need a consistency check for this case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list