What you may need to know about source URI for an <af:inlineFrame>

The <af:inlineFrame> component creates an inline frame tag. The content of the inline frame is loaded through the source attribute.
e.g: <af:inlineFrame id="if1" source="/faces/someView.jspx"/>

Please note that, <af:inlineFrame> let you to define the 'relative' source URLs in two ways.

1. Relative to the current web application

<af:inlineFrame id="if1" source="/faces/someView.jspx"/>
In this case the source is looked up relative to the current web application's context. This approach is useful if the page resides in the same 'war' file

2. Relative to the server root

<af:inlineFrame id="if1" source="//<app_context>/faces/someView.jspx"/>
Please note that URL starts with double forward slash in this case. Here the source is looked up relative to the server root. This is very useful if the you need to load a page from another 'war' file within the same server root. Apparently this feature frees you from writing down the custom EL to extract the server root and using the same to construct the URIs.


  1. Hi Jobinesh,

    In addition to your two ways above, you could also define a source URI with a complete URL like "http://soadev.blogspot.com". The task details of the Oracle BPM worklist app is the best example for this.


  2. Hi Jobinesh,
    I am trying to use inlineFrame for embedding pages form OPA (Oracle Policy Automation) in our adf application. These pages contains series of question answer set and some button too. so you answer a question and go to next page via link or button and so on. These whole page is wrapped inside inlineFrame. Now when there are buttons.. they causes the browser to navigate to actual url itself.
    Is there a way that this can be prevented ?

  3. Greetings from México Jobinesh!
    is expression language available through this component?


Post a Comment


The views expressed on this blog are my own and do not necessarily reflect the views of my employer.