IParser and Resource.id

[Quentin Li]

Hi,

I have got document bundles where URN-encoded UUIDs are used in entry.fullUrl. Resources themselves may or may not have a logical ID.
When I parse the documents with the IParser, it messes logical IDs. If the resource did not have a logical ID, by default, the parser assigns the UUID, and if I disable overrideResourceIdWithBundleEntryFullUrl, the ID is set to null. If the resource had a logical ID, the parser still overrides it with the UUID by default, and with 'resourceType/logicalId' if I disable overrideResourceIdWithBundleEntryFullUrl.

The issue is that all these IDs are invalid (except for null), they do not conform to [A-Za-z0-9\-\.]{1,64}. When I want to validate the resource with a ValidationEngine, it fails. Note that passing an InputStream instead of a Resource to the ValidationEngine works as expected.

Is it possible to validate these documents with the resource instead of the stream?
How should the parser be configured?
And why is the parser generating non-compliant IDsos?

Thank you!

Kind regards,

Quentin