mevenide

Invalid XML document causes Project Object Model Editor to crash

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: mevenide-eclipse
  • Labels:
    None
  • Number of attachments :
    1

Description

Eclipse User Message:
Unable to create editor. This message may be due to a bug in the editor, not a problem with the file you are trying to edit. First close this error message and then use "Open With..." to open the file in a different editor. Reason for the failure: Could not obtain Project reader

Error Message:
Unable to create editor ID org.mevenide.ui.eclipse.editors.pom.MevenidePomEditor: Could not obtain Project reader

Error Message Stack Trace:
org.eclipse.ui.PartInitException: Could not obtain Project reader
at org.mevenide.ui.eclipse.editors.pom.MevenidePomEditor.init(MevenidePomEditor.java:411)
at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:857)

To replicate:

  • Open a valid "project.xml" in Project Object Model Editor (prove that the editor is still working)
  • Close the editor
  • Open "project.xml" using the "Text Editor" add an "&" anywhere as the text of a tag. Since this is invalid XML and should have been "&"
  • Close the editor
  • Try to open "project.xml" in Project Object Model Editor, it will now fail with the error above.

To resolve these issues use an XML aware editor like, XMLBuddy and validate the XML. It should tell you why it is invalid so you can then fix it.

Bae

  1. XML File
    project.xml
    01/Jul/05 5:28 AM
    11 kB
    JADOULLE Jérôme

Issue Links

duplicates

Improvement - An improvement or enhancement to an existing feature or task. MEVENIDE-1 provide user-friendly message when opening invalid poms

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Faron Dutton added a comment -

The only difference is the issue's priority.

Show
Faron Dutton added a comment - The only difference is the issue's priority.
Hide
Permalink
Sébastien Arbogast added a comment -

I've validated my POM with Oxygen XML and the following parameters :

<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v3_0_0.xsd">

But I still get the same error message when I try to open it with Mevenide POM editor. Is it normal ?

Show
Sébastien Arbogast added a comment - I've validated my POM with Oxygen XML and the following parameters : <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v3_0_0.xsd "> But I still get the same error message when I try to open it with Mevenide POM editor. Is it normal ?
Hide
Permalink
gilles dodinet added a comment -

sebastien,

although the editor opens correctly with mevenide 0.4.0 (targetting eclipse 3.1.x currently), the editor is unable to read correctly the project and all fiels remain blank, but no message. so, if you're using 0.4.0, no it's not normal (but, once again, this doesn't mean that the editor handles namespaces correctly). on another topic mevenide provides a validator which relies on a slighty modified version of the xsd, which tags id as invalid - to prevent use of this deprecated element.

Show
gilles dodinet added a comment - sebastien, although the editor opens correctly with mevenide 0.4.0 (targetting eclipse 3.1.x currently), the editor is unable to read correctly the project and all fiels remain blank, but no message. so, if you're using 0.4.0, no it's not normal (but, once again, this doesn't mean that the editor handles namespaces correctly). on another topic mevenide provides a validator which relies on a slighty modified version of the xsd, which tags id as invalid - to prevent use of this deprecated element.
Hide
Permalink
JADOULLE Jérôme added a comment -

Gilles,

I don't really understand the the conclusion of your statement. Does it mean that using mevenide v0.4.0 with eclipse 3.1 doesn't work at the time being or just that the XSD file used is an invalid one?

I have the exact same problem as the one you are talking about:
Using Eclipse 3.1 final, maven 1.0.2 and mevenide 0.4.0.

The XSD I use in my project.xml file is :
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/3.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/3.0.0 maven-v3_0_0.xsd">

and the problem occuring when validating with mevenide is :
cvc-complex-type.2.4.b: The content of element 'project' is not complete. One of '

{"":artifactId}

' is expected.

note that I have the <id>, <artifactId> and <groupId> tags defined.
Simply removing the Id tag doesn't help, i still get an empty POM Editor window...

Is this problem only due to the fact that the XSD used isn't the one working with mevenide or is it really a bug in mevenide?

Show
JADOULLE Jérôme added a comment - Gilles, I don't really understand the the conclusion of your statement. Does it mean that using mevenide v0.4.0 with eclipse 3.1 doesn't work at the time being or just that the XSD file used is an invalid one? I have the exact same problem as the one you are talking about: Using Eclipse 3.1 final, maven 1.0.2 and mevenide 0.4.0. The XSD I use in my project.xml file is : <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/3.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/3.0.0 maven-v3_0_0.xsd"> and the problem occuring when validating with mevenide is : cvc-complex-type.2.4.b: The content of element 'project' is not complete. One of ' {"":artifactId} ' is expected. note that I have the <id>, <artifactId> and <groupId> tags defined. Simply removing the Id tag doesn't help, i still get an empty POM Editor window... Is this problem only due to the fact that the XSD used isn't the one working with mevenide or is it really a bug in mevenide?
Hide
Permalink
JADOULLE Jérôme added a comment -

Project.xml file used.
It is validated by XMLBuddy (with maven-v3_0_0.xsd schema) but produces the error i am talking about when validating it with mevenide 0.4.0 pomEditor. The Editor doesn't crash but cannot read the project.xml file (=> prints all empty fields).

Show
JADOULLE Jérôme added a comment - Project.xml file used. It is validated by XMLBuddy (with maven-v3_0_0.xsd schema) but produces the error i am talking about when validating it with mevenide 0.4.0 pomEditor. The Editor doesn't crash but cannot read the project.xml file (=> prints all empty fields).

People

  • Assignee:
    Jeffrey Bonevich
    Reporter:
    Barrie Treloar
Vote (0)
Watch (1)

Dates

  • Created:
    Updated: