[ADF-11.1.2.2] Design tab of jspx/jsff goes blank becuase of web.xml config

Question

Hi,
I had my project created in 11.1.2.0 version and got upgraded to 11.1.2.2 recently.
I think there is one following problem with new version:- When you create a new page (jspx) and drag and drop a BTW, the page at designer becomes blank. That goes for all pages under webproject. I debug and found the root cause.
under web.xml file, there are different context-param tags.
when I drag and drop BTF in jspx page, jdeveloper insert following new tag in web.xml
  <context-param>
    <description>Security precaution to prevent clickjacking: bust frames if the ancestor window domain(protocol, host, and port) and the frame domain are different. Another options for this parameter are always and never.</description>
    <param-name>org.apache.myfaces.trinidad.security.FRAME_BUSTING</param-name>
    <param-value>differentOrigin</param-value>
  </context-param>I don't know why, but this create some problem in jdeveloper and the designer tag goes blank. If I remove the above tag, it start working fine.
Is this the issue with jdeveloper ?

Answer 1

Hi,
Timo, This is not an issue with new application. I will tell you the reason.
Frank, for 11.1.2.0 project, I think you are talking about
<context-param>
    <description>Security precaution to prevent clickjacking: bust frames if the ancestor window domain(protocol, host, and port) and the frame domain are different. Another options for this parameter are always and never.</description>
    <param-name>oracle.adf.view.rich.security.FRAME_BUSTING</param-name>
    <param-value>differentDomain</param-value>
  </context-param>and I was talking about following tag in my previous post
  <context-param>
    <description>Security precaution to prevent clickjacking: bust frames if the ancestor window domain(protocol, host, and port) and the frame domain are different. Another options for this parameter are always and never.</description>
    <param-name>org.apache.myfaces.trinidad.security.FRAME_BUSTING</param-name>
    <param-value>differentOrigin</param-value>
  </context-param>Look at param-name tag, it's different.
Vinay, thank you very much for the link that makes whole thing clear :)
I tell you the whole scenario.
When I created the project in 11.1.2.0, web.xml had following tag
<context-param>
    <description>Security precaution to prevent clickjacking: bust frames if the ancestor window domain(protocol, host, and port) and the frame domain are different. Another options for this parameter are always and never.</description>
    <param-name>oracle.adf.view.rich.security.FRAME_BUSTING</param-name>
    <param-value>differentDomain</param-value>
  </context-param>When you create a new project in 11.1.2.2, web.xml already have following tag
  <context-param>
    <description>Security precaution to prevent clickjacking: bust frames if the ancestor window domain(protocol, host, and port) and the frame domain are different. Another options for this parameter are always and never.</description>
    <param-name>org.apache.myfaces.trinidad.security.FRAME_BUSTING</param-name>
    <param-value>differentOrigin</param-value>
  </context-param>but not the "oracle.adf.view.rich.security.FRAME_BUSTING" tag, since it is deprecated in newer version.
The problem comes when you migrate 11.1.2.0 version project to newer version. Jdeveloper adds "org.apache.myfaces.trinidad.security.FRAME_BUSTING" tag instead of replacing the deprecated tag "oracle.adf.view.rich.security.FRAME_BUSTING" when you drag and drop BTF in jspx file for the first time. As per the link by vinay, developer has to "manually" modify the web.xml content manually (if not automatically done by Jdeveloper) before we proceed with any further development in newer version.
The solution is to follow what is written in http://jdevadf.oracle.com/adf-richclient-demo/docs/release-notes.html#New_in_this_Release :)