I've been thinking a bit more on the subject and I think I'm almost there. To add metadata at client side I would also need a new client-side aspect right? It isn't mentioned in the original response, only that ThreadMetaData can be used, but I don't see any way to use it other than with a new client-side aspect, in addition to the mergemetadata interceptor. Looking at the code of InvokeRemoteInterceptor it seems there isn't really a problem in sending over references of objects from client to server and vice versa, through the use of metadata (I think if I use the AS_IS type only the unaltered reference gets sent which is sufficient, as the client's only job is to safeguard, not use it). So my new service could create a dispatcher on the server on the first invocation, which holds which target we need for the invocation. The server-side aspect can pass its reference to the client through the invocationresponse. The client can then include that reference with every invocation, the serveraspect asks that reference for the target and changes it in the invocation.. If this is all correct (confirmation?), it leaves me with this: 1) Where do i deploy my new developed aspects? 2) Is there an eclipse configuration that recognises @service etc? 3) Is there an alternative to deploying each beanimplementation in a seperate container? Thanks for listening View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4019286#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...