"jaikiran" wrote : 1) One of the possible reasons, that i can think of, why the bean developer would want to do this is to provide a different transport to use. Is there any other valid reason why the developer would want to do this? The most pressing reason is the transport. I'm sure app developers could come up with a reason for many equivalent bindings - maybe they're migrating to a new JNDI name scheme and want to keep the old for backwards-compatibility? "jaikiran" wrote : 2) Does this multiple bindings apply on to Remote business interfaces? Is there any specific reason why the same reasoning can't be used to have something like @LocalBindings? Yes, I'm in favor of adding N Local Bindings support. What's interesting is that there's no backing metadata model (ie. LocalBindingMetaData) for this. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176872#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...