[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-2022) Extend ESB Editor to support some important objects presented in XML with "free content" (not specified by XML schema)

[Max Andersen (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBIDE-2022?page=all ]

Max Andersen updated JBIDE-2022:
--------------------------------

    Fix Version/s: 2.2.x

ok for 2.2.

Slava, I suggest you take one of these examples you found and implement and get feedback on that one, instead of doing the whole set without feedback. 

Burr, any single or small set of the predefined actions that would be most interesting use as a guineypig ?

> 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
>             Fix For: 2.2.x
>
>
> 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