There are two problems in the design itself: 1. The transport should be independent of the jndi binding. So depending on which transport I use to connect to jndi (for example https) I should get another client binding. This is an AS issue. 2. The relationship between remote business interfaces and remote bindings is as of yet not properly specified. Let's focus on number 2, because #1 takes more than a simple fix. The goal is to give the bean developer the ability to specify a client bind url per remote business interface. Now in your example you have 2 bindings and 1 interface. In my mind clientBindUrl is an attribute of the remote business interface. But this doesn't allow for multiple bindings per interface. I'm open for any suggestions, but it should not lead to an API change. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166968#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...