[
https://jira.jboss.org/jira/browse/JBIDE-3974?page=com.atlassian.jira.plu...
]
Maurice Zeijen commented on JBIDE-3974:
---------------------------------------
I hadn't noticed that you can use the properties perspective on the connections. Some
features in there will probably make some of my feature requests different. Sorry about
that.
Regarding the Selector generate policies, I think only three policies would make sense:
- Shortest/Safest path
- Full path
The "Shortest/Safest" path policy would make the other three policies obsolete,
because it would select the best path possible.
Use the shortes unique selector path instead of the full selector
path
----------------------------------------------------------------------
Key: JBIDE-3974
URL:
https://jira.jboss.org/jira/browse/JBIDE-3974
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Affects Versions: 3.0.0.CR2
Reporter: Maurice Zeijen
Assignee: Xue Peng
Attachments: picture1.jpg
Currently the graph editor uses the full selector path. Always using the full selector
path may seem the safest path but it can have serious performance implications for Smooks.
A binding with a short selector is resolved faster then one with a long selector. It would
be better if the graph editor would use the shortest unique selector path.
Example:
<order>
<customer>
<id>432</id>
</customer>
<order-items>
<order-item>
<id>111</id>
<quantity>2</quantity>
<price>8.90</price>
</order-item>
</order-items>
</order>
If you would bind the 'id' element of order-item to some bean then currently the
following path would be generated by the graph editor: order order-items order-item id
If the graph editor would generate the shortest unique path, then it would be: order-item
id
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira