[jboss-jira] [JBoss JIRA] (WFLY-1941) can not undefine connection-factory's connector attribute

[Jeff Mesnil (JIRA)]

Jeff Mesnil created WFLY-1941:
---------------------------------

             Summary: can not undefine connection-factory's connector attribute
                 Key: WFLY-1941
                 URL: https://issues.jboss.org/browse/WFLY-1941
             Project: WildFly
          Issue Type: Feature Request
          Components: JMS
    Affects Versions: 8.0.0.Alpha4
            Reporter: Jeff Mesnil
            Assignee: Jeff Mesnil


use case:

{noformat}
[standalone at localhost:9990 /] /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:undefine-attribute(name=connector)
{
    "outcome" => "failed",
    "failure-description" => "JBAS014749: Operation handler failed: JBAS011664: Runtime handling for connector is not implemented",
    "rolled-back" => true
}
{noformat}

and the server outputs the error:

{noformat}

17:05:08,295 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014612: Operation ("undefine-attribute") failed - address: ([
    ("subsystem" => "messaging"),
    ("hornetq-server" => "default"),
    ("connection-factory" => "RemoteConnectionFactory")
]): java.lang.UnsupportedOperationException: JBAS011664: Runtime handling for connector is not implemented
        at org.jboss.as.messaging.jms.ConnectionFactoryWriteAttributeHandler.applyOperationToHornetQService(ConnectionFactoryWriteAttributeHandler.java:184)
        at org.jboss.as.messaging.jms.ConnectionFactoryWriteAttributeHandler.applyUpdateToRuntime(ConnectionFactoryWriteAttributeHandler.java:96)
        at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:101) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:608) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
        ...
{noformat}

The operation should fail but for another reason: we must check whether the discovery-group-name attribute (which is an alternative to the connector) is defined on the model. If it is not, it's an error to undefine the connector.

However, the code in ConnectionFactoryWriteAttributeHandler must also be updated to prevent updating an attribute that has *no* corresponding field in the ConnectionFactoryControl interface.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira