Author: prabhat.jha(a)jboss.com Date: 2009-08-11 15:14:29 -0400 (Tue, 11 Aug 2009) New Revision: 13742 Modified: docs/enterprise/tags/Enterprise_Portal_Platform_4_3_GA_CP02/Reference_Guide/en-US/Migration.xml Log: more JBpm to jBPM Modified: docs/enterprise/tags/Enterprise_Portal_Platform_4_3_GA_CP02/Reference_Guide/en-US/Migration.xml =================================================================== --- docs/enterprise/tags/Enterprise_Portal_Platform_4_3_GA_CP02/Reference_Guide/en-US/Migration.xml 2009-08-11 19:09:15 UTC (rev 13741) +++ docs/enterprise/tags/Enterprise_Portal_Platform_4_3_GA_CP02/Reference_Guide/en-US/Migration.xml 2009-08-11 19:14:29 UTC (rev 13742) @@ -23,10 +23,10 @@ <para>The columns SER_STATE of the table JBP_INSTANCE and SER_STATE of the table JBP_INSTANCE_PER_USER have changed from a length of 50000000 to 16384. You can either alter the tables or modify the hibernate mapping file <literal>portal-core-sar/conf/hibernate/instance/domain.hbm.xml </literal> to set back the length to 50000000 if your database allows it.</para> - <para>The major changes on the schema are related to JBpm as stated in the jBPM 3.2 release notes. JBoss Portal 2.6 was using JBpm 3.1 while - the Enterprise Portal Platform 4.3 is using JBpm 3.2. Here is the relevant part from the JBpm release note:</para> + <para>The major changes on the schema are related to jBPM as stated in the jBPM 3.2 release notes. JBoss Portal 2.6 was using jBPM 3.1 while + the Enterprise Portal Platform 4.3 is using jBPM 3.2. Here is the relevant part from the jBPM release note:</para> <section> - <title>JBpm 3.2 release note extract</title> + <title>jBPM 3.2 release note extract</title> <para>jPDL Database Schema Updates from 3.1.x to 3.2.x <programlisting><![CDATA[ create table JBPM_JOB (