WLS Data Source JNDI Changes to persistence.xml Not Working Using Deployment Plan (Plan.xml) (Doc ID 2679486.1)

Last updated on NOVEMBER 21, 2024

Applies to:

Symptoms

On the WLS Admin Console when the deployed JPA Application that uses a Data Source is updated using a Deployment Plan (Plan.xml) to change the JNDI reference of the Data Source in persistence.xml within the Application, the changes reflect in the Admin Console while they are not reflected in the deployed Application. However the similar change when applies to Context-Root of the application it gets changed and works as expected.

Following is the example scenario:

(1) The Application has persistence.xml that has JTA Data Source defined to 'jdbc/ExampleDS'.

(5) After the application is updated and in Active state, the application TestApp can be accessed via new Context-Root 'TestNew'.

(6) On the Admin Console: Deployments -> TestApp -> Configuration -> General, in this page the 'Context Root' now shows as 'TestNew'.

(7) On the Admin Console: Deployments -> TestApp -> Configuration -> Persistence -> TestApp -> Data Sources, in this page 'Jta Data Source JNDI Name' shows as 'jdbc/TestDS', matches with what is defined in persistence.xml inside the Application.

However when the application is accessed that makes use of the portion that makes use of the Data Source defined in persistence.xml, it is still using the JTA Data Source 'jdbc/ExampleDS' instead that is updated using Plan.xml (jdbc/TestDS).

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.