StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PObindService from other app but same userid/process
primarykey
Id
6630775
data
AcceptedAnswerId
6699022
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-07-08T21:34:46.583
FavoriteCount
2
LastActivityDate
2018-03-30T16:21:54.510
LastEditDate
2018-03-30T16:21:54.510
LastEditorUserId
3290339
OwnerUserId
476884
ParentId
0
PostTypeId
1
Score
1
ViewCount
1642
LastEditorDisplayName
text
Body
This is about memory-based IPC (like to <a href="http://developer.android.com/guide/topics/fundamentals/bound-services.html#Binder" rel="nofollow">LocalService</a> example) but for two apps running in the same process: I have two apps (<code>App1</code>, <code>App2</code>) and a shared project (<code>Shared</code>) which defines some interfaces and abstract classes for both apps: <pre><code>Shared (regular Java project, references android.jar) - abstract myAbstractService - Binder myBinder App1 (Android Project, references Shared) - MainActivity App2 (Android Project, references Shared) - myService extends myAbstractService </code></pre> Both apps run within the same process (<code>my.process</code>, defined in <code><application></code>), <code>App2</code> publishes <code>com.www.app2.myService</code>: <pre><code><-- Both Apps run in the same process --> <manifest  android:sharedUserId="my.shareduser">  <application  android:process="my.process"> <-- App2 exports the service --> <service android:name="com.www.app2.myService" android:exported="true"> <intent-filter> <action android:name="com.www.app2.myService" /> </intent-filter> </service> </code></pre> This is the abstract <code>myAbstractService</code> (<code>myService</code> doesn't add anything new yet): <pre><code>abstract public class GameClient extends Service { private static final String LOGTAG = "GameClient"; private myBinder binder = new myBinder(); public IBinder onBind(Intent intent) { Log.d(LOGTAG, "onBind()"); return this.binder; } public class myBinder extends Binder { public void sendMessage() { Log.d(LOGTAG, "sendMessage()"); } } } </code></pre> When I try to bind to <code>myService</code> (App2) from my <code>MainActivity</code> (App1): <pre><code>public void onServiceConnected(ComponentName name, IBinder service) { Log.d("MS", service.getClass().toString()); main.this.t = (myBinder) service; // Exception in this line of course } </code></pre> I get an exception: <blockquote> DEBUG/MS(5464): class com.www.shared.myBinder ERROR/AndroidRuntime(5464): java.lang.ClassCastException: com.www.shared.myBinder </blockquote> As both apps run in the same process, memory-coupled communication should work (at least I thought). I really don't want to use the message-based or broadcast-based communication as I'll send quite some messages around. I suspect this exception happens due two different classloaders being used for the same class? Is this approach simply not possible/wrong or am I missing something? Update: My aim is to write a very modular application, where App1 is used as a delegating and starting application of other modules (apps). As I don't want to ship <code>App1</code> with every app depending on it, I made it it's own app. Let's say I have a third app (App3, Android project). App2 & App3 are both started by App1 (responsible for setting up connections while App2 & App3 provide different application logic (but having the same interface). On a second thought I think this could be solved with an android library as well (App1 & Shared merged as the library with <code>App2</code> and <code>App3</code> starting an Activity of this library and waiting for the result)? However the data is not parcelable (network connections) and I have no idea how this library could be distributed independently over the android market (like <code>App2</code> and <code>App3</code> are published there but ask for the library to be installed too). Would this resolve that problem at all?
Tags
<android><android-service><ipc><android-binder>
Title
bindService from other app but same userid/process
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USFge
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.