Hello,
Oracle JDeveloper 11.1.1.5.0 and WebLogic Server Version: 10.3.5.0
I am using Oracle MDS Customization class with the following classes:
oracle.adf.view.rich.change.MDSDocumentChangeManager
org.apache.myfaces.trinidad.change.ChangeManager
org.apache.myfaces.trinidad.change.MoveChildComponentChange
Based on these classes I am moving UI components
<af:panelStretchLayout>
<f:facet name="center">
<af:region />
</f:facet>
</af:panelStretchLayout>
into another component thanks to the MDS.
Once I do the movement and persist, I receive the following waning message:
*<RegionRenderer> <encodeAll> The region component with id: pt1:r1:0:pt2:r1:0:r1 has detected a page fragment with multiple root components. Fragments with more than one root component may not display correctly in a region and may have a negative impact on performance. It is recommended that you restructure the page fragment to have a single root component.*
When I run the application in Oracle JDeveloper 11.1.1.5.0, it work fine, but when I deploy it on WebLogic Server Version: 10.3.5.0 it is not working.
I receive the same warning message on the server and in JDeveloper.
I think that MDS makes a copy of the components that I move because of that it says me that "a page fragment with multiple root components"
The problem is
not because of duplication any of the tags <af:document> <f:view><f:form> <html> <head> <body>
After the movement and persistence, I also call the FacesContext to reset its view root with the following code:
FacesContext context =FacesContext.getCurrentInstance();
String currentView = context.getViewRoot().getViewId();
ViewHandler vh = context.getApplication().getViewHandler();
UIViewRoot x = vh.createView(context, currentView);
x.setViewId(currentView);
context.setViewRoot(x);
The idea is that the entire JSF tree to be rebuild on entering page with aim to clear previously drag and drop settings.
Do you know how I can overcome the problem on the server WebLogic Server Version: 10.3.5.0?
This worked on Oracle JDeveloper 11.1.1.3.0 and now the problem is with Oracle JDeveloper 11.1.1.5.0.
Regards,
Niki