Brian Stansberry created WFCORE-641: --------------------------------------- Summary: The discovery-option "module" attribute should support undefined values Key: WFCORE-641 URL: https://issues.jboss.org/browse/WFCORE-641 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 1.0.0.CR1 The xsd says the following for the discovery-optionType 'module' attribute: {code} <xs:attribute name="module" type="xs:string" use="optional"> <xs:annotation> <xs:documentation> The module from which the DiscoveryOption implementation should be loaded. If not provided, the DiscoveryOption implementation must be available from the Host Controller's own module. </xs:documentation> </xs:annotation> </xs:attribute> {code} But the MODULE attribute definition does not allow undefined. But still, DiscoveryOptionAddHandler is coded as if undefined is allowed, but poorly so as it would pass an illegal null into ModuleIdentifier.fromString. I like the behavior described in the xsd and think the AD and the handlers should be corrected. -- This message was sent by Atlassian JIRA (v6.3.11#6341)