Date: Thu, 28 Mar 2024 15:51:18 +0000 (UTC) Message-ID: <1070413329.19.1711641078206@b7d8c45808f1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_18_951390003.1711641078205" ------=_Part_18_951390003.1711641078205 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Namespace: urn:mace:shibboleth:2.0:resolv=
er
Schema: http://shibboleth.net/schema/idp/shibboleth-attribute-resolver.xsd<=
/a>
The <ContainerManagedConnection>
element specifi=
es a connection via a JNDI DataSource resource provided by the container. T=
his requires container-specific configuration steps, generally including ad=
ding 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 mu= ltiple data connectors and to configure alternate pooling implementations. = This is no longer the case; rather than rely on this mechanism, the new BeanManagedConnection element is the suggested= alternative.
<Cont= ainerManagedConnection resourceName=3D"JNDIConnector"> <Property name=3D"JNDPProp1" value=3D"Value"/> <Property name=3D"JNDPProp2" value=3D"Value2"/> </ContainerManagedConnection>