Group items matching

in title, tags, annotations or url

jboss.as.jpa.adapterModule

jboss.as.jpa.adapterClass

org.jboss.as.jpa.hibernate3.hibernatePersistenceProviderAdaptor

Working with other persistence providers

A project to build integration for persistence providers like EclipseLink, is here.

Troubleshooting

“org.jboss.as.jpa” logging can be enabled to get the following information: INFO - when persistence.xml has been parsed, starting of persistence unit service (per deployed persistence.xml), stopping of persistence unit service DEBUG - informs about entity managers being injected, creating/reusing transaction scoped entity manager for active transaction TRACE - shows how long each entity manager operation took in milliseconds, application searches for a persistence unit, parsing of persistence.xml

To enable TRACE, open the as/standalone/configuration/standalone.xml (or as/domain/configuration/domain.xml) file. Search for <subsystem xmlns="urn:jboss:domain:logging:1.0"> and add the org.jboss.as.jpa category

Packaging the Hibernate 3.5 or greater 3.x JPA persistence provider with your application

jboss.as.jpa.providerModule needs to be set to hibernate3-bundled.

<property name="jboss.as.jpa.providerModule" value="hibernate3-bundled" />

Sharing the Hibernate 3.5 or greater JPA persistence provider between multiple applications

Applications can share the same Hibernate3 (for Hibernate 3.5 or greater) persistence provider by manually creating an org.Hibernate:3 module (in the AS/modules folder). Steps to create the Hibernate3 module:

<property name="jboss.as.jpa.providerModule" value="org.hibernate:3" />

Changes for Hibernate 3.5 applications

if your application uses Hibernate 3 classes that are not available in Hibernate 4, for example, some of the validator or search classes, you may see ClassNotFoundExceptions when you deploy your application. If you encounter this problem, you can try one of two approaches: You may be able to resolve the issue by copying the specific Hibernate 3 JARs containing those classes into the application "/lib" directory or by adding them to the classpath using some other method. In some cases this may result in ClassCastExceptions or other class loading issues due to the mixed use of the Hibernate versions, so you will need to use the second approach. You need to tell the server to use only the Hibernate 3 libraries and you will need to add exclusions for the Hibernate 4 libraries. Details on how to do this are described here: JPA Reference Guide.

In previous versions of the application server, the JCA data source configuration was defined in a file with a suffix of *-ds.xml. This file was then deployed in the server's deploy directory. The JDBC driver was copied to the server lib/ directory or packaged in the application's WEB-INF/lib/ directory. In AS7, this has all changed. You will no longer package the JDBC driver with the application or in the server/lib directory. The *-ds.xml file is now obsolete and the datasource configuration information is now defined in the standalone/configuration/standalone.xml or in the domain/configuration/domain.xml file. A JDBC 4-compliant driver can be installed as a deployment or as a core module. A driver that is JDBC 4-compliant contains a META-INF/services/java.sql.Driver file that specifies the driver class name. A driver that is not JDBC 4-compliant requires additional steps, as noted below.

DataSource Configuration

domain mode, the configuration file is the domain/configuration/domain.xml

standalone mode, you will configure the datasource in the standalone/configuration/standalone.xml

MySQL datasource element:

        <connection-url>jdbc:mysql://localhost:3306/YourApplicationURL</connection-url>        <driver-class> com.mysql.jdbc.Driver </driver-class>        <driver> mysql-connector-java-5.1.15.jar </driver>

       <security>            <user-name> USERID </user-name>            <password> PASSWORD</password>        </security>

example of the driver element for driver that is not JDBC 4-compliant. The driver-class must be specified since it there is no META-INF/services/java.sql.Driver file that specifies the driver class name.

 <driver-class>com.mysql.jdbc.Driver</driver-class>

JDBC driver can be installed into the container in one of two ways: either as a deployment or as a core module

Install the JDBC driver

Install the JDBC driver as a deployment

In AS7 standalone mode, you simply copy the JDBC 4-compliant JAR into the AS7_HOME/standalone/deployments directory

example of a MySQL JDBC driver installed as a deployment:     AS7_HOME/standalone/deployments/mysql-connector-java-5.1.15.jar

and allows data modifications to be queued up (like a shopping cart),

EXTENDED

is managed by the underlying persistence provider.

an entity is new if it has just been instantiated using the new operator, and it is not associated with a persistence context. It has no persistent representation in the database and no identifier value has been assigned.

a managed entity instance is an instance with a persistent identity that is currently associated with a persistence context.

the entity instance is an instance with a persistent identity that is no longer associated with a persistence context, usually because the persistence context was closed or the instance was evicted from the context.

a removed entity instance is an instance with a persistent identity, associated with a persistence context, but scheduled for removal from the database.

Replacing the current Hibernate 4.0.x jars with a newer version

update the current as7/modules/org/hibernate/main folder

Delete *.index files in as7/modules/org/hibernate/main and as7/modules/org/hibernate/envers/main folders

Remove the older jars and copy new Hibernate jars into as7/modules/org/Hibernate/main + as7/modules/org/Hibernate/envers/main.

Update the as7/modules/org/hibernate/main/module.xml

as7/modules/org/hibernate/envers/main/module.xml to name the jars that you copied in.

of the JOINED mapping strategy which require a discriminator

GraniteDS now fully supports Hibernate 4

use the granite-hibernate4.jar instead of granite-hibernate.jar

Flex 4.5 broke a few APIs and there were two main issues with Tide : The client libraries crashed when run in a mobile application The PagedQuery was unusable

These two issues are now fixed

granite-flex45.swc

Flex SDK 4.5 here

Note that dpHibernate doesn't depend on Spring

entity classes must implement the org.dphibernate.core.IhibernateProxy interface, both on the Java and Actionscript classes

Application-created persistence units

Native Hibernate applications

native (i.e. non-JPA)

JPA applications that create an EntityManagerFactory on their own, either using the PersistenceProvider SPI directly or through an intermediary mechanism such as Spring's LocalContainerEntityManagerFactoryBean

standard Java EE-applications may ignore the provider implementation and rely on the standard features provided by the container - JBoss AS7 supporting standard JPA 1.0 and 2.0

future versions of JBoss AS7 it will be possible to use alternative persistence provider implementations

map multiple properties as @Id properties

annotated the property as

map multiple properties as @Id properties and declare an external class to be the identifier type

declared on the entity via the @IdClass annotation

The identifier type must contain the same properties as the identifier properties of the entity: each property name must be the same, its type must be the same as well if the entity property is of a

last case is far from obvious

not responsible for the relationship

mappedBy

To use one of the target entity property as a key of the map, use

if the map key type is another entity

All entities marked as [Managed] are considered as corresponding to Hibernate/JPA managed entities on the server

It is highly recommended to use JPA optimistic locking in a multi-tier environment (@Version annotation

In conclusion, the recommended approach to avoid any kind of subtle problems is to have a real uid property which will be persisted in the database

Here all loaded collections of the Person object will be uninitialized so uperson contains only the minimum of data to correctly merge your changes in the server persistence context

Tide uses the client data tracking (the same used for dirty checking, see below) to determine which parts of the graph need to be sent.

Dirty Checking and Conflict Handling

Data Validation

Tide integrates with Hibernate Validator 3.x and the Bean Validation API (JSR 303) implementations, and propagate the server validation errors to the client UI components

Data Paging

Maven 3 is highly recommended but Maven 2.2 should also work

CDI archetype defines an embedded GlassFish run configuration

mvn embedded-glassfish:run