-
1. Re: updates in the PVM
tom.baeyens Oct 19, 2007 8:28 AM (in response to porcherg)the ivy configurations have been updated to support the use of the persistence test framework in other modules.
identity has now a minimal setup in which this is done.
furthermore i'm working on getting the database test suite on hudson in as many combinations as i can. that explains the evolution in the ivy files.
as for the jbpm prefix, I needed some prefix as we couldn't go do identity.jar, task.jar, enterprise.jar and so on. that would lead to collisions. i took jbpm as a prefix since that makes more sense then prefix all the other libraries with pvm and rename pvm to pvm-core or something like that. -
2. Re: updates in the PVM
mvaldes Oct 19, 2007 8:36 AM (in response to porcherg)I will definetly prefer to use pvm (for the core) and pvm-identity, pvm-task... for others.
Otherwise, common modules should not have any reference to products names
regards,
Miguel Valdes -
3. Re: updates in the PVM
tom.baeyens Oct 19, 2007 8:59 AM (in response to porcherg)"porcherg" wrote:
- the persistenceService interface has changed (for example "persist" method is now "save"). This is a minor update we can adapt the extension.
this is done to avoid confusion that would arise from having a hibernate persistence service method like this:public void persist(Object object) { session.save(object) }
if i recall correctly, i have heard from Gavin long time ago that there are some differences between hibernate's save and persist methods. But recently i saw in a stacktrace that save delegates to persist.
if anyone can shed a light on persist versus save on the hibernate session, that would be good. -
4. Re: updates in the PVM
mvaldes Oct 19, 2007 1:13 PM (in response to porcherg)Tom,
Shall we change so jbpm-pvm by pvm and agree on using pvm as a prefix for other modules ?
Again, not really a good, IMO, to reference products names !
regards,
Miguel