[android-developers] Why does Binder onTransact throw a RemoteException?

I was doing some remote service code using AIDL and saw that my auto-generated implementations of the Stub functions throw a RemoteException. I traced it back through the generated AIDL code into android.os.Binder.java execTransact where the exception gets parcelled into the reply, which looks fine, except that android_util_Binder.cpp takes that exception, logs it to LogCat, and continues as if everything is ok.

What is the point of the RemoteException if a RuntimeException has the same effect? Is it so that one day RemoteExceptions can get passed IPC (the log line hints that this is not implemented yet)? or will that probably never happen.

Thanks, Maurits

--
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en