Index: modules/jpdl/src/main/java/org/jbpm/jpdl/internal/activity/JpdlBinding.java
===================================================================
--- modules/jpdl/src/main/java/org/jbpm/jpdl/internal/activity/JpdlBinding.java	(revision 6461)
+++ modules/jpdl/src/main/java/org/jbpm/jpdl/internal/activity/JpdlBinding.java	(working copy)
@@ -56,7 +56,7 @@
         parse.addProblem(XmlUtil.errorMessageAttribute(element, "name", name, "is empty"), element);
       }
 
-      boolean isActivityAllowSlash = false;
+      boolean isActivityAllowSlash = true;
       Boolean candidateCondition = (Boolean) EnvironmentImpl.getFromCurrent("jbpm.activity.allow.slash", false);
       if (candidateCondition != null) {
         isActivityAllowSlash = candidateCondition.booleanValue();
Index: modules/userguide/src/main/docbook/en/modules/ch09-Configuration.xml
===================================================================
--- modules/userguide/src/main/docbook/en/modules/ch09-Configuration.xml	(revision 6461)
+++ modules/userguide/src/main/docbook/en/modules/ch09-Configuration.xml	(working copy)
@@ -101,12 +101,13 @@
               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.
+              <para>Before jBPM 4.4, 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>
+              So since jBPM 4.4, we allowed slash(/) in the name of activity by default.
+              If someone want to use the previous validation rule for slash(/) in jBPM 4.4,
+              he could add this configuration parameter into jbpm.cfg.xml.</para>
               <programlisting>
 &lt;jbpm-configuration>
   &lt;import resource="jbpm.default.cfg.xml" />
@@ -114,11 +115,10 @@
   &lt;import resource="jbpm.jpdl.cfg.xml" />
 
   &lt;process-engine-context>
-    <emphasis role="bold">&lt;true name='jbpm.activity.allow.slash'/></emphasis>
+    <emphasis role="bold">&lt;false name='jbpm.activity.allow.slash'/></emphasis>
   &lt;/process-engine-context>
 &lt;/jbpm-configuration>
               </programlisting>
-              <para>By using this, JpdlBinding will skip validation for slash(/) in activity name.</para>
           </listitem>
       </itemizedlist>
     </para>