Description Sebastien Tardif 2009-06-25 13:57:27 EDT

Below is persistence.xml defining two different persistence-unit reusing old native TopLink mapping. Strangely, the SessionCustomizer of each persistence-unit is called two times. It seems that all sessions in sessions.xml are initialized in each mention in the <properties> section. 

Please fix, that's not right.

<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" version="1.0">
<persistence-unit name="AllInOne" transaction-type="JTA">
<description>This represent all CITYADM schema mappings. It does include pmsi.</description>
<jta-data-source>jdbcxa/CityTimeDataSource</jta-data-source>
<exclude-unlisted-classes>false</exclude-unlisted-classes>
<properties>
<property name="eclipselink.session-name" value="AllInOne"/>
<property name="eclipselink.sessions-xml" value="sessions.xml"/>
</properties>
</persistence-unit>
<persistence-unit name="DataServices" transaction-type="JTA">
<description>This represent all REPORTADM schema mappings</description>
<jta-data-source>jdbcxa/DataServicesDataSource</jta-data-source>
<exclude-unlisted-classes>false</exclude-unlisted-classes>
<properties>
<property name="eclipselink.session-name" value="DataServices"/>
<property name="eclipselink.sessions-xml" value="sessions.xml"/>
</properties>
</persistence-unit>
</persistence>