JNDI Registry Service
6.20 |
7.0 |
Objects are replicated using the DBMS Service. Local objects are created using the “+/…” concept. By default, the objects are global. |
Objects are replicated using messaging. By default, the objects are local. There is no special concept for local/global objects. |
Solution: |
|
For global bindings, use InitialReplicatingContextFactoryImpl instead of InitialContextFactoryImpl or set ("Replicate", "true") in the environment (properties) when you construct initial contexts. |
|
Change reason: |
|
Using special syntax is not convenient; the local binding is default for performance reasons. |
|
6.20 |
7.0 |
You can look up from the root ignoring the “domain = true” property in the initial context environment. Therefore, looking up enterprise beans, works without using java:comp/env/… in front (as the names bound in the root are the same as the references in the application’s context). |
The structure was changed. Lookup from the root by applications is not possible. |
Solution: |
|
Remove the hard-coded lookups for objects in the root. Create references to the application’s context. |
|
Change reason: |
|
Unexpected behavior when implicitly trying to look up from the root. |
|
See also:
Naming System
(in the Administration Manual)
Naming (JNDI)
(in the Development Manual)