Author: rebody Date: 2010-07-03 21:20:54 -0400 (Sat, 03 Jul 2010) New Revision: 6457 Modified: jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch09-Configuration.xml Log: format userguide Modified: jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch09-Configuration.xml =================================================================== --- jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch09-Configuration.xml 2010-07-04 01:07:22 UTC (rev 6456) +++ jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch09-Configuration.xml 2010-07-04 01:20:54 UTC (rev 6457) @@ -97,10 +97,16 @@ By default, the rule of validation as followed: <itemizedlist> <listitem> - <para>If the activity has a name, the name shouldnot be empty. The <literal>""</literal> isnot allowed to be used by the name of activity.</para> + <para>If the activity has a name, the name shouldnot be empty. + The <literal>""</literal> isnot allowed to be used by the name of activity.</para> </listitem> <listitem> - <para>The name of activity cannot contain slash(/). It comes from jBPM 3.x. Because jBPM 3.x supported <literal>hierarchical names</literal>, it allowed an execution could jump from a super-state to the other level of activities. But in jBPM 4.x, there would be no chance to achieve this feature. So if someone want to use slash(/) in the name of activity. He could add this configuration parameter into jbpm.cfg.xml.</para> + <para>The name of activity cannot contain slash(/). It comes from jBPM 3.x. + Because jBPM 3.x supported <literal>hierarchical names</literal>, + it allowed an execution could jump from a super-state to the other level of activities. + But in jBPM 4.x, there would be no chance to achieve this feature. + So if someone want to use slash(/) in the name of activity. + He could add this configuration parameter into jbpm.cfg.xml.</para> <programlisting> &lt;jbpm-configuration> &lt;import resource="jbpm.default.cfg.xml" />