Usage of jBPM core:process-definitions needs clarification ---------------------------------------------------------- Key: JBSEAM-1034 URL: http://jira.jboss.com/jira/browse/JBSEAM-1034 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 1.2.0.GA Environment: All Reporter: Arjan van Bentem Priority: Minor 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira