anonymous wrote : I thought it would be a too tight dependency between the SFSB. For instance, if you inject SFSB A into SFSB B and SFSB C and change some business logic in A maybe B or C are broken because they use some methods of A. If you look at service oriented architectures (like SOA) - that's the way your software components work together. In seam, you inject the components to each other and in a SOA architecture you have some more intelligent components like the ESB which routes the service calls to the right component (maybe version of a component's interface). But if you break/modify a service, the others have to know that. The same as in the old days of CORBA :-) Regards, Cyrill View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121624#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...