The declarative JNDI component is based on an Eclipse extension point. The use of the Eclipse extension point registry provides the ability for objects to dynamically be added and removed from the JNDI registry by providing extension points as a part of the plugin.xml
files of installation artifacts.
This JNDI binding extension point is called com.ibm.pvc.jndi.provider.java.binding
An example of the usage of this extension point would be similar to the following:
point = "com.ibm.pvc.jndi.provider.java.binding”>
Note that a required component of the com.ibm.pvc.jndi.provider.java.binding
extension point is the objectFactory-id
. The WebSphere
® Deployment client provides three ObjectFactory
is used exclusively for embedded transaction container bundles, while the GenericObjectFactory
allows for an XML description of any Java
™ object, including primitive constructor parameters, and the ability to call methods on the object once it has been created, but before it is bound into the JNDI registry and returned to a client application. The TxnDataSourceObjectFactory
provides the ability to create and bind into JNDI transaction capable DataSource
objects that are required by the embedded transaction container.
No matter what specific object factory is used, all JNDI objects declaratively described are required to provide the com.ibm.pvc.jndi.provider.java.binding
in their plugin.xml
files. Some object factories may also provide another extension point to that needs to be implemented as well, such as the GenericObjectFactory
WSObjectFactoryParent topic: Configuring enterprise definitions (JNDI)
The WSObjectFactory is responsible for providing a pre-initialized instance of Web services client stub for Apache Axis in the IBM
® Expeditor runtime.