There is two issues that need to be addressed by the API: a) EJB MetaData access b) Invocation handling Back at JBW, we talked about solving the later by going through the MC bus: http://labs.jboss.com/file-access/default/members/jbossmc/freezone/docs/2... Andrew, can you confirm that an indirect MC invocation is equivalent to an invocation through the EJB container? The meta data piece is a deployment issue. WS requires access to the EJB meta data down to session and mdb meta data details. One idea was to use something similiar to Container.resolveAnnotation(...), however I see that this part has been deprecated. What's the replacement for it? I havn't spent much time on these issues lately, so any comments and ideas are welcome. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132748#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...