2 Replies Latest reply on May 29, 2008 4:05 AM by tom.baeyens

    remove timer session bean altogether?

    aguizar

      Having two timer beans might lead to confusion, so I am considering removing the timer session bean and document that it has been superseded by the entity bean. Does anyone foresee any significant consequence to this?

        • 1. Re: remove timer session bean altogether?
          aguizar

          The merging of CommandListenerBean and JobListenerBean, as in PVM, is another point to consider.

          Neither the timer bean nor the job listener bean are meant to be invoked directly by clients, unlike the command service and command listener, which makes compatibility concerns moot.

          • 2. Re: remove timer session bean altogether?
            tom.baeyens

            keep it as is so that old configuration files still keep working.

            users that don't have a problem with it don't want to be forced to look in the release notes to find what they should change in their configuration.

            i don't see the problem of keeping it in the codebase.

            removing the old stuff from the docs is a good idea, though. to prevent that new users configure the old stuff.