| @Steve: right, but the problem remained at the time. Just a heads up on that issue of mine:
This migration was not a priority so I let it rest for some time. Last Thursday I just updated all to Hibernate 5.1.0.Final and Payara 4.1.1.161_1, and everything worked perfectly. (Naturally as a prerequisite, one needs to update the jboss-logging jar + clean osgi cache on Payara on the one hand, and have up-to-date persistence.xml hibernate properties on the other hand - I'm writing them below for the record). I have the feeling I was at the wrong place at the wrong time back in November... The (probably always) working persistencde.xml
<?xml version="1.0" encoding="UTF-8"?>
<persistence xmlns="http://xmlns.jcp.org/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence
http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd"
version="2.1">
<persistence-unit name="whateverPU" transaction-type="JTA">
<provider>org.hibernate.jpa.HibernatePersistenceProvider</provider>
<jta-data-source>java:comp/DefaultDataSource</jta-data-source>
<class>com.whatever.jpa.Status</class>
<properties>
<property name="hibernate.dialect" value="org.hibernate.dialect.DerbyTenSevenDialect"/>
<property name="hibernate.show_sql" value="true"/>
<property name="hibernate.default_schema" value="HHH10262"/>
<property name="javax.persistence.jdbc.driver" value="org.apache.derby.jdbc.ClientDriver"/>
<property name="javax.persistence.jdbc.url" value="jdbc:derby://localhost:1527/sun-appserv-samples"/>
<property name="javax.persistence.jdbc.user" value="HHH10262"/>
<property name="javax.persistence.jdbc.password" value="HHH10262"/>
<property name="hibernate.transaction.jta.platform" value="SunOne"/>
</properties>
</persistence-unit>
</persistence>
|