I updated the persistence files:
- JpaPersistenceSession is now only an abstract class where jpa 'standard' methods are defined. Extensions to the Jpa spec are declared as abstract methods (maybe we can move the declarations to PersistenceService interface).
- HibernateJpaPersistenceSession, OpenjpaJpaPersistenceSession and ToplinkJpaPersistenceSession extends this abstract class and implement the extensions methods.

These implementations have compilation dependencies with openjpa and toplink, that's why I added them in a lib/ directory (but it's only temporary, maybe these dependencies can be added in jboss repository or managed by ivy/maven)

there are 3 methods which are implementation specific:
- isPersistable: returns true if the class is an entity and can be persisted
- getPrimaryKey(object) : returns the primary key for a given object
- getPrimaryKeyType(class): returns the type of the PK for the given class.

These methods are tested in the PrimaryKeyTest class.
PK methods are tested with:
- a pk of type long
- a embeddedId pk
- a idclass pk
I don't know if it works with an id which is an entity.


For the 'long' id, hibernate and toplink implementations of getPrimaryKeyType return 'java.lang.Long' instead of 'long'. Is this an issue ?

I added a test 'testProxy' in ProcessDefinitionTest. This test fails, but this may be an example of the Proxy vs Object clash problem.

regards,
Guillaume