Philip Helger

@tjeb thanks for the swift response. I had created copies of the previous spec versions - you can find them at https://github.com/phax/ph-schematron/tree/master/docs The interesting link in the source issue points...

Sorry I found no time yet, to properly respond to this, but I want to. My assumption is, that this is exactly the "magic" in the boilerplate code, the XSLT...

Is it possible, that you eventually changed the configuration when updating the version? Or are you using non-standard document type identifiers inside of your SMP?

Okay, with version 7.1.2 In introduced the identifier type `peppol-lax` (see #275). There was an additional fix for that in v7.1.3. So can you please update to the latest version...

@tiagojmmartins can you please give me a short update, if changing to `peppol-lax` helped? Thanks

@jjtilly Sorry, that improvement was basically only for the SQL version. Please create a new issue for that - thanks Edit: Just did it: #333

@skizup lets take this separately. Can you please show me the "cause" of the SQLException you shown in the logs? Seems some DB specific problem...

@skizub In your original post you added this image:  I would need to know the further details of the stack trace in that image (the "caused by..." stuff). Can...

The problem is, that the creation of the Service Group in the SML did not work. Please make sure you selected the correct "SML" in the "SMP Settings". Should be...

Well yes it works now, but also means: Your participants don't end up in the SML and therefore they are not disoverable by other Peppol participants. Are you using Peppol...