[
https://issues.jboss.org/browse/AS7-3296?page=com.atlassian.jira.plugin.s...
]
Tomaz Cerar commented on AS7-3296:
----------------------------------
The proper way to fix/improve this would be if we would define all attributes that exists
for all options available but according to this:
https://github.com/dmlloyd/xnio/blob/3.x/api/src/main/java/org/xnio/Optio...
that would be a big overhead, it could be possible to dynamically define the list of all
AttributeDefinition's via reflection but I don't see any benefit of this.
Just moving complex attribute it to child resources it would not fix much unless we also
provide add/remove operations for whole context...
Fix inconsistent handling of property types in remoting subsystem
-----------------------------------------------------------------
Key: AS7-3296
URL:
https://issues.jboss.org/browse/AS7-3296
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Remoting
Reporter: Brian Stansberry
Assignee: Tomaz Cerar
Fix For: 7.1.0.Final
The outbound-connection resources are storing properties in a complex attribute instead
of in child resources. That's inconsistent with other usage in the subsystem, so it
needs to be fixed.
--
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