Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid content was found starting with element 'comments' #3527

Closed
volodya-lombrozo opened this issue Nov 21, 2024 · 3 comments
Closed

Invalid content was found starting with element 'comments' #3527

volodya-lombrozo opened this issue Nov 21, 2024 · 3 comments

Comments

@volodya-lombrozo
Copy link
Member

volodya-lombrozo commented Nov 21, 2024

I'm trying to update eo-parser library in the jeo-maven-plugin to 0.42.0 version and got the following exception:

Invalid content was found starting with element 'comments'  

For the XMIR (excerpt):

<program>
   ....
   <objects>
   ....
   </objects>
   <comments>
      <comment line="4">This is the default 64+ symbols comment in front of named abstract object.</comment>
      <comment line="26">This is the default 64+ symbols comment in front of named abstract object.</comment>
      <comment line="44">This is the default 64+ symbols comment in front of named abstract object.</comment>
   </comments>
</program>

This XMIR was received after the following modifications:

  1. Disassemble Java bytecode to XMIR
  2. Translate XMIR to PHI
  3. Translate PHI back to XMIR ( unphi)
  4. Then I get this XMIR, convert it to EO new Xmir.Default(this.canonical).toEO(), then parse it again new EoSyntax(this.name, new InputOf(eoprog)).parsed();

And on the (4) step I get the exception, I showed above.
Expected behaviour: when we transform XMIR to EO and back it shouldn't produce errors.

@volodya-lombrozo
Copy link
Member Author

@yegor256 @maxonfjvipon Take a look, please. It's a blocker.

@yegor256
Copy link
Member

@volodya-lombrozo probably you used an old version of XSD. Are you sure you don't have your own copy of it and uses just eo-parser package with the XSD inside?

@volodya-lombrozo
Copy link
Member Author

@yegor256 It seems to have helped. Thank you! I had a duplicate of XMIR.xsd in my resources, and removing it solved the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants