[
https://jira.jboss.org/browse/JBIDE-6085?page=com.atlassian.jira.plugin.s...
]
Viacheslav Kabanovich commented on JBIDE-6085:
----------------------------------------------
Yes, exactly.
And I would divide this examples into 2 groups.
A) Schema-like rules. If BusinessRulesProcessor were discribed by xsd schema instead of
usage of common tags <action> and <property>, rules (1), (3), (4), (6) and (7)
would be set as restrictions in schema and validated by wst validator. Model of ESB editor
can readily take that validation to itself by setting restrictions in metadata. I have not
enforced them before, because I was not sure that they are quite strict.
B) Rules that describe interaction of several properties - (2) and (5), that cannot be
readily described in schema or metadata, they are only for specific ESBCoreValidator
validator.
I will implement the rules for BusinessRulesProcessor in 3.2.0.Beta, that will be as
example for further work.
Implement Validation of ESB config file
---------------------------------------
Key: JBIDE-6085
URL:
https://jira.jboss.org/browse/JBIDE-6085
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Affects Versions: 3.1.0.GA
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 3.3.x
Attachments: ESBValidation_Marker.png, ESBValidatorPreferences .png
We have no validation implemented for consistency of objects, especially of actions that
formally may be supplied by any set of properties while each action class requires a
specific configuration.
We should implement validation similar to that we have for beans in Seam and CDI.
Documentation on ESB contains many rules on consistency of ESB objects not covered by
simply complying with xml schema.
--
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