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.