[
https://jira.jboss.org/jira/browse/JBIDE-5726?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBIDE-5726:
-------------------------------------
It only needs to be removed if the user changes it to something that selects a different
node. If the user just makes the selector more/less specific, then it doesn't need to
be removed.
Example... if the selector was "order/header/customer/name" and the user changes
it to:
1. "order/header/customer/address", then it should be removed.
2. "customer/name", then it doesn't need to be removed, because it is
selecting the same element, but is just less "specific".
In reality, the only reason a user might do #2 above is for performance reasons - a less
specific selector is faster to match. I think we should just make these properties
readonly (and if possible... move them to the connection where imo they belong).
Show Decode Parameters on Java Binding connection
-------------------------------------------------
Key: JBIDE-5726
URL:
https://jira.jboss.org/jira/browse/JBIDE-5726
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Reporter: Tom Fennelly
Assignee: Xue Peng
Priority: Critical
Fix For: 3.1.0.CR2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
At the moment, we show the data decode paramaters/configuration when the user clicks on
the target bean property. This information is not really associated with the target bean
property... it is a associated with the source to target binding i.e. the connection
between the source and target.
--
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