the fundamental question is in fact a question of granularity my application (as many do prob) exists out of a collection of 'modules' (jars), a group of classes that together offer a more or less independent service. i could put alle the modules (jars) inside one big ear and avoid inter ear communication but that reduces (hot) redeployment options and has a negative impact on my development cycle. ideally i would have OSGi like possibilities to load jars dynamically and control very specifically which interfaces they expose to the outside world i have been wondering about the role of JMX. however, at this time there is not yet a link between JMX services and/or SEAM components and/or SF or SL session beans. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081130#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...