Default.jsp

<%@ page session="false" buffer="none" %>

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">


<%--
NOTE: By default, automatic reloading of theme and skin JSP files is turned off.
To see the changes you make to this file without stopping and restarting
the server, follow the instructions for enabling automatic JSP reloading
in the InfoCenter.

Do not enable automatic JSP reloading in a production environment
because performance will decrease.

NOTE: Default.jsp uses the @include JSP directive to include jsp fragments
(denoted by the.jspf extension) which compiles these files into the servlet
for Default.jsp. If you change these files, "touch" the version
of Default.jsp which includes it to see your changes.
You can do this by editing Default.jsp and saving it.
--%>

<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<%@ taglib uri="http://java.sun.com/jstl/core_rt" prefix="c-rt" %>
<%@ taglib uri="http://www.ibm.com/xmlns/prod/websphere/portal/v6.0/portal-navigation" prefix="portal-navigation" %>
<%@ taglib uri="http://www.ibm.com/xmlns/prod/websphere/portal/v6.0/portal-dynamicui" prefix="portal-dynamicui" %>
<%@ taglib uri="http://www.ibm.com/xmlns/prod/websphere/portal/v6.0/portal-logic" prefix="portal-logic" %>
<%@ taglib uri="http://www.ibm.com/xmlns/prod/websphere/portal/v6.0/portal-core" prefix="portal-core" %>
<%@ taglib uri="http://www.ibm.com/xmlns/prod/websphere/portal/v6.0/portal-fmt" prefix="portal-fmt" %>
<%@ taglib uri="http://www.ibm.com/xmlns/prod/websphere/portal/v6.0/portal-theme-ext" prefix="portal-theme-ext" %>
<%@ taglib uri="/WEB-INF/tld/portal-internal.tld" prefix="portal-internal" %>
<%@ taglib uri="/WEB-INF/tld/people.tld" prefix="pa" %>
<%@ taglib uri="/WEB-INF/tld/menu.tld" prefix="menu" %>

<portal-core:constants/>
<portal-core:defineObjects/>
<portal-internal:adminNavHelper/>
<portal-theme-ext:initthemepolicy/>

<jsp:useBean id="themePolicy" class="com.ibm.portal.theme.policy.ThemePolicyBean" scope="page"/>

<% themePolicy.setValuesMap(portalThemePolicyMap);%>





<html <portal-fmt:bidi dir="rtl"> dir="rtl" </portal-fmt:bidi>>

<%@ include file="./head.jspf" %>

<body <%=bidiDirAttr%> onload="if (javascriptEventController) { javascriptEventController.enableAll(); }" >

<div id="FLYParent">

    <div class="themeHeader">
        <%@ include file="./banner.jspf" %>
    
        <portal-logic:if portletSolo="no">
            <%@ include file="./topNav.jspf" %>
        </portal-logic:if>
    </div>
    
    <%--
    In IE the width of tables is calculated incorrectly, resulting in the page
    contents often being too large to render next to the side navigation. This causes
    them to wrap and render below the navigation, requiring the user to scroll after each
    requiest to view the content.
    
    To circumvent the problem, we wrap the sidenav and maincontent in a table. This table's
    width is 100% of the browser, so child tables get their width set correctly
    --%>
    
    <table style="width:100%; height:100%;" cellpadding="0px" cellspacing="0px">
    <tr>
    
    <td valign="top">
        <portal-logic:if portletSolo="no">
            <%@ include file="./sideNav.jspf" %>
        </portal-logic:if>
    </td>
    
    <td width="100%" height="100%" valign="top">
    
        <a name="wpsMainContent"> </a>
    
    
        <%-- Call the portal engine command to render the portlets for this page --%>
        <div id="mainContent">
            <portal-core:screenRender/>
        </div>
    
    </td>
    </tr>
    </table>
    
    <portal-logic:if portletSolo="no">
    
        <%@ include file="./footer.jspf" %>
    
        <c:if test="${!isSafari}">
            <%@ include file="./flyout.jspf" %>
        </c:if>
    
    </portal-logic:if>
    
    <portal-logic:if loggedIn="yes">
        <pa:peopleend/>
        </portal-logic:if>

</div>

<%--
If no user is logged in, there's no reason to remember the flyout state. This
way the flyout state for a user that has logged out will also be reset. We also
want to include a link to the sitemap on the page where the user is not logged in
since the main menu will not be accessible to a search crawler.
--%>

<portal-logic:if loggedIn="no" portletSolo="no" >

    <script type="text/javascript">wpsFLY_clearStateCookie(); </script>

    <portal-navigation:urlGeneration contentNode="ibm.portal.Site Map.Site Map" >
        <a href="<%wpsURL.write(out);%>" > </a>
    </portal-navigation:urlGeneration>

</portal-logic:if>

<c:if test="${!isSafari}">
    <portal-logic:if portletSolo="no" loggedIn="yes" >
        <script type="text/javascript">wpsFLY_onloadShow(<%=isRTL%>);</script>
    </portal-logic:if>
</c:if>

</body>
</html>