Toplink JPA properties in persistence unit are ignored

Question

I'm trying to make some EJB3 stateless session bean webservices, using the toplink essentials (build b41 beta 2) shipped with OC4J stand-alone 10.1.3.3.0.
Basically I have a 'model' project with my EJB3 entity beans, and a persistence.xml. Then I have a webservice project, that has the model project as a dependency. Both projects are in the same application in JDeveloper. I use a deployment profile to deploy to my seperate OC4J stand-alone instance.
My service runs and deploys fine. The persistence unit is read, and the correct datasource is selected and logged in on. However I notice two things:
- the container complains during deployment, telling me property toplink.server.platform.class.name is deprecated and I should use toplink.target-server. However, I've set the property toplink.target-server as a property in my persistence.xml file...
- I don't see any Toplink logging, although I've set the property toplink.logging.level to FINE in the persistence.xml.
This leads me to believe that the properties are somehow ignored. Has anyone experienced this as well? Any hints/tips/suggestions on how to fix this?
Cheers,
Bas
My persistence.xml:
<?xml version="1.0" encoding="windows-1252" ?>
<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" xmlns="http://java.sun.com/xml/ns/persistence">
  <persistence-unit name="VervoerPublicatiesPU" transaction-type="JTA">
    <provider>oracle.toplink.essentials.PersistenceProvider</provider>
    <jta-data-source>jdbc/SQLPUBDS</jta-data-source>
    <class>a.b.c.A</class>      
    <class>a.b.c.B</class>
    <properties>
        <property name="toplink.logging.level" value="FINE"/>
        <property name="oracle.toplink.essentials.config.CacheType" value="SoftWeak"/>
        <property name="toplink.target-database" value="SQLServer"/>
        <property name="toplink.target-server" value="OC4J_10_1_3"/>
    </properties>
  </persistence-unit>
</persistence>

Answer 1

I debugged this problem a few weeks ago. There are 2 things going on:
1. The EJB3 container is automatically adding the property 'toplink.server.platform.class.name' into what is passed to TopLink to ensure the proper container is configured. I have had a bug filed to get this changed to toplink.target-server in the 10.1.3.4 patch-set.
2. The logging by default goes into the OC4J log found in <HOME>\j2ee\home\log\oc4j
You can re-configure OC4J to also log these messages to stdout or if you only want them to stdout you can simply set the logging-type in the persistence unit properties.
      <property name="toplink.logging.logger" value="DefaultLogger"/>Doug