I'm migrating a portal that's build on WebSphere Portal 6.1 to 7. Now I would like to take advantage of the new tableless theme architecture in Portal 7; which leverages static content pages instead of the traditional standard portal pages.
As of now I've already created the new theme and created some custom layout templates, so all that's left is for me to start converting the old traditional standard pages to static content pages.
In a attempt to perform this task I created a standard page and static page, exported the XML from the static page, replaced the content node's id of the static page with the standard page's id, and re-imported the XML. Now as a result of this I get the following exception:
com.ibm.wps.command.xml.XmlCommandException: EJPXA0150E: The resource was found, but in the wrong context. In the XML input, it is contained in page [ObjectIDImpl 'Z6_ADFR4GL108G230IJR66JLR00O2', CONTENT_NODE, VP: 6112, [Domain: rel], DB: E017-AABD4D600D004131809CDB9859370058], but in the portal it is contained in page [ObjectIDImpl 'Z6_ADFR4GL10O8ID0IJRSTU121GF2', CONTENT_NODE, VP: 6112, [Domain: rel], DB: E017-AABD4D600D0023D9809C9B771F44804F]. [component Z7_ADFR4GL10O8ID0IJRSTU121GF6]
at com.ibm.wps.command.xml.items.ComponentItem.locate(ComponentItem.java:495)
at com.ibm.wps.command.xml.UpdateEngine.tryLocateItem(UpdateEngine.java:383)
at com.ibm.wps.command.xml.UpdateEngine.locateItem(UpdateEngine.java:415)
at com.ibm.wps.command.xml.UpdateEngine.processItem(UpdateEngine.java:230)
at com.ibm.wps.command.xml.UpdateEngine.processItem(UpdateEngine.java:238)
at com.ibm.wps.command.xml.UpdateEngine.updateTopLevelItem(UpdateEngine.java:188)
at com.ibm.wps.command.xml.XmlAccessHandler.fillObjectModel(XmlAccessHandler.java:345)
at com.ibm.wps.command.xml.XmlAccessHandler.endElement(XmlAccessHandler.java:227)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
Through My research I found out that this appear to not be possible, because of the way Portal handle the different types of pages. The standard dynamic portal pages are handled differently. These are configured at portal's databases, however the static portal pages are not, hence the error about the wrong context.