-
Notifications
You must be signed in to change notification settings - Fork 56
Add Exception Type Parsing #1031
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
Open
Pandrex247
wants to merge
2
commits into
eclipse-ee4j:master
Choose a base branch
from
Pandrex247:Add-Exception-Type-Parsing
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Shouldn't
exceptionTypesbe updated somewhere, perhaps here? Otherwise - how it gets populated?Edit: I've removed locally this method and collection+getter and the test is fine with such change. Do we need
exceptionTypesin this class?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.
I agree with @pzygielo. This code doesn't do anything right now.
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.
I will review - I was simply cherry-picking from our fork (I didn't make the original change)
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.
This is an inherited method from the
SignatureVisitorclass from ASM: SignatureVisitor#L153.There is an identical implementation of it over in the
SignatureVisitorImplclass here in HK2: SignatureVisitorImpl#L88.So I assume the original intent was to simply mirror the behaviour of the
SignatureVisitorImplclass.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.
Could be to follow established pattern, right.
What would be the role of
exceptionTypes?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.
Would need to spend some time digging into it with a debugger - it's a bit abstract for my eyes to dry-run through.
The interface method from
MethodModel(and presumablyMethodModelImpl) gets used over in Payara for MicroProfile OpenAPI processing here and here.Within HK2 itself the important changes within this PR seem to be working on the
MethodModelwithin theModelClassVisitor(here). This code is preceded by reading the method signature (which is where thisMethodSignatureVisitorImplclass comes into play), during which at least one code path seems to "visit" the exception type (which is where I start getting lost without a debugger).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.
@Pandrex247, list
exceptionTypesat L39 always stay empty because it never updated.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.
Probably we don't know.
getExceptionTypesreturns original, mutable list so this MIGHT be updated anywhere, out of control of the class.I understand
getParametersdoes the same.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.
But
parameterscollection is filled in thevisitParameterType()method at L63 of theMethodSignatureVisitorImplclass.Actual exception types processing occurs in the
ModelClassVisitorclass beginnin with L284.In this case even out of control HK2.
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.
The current solution seems to work, the test passes. I debugged it now and found out that ASM doesn't pass info about exceptions in the
signatureargument tovisitMethodofModelClassVisitor. It only passes the info in the separate argumentexceptions.As a result, the method
visitExceptionTypehere is never called. That's why it isn't enough to implement it.However, I managed to get it working by manually calling the
visitExceptionType()and thenvisitClassTypemethods on the visitor for each exception in thevisitMethodclass, right after the visitor is called by ASM signature reader. With this, things work as they should and the code is in line with the existing code, just with some help to the ASMSignatureReader, which doesn't find info about exceptions in the signature.Here's are the changes: https://github.com/Pandrex247/glassfish-hk2/compare/Add-Exception-Type-Parsing...OndroMih:glassfish-hk2:ondromih-Add-Exception-Type-Parsing?expand=1
If it's OK like this, we can accept this PR and then I'll raise another PR with my improvements.