[ https://jira.jboss.org/browse/JBIDE-7768?page=com.atlassian.jira.plugin.s... ] Marek Baluch updated JBIDE-7768: -------------------------------- Attachment: broken_validation.jpg -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7768?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt commented on JBIDE-7768: ------------------------------------------- Yep, this is a known issue, specifically the malformed XML problem. Also, unknown BPEL elements are not detected and flagged as errors. See: https://jira.jboss.org/browse/JBIDE-6017 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7768?page=com.atlassian.jira.plugin.s... ] Robert (Bob) Brodt updated JBIDE-7768: -------------------------------------- Fix Version/s: 3.2.0.CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7768?page=com.atlassian.jira.plugin... ] Robert (Bob) Brodt resolved JBIDE-7768. --------------------------------------- Resolution: Done As a result of several other, unrelated bug fixes, I think we're OK. Like any language, there are two classifications of errors: syntactic (XML well-formedness) and semantic (BPEL validness). Assuming there are no XML syntax errors, BPEL validation is currently performed when a file is saved, and MOST of the OASIS "Static Analysis" checks [1] are done. There are still one or two that aren't covered yet - I'll have to dig further to figure out which ones, but these are minor. The editor DOES validate against the OASIS BPEL schema [2] and [3] so if you try to use a custom extension, it will warn you about that. There are also some issues with abstract process definitions, such as namespace prefix resolution (the code assumes xmlns:bpel="http://docs.oasis-open.org/wsbpel/2.0/process/executable...) which will lead to undefined namespace prefix errors. But, AFAIK, abstract processes are seldom used and only for documentation purposes. As far as syntax errors are concerned, it is possible to mess up a BPEL file in varying degrees by intentionally switching to the XML view and, for example, removing an opening tag, or writing crappy XML (NOTE: the level of crappyness depends on the user's understanding of XML to begin with ;) These types of errors ARE caught by the XML parser and decorated in the XML Source view with an error icon, although the Design view will typically be completely blank except for a Start and End activity. But again, that depends on the level of crappyness and which BPEL element(s) are in error. There was a time when these kinds of errors would totally corrupt a BPEL file when you tried to save it, but I haven't seen any more instances of this. In either case, both the Design View and Source View are decorated with error markers to the extent we can determine where the error lies. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7768?page=com.atlassian.jira.plugin... ] Pavol Srna closed JBIDE-7768. ----------------------------- I added some errors and these were detected correctly. Closing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira