[
https://jira.jboss.org/browse/JBIDE-6825?page=com.atlassian.jira.plugin.s...
]
Robert (Bob) Brodt commented on JBIDE-6825:
-------------------------------------------
I almost forgot: the other part of this is that the editor does NOT report the invalid XML
as an error! This is because the editor uses a different EMF Resource reader for the
initial model loading. This reader does not validate the XML - it is simply ignored and
allowed to load the remainder of the document.
There are 3 (count 'em!) different versions of the BPEL EMF Resource reader classes:
org.eclipse.bpel.ui.util.BPELReader
org.eclipse.bpel.validator.BPELReader
org.eclipse.bpel.model.resource.BPELReader
The first is the one used by the editor during the initial loading phase. The second
version is used by the BPEL Builder for validation, the third is used at various random
times during the model's lifecycle. We need to reconcile these three versions, at
least to the point where they all do SAXParserExeption handling and reporting.
BPEL Validator throws NPE when saving an unrelated BPEL process
---------------------------------------------------------------
Key: JBIDE-6825
URL:
https://jira.jboss.org/browse/JBIDE-6825
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel
Environment: All
Reporter: Robert (Bob) Brodt
Assignee: Robert (Bob) Brodt
Fix For: 3.2.x
If a BPEL project contains an invalid BPEL resource that fails XML parsing, the validator
will report a problem when ANY other BPEL resource in the same project is saved during
editing. The Builder throws an NPE when it tries to remove error markers in imported
resource (i.e. WSDLs and XSDs) - this happens in
Builder.deleteMarkersInReferencialResources().
--
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