I found similar problems :
- in org.jpbm.wire.binding.StandardMessageServiceBinding, "persistenceService" should be changed to "dbSession"
- in org.jpbm.wire.binding.StandardTimerServiceBinding, "persistenceService" should be changed to "pvmDbSession"
- in org.jpbm.env.session.hibernate.HibernatePvmDbSession, the implemented interface is not DbSession but PvmDbSession
thanks again !
it's fixed in cvs.
do you already have commit rights ? do you want it ?
In addition to Pascal, 3 more guys will join our team next weeks (most of them will work on standard vs enterprise services).
I think its time to get corporate svn commit rights rather than contributor by contributor... what do you think ?
Could you tell me how that works at jboss ?
i don't know how it works. but it's definitely something that you can get.
let me figure out how to get this done.
I'm still working on timers and I created an API to define a timer service.
It is close to the standard Java Time mechanism, but instead of using TimerTask I was planning to use Job. It means that you schedule a Job to be executed some time in the future.
Then, using the bridge pattern, I intend to provide different implementations to have a TimerService working in memory or persisted, in a J2EE or a stand-alone version.
But I don't understand why, in the Command interface (package org.jbpm.client), the method execute needs to have an environment. The environment should be accessible via Environment.getCurrent().
Could you explain this to me?