| = InitialContext Configuration | |
| :index-group: Unrevised | |
| :jbake-date: 2018-12-05 | |
| :jbake-type: page | |
| :jbake-status: published | |
| A InitialContext can be declared via xml in the | |
| `<tomee-home>/conf/tomee.xml` file or in a `WEB-INF/resources.xml` file | |
| using a declaration like the following. All properties in the element | |
| body are optional. | |
| [source,xml] | |
| ---- | |
| <JndiProvider id="myInitialContext" type="javax.naming.InitialContext"> | |
| </JndiProvider> | |
| ---- | |
| Alternatively, a InitialContext can be declared via properties in the | |
| `<tomee-home>/conf/system.properties` file or via Java VirtualMachine | |
| `-D` properties. The properties can also be used when embedding TomEE | |
| via the `jakarta.ejb.embeddable.EJBContainer` API or `InitialContext` | |
| [source,properties] | |
| ---- | |
| myInitialContext = new://JndiProvider?type=javax.naming.InitialContext | |
| ---- | |
| Properties and xml can be mixed. Properties will override the xml | |
| allowing for easy configuration change without the need for $\{} style | |
| variable substitution. Properties are not case-sensitive. If a property | |
| is specified that is not supported by the declared InitialContext a | |
| warning will be logged. If a InitialContext is needed by the application | |
| and one is not declared, TomEE will create one dynamically using default | |
| settings. Multiple InitialContext declarations are allowed. # Supported | |
| Properties | |
| Property | |
| Type | |
| Default | |
| Description |