Tom, Thanks for your reply. In the end it boils down to the age old question: what is first chicken or the egg? Process importing components or components importing process. Let's take the approach of process importing components - chicken first. Given the current process fragment: I could change it to: ----------- import ..\sca\ConsumerFacade.composite ... <action sca-component-reference="RequestParser"/> ----------- And done! Isn't this a cleaner separation of process and assmbly responsibility? With a bit more work to integrate an sca tuscany runtime and jpdl runtime - there is so much to gain! JPDL can tap into any (almost any - sca component types are constantly growing ...) type of components defined in sca. The component impls would also implement ActionHandler - easy right? The SCA api is straight forward: // line below can be triggered by the above // "import ..\sca\ConsumerFacade.composite" statment scaDomain = SCADomain.newInstance("ConsumerFacade.composite"); // line below is triggered when you need the action to be executed requestParserService = scaDomain.getService(RequestParserImpl.class, "RequstParserComponent"); So what is left? 1. Change jpdl schema to allow: <action sca-component-reference="RequestParser"/> 2. Make some room in jpdl api to allow references to scaDomain.getService(...) calls. I would be glad to contribute some time to the above. Regards, Radu Marian View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149814#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...