Embedded Isolation Method
When you set the Isolation Method property of an iView to Embedded , you create a simple HTML iView whose content is written "as is" into the HTML of the page . As a result, a content-loading event in the iView, such as launching a link or submitting a form, refreshes the whole page.
Features and Implications
-
iView content is collected at the server side and sent to the client with the entire page.
-
A request from the client to the server causes the server to reload all the iViews on the page.
-
This prevents unnecessary requests to the server.
-
Performance may be degraded.
-
-
PageBuilder has no control over the appearance of the iView content:
-
Content is presented "as is" in the browser.
-
The size of the iView depends on the content.
-
iView height is not controlled by the page.
-
The page does not add scrollbars to iViews.
-
-
Both server-side and client-side events are supported.
Limitations
-
A page may contain several form-type iViews. One iView may lose the information in its input fields when another form on the page is submitted.
-
Content that is external to the portal server requires special handling.
Content-loading events on embedded iViews cause the loss of iViews that are in iFrames. It is not recommended to put embedded and isolated iViews on the same page.
A regular portal iView that is set to Embedded should not be placed on a Web Dynpro page. If it is, a warning message is generated and its isolation method is changed automatically to URL .