-
-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parseexception with ancestors fix #365
Merged
stevespringett
merged 3 commits into
CycloneDX:master
from
dmeibusch:parseexception_with_ancestors_fix
May 14, 2024
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
<?xml version="1.0" encoding="UTF-8"?> | ||
<bom xmlns="http://cyclonedx.org/schema/bom/1.2" | ||
serialNumber="urn:uuid:3e671687-395b-41f5-a30f-a58921a69b79" | ||
version="1"> | ||
<metadata> | ||
<component type="library"> | ||
<group>com.acme</group> | ||
<name>sample-library</name> | ||
<version>1.0.0</version> | ||
<pedigree> | ||
<ancestors> | ||
<component type="library"> | ||
<group>org.example</group> | ||
<name>sample-library-ancestor-1</name> | ||
<version>1.0.0</version> | ||
</component> | ||
<component type="library"> | ||
<group>org.example</group> | ||
<name>sample-library-ancestor-2</name> | ||
<version>1.0.0</version> | ||
</component> | ||
</ancestors> | ||
<descendants> | ||
<component type="library"> | ||
<group>org.example</group> | ||
<name>sample-library-descendant</name> | ||
<version>1.0.1</version> | ||
</component> | ||
</descendants> | ||
<variants> | ||
</variants> | ||
</pedigree> | ||
</component> | ||
</metadata> | ||
</bom> |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I can determine, the issue arises due to
MetadataDeserializer
using the shortcut of reading the tree from the XML (this is only an XML issue) token stream, then using a unconfiguredObjectMapper
to convert to the target types. The context is then lost (e.g. XML parser, XML deserialization context) within child deserializers and we enter this deserializer re-parsed then tree now as plain JSON tokens with a vanilla JSON parser.This list of components (when nested in metadata/../ancestors etc) might be absent (no tokens), a single object, or an array of objects. Fix here is to explicitly handle these cases.
Not 100% happy - still a hack on top of the existing hack to handle component object lists. 🤷