The ModSvcProvider kmodule binds a service provider factory into JNDI. The ModSvcProvider kmodule is implemented by com.fs.pxe.server.modsfwk.ModSvcProvider.
| Name |
Type |
Required? |
Description |
| JndiName |
String |
No. |
the JNDI name under which the service provider will be bound. The PXE domain will lookup service providers using this name. |
| TransactionManagerName |
String |
Yes. |
the JDNI name of the transaction manager. Note that this should match the JNDI name at which a transaction manager is deployed, e.g., via the ModJOTM kmodule. |
| ProviderClass |
String |
Yes. |
the fully-qualified classname of the implementation of the service provider. |
| ProviderURI |
String |
Yes. |
a unique URI for the service provider. A system deployment descriptor will reference a service provider by its URI. |
| ProviderProperties |
String |
No. |
provides additional deployment-scope configuration properties for a service provider in the syntax name1=value1;name2=value2.... These are not to be confused with service-scope properties specified in a system deployment descriptor]. |
The ModSvcProvider kmodule does not have any generic dependencies, but individual service providers may require some services to be started prior to deployment by the [{{ModSfwk}}] kmodule.
