[
https://issues.jboss.org/browse/AS7-3758?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-3758:
---------------------------------------
OK, I understand now. For <inet-address> it works because the xml parser itself
(CommonXml.java) is creating the node as type EXPRESSION, but for <loopback-address>
it isn't. I'll fix that as well when I merge your patch, Scott.
ParsedInterfaceCriteria.parseCriteria is not maintaining
ExpressionValues
-------------------------------------------------------------------------
Key: AS7-3758
URL:
https://issues.jboss.org/browse/AS7-3758
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Scott Stark
Assignee: Scott Stark
Labels: network
Original Estimate: 1 hour
Remaining Estimate: 1 hour
The parsing of interfaces is throwing away ExpressionValues that are created from
parsePossibleExpression since the resulting ExpressionValue is not passed onto the
For example, in this LOOPBACK_ADDRESS block, the input property.getValue() is passed to
the LoopbackAddressInterfaceCriteria ctor rather than the ExpressionValue that is created
by parsePossibleExpression:
case LOOPBACK_ADDRESS: {
ModelNode value = property.getValue();
value = parsePossibleExpression(value);
checkStringType(value, element.getLocalName(), true);
return new LoopbackAddressInterfaceCriteria(property.getValue());
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira