[
http://jira.jboss.com/jira/browse/JBIDE-2399?page=comments#action_12418234 ]
Max Rydahl Andersen commented on JBIDE-2399:
--------------------------------------------
Well first question is wether we have a ESB runtime or SOA-P/EAP runtime or both ? :)
In other places we have an AS, Seam, Java, JBossWS runtime...so following that it would be
a ESB runtime we would need.
EAP/SOA-P is more a "overarching" version....not sure how to support that/if it
is relevant.
Validation of ESB files for specific SOA-P versions
---------------------------------------------------
Key: JBIDE-2399
URL:
http://jira.jboss.com/jira/browse/JBIDE-2399
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: esb
Reporter: John Graham
Assigned To: John Graham
Given that the SOA-P run time will change from release to release, we need some generic
way of validating ESB files in Eclipse projects for specific run time versions. This might
be done at the package level (that is, when creating a deployment package), but ideally
would be done "live:" as the user makes changes, warnings/errors would appear in
the Eclipse Problems view. To accomplish this, we would need to set a (minimum? probably
not, because backward compatibility is not supported) "SOA-P run time level"
(like the JVM level) and have a validation model for checking. The idea is to avoid simple
compatibility errors appearing at run time where they could have been noticed at design
time.
(This is related to, but larger than, the ESB reference tracking work.)
--
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