[XMLBEANS-628] XMLBeans compiler plugin not stateless between subsequent build steps

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Version 5.1.0
• Component/s: Compiler
• Assignee: Unassigned
• Reporter: Johannes
• Created: 07/Sep/22 14:20
• Updated: 07/Sep/22 14:56

Description

I have a multi-module maven build generating and compiling XMLBeans bindings for multiple XML schemas (using the compile goal).

When I execute just a single build out of them, the result is correct and executable.

But when executing them subsequent in the same maven build (and thus the same Java VM session), the subsequent builds are affected by the first one and the schema bindings (xsb files) are written to the wrong package - leading to a LinkageError reported at runtime.

Output of the first JAR (compiling ebics_hev.xsd from here):

Package org/ebics/h000 contains the sub packages attributegroup,, element, ... system, type

Output of the second JAR (compiling H005 schemas from the same source):

Package org/ebics/h005 contains interfaces and an impl sub package.

There is another package org/ebics/h000 containing the attributegroup, element, ... system, type

 

At runtime this leads to:

Caused by: java.lang.LinkageError: Loading of resource {urn:org:ebics:H005}ebicsKeyManagementResponse.ebicskeymanagementresponse2269doctypefailed, information from {urn:org:ebics:H005}ebicsKeyManagementResponse.index.xsb is  out of sync (or conflicting index files found)
    at org.apache.xmlbeans.impl.schema.XsbReader.checkContainerNotNull(XsbReader.java:654)
    at org.apache.xmlbeans.impl.schema.XsbReader.finishLoadingType(XsbReader.java:1038)
    at org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.resolveHandle(SchemaTypeSystemImpl.java:938)
    at org.apache.xmlbeans.impl.schema.ElementFactory.<init>(ElementFactory.java:29)
    at org.apache.xmlbeans.impl.schema.AbstractDocumentFactory.<init>(AbstractDocumentFactory.java:33)
    at org.apache.xmlbeans.impl.schema.DocumentFactory.<init>(DocumentFactory.java:23)
    at org.ebics.h004.EbicsKeyManagementResponseDocument.<clinit>(EbicsKeyManagementResponseDocument.java:23)

 

Since this happens only when building these schemas in the same maven build, the reason must be some state in the XMLBeans plugin.