Hi John,
John D. Ament wrote:
> Hi Marina,
>
> So I just want to confirm then. Is it your belief that the portable
> JNDI locations should be used for both local and remote lookups, based
> on the current spec (EJB 3.1)?
I'm 100% sure the portable JNDI names are defined for both, remote and
local views. See e.g. the example under "4.4.2.2 Session bean exposing
multiple client views".
Best,
-marina
>
> Thanks,
>
> John
>
>
> On Wed, Nov 21, 2012 at 5:06 PM, Marina Vatkina
> <marina.vatkina_at_oracle.com <mailto:marina.vatkina_at_oracle.com>> wrote:
>
> John,
>
> The standard JNDI names are the same for remote and local
> invocations. If you are asking about names that include host and
> port of the target server, it's probably a no-go as the interop
> (and even remote client) are targeted for becoming optional in the
> future Java EE version(s).
>
> Best,
> -marina
>
>
> John D. Ament wrote:
>
> Experts,
>
> A question was raised recently regarding Remote JNDI
> locations. Currently, the specs define standardized local
> JNDI names. There is no guarantee that the remote names would
> be the same. Is it possible to come up with standardized
> naming conventions for remote EJBs (session beans) that can be
> looked up in a consistent manner across application servers?
>
> Thanks,
>
> John
>
>