unfortunately using the complete path didn't make any difference at all :( Reflection, afaik, are handy if some method's/api's are missing and thus you can fall back on another implementation.. But I'm afraid in my case it would always fall back to the other implementation, thus never using my Logger class :( After all, I can check if it recognizes my class, but if it simply doesn't then I actually wouldn't have any use in calling an alternative or whatever...
On 22 jun, 16:43, Gyan <gnanesh....@gmail.com> wrote: > Try giving the entire context path all the time. > > myprojects.android.loggingModule.Logger.Log() > > Or try using reflections API built in Android!! > > Gyan -- 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
