The current implementation treats @RemoteBinding as an additional binding to the defaults.
This makes for a situation that may present collisions.
Given:
@Stateless(name="MyBean")
| @Remote(MyRemote.class)
| @RemoteBinding(jndiBinding="MyBean")
| class MyBean{...}
Right now this would produce:
/MyBean - Explicit from @RemoteBinding
| /MyBean/remote - Default Remote Business Interface Proxy Binding
...this makes for a CCE when attempting a Context.bind() on the 2nd entry because
"MyBean" would not be a subcontext.
So I'm going to make a rule that says:
"If at least one @RemoteBinding is specified, then the default remote business
interface binding will not be applied."
Anyone see problems w/ this approach?
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184366#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...