From portal-commits at lists.jboss.org Wed Mar 28 10:48:17 2007 Content-Type: multipart/mixed; boundary="===============8479322966411975799==" MIME-Version: 1.0 From: portal-commits at lists.jboss.org To: portal-commits at lists.jboss.org Subject: [portal-commits] JBoss Portal SVN: r6866 - docs/trunk/referenceGuide/en/modules. Date: Wed, 28 Mar 2007 10:48:17 -0400 Message-ID: --===============8479322966411975799== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: bdaw Date: 2007-03-28 10:48:17 -0400 (Wed, 28 Mar 2007) New Revision: 6866 Modified: docs/trunk/referenceGuide/en/modules/migration.xml Log: small update Modified: docs/trunk/referenceGuide/en/modules/migration.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- docs/trunk/referenceGuide/en/modules/migration.xml 2007-03-28 14:09:08 = UTC (rev 6865) +++ docs/trunk/referenceGuide/en/modules/migration.xml 2007-03-28 14:48:17 = UTC (rev 6866) @@ -57,6 +57,8 @@ Database + All things described in this section can be done using Admi= nPortlet. Treat this directions more as guideline + if you need to automate migration for big portal deployment. Database schema wasn't changed between 2.4 and 2.6 releases, b= ut still content that is kept in it changed slightly in few areas. You can easily update the data = manually by using tools proper for your @@ -89,6 +91,7 @@ + Instead of editing database you can destroy those instan= ces in AdminPortlet and recreate them. NavigationPortlet from JBP 2.4 is not = present anymore. Its functionality is now realized by PageCustomizerInterceptor so all refer= ences to NavigationPortlet should @@ -112,6 +115,7 @@ + Instead of editing database you can just remove Navigati= onPortletInstance using AdminPortlet. CMS --===============8479322966411975799==--