[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1998) JBoss ESB Editor Usability Enhancments

[ http://jira.jboss.com/jira/browse/JBIDE-1998?page=comments#action_12407009 ] Viacheslav Kabanovich commented on JBIDE-1998: ---------------------------------------------- Yes, all this can be done. I have a few questions. Fig.1 Is it correct that presenting Properties as table with 2 columns Name & Value is needed everywhere in ESB editor, not only in Action's form? Fig.2 a) ' "tag" should be "Tag" ' - I assume that capitalization of names of attributes used in lists and tables in forms in our XML editor is to become common in Studio, not being restricted to cases mentioned in this issue. b) Presentation for element <route-to>, as well as Fig.5 presentation of <object-path> In schema for JBoss ESB, these elements are just part of any XML. XModel has flexible mechanism for building labels, but of course, each particular case is to programmed, there can be no way to guess what presentation is needed for an arbitrary xml tag. So the question is, do these 2 cases exhaust the specifics of ESB editor? If not, may we have complete list of cases here? Fig.3 a) ' "Jms Bus" is "Channel" ' - does this apply only to "Jms Bus" or to any kind of bus? Now each bus is 'decorated' with FTP, JBR and so on. Have I to use always just one word 'Channel' or 'FTP Channel, 'JBR Channel'; or leave non-JMS as is? b) ' "Bus id" is "ID" ' - the same question, is it for any kind of bus or JMS only? One more question for better understanding: is general idea to hide the word 'bus' anywhere in ESB editor? c) presenting property value. Is it sufficient just to bind "Value" column to "value" attribute? If property value is set by inner XML, tree viewer shows it. Or, in this case Value in table may be displayed as 'XML'. Fig.4 - no questions Fig.5 - see Fig.2 b) comment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira