Validierung mehrer XRechnungs-Versionen fehlerhaft

[quotschmacher]

Für ein Projekt muss ich verschiedene XRechnungs-Versionen validieren können. Dazu habe ich einen Docker-Container, der sich mehrere Szenarien runterlädt und den Validator im Daemon-Mode startet. Dabei habe ich ein sehr komisches Verhalten beobachtet. Insgesamt mit 4 Testrechnungen mit den Versionen 2.1, 3.0, 2.2 und 1.1

Fall 1

Ich starte den Validator mit folgendem Befehl

CMD ["java", "-jar", "validationtool-1.5.0-java8-standalone.jar", \
  "-s", "V302=/validator/scenario1/scenarios.xml", "-r", "V302=/validator/scenario1", \
  "-s", "V231=/validator/scenario2/scenarios.xml", "-r", "V231=/validator/scenario2", \
  "-s", "V220=/validator/scenario3/scenarios.xml", "-r", "V220=/validator/scenario3", \
  "-s", "V211=/validator/scenario4/scenarios.xml", "-r", "V211=/validator/scenario4", \
  "-s", "V201=/validator/scenario5/scenarios.xml", "-r", "V201=/validator/scenario5", \
  "-D", "-P", "8080", "-H", "0.0.0.0"]

Ich gehe davon aus, dass die Versionen der XRechnungs-Szenarien aus den Namen abzuleiten sind. Geladen werden die Szenarien in folgender Reihenfolge:

1. 3.0.2
2. 2.0.1
3. 2.1.1
4. 2.2.0
5. 2.3.1

Damit erhalte ich dann folgende Ergebnisse:

• 2.1
• 3.0
• 2.2
• 1.1

Das die Rechnung in der Version 1.1 auf kein Szenario passt, ist in diesem Fall ja klar.

Fall 2

Kommando zum Start:

CMD ["java", "-jar", "validationtool-1.5.0-java8-standalone.jar", \
  "-s", "V302=/validator/scenario1/scenarios.xml", "-r", "V302=/validator/scenario1", \
  "-s", "V231=/validator/scenario2/scenarios.xml", "-r", "V231=/validator/scenario2", \
  "-s", "V220=/validator/scenario3/scenarios.xml", "-r", "V220=/validator/scenario3", \
  "-s", "V211=/validator/scenario4/scenarios.xml", "-r", "V211=/validator/scenario4", \
  "-s", "V201=/validator/scenario5/scenarios.xml", "-r", "V201=/validator/scenario5", \
  "-s", "V110=/validator/scenario6/scenarios.xml", "-r", "V110=/validator/scenario6", \
  "-D", "-P", "8080", "-H", "0.0.0.0"]

Reihenfolge, in der die Szenarien geladen werden:

1. 3.0.2
2. 2.0.1
3. 2.1.1
4. 1.1
5. 2.2.0
6. 2.3.1

Ergebnisse der Validierung:

• 2.1
• 3.0
• 2.2
• 1.1

Zum Einen finde ich die Reihenfolge des Ladens komisch, zum anderen kann ich nicht verstehen, das im zweiten Fall auf einmal alle Rechnungen, die im ersten Fall noch akzeptiert wurden, dann abgelehnt werden mit der Meldung:

[quotschmacher]

Es sieht so aus, als hätte das auch was mit der #122 zu tun...

[davewwww]

i run into the same problem and can therefore neither use the validator nor validate it in a legally secure manner.

"Es wird empfohlen das Dokument zurückzuweisen. Da kein Pruefszenario gegriffen hat"

any suggestions on how to solve this?

[msccip]

One scenarios.xml including all the versions you want to validate.

[quotschmacher]

@msccip When combining multiple files into one, what should I consider? Anything I need to be careful about?

[msccip]

@quotschmacher
You must use the entries from the respective scenarios.xml of the different releases. Do not copy and adapt the entries from the current scenario. And you should modify the descriptions accordingly to distinguish between the versions on the validation logs:

<!-- XRechnung Standard (CIUS) UBL Invoice 3.0 -->
<scenario>
<name>EN16931 XRechnung (UBL Invoice) 3.0</name>

etc.
Otherwise, there's imho nothing else to consider. Once you've created the foundation, the effort for future releases is manageable.

[quotschmacher]

@msccip thanks. what about the resources folder? combine all of them and when two files with the same name are present use the newest one? or adjust path in the <scenario>-section?

[msccip]

@quotschmacher
I don't understand your question. For every version there is a seperate resource-directory. Where is the problem ? You have nothing to adjust if you follow the procedure described above.

[quotschmacher]

@msccip
i mean for example this one:

    <validateWithXmlSchema>
      <resource>
        <name>XML Schema for UN/CEFACT XML (SCRDM - CII
                    uncoupled)</name>
        <location>resources/cii/16b/xsd/CrossIndustryInvoice_100pD16B.xsd</location>
      </resource>
    </validateWithXmlSchema>

does this file change over the releases of different (newer) scenarios?

with scenarios like this

    <validateWithXmlSchema>
      <resource>
        <name>XML Schema for UBL 2.1 CreditNote</name>
        <location>resources/ubl/2.1/xsd/maindoc/UBL-CreditNote-2.1.xsd</location>
      </resource>
    </validateWithXmlSchema>

i do not see any problems.

[msccip]

@quotschmacher
they may have changed in newer versions, but then they are located in other directories: cii/22b or ubl/2.2. However, these are not yet used by xrechnung. So to date there have been no changes.

[karladler]

Merging all scenarios into one scenario.xml file requires the resources to be merged as well.
Since some of the paths are the same, but the file contents are not, it feels more than wrong, just to use the same base folder here. I wrote a script updating the resource paths in xml and putting the files in separate folders. IMHO this is how it should work out of the box.

[msccip]

@karladler
which files do you mean ? I have been using this procedure for years and have never had a problem.

[quotschmacher]

@msccip i wrote a small .net programm that is combining the scenarios to one file. this works so far - but if there are too many scenarios (33 in my case) i get the following error: Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
did you experience this, too or shall i write another ticket and close this one?

[msccip]

@quotschmacher
I currently have "only" 26 scenarios, but I had the same problem. It works for me with this setting: java -Xmx1024M -Xms512M ...

[phax]

We acknowledge the issue but we also see it as a duplicate of #122. Further commenting will be done in #122