You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Files that are written when serializing to AASX have their file path entry written with the file:// URI scheme, which breaks the ability to view the files using the AASX explorer, as it is an absolute file URI.
However, the file can't be written without the leading slash as well, because a part name has to start with a slash.
What is the exact reason, that files are converted to absolute file URIs during serialization? I can't think of any case where this would be correct in the context of an AASX, as the files are always within the archive and thus relative to the archive root (of course the AASX explorer could be changed to allow reading such URIs from the local archive root, but that sounds also not quite correct).
Files that are written when serializing to AASX have their file path entry written with the
file://
URI scheme, which breaks the ability to view the files using the AASX explorer, as it is an absolute file URI.However, the file can't be written without the leading slash as well, because a part name has to start with a slash.
What is the exact reason, that files are converted to absolute file URIs during serialization? I can't think of any case where this would be correct in the context of an AASX, as the files are always within the archive and thus relative to the archive root (of course the AASX explorer could be changed to allow reading such URIs from the local archive root, but that sounds also not quite correct).
The code that performs the conversion is located here: https://github.com/eclipse-aas4j/aas4j/blob/main/dataformat-aasx/src/main/java/org/eclipse/digitaltwin/aas4j/v3/dataformat/aasx/AASXSerializer.java#L251
If the
file://
prefix is manually removed afterwards from the XML within the archive, accessing the file works.The text was updated successfully, but these errors were encountered: