2 Replies Latest reply on Mar 19, 2008 3:40 AM by tom.baeyens

    Environment problem in StandardCommandService



      In the last revisions, StandardCommandService was modified to use the current environment instead of creating a new one. Tests fail because DispatcherThread executes AcquireJobsCommand and the environment is null.

      Pascal Verdage

        • 1. Re: Environment problem in StandardCommandService

          There was a problem with the interceptors. They were not added to the environment used for timer tests.

          There is still a problem with EnvironmentInterceptor, when it is used by an eagerly initialized object. The interceptor tries to use the current environment to access the environment factory, but there is no environment (eager objects are created during environmentFactory creation).

          As a workaround, we remove eager init for JobExecutor.

          Pascal and Guillaume

          • 2. Re: Environment problem in StandardCommandService


            for me, the job executor doesn't have to work just yet in this release.

            just for the future: if such a test is important for you guys, make sure it is in the test suite. cause then it certainly grabs my attention and i won't release before the test suite runs.