2 Replies Latest reply on Aug 9, 2010 3:37 AM by charles_a

    "error: mail template not found" preventing deployment. Bug?

    charles_a

      Hi all,

       

      we have deployed multiple version of a process with the same key. After deployment, we suspend all but the latest deployment of a process to ensure only one active version of a process (if running instances exists, we migrate them).

       

      Now, we´ve removed an old mail template used in an old process definitions (it´s not used in the still active definition, it´s in a version "some deployments ago").

       

      We encounter the message "error: mail template not found" which prevents deployment.

       

      I´ve done some debugging and it seems that in class ProcessDeployer the method checkKey loads all existing process definitions for a specific key. During the initialization of the ProcessDefinition object the exception occurs.

       

      How is it supposed to work? Maybe it should only search for still active ProcessDefinitions in the checkKey method? Is probably the jpdl parser too strict here, because the parser seems fine with old processes having usercode defined that also doens´t exist anymore (assignmenthandler classes for example)?

       

      Thanks for your help,

       

      Charles

        • 1. Re: "error: mail template not found" preventing deployment. Bug?
          rebody

          Hi Charles,

           

          Because jBPM4 should prevent the process definitions who have same key with different names.  So it will try to deploy all of process definitions from database.

           

          I think you could delete those deployments which won't be used.  As you pointed those process definition's class or mail templates had been removed,  So they can't be reused any more.

          • 2. Re: "error: mail template not found" preventing deployment. Bug?
            charles_a

            Hi Huisheng Xu,

             

            thanks for your reply. You are right, deleting should do the job. We have high requirements for historization and it´s a bit disadvantageous that the deployments must be deleted to avoid the above error. But as the history process information is left in the database, it´s ok for us and we´ll keep track of the deployment history ourself. Thanks for the clarification!

             

            Cheers,

            Charles