[portal-commits] JBoss Portal SVN: r7577 - docs/trunk/referenceGuide/en/modules.

Author: thomas.heute(a)jboss.com Date: 2007-06-27 07:11:01 -0400 (Wed, 27 Jun 2007) New Revision: 7577 Modified: docs/trunk/referenceGuide/en/modules/workflow.xml Log: Make the code fit on a page Modified: docs/trunk/referenceGuide/en/modules/workflow.xml =================================================================== --- docs/trunk/referenceGuide/en/modules/workflow.xml 2007-06-27 10:10:44 UTC (rev 7576) +++ docs/trunk/referenceGuide/en/modules/workflow.xml 2007-06-27 11:11:01 UTC (rev 7577) @@ -17,44 +17,47 @@ <para> The JBPM Workflow service is packaged as an mbean and takes care of all the low-level JBPM related functions. The configuration is found in jboss-portal.sar/portal-cms.sar/portal-workflow.sar/META-INF/jboss-service.xml. The mbean service configuration is as follows: - <programlisting> - <![CDATA[ - <!-- Hibernate service --> - <mbean - code="org.jboss.portal.jems.hibernate.SessionFactoryBinder" - name="portal:service=Hibernate,type=Workflow" - xmbean-dd="" - xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> - <xmbean/> - <depends>jboss.jca:service=DataSourceBinding,name=@portal.datasource.name@</depends> - <attribute name="DoChecking">true</attribute> - <attribute name="ConfigLocation">conf/hibernate/workflow/hibernate.cfg.xml</attribute> - <attribute name="JNDIName">java:/portal/workflow/WorkFlowSessionFactory</attribute> - </mbean> - - <!-- Workflow service --> - <mbean - code="org.jboss.portal.workflow.service.WorkflowServiceImpl" - name="portal:service=Workflow,type=WorkflowService" - xmbean-dd="" - xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> - <xmbean/> - <depends>portal:service=Hibernate,type=Workflow</depends> - <attribute name="JbpmConfigurationXml"> - <jbpm-configuration> - <jbpm-context> - <service name="persistence" factory="org.jbpm.persistence.db.DbPersistenceServiceFactory"/> - </jbpm-context> - <string name="resource.hibernate.cfg.xml" value="conf/hibernate/workflow/hibernate.cfg.xml"/> - <string name="resource.business.calendar" value="org/jbpm/calendar/jbpm.business.calendar.properties"/> - <string name="resource.default.modules" value="org/jbpm/graph/def/jbpm.default.modules.properties"/> - <string name="resource.converter" value="org/jbpm/db/hibernate/jbpm.converter.properties"/> - <string name="resource.action.types" value="org/jbpm/graph/action/action.types.xml"/> - <string name="resource.node.types" value="org/jbpm/graph/node/node.types.xml"/> - <string name="resource.varmapping" value="org/jbpm/context/exe/jbpm.varmapping.xml"/> - </jbpm-configuration> - </attribute> - </mbean> + <programlisting><![CDATA[<!-- Hibernate service --> +<mbean + code="org.jboss.portal.jems.hibernate.SessionFactoryBinder" + name="portal:service=Hibernate,type=Workflow" + xmbean-dd="" + xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> + <xmbean/> + <depends>jboss.jca:service=DataSourceBinding,name=@portal.datasource.name@</depends> + <attribute name="DoChecking">true</attribute> + <attribute name="ConfigLocation">conf/hibernate/workflow/hibernate.cfg.xml</attribute> + <attribute name="JNDIName">java:/portal/workflow/WorkFlowSessionFactory</attribute> +</mbean> + +<!-- Workflow service --> +<mbean + code="org.jboss.portal.workflow.service.WorkflowServiceImpl" + name="portal:service=Workflow,type=WorkflowService" + xmbean-dd="" + xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> + <xmbean/> + <depends>portal:service=Hibernate,type=Workflow</depends> + <attribute name="JbpmConfigurationXml"> + <jbpm-configuration> + <jbpm-context> + <service name="persistence" + factory="org.jbpm.persistence.db.DbPersistenceServiceFactory"/> + </jbpm-context> + <string name="resource.hibernate.cfg.xml" + value="conf/hibernate/workflow/hibernate.cfg.xml"/> + <string name="resource.business.calendar" + value="org/jbpm/calendar/jbpm.business.calendar.properties"/> + <string name="resource.default.modules" + value="org/jbpm/graph/def/jbpm.default.modules.properties"/> + <string name="resource.converter" + value="org/jbpm/db/hibernate/jbpm.converter.properties"/> + <string name="resource.action.types" value="org/jbpm/graph/action/action.types.xml"/> + <string name="resource.node.types" value="org/jbpm/graph/node/node.types.xml"/> + <string name="resource.varmapping" value="org/jbpm/context/exe/jbpm.varmapping.xml"/> + </jbpm-configuration> + </attribute> +</mbean> ]]> </programlisting> </para> @@ -71,33 +74,33 @@ In the following file, jboss-portal.sar/portal-cms.sar/META-INF/jboss-service.xml, activate this feature on the org.jboss.portal.cms.impl.jcr.JCRCMS MBean <programlisting> <![CDATA[ - <mbean - code="org.jboss.portal.cms.impl.jcr.JCRCMS" - name="portal:service=CMS" - xmbean-dd="" - xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> - <xmbean/> - <!-- The datasource hibernate depends on, it can be commented when the file store is used --> - <depends>jboss.jca:service=DataSourceBinding,name=PortalDS</depends> - <depends>portal:service=JAASLoginModule</depends> - <depends>portal:service=Hibernate,type=CMS</depends> - <depends>portal:service=Module,type=IdentityServiceController</depends> - <!--depends optional-attribute-name="UserModule" proxy-type="attribute">portal:service=Module,type=User</depends--> +<mbean + code="org.jboss.portal.cms.impl.jcr.JCRCMS" + name="portal:service=CMS" + xmbean-dd="" + xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> + <xmbean/> + <!-- The datasource hibernate depends on, + it can be commented when the file store is used --> + <depends>jboss.jca:service=DataSourceBinding,name=PortalDS</depends> + <depends>portal:service=JAASLoginModule</depends> + <depends>portal:service=Hibernate,type=CMS</depends> + <depends>portal:service=Module,type=IdentityServiceController</depends> + <!-- Uncomment this to activate publish/approval workflow integration --> + <depends optional-attribute-name="ApprovePublishWorkflow" + proxy-type="attribute">portal:service=ApprovePublish,type=Workflow</depends> - - <!-- Uncomment this to activate publish/approval workflow integration --> - <depends optional-attribute-name="ApprovePublishWorkflow" proxy-type="attribute">portal:service=ApprovePublish,type=Workflow</depends> - - - - <depends optional-attribute-name="StackFactory" proxy-type="attribute">portal:service=InterceptorStackFactory,type=Cms</depends> - <attribute name="DoChecking">true</attribute> - <attribute name="DefaultContentLocation">portal/cms/conf/default-content/default/</attribute> - <attribute name="DefaultLocale">en</attribute> - <attribute name="RepositoryName">PortalRepository</attribute> - <attribute name="HomeDir">${jboss.server.data.dir}${/}portal${/}cms${/}conf</attribute> - <attribute name="Config"> + <depends optional-attribute-name="StackFactory" proxy-type="attribute"> + portal:service=InterceptorStackFactory,type=Cms + </depends> + <attribute name="DoChecking">true</attribute> + <attribute name="DefaultContentLocation"> + portal/cms/conf/default-content/default/</attribute> + <attribute name="DefaultLocale">en</attribute> + <attribute name="RepositoryName">PortalRepository</attribute> + <attribute name="HomeDir">${jboss.server.data.dir}${/}portal${/}cms${/}conf</attribute> + <attribute name="Config"> ]]> </programlisting> </para> @@ -108,67 +111,67 @@ The configuration for this workflow service is found in the jboss-portal.sar/portal-cms.sar/portal-workflow.sar/META-INF/jboss-service.xml file <programlisting> - <![CDATA[ - <!-- ApprovePublish workflow service --> - <mbean - code="org.jboss.portal.workflow.cms.ApprovePublishImpl" - name="portal:service=ApprovePublish,type=Workflow" - xmbean-dd="" - xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> - <xmbean/> - <depends optional-attribute-name="WorkflowService" proxy-type="attribute"> - portal:service=Workflow,type=WorkflowService - </depends> - <depends optional-attribute-name="IdentityServiceController" proxy-type="attribute"> - portal:service=Module,type=IdentityServiceController - </depends> - <!-- JBPM process definition --> - <attribute name="Process"> - <!-- cms approval workflow --> - <process-definition name="approval_workflow"> - <start-state> - <transition to="request_approval"/> - </start-state> - <task-node name="request_approval" signal="first"> - <task name="approve_publish"> - <assignment class="org.jboss.portal.cms.workflow.PublishAssignmentHandler"/> - <event type="task-start"> - <action class="org.jboss.portal.cms.workflow.FinalizePublish"/> - </event> - <exception-handler> - <action class="org.jboss.portal.workflow.cms.TaskExceptionHandler"/> - </exception-handler> - </task> - <transition name="approval" to="end"/> - <transition name="rejection" to="end"/> - </task-node> - <end-state name="end"/> - </process-definition> - </attribute> - <!-- - overwrite = false creates the process first time if does not exist, for - subsequent server restarts, this process definition remains in tact - - overwrite = true creates the process first time if does not exist, - for subsequent server restarts, it creates a new version of the process definition - which will be used for processes created from then onwards. Old processes created - for an older version of the definition remain in tact and use their corresponding - process definition. - - Typically use overwrite=false and overwrite=true only when a new process definition - related to this workflow needs to be deployed - --> - <attribute name="Overwrite">false</attribute> - <!-- - a comma separated list of portal roles that are designated - to act as workflow managers. They are allowed to - approve/reject content publish requests - --> - <attribute name="ManagerRoles">Admin</attribute> - <attribute name="JNDIName">java:portal/ApprovePublishWorkflow</attribute> - </mbean> - ]]> - </programlisting> + <![CDATA[ +<!-- ApprovePublish workflow service --> +<mbean + code="org.jboss.portal.workflow.cms.ApprovePublishImpl" + name="portal:service=ApprovePublish,type=Workflow" + xmbean-dd="" + xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> + <xmbean/> + <depends optional-attribute-name="WorkflowService" proxy-type="attribute"> + portal:service=Workflow,type=WorkflowService + </depends> + <depends optional-attribute-name="IdentityServiceController" proxy-type="attribute"> + portal:service=Module,type=IdentityServiceController + </depends> + <!-- JBPM process definition --> + <attribute name="Process"> + <!-- cms approval workflow --> + <process-definition name="approval_workflow"> + <start-state> + <transition to="request_approval"/> + </start-state> + <task-node name="request_approval" signal="first"> + <task name="approve_publish"> + <assignment class="org.jboss.portal.cms.workflow.PublishAssignmentHandler"/> + <event type="task-start"> + <action class="org.jboss.portal.cms.workflow.FinalizePublish"/> + </event> + <exception-handler> + <action class="org.jboss.portal.workflow.cms.TaskExceptionHandler"/> + </exception-handler> + </task> + <transition name="approval" to="end"/> + <transition name="rejection" to="end"/> + </task-node> + <end-state name="end"/> + </process-definition> + </attribute> + <!-- + overwrite = false creates the process first time if does not exist, for + subsequent server restarts, this process definition remains in tact + + overwrite = true creates the process first time if does not exist, + for subsequent server restarts, it creates a new version of the process definition + which will be used for processes created from then onwards. Old processes created + for an older version of the definition remain in tact and use their corresponding + process definition. + + Typically use overwrite=false and overwrite=true only when a new process definition + elated to this workflow needs to be deployed + --> + <attribute name="Overwrite">false</attribute> + <!-- +a comma separated list of portal roles that are designated +to act as workflow managers. They are allowed to +approve/reject content publish requests + --> + <attribute name="ManagerRoles">Admin</attribute> + <attribute name="JNDIName">java:portal/ApprovePublishWorkflow</attribute> +</mbean> + ]]> + </programlisting> </para> </sect1> </section>