Page Comparison

The <ContainerManagedConnectiononal>ContainerManagedConnection> element specifies a connection to via a JNDI database connection 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 urn:mace:shibboleth:2.0:resolver:dc dc schema, which can be is located at http://shibboleth.net/schema/idp/shibboleth-attribute-resolver-dc.xsd.  

...

<dc:ContainerManagedConnectiononalContainerManagedConnection resourceName="JNDIConnector">
  <dc:Property name="JNDPProp1" value="Value"/>
  <dc:Property name="JNDPProp2" value="Value2"/>
</dc:ContainerManagedConnectiononal>ContainerManagedConnection>

Attributes

Only one attribute may be present resourceName being The only attribute defined is resourceName, the identifier of the JNDI source resource to providelookup.

Child Elements

Zero or more more <Property> elements can be provided.  Each of these elements has Each must contain two attributes: name and value. These provide the custom properties to be passed to the JNDI connection

Notes

 data source.