[
https://jira.jboss.org/jira/browse/JBIDE-3556?page=com.atlassian.jira.plu...
]
John Graham commented on JBIDE-3556:
------------------------------------
Kevin has mentioned elsewhere that these new features will appear in a .org version of the
ESB.
These changes would be backward compatible: all the "new" schema says is that
there are additional optional elements/attributes available in certain places. If these
are not used, then the resulting configuration would work with .org ESB versions (assuming
here that we keep the schema name/version exactly as-is currently, and just change the
content. If we change the schema name/version, then our configurations will not deploy
currently.)
(One caveat to the above: the restrictions from string to string:255 mean that any
existing configurations using more than 255 characters for these attributes will be
invalid, but that's a whole other issue to consider, and definitely a corner case --
users are not likely to approach 255 characters for these attributes, AFAIK.)
Finally, note that there is another alternative: leave things as-is for this release and
simply document the unsupported SOA-P features. This is the alternative voted for by Mark
L. We should consider whether doing anything about this right now makes sense, given that
ESB/SOA-P management is ok with the documentation-only choice.
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