Better action support for ESB editor in JBT ------------------------------------------- Key: JBESB-3321 URL: https://jira.jboss.org/browse/JBESB-3321 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Libor Zoubek I was going through ESB editor for last few days and I was wondering why there is almost no support for ESB actions. As the action configuration in (jboss-esb.xml) is defined as almost xs:any, editor is not able to guess, what a config elements is an action able to read. I'd like to suggest new feature for actions. Every action class could provide additional information about its configuration structure. This could be accomplished for example by xsd schema (with all elements documented). Schemes would be available within jar containing an action, with corresponding file name. ESB editor would be able to load this XSD and could be more helpful when configuring given action. Editor could generate forms from loaded XSD, so ESB integrators wouldn't need to refer to programmer guide.If needed, in next phase we could define scheme which would be included in action's schemes and would provide non-tirvial element types like file, url etc. For example : Action A which as a configuration accepts this config tree : <file delete="true">/tmp/file</filewould define schema A.xsd which would look similar to this: <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:editor="http://anosvn.jboos.org/esb/esbeditor.xsd" <element name="file" editor:type="file" <annotation><documentation>file to be processed</documentation></annotation <simpleType <attribute name="delete" type="boolean" <annotation><documentation>Delete after processing</documentation></annotation </attribute </simpleType</element<schema Same behavior of editor would apply to 3rd-party action implementations. Moreover, this could impact ESB engine too, which could be able to validate action config against XSD schema and report configuration errors during deployment. What do you think? Libor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira