Thanks a lot for that input. But, there has to be a solution for it. Otherwise, its not correct to call Android open source if they do not allow me to add my own classes by extending the existing ones.
As far as I know, there is no such behaviour in normal Java Applications when run on a Sun JVM. Is this a special behaviour exhibited by Dalvik VM. What is the possible workaround for this problem. On Oct 27, 1:48 am, fadden <fad...@android.com> wrote: > On Oct 25, 11:16 pm, Raman <raman86...@gmail.com> wrote: > > > I am trying to extend a class in android.widget, specifically > > AbsSpinner class for some change in behaviour. For that I need to > > access some protected members of the Classes up in the hierarchy, so I > > decided to put my new class in the same package android.widget > > It compiles fine in Eclipse but when I run it, it gives me > > java.lang.VerifyError. > > You can view the failure details with "adb logcat". > > You cannot access protected members in this way, because your class is > being loaded by a different class loader. The package has the same > name, so the compiler is happy, but at runtime it's not considered to > be part of the same package. > > In a future release of the VM this will cause an IllegalAccessError at > runtime rather than a VerifyError at startup. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
