[ http://jira.jboss.com/jira/browse/JBIDE-1998?page=all ] Burr Sutter updated JBIDE-1998: ------------------------------- Attachment: Filter_Editor.jpg -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-1998?page=all ] Burr Sutter updated JBIDE-1998: ------------------------------- Attachment: object_path_editor.jpg -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-1998?page=comments#action_12406996 ] Max Andersen commented on JBIDE-1998: ------------------------------------- Attaching sample files would be a Good Thing ;) I'll assume that for those changes you say we should show an attribute value instead of the tag name we should show "unspecfied" or something ? (Slava, do we have a common way of doing that today ?) -- 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

[ 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

[ http://jira.jboss.com/jira/browse/JBIDE-1998?page=comments#action_12407085 ] Burr Sutter commented on JBIDE-1998: ------------------------------------ Q: 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? A: Yes, ideally all the properties tables would be 2 columns so that the value is easy to see. Here are some examples: <property name="script" value="/scripts/setup_key.groovy" /> - it is important to see the "/scripts/setup_key.groovy" without having to hit the Edit button. <property name="command" value="StartProcessInstanceCommand" /> <property name="process-definition-name" value="bpm4_ESBOrderProcess" /> <property name="key" value="body.businessKey" /> <property name="resource-config" value="/smooks-config.xml" /> <property name="status" value="40" /> <property name="ruleSet" value="Priority_Rules.drl" /> <property name="ruleReload" value="true" /> Now, I don't expect you to deal with properties (in a 2 column sense) that look like this one, unless you know some magic. ;-) <property name="object-paths"> <object-path esb="body.orderHeader" /> <object-path esb="body.customer" /> </property> Q: 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. A: I was trying to suggest that on screen labels (not data) be capitalized. Q: 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? A: I'm not sure that this complete. There are the only two uses that I'm aware of. Let me find out more. Q: 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? A: We were thinking just the word "Channel" to make it generic, cleaner. Q: b) ' "Bus id" is "ID" ' - the same question, is it for any kind of bus or JMS only? A: Any of the transports/channels. JMS, FTP, File, HTTP, etc. Q: One more question for better understanding: is general idea to hide the word 'bus' anywhere in ESB editor? A: I feel the word "bus" is somewhat confusing and often redundant. People perceive the "bus" to be the engine itself, not a specific transport/channel/connection/endpoint within the "bus". The primary goal of the current jboss-esb.xml is to describe a service(s) and its endpoint(s) not the "bus" as a whole. Q: 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'. A: the "value" attribute should suffice and simply saying "XML" in the value column for the more complex options make sense to me. The user can either see it in the tree-control or hit the edit button to get the details. -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-1998?page=comments#action_12407313 ] Max Andersen commented on JBIDE-1998: ------------------------------------- Slava, I suggest you close this one and opens another issue for ESB's apparent "free content" support. -- 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