6 Replies Latest reply on Feb 21, 2008 10:17 AM by pascal.verdage

    JobExecutor binding error

    pascal.verdage

      Hi,

      I'm an intern at Bull and I will work on timers, so I'm looking at existing code and try some tests.

      JobExecutorTest raises an error because field JobExecutor.commandExecutor is not found.

      To fix this, you should change org.jpbm.wire.binding.JobExecutorBinding, line 65:
      "commandExecutor" to "commandService"

      Regards,
      Pascal Verdage

        • 1. Re: JobExecutor binding error
          tom.baeyens

          change committed

          • 2. Re: JobExecutor binding error
            pascal.verdage

            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

            Regards,
            Pascal

            • 3. Re: JobExecutor binding error
              tom.baeyens

              thanks again !
              it's fixed in cvs.

              do you already have commit rights ? do you want it ?

              • 4. Re: JobExecutor binding error

                Tom,

                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 ?

                regards
                Miguel Valdes

                • 5. Re: JobExecutor binding error
                  tom.baeyens

                  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.

                  • 6. Re: JobExecutor binding error
                    pascal.verdage

                    Hi,

                    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?

                    Thanks,
                    Pascal