[jboss-jira] [JBoss JIRA] (AS7-3758) ParsedInterfaceCriteria.parseCriteria is not maintaining ExpressionValues
[
https://issues.jboss.org/browse/AS7-3758?page=com.atlassian.jira.plugin.s...
]
Scott Stark commented on AS7-3758:
----------------------------------
It turns out that the current usage for INET_ADDRESS where the default configuration is
${jboss.bind.address.management:127.0.0.1}, sees an incoming Property with a ModelValue
type of ExpressionValue, so the current call to
createInetAddressCriteria(property.getValue()) is propagating an ExpressionValue. The call
to parsePossibleExpression(value) happens to be a noop that does not affect the outcome.
This is not the case for the LOOPBACK_ADDRESS test I had done.
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