On Oct 26, 9:10 pm, Raman <[email protected]> wrote: > 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.
What I'm saying is that changing the package name will not help or hinder; it simply makes no difference. You're not in the same package, so anything that requires package-scope access will continue to not work. This behavior is correct according to the specification. Classes can access "protected" members of the superclass, but not private or default (package) scope. What field/member is specifically failing? (If you get the output from "adb logcat" above the VerifyError it will tell you exactly what's failing.) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
