ADF: Cannot find reason for SEVERE error in WLS log

Question

JDeveloper 11.1.1.1.0
When I deploy my ADF application to integrated WLS, I keep geting following log messages:
10.7.2009 9:09:17 oracle.adfinternal.view.faces.renderkit.rich.RichRenderKit isNavigating
SEVERE: The original view root was not set.
10.7.2009 9:09:20 oracle.adfinternal.view.faces.renderkit.rich.RichRenderKit isNavigating
SEVERE: The original view root was not set.
10.7.2009 9:11:04 oracle.adfinternal.view.faces.renderkit.rich.RichRenderKit isNavigating
SEVERE: The original view root was not set.
10.7.2009 9:11:09 oracle.adfinternal.view.faces.renderkit.rich.RichRenderKit isNavigating
SEVERE: The original view root was not set.
What is the problem?
Edited by: mskarabo on Jul 10, 2009 9:34 AM

Answer 1

Hi,
another situation when this could happen:
In my main jspx I have an af:panelTabbed with an af:region in each of the af:showDetailItems. The regions refer to bounded task flows consisting of only one view (a page fragment) using bindings. The jspx is below, with two additional showDetailItems for testing (sdi3, sdi4).
<f:view>
  <af:document id="d1" title="TEST RichRenderKit isNavigating SEVERE error">
    <af:form id="f1">
      <af:panelTabbed id="pt1">
        <af:showDetailItem text="TaskFlow1" id="sdi1">
          <af:region value="#{bindings.MyTaskFlow1.regionModel}" id="r1"/>
        </af:showDetailItem>
        <af:showDetailItem text="TaskFlow2" id="sdi2">
          <af:region value="#{bindings.MyTaskFlow2.regionModel}" id="r2"/>
        </af:showDetailItem>
        <af:showDetailItem text="showDetailItem 1" id="sdi3">
          <af:outputText id="ot1" value="test"/>
        </af:showDetailItem>
        <af:showDetailItem text="showDetailItem 2" id="sdi4"/>
      </af:panelTabbed>
    </af:form>
  </af:document>
</f:view>The error message appears in the log window only when navigating from a tab that uses a task flow as a region.
(E.g. the error shows when navigating from sdi1 or sdi2 to any other tab, but does not show when navigating from sdi3 or sdi4 to any other tab.)
Hope this helps to identify the problem.
Regards,
Patrik