simon wrote: > But as i mentioned, i would like to call the instance of MY > ContentProvider as i want to call methods that are included in MY > ContentProvider and not in the Interface.
Don't put those methods on the ContentProvider. Put them in a service, or in the activity. If they are simple utility methods, put them in some separate public Java class in your project and use them wherever you need to. Bear in mind that the ContentProvider system, as far as I know, is meant to work across process boundaries. That's why you get an IContentProvider back when you call getProvider() on the ContentResolver. That's the IPC interface (IPC=inter-process communication) to the actual ContentProvider implementation. It'd be nice if a content provider could offer a separate IPC interface beyond IContentProvider, just like a regular service can, but it's not obvious how one would do that, at least with the current SDK. -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training on the Ranch in September! http://www.bignerdranch.com --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
