[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
Burr Sutter (JIRA)
jira-events at lists.jboss.org
Tue Apr 8 13:56:54 EDT 2008
[ http://jira.jboss.com/jira/browse/JBIDE-2022?page=comments#action_12407597 ]
Burr Sutter commented on JBIDE-2022:
------------------------------------
The real tricky part will be the fact that each Actions configuration is unique and NOT prescribed in a java interface. My only suggestion is that you have the ESB team produce a template XML config, per action that the tool can use a template for the end-user.
> Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-2022
> URL: http://jira.jboss.com/jira/browse/JBIDE-2022
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: esb
> Affects Versions: 2.1.0.beta1
> Reporter: Viacheslav Kabanovich
> Assigned To: Viacheslav Kabanovich
>
> XML schema for ESB allows <property> tag to have any XML content,
> and it allows for elements using tags <property> as its children to declare
> any set of properties.
> That makes XML quite flexible, but the ESB editor based on that only cannot
> assist customers in setting specific properties. We have only common form
> for editing elements described as ANY in dtd/schema.
> What is done for presentation of <route-to> and <object-path> is just a small
> portion of what ESB editor may be customized into.
> It seems that since actions, for instance, are based on Java classes,
> the structure of a specific action is well defined by its Java class,
> both property names and their types.
> It means that each action Java class could contribute to XML schema and specific
> forms in ESB editor.
> Of course, it may not be reasonable to complicate actual ESB XML schema,
> but editor may be based on an extended schema.
> So, do you think that ESB editor should recognize some specific objects
> (e.g. action based on org.jboss.soa.esb.actions.ContentBasedRouter)
> and implement for them more sophisticated set of forms and
> context commands than those based on generic schema?
--
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
More information about the jbosstools-issues
mailing list