This content has been marked as final. Show 2 replies
The JNDI Name for this bean is non-deterministic, as there's nothing to signal a true default.
Any specific reason why we need to know the "default" jndiname? Aren't we going to treat all jndi names equally?
Any specific reason why we need to know the "default" jndiname?
Turns out: I don't think so. I ran into this while going through out @RemoteBinding handling to ensure all the bindings were made, and thought this might turn into a hitch of some type.
Aren't we going to treat all jndi names equally?
Not all. :)
That example makes for two bindings for the "Default Remote Business Interface using the default interceptor stack and remoting to the default Connector". So it turns out we can pick either for the "Default JNDI Name".
But some explicit @RemoteBindings will have different properties.
Further, there's the interface-specific bindings which may be invoked upon to get SessionContext.getInvokedBusinessInterface(). The intention is not to look these up directly, but they're the injection targets for the ENC of each component.