|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
The problem so far was that I didn't see a really good way how the descriptor could be provided for user-created nodes.
The fact that only sub paths can be created and thus - if I get that right - only property nodes can be added changes things, though. We could return a PropertyDescriptor from these nodes, maybe also trying to find the "real" descriptor from the model, based on the name of the added nodes. In case a non-existent node is added, getConstraintDescriptors() could return an empty set. Not sure what to do about getElementClass() in this case, though.
The general question is whether we really want to expose all that info via the node API. We basically only need the kind and the parameter index, thus I grew fond of the idea of only exposing this info directly on Node.