[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3556) Support SOA-P 4.3 version of ESB configuration schema

[Max Rydahl Andersen (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448040#action_12448040 ] 

Max Rydahl Andersen commented on JBIDE-3556:
--------------------------------------------

ok, looking into this then this is simply non-fixable without changing ESB or SOA-P examples/implementation since no matter the version of ESB it always points to http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.0.1.xsd (or even worse, no xsd is even declared).

Besides it being a completely broken idea to use SVN trunk to be a location for an .xsd it is also bad there is no consistent logical name used.
If that name or url had been different between the versions we could actually been able to differentiate.

That being said this simply looks like backwards compatible changes which we also see happening in hibernate, seam and other frameworks without a change in name/version. This happens to avoid havening to update xml files headers for every minor release, but the downside is that an xml editor will provide completions that might not be possible dependent on the underlying runtime. Something we need to live with.

I therefore suggest that we simply update the editor to use the latest version of the XSD assuming all the changes are backward compatible.

Any objections ?

> Support SOA-P 4.3 version of ESB configuration schema
> -----------------------------------------------------
>
>                 Key: JBIDE-3556
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3556
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: esb
>    Affects Versions: 3.0.0.cr1
>            Reporter: John Graham
>            Priority: Critical
>             Fix For: 3.0.0.CR2
>
>         Attachments: jbossesb-1.0.1.xsd
>
>
> The SOA-P 4.3 version of the jboss-esb configuration schema is different from the one delivered with ESB 4.4 (which is what the current JBT ESB configuration editor uses). 
> Unfortunately, the version numbers on these two schema are the same, so all we can do is add the support for the additional (SOA-P 4.3) features and accept the fact that ESB 4.4 users might generate configuration files that can't be deployed (if they use these new features with an ESB 4.4 runtime).
> The SOA-P schema is attached, but here are the diffs:
> 1. A "service" element can have an optional "security" element child.
> 2. The data types for the "category," "name," and "description"
> attributes on a service element have changed from string to string
> bounded at 255 characters.
> 3. Attributes "webservice" and "validate" have been added to the
> "action" element.
> 4. an "invmTransacted" attribute has been added to "service" elements.
> 5. "inXsd," "outXsd," and "faultXsd" attributes have been added to
> "action" elements.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira