[jboss-jira] [JBoss JIRA] (WFCORE-3322) Invalid socket-binding config in remoting connector resource does not lead to model integrity failure

[Brian Stansberry (JIRA)]

Brian Stansberry created WFCORE-3322:
----------------------------------------

             Summary: Invalid socket-binding config in remoting connector resource does not lead to model integrity failure
                 Key: WFCORE-3322
                 URL: https://issues.jboss.org/browse/WFCORE-3322
             Project: WildFly Core
          Issue Type: Bug
          Components: Remoting
            Reporter: Brian Stansberry
            Assignee: Brian Stansberry


A remoting connector with a socket-binding attribute pointing to a non-existing s-b does not fail with a capability validation failure:

{code}
[standalone at localhost:9990 /] /subsystem=remoting/connector=remoting-connector:add(security-realm=ApplicationRealm,socket-binding=remoting)
{
    "outcome" => "failed",
    "failure-description" => {
        "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.network.socket-binding.remoting"],
        "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.remoting-connector is missing [org.wildfly.network.socket-binding.remoting]"]
    },
    "rolled-back" => true
}
{code}

As in all such cases of missing cap validation, that means it doesn't fail at all in admin-only:

{code}
[standalone at localhost:9990 /] reload --admin-only=true
[standalone at localhost:9990 /] /subsystem=remoting/connector=remoting-connector:add(security-realm=ApplicationRealm,socket-binding=remoting)
{"outcome" => "success"}
{code}

Problem is ConnectorAdd isn't passing its attributes into the superclass, which means the superclass' recording of capability requirements isn't done.

I'll check for other occurrences of this pattern in the subsystem.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)