DO NOT REPLY [Bug 28121] - Extension doesn't work on inner classes

[bu...@apache.org]

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=28121>.
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=28121

Extension doesn't work on inner classes





------- Additional Comments From keshlam@us.ibm.com  2004-04-01 14:05 -------
In 99.9995% of the coding cases, inner classes Should Not be explicitly
referenced. If their author wanted them to be invoked directly, they wouldn't be
Inner (or, at the very least, would implement an externally public interface and
would be manipulated through that). The fact that they just happen to be given
names such as Outerclass$Innerclass is just an artifact of Java's implementation
and wasn't intended to be a promise that they could be accessed directly.

So I'm inclined to declare this a Known Restriction and document it, rather than
attempting to "fix" it. The few people who really need to achieve it can work
around it by writing an actual extension class which passes requests through to
the inner class; that keeps this questionable coding practice in *their* code
rather than in ours.