Validation of XPlan writer erroneously throws warnings on missing objects #890
Labels
Comments
|
@JohannaOtt Do you have the example file(s) used in the issue description? |
|
I can currently not re-produce the issue. Currently waiting for confirmation if it can be closed. |
|
It is re-producible, checked the wrong logs. |
|
This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in two weeks if no further activity occurs. Thank you for your contributions. |
emanuelaepure10
added a commit
to emanuelaepure10/hale
that referenced
this issue
Jul 11, 2024
stempler
pushed a commit
to emanuelaepure10/hale
that referenced
this issue
Jul 11, 2024
stempler
pushed a commit
to emanuelaepure10/hale
that referenced
this issue
Jul 11, 2024
we-release bot
pushed a commit
that referenced
this issue
Aug 7, 2024
## [5.3.0](v5.2.1...v5.3.0) (2024-08-07) ### Features * support loading Shapefiles for XML schemas ([0f64ad3](0f64ad3)) * support loading single Shapefile from folder ([eb83a2f](eb83a2f)) ### Bug Fixes * avoid arbitrary file access during archive extraction ("Zip Slip") ([5c82a4b](5c82a4b)) * **deps:** update dependency to.wetransform.offlineresources.feature to v2024.7.31.bnd-fohraq ([5f8fbd7](5f8fbd7)) * replace broken or risky cryptographic algorithm ([9903a9f](9903a9f)) * Xplan validation erroneously throws warning on missing objects ([23bcc04](23bcc04)), closes [#890](#890)
|
🎉 This issue has been resolved in version 5.3.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version 4.1.0.SNAPSHOT
Build 763247191
Revision df620a7
When transforming several objects to XPlan and exporting them with the Xplan writer using the functionality to create separate output files for every plan element, the writer throws many warnings all following the same pattern
The warning is about objects that are referenced, but are missing. This is not true for the data - the gml files are containing both objects that are referencing each other.
The warning occurs multiple times for each of the exported plans.
The text was updated successfully, but these errors were encountered: