<%-- - FILE - template.jspf - - DESCRIPTION - A template containing UI code to display Global buttons, subTabs, - pageHeader, error messages, train and navigation buttons (if required). - - MODIFIED (MM/DD/YY) - vsagar 07/18/06 - 10.2.0.3.0 backport - vsagar 07/18/06 - 10.2.0.3.0 backport - tasingh 10/20/05 - created --%> <%@ page contentType="text/html; charset=UTF-8" %> <%@ include file="/oemNoscript.jspf" %> <%--uix Tag Library--%> <%@ taglib uri="http://xmlns.oracle.com/uix/ui" prefix="uix" %> <%@ taglib uri="http://xmlns.oracle.com/oem/jsp/tag" prefix="oem" %> <%--Common UI messages --%> <%--ResourceBundle for common labels/headers etc--%> <%--ResourceBundle for labels/headers specific to Target Selector--%> <%--ResourceBundle for ASProv labels/headers etc--%> <%--To help in partial page renderring--%> <%@ include file="/enablePPR.jspf" %> <%-- - To display "Oracle Enterprise Manager" followed by - UserName on PageTitle. To append page specific string - in the title implement getPageHeader() in the - CONTROLLER CLASS. --%> <%@ include file="/oemTitle.jspf" %> <%-- - We need to show a subTrain if the page that invoked target selector - is a part of a train wizard and select instance page is set to be - shown. If a subTrain is not to be shown then breadCrumbs should be - shown. However, if code to render train is present, then breadCrumbs - are automaticaly not shown. So a typical solution will be to use a - a switcher to include the code to render train, however that results - in an error (location tag should be an immediate child of pageLayout) - So, a work around is to wrap whole of the code inside pageLayout - in a switcher. This will ofcourse result in code redundancy, but - atleast it will work. --%> <%--To display GlobalTabs, Buttons, Footer, Copyright etc--%> <%--<%@ include file="/oemGlobal.jspf" %>--%> <%--The message box to show error/info messge etc--%> <%-- - The page specific contents will be attached here. - Following tag does that. In the JSP page all - contents should be WITHIN the 'buildTree' tag - with attributes - nodeID="pageContent" and - scope="request" - Also this template should be included in all - JSP pages (except wizard pages) at the end as follows - <%@ include file="template.jspf"%> --%> <%--The cancel, next, back and select Buttons--%> <%--Cancel button--%> <%-- - Next and Back buttons: In case, user selects RAC database, - then we need to show the DB instances corresponding to the - RAC database he selected. That is a separate step, that is - why Next button will be shown. --%> <%--Select Button--%> <%-- - Now, all the above code is repeated without the code to - render train. --%> <%--To display GlobalTabs, Buttons, Footer, Copyright etc--%> <%--<%@ include file="/oemGlobal.jspf" %>--%> <%--The message box to show error/info messge etc--%> <%-- - The page specific contents will be attached here. - Following tag does that. In the JSP page all - contents should be WITHIN the 'buildTree' tag - with attributes - nodeID="pageContent" and - scope="request" - Also this template should be included in all - JSP pages (except wizard pages) at the end as follows - <%@ include file="template.jspf"%> --%> <%--The cancel, next, back and select Buttons--%> <%--Cancel button--%> <%-- - Next and Back buttons: In case, user selects RAC database, - then we need to show the DB instances corresponding to the - RAC database he selected. That is a separate step, that is - why Next button will be shown. --%> <%--Select Button--%>