This page is to list down all issues that I face while working with ADF/Webcenter (Fusion Middleware products)
ADF - Error in Jdev as shown below
Caused by: oracle.jbo.PersistenceException: JBO-34000: Definition class name missing in XML file of type taskFlow at oracle.adf.model.binding.DCDefBase.createAndLoadFromXML(DCDefBase.java:402) at oracle.adf.model.binding.DCBindingContainerDef.loadExecutables(DCBindingContainerDef.java:1405) at oracle.adf.model.binding.DCBindingContainerDef.loadChildrenFromXML(DCBindingContainerDef.java:1201) at oracle.adf.model.binding.DCDefBase.loadFromXML(DCDefBase.java:325)
Solution: Add following entries in DataBindings.cpx
We use content presenter to show content from UCM. Content definition is defined by region-definition file and its template is create in webcenter. Let say we want to show news items in webcenter page.
First we define our news item. It may consist a title, a description and an image. All this definition goes in region definition file say NEWS_REG_DEF
In our webcenter content presenter template we refer region defintion and its element to show content. For example to show title of a news we use
BUT there is a problem with this. If user has some special characters like quotes in text_element element, it will start showing "e in UI. To avoid that we can use escape="false".
Now special characters will not appear in UI.
BUT at times we want to show text element with some specific styling. Using escape false, system will ignore any styleclass mentioned with outputtext.
As a solution we can create a panelgrouplayout around outputtext and specify styles on panelgrouplayout.
NOTE: PanelGroupLayout can only provide default styles. If element is of type wysiwyg, contributor can put styling while creating content and in that case those styling will take preference. Functionally and Technically it makes sense also. That is why I referred it as a default syling by panelgrouplayout. It will only work if contributor has not overridden it by providing his own setting.
Disclaimer: Any views or opinions presented in this blog are
solely those of the author and do not necessarily represent those of the