On 21 jul, 11:13, Dianne Hackborn <[email protected]> wrote: > There isn't enough information here to know if it is a bug in the > platform... off-hand, I would guess not, since most of the logic in > marshalling/unmarshalling such things needs to be written by the developer > and doesn't come from the platform. Plus there isn't a > Parcel.readFromParcel() method so it is even harder to tell... if this is > actually Parcel.readParcelable(), you need to make sure you are using the > class loader for -your- app, which is the one that knows about your class > loader. The system class loader only knows about the core framework > classes.
Thank you. Yes, I meant readParcelable(), sorry about that. I guess I need to pass the right classloader then. I thought that 'default' meant the classloader for my app. > > That all side, a possibly larger question is... do you need to do this at > all? If the service is not explicitly running in its own process but just > in the normal same process as the rest of the app, there is no reason to use > aidl at all. If it has been set up to run in another process, is there > really a good reason to do this instead of just using the much simpler (and > usually more efficient) approach of running locally? > It's necessary, because it is a service that communicates with a number of applications simultaneously. Also note that passing this tree is not something that needs to be done a lot of times, usually just once for an application, so it's not really an issue if it's an expensive operation. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
