Hi, everyone! I have an use case that can have specific behavior depending on the client where the application is deployed. To add such a caracteristic to the code, without having to change it based on each client, I've made pageflow definition and business process definition "scripts", therefore leaving the views involved in the use case much cleaner. To change use case behavior for a certain client, all I have to do is deploy a different process/pageflow definition for him, and the interface behaves according to his needs. Nice. But what I fail to accomplish now is the same level of abstraction for components. I would like to create, if possible of course, an interface as a component. And use this to control the tasks of my business process. Depending on the implementation of such interface that is deployed, actions would behave differently. I'm struggling to accomplish this using drools. My architecture is composed of a .EAR file containing ejb-common and web-common projects, for all common artifacts shared between clients. I would like to add new modules representing custom (or specific) interfaces for each client. So, I came here for suggestions. Do you guys know of any pitfalls of what I'm trying to achieve? (if that's possible at all...) Thanks in advance! Rodrigo View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112221#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...