Include DescriptorFields (method parameter metadata), indirection to support dynamic resolution (EJBs) #1
Conversation
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
…should be able to name parameters with this.
…oke JMX operations upon. Long term, it would make sense to use the BeanUtils bits to find the getter / setters, and would make sense to add extension points to inspect other class-level annotations while making decisions about Attribute / Method accessiblility.
|
German Escobar » jmx-annotations #10 SUCCESS |
Author
|
Any change this will get accepted? |
Author
|
One last try before I give up. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Greetings!
I'd like to submit my changes upstream. I'm about to publish a cdi extension which can publish cdi and jee beans as MBeans in another repo and figured it would be worth pushing this upstream.
The layer of indirection was added so that alternative implementations can resolve delegates from proxy info (say, JNDI lookups in the case of EJBs) and done in a manner that shouldn't harm the operation of the core library.
Regards,
-Bryan