ContainerManagedConnection> element specifies a connection via a JNDI DataSource resource provided by the container. This requires container-specific configuration steps, generally including adding the resource definition to the webapp context descriptor, and adding a reference to it in the deployment descriptor (web.xml).
In older versions, this was the only way to share a DataSource across multiple data connectors and to configure alternate pooling implementations superior to the c3p0 library used in the IdP's ApplicationManagedConnection implementation. This is no longer the case; rather than rely on this mechanism, the new BeanManagedConnection option is the suggested choice.
Schema Name and Location
This element is defined by the
schema, which is located at http://shibboleth.net/schema/idp/shibboleth-attribute-resolver.xsd.
The only attribute defined is
resourceName, the identifier of the JNDI resource to lookup.
Zero or more
<Property> elements can be provided. Each must contain two attributes:
value. These provide custom properties to be passed to the JNDI data source.