[
https://issues.jboss.org/browse/WFLY-570?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on WFLY-570:
----------------------------------
It would cause an insignificant overhead, yes, unless people are already using booleans in
their management operation requests in which case it will remove an insignificant
overhead. Model node data structures are already more or less dynamically typed and
intended to be so. And, management operations are infrequent enough that there are
unlikely to ever be circumstances where this kind of conversion will ever have a
measurable performance impact.
Check ModelTypes in jacorb subsystem
------------------------------------
Key: WFLY-570
URL:
https://issues.jboss.org/browse/WFLY-570
Project: WildFly
Issue Type: Task
Components: Domain Management, IIOP
Affects Versions: 8.0.0.Alpha1
Reporter: Brian Stansberry
Fix For: 9.0.0.CR1
There are a number of attributes in the Jacorb subsystem that use ModelType.STRING for
things that look like booleans. Check through the attributes and change to
ModelType.BOOLEAN where appropriate.
This shouldn't raise a compatibility issue, since ModelType.BOOLEAN is freely
convertible to ModelType.STRING, and vice-versa so long as the string represents as
boolean (which it would have to do for the attribute to work anyway.) If anything is
changed though, a Console subtask should be created to look into any UI implications.
--
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