The @LocalBinding annotation is for the default business interface proxy of the bean (which will implement all the local business interfaces). If you want to lookup interface specific proxy, we already bind those to the JNDI with the following syntax:
You will be able to see these JNDI names on the console.
Thank you for your response. However, if you look in my original post, I explained that:
"As part of the migration from 2.1 to 3.0, I am using the @LocalBinding annotation to ensure that the JNDI names of the migrated and un-migrated session beans stay consistent."This means that I do not want to use the default JBoss JNDI bindings, because they follow a different pattern than those of our 2.1 beans. My question is whether I can define different bindings for the different interfaces that a bean implements. It's looking like the answer is "no", since you cannot have more than one @LocalBinding annotation.