DO NOT REPLY [Bug 41660] - Fields in Annotations and AnnotationEntry are private, should be protected

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41660>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41660





------- Additional Comments From [email protected]  2007-03-10 11:56 -------
I need to extend them in order to tell BCEL how to process non-standard annotations. Currently BCEL is 
hard-coded for the existing annotation names: RuntimeInvisibleAnnotations, 
RuntimeInvisibleAnnotations, RuntimeInvisibleParameterAnnotations, and 
RuntimeVisibleParameterAnnotations. However, with the JSR-308 proposal, new annotation names are 
likely on the way: RuntimeInvisibleTypeAnnotations/RuntimeVisibleTypeAnnotations and (possibly) 
RuntimeInvisibleStatementAnnotations/RuntimeVisibleStatementAnnotations.

Now, I'd like to use BCEL to parse and display these new annotation types. In fact, I've already written 
such a utility here:

http://volta.svn.sourceforge.net/viewvc/volta/util/dump-annotations/

However, the utility can't work with the current BCEL trunk because the Annotations and AnnotationEntry 
classes have private inaccessible fields. This makes extending those classes in any meaningful way 
impossible. But if I simply modify BCEL so that those fields are exposed to subclasses, then my utility 
works perfectly.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.