[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-6825) BPEL Validator throws NPE when saving an unrelated BPEL process

Robert (Bob) Brodt (JIRA) jira-events at lists.jboss.org
Sat Aug 14 00:51:12 EDT 2010


     [ https://jira.jboss.org/browse/JBIDE-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert (Bob) Brodt resolved JBIDE-6825.
---------------------------------------

    Resolution: Done


Committed revision 24172.
This fixes a bunch of NPEs and adds XML parser error messages to BPEL resources for the case where the resource XML is completely hoarked.

Still need to figure out why the model defines both a org.eclipse.core.resources.builders and a org.eclipse.wst.validation.validator extension point - both of these eventually call the model Builder.validate(). The result is that ALL BPEL files in a project get validated TWICE whenever you save a BPEL editor resource. Created JBIDE-6839 for this issue.

> 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

        


More information about the jbosstools-issues mailing list