Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-1034

Usage of jBPM core:process-definitions needs clarification

    Details

      Description

      The Seam documentation for "21.6. Configuring jBPM in Seam" describes how to add jBPM process definitions to components.xml:

      <core:jbpm>
      <core:pageflow-definitions>
      <value>createDocument.jpdl.xml</value>
      <value>editDocument.jpdl.xml</value>
      <value>approveDocument.jpdl.xml</value>
      </core:pageflow-definitions>
      <core:process-definitions>
      <value>documentLifecycle.jpdl.xml</value>
      </core:process-definitions>
      </core:jbpm>

      Nice, but as a side-effect a new copy is inserted into the database each time JBoss AS is started, even if the deployed EAR has not changed. This, of course, can only be noticed if in the example hibernate.cfg.xml from the DVD Store example the line

      <property name="hbm2ddl.auto">create-drop</property>

      is changed into

      <property name="hbm2ddl.auto">update</property>

      Apparently using <core:pageflow-definitions> is considered to be a developers tool:

      http://www.jboss.com/index.html?module=bb&op=viewtopic&t=98430
      http://www.jboss.com/index.html?module=bb&op=viewtopic&t=90206
      http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103819

      I think this needs some clarification in the documentation, but unfortunately (right now) I would not know what is the preferred way to deploy processes in Seam on a production machine. The third topic might include some ideas from others on that.

      Arjan.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                pmuir Pete Muir
                Reporter:
                avbentem Arjan van Bentem
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: