Olaf Heimburger's Blog

The second comment on my previous post provoked an answer.

In OC4J you have the ability to use a number of different JNDI context factories. Each of them helps to create an InitialContext and comes with different functionalities.

The most commonly used context factories are:

• internal context factory - you get this one by simply calling the default constructor of InitialContext and don't have an jndi.properties in your class path and are within the OC4J container.
• RMIInitialContextFactory - This one is commonly used to connect to the OC4J container. It ignores every configuration and also doesn't need the "java:comp/env/" prefix. (Here the second comment is true.)
  
• ApplicationClientInitialContextFactory - This context factory takes care of your JNDI environment (esp. in META-INF/application-client.xml) and honor's the "java:comp/env/" environment prefix.

This is the flexibility of OC4J and it is up to you to use the right context factory in your application. Flexibility sometimes has a pay off, but I don't to start a thread on this. Some people love flexibility, eg. some Eclipse zealots...

On the upcoming posts, I'll cover the XML parser and Hivemind configuration issues (Hint: No need to change the source code...).

Stay tuned.