Ignore:
Timestamp:
03/02/12 18:46:27 (11 years ago)
Author:
Garth Braithwaite
Message:

ut secure view webapp - made changes to the right app this time.

File:
1 edited

Legend:

Unmodified
Added
Removed

  • adopters/ut/branches/1.8/src/main/webapps/secure-view/WEB-INF/web.xml

    r3609 r3610  
    77    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
    88>
    9 
    10 <!-- IMPORTANT: This file's contents are position dependent for 2.3 DTD.   
    11         To see what elements in what positions see:
    12         http://e-docs.bea.com/wls/docs61/webapp/web_xml.html
    13 -->
    149
    1510        <icon>
    … …  
    5954                <param-value>ibisph-view</param-value>
    6055        </context-param>
    61 <!--
    62         <context-param>
    63                 <param-name>log4jConfigLocation</param-name>
    64                 <param-value>WEB-INF/config/log4j.xml</param-value>
    65         </context-param>
    66         <context-param>
    67                 <param-name>log4jRefreshInterval</param-name>
    68                 <param-value>1000</param-value>
    69         </context-param>
    70 -->
    71 
    72         <!-- ========================================================= F I L T E R S
    73                 The IBIS Filters can either be specified in this web.xml file or handled
    74                 within the Spring environment.  To allow filters to have their values
    75                 set via property files or Spring bean injection configuration files as
    76                 well as to utilize the more robust filter url mapping mechanism the
    77                 Spring filter mechanism is used.
    78 
    79                 The IBIS filters used by the system is implemented by using these of 2
    80                 types of Spring filters:
    81                 - DelegatingFilterProxy - part of the core spring web package.  This
    82                   filter proxy simply wraps a normal filter object and allows spring
    83                   bean managemement/injection.  It does NOT provide any filter mapping.
    84 
    85                 - FilterChainProxy is part of the security package.  In addition to what
    86                   the DelegatingFilterProxy object provides, it adds a filter mapping
    87                   and chaining mechanmism.  This chaining is specified as a property in
    88                   an ANT style url configuration.  This approach has been implemented for
    89                   this app since it is easier to doc and understand the URL mapping vs
    90                   normal web.xml filter mappings.
    91 
    92                 Both are used for IBIS-PH.  The initial "real" filter is the delegate
    93                 which simply passes things off to the bean enabled chain proxy.  This
    94                 provides the ability to use the life cycle init parameter and allows
    95                 the properties to be set via the configuration xml file.
    96 
    97                 NOTE: For "Delegated" IBIS filters that extend/are based on the Abstract
    98                 PathPatternFilter, the filterLifecycle property must be set to true. 
    99                 This can also be done via the "targetFilterLifecycle" init-param.  This
    100                 must be set to true so that the filters will have their required the
    101                 init methods called properly.
    102 
    103                 <init-param>
    104                         <description>
    105                                 Enforces invocation of the Filter.init and Filter.destroy lifecycle
    106                                 methods on the target bean, letting the servlet container manage the
    107                                 filter lifecycle. 
    108                         </description>
    109                         <param-name>targetFilterLifecycle</param-name>
    110                         <param-value>true</param-value>
    111                 </init-param>
    112 
    113           SEE: Version 1.7 and prior, April, 2008 for the older web.xml that had the
    114           filter and filter mappings completely defined within the web.xml w/o spring.
    115         -->
     56
     57
    11658        <filter>
    11759                <filter-name>StandardFilters</filter-name>
    … …  
    15395
    15496
    155 
    15697        <!-- ===================================================== L I S T E N E R S -->
    157 
    158         <!--
    159                 Loads a listener that uses the context-param named contextConfigLocation
    160                 defined above to load the bean definitions when the context is loaded.
    161        
    162                 - Loads the root application context of this web app at startup.
    163                 - The application context is then available via
    164                         WebApplicationContextUtils.getWebApplicationContext(servletContext).
    165 
    166                 - This also allows for custom objects that can load global property
    167                         files at startup etc. see/implement: ServletContextListener
    168 
    169                 NOTE: Some containers (like Tomcat) prefer listeners, some like Websphere
    170                 like servlets.  Listed below is the servlet code for such enviros.
    171 
    172                 <servlet>
    173                         <servlet-name>Log4jConfigServlet</servlet-name>
    174                         <servlet-class>org.springframework.web.util.Log4jConfigServlet</servlet-class>
    175                         <load-on-startup>1</load-on-startup>
    176                 </servlet>
    177                 <servlet>
    178                         <servlet-name>ContextLoaderServlet</servlet-name>
    179                         <servlet-class>org.springframework.web.context.ContextLoaderServlet</servlet-class>
    180                         <load-on-startup>2</load-on-startup>
    181                 </servlet>
    182         -->
    18398        <listener>
    18499                <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
    185100        </listener>
    186 
    187         <!-- Publishes events for session creation and destruction through the app
    188                 context.  Optional unless concurrent session control is being used.
    189         -->
    190         <listener>
    191                 <listener-class>org.springframework.security.ui.session.HttpSessionEventPublisher</listener-class>
    192         </listener>
    193        
    194         <listener>
    195                 <listener-class>org.springframework.web.util.Log4jConfigListener</listener-class>
    196         </listener>   
    197 
    198101
    199102
    … …  
    210113
    211114
    212 
    213115        <!-- ======================================= S E R V L E T   M A P P I N G S
    214116                NOTE: need to map each system and NOT have a general /* mapping because
    … …  
    228130        </servlet-mapping>
    229131
    230         <!-- NOTE: These mappings are mainly used as a mechanism to remove a path prefix.
    231                 For this to work, the request's getPathInfo() method is used, not the get
    232                 URL method.  Also, for Spring's dispatcher_request servlet to property resolve/
    233                 handle full paths the "alwaysUseFullPath" property must be set to "true".
    234                 Example of usage is for ip charts it strips off the /indicator/graphic/ from
    235                 the path so it's one less item to parse - exposing the chart name as the first
    236                 item.  This also makes it easier if at some point for the charting
    237                 functionality to be moved to a seperate servlet.
    238         -->
    239132        <servlet-mapping>
    240133                <servlet-name>Dispatcher.Servlet</servlet-name>
    … …  
    279172                <url-pattern>/Welcome</url-pattern>
    280173        </servlet-mapping>
    281 
    282 <!--
    283         <servlet-mapping>
    284         <servlet-name>ibisq-cgi</servlet-name>
    285         <url-pattern>/cgi-bin/*</url-pattern>
    286     </servlet-mapping>
    287 -->
    288 
    289174
    290175
    … …  
    301186        </jsp-config>
    302187
    303  
    304  
     188
    305189        <!-- =========================================== S E S S I O N   C O N F I G -->
    306190        <session-config>
    … …  
    308192                <session-timeout>30</session-timeout>
    309193        </session-config>
    310 
    311194
    312195
    … …  
    423306-->
    424307</web-app>
    425 
Note: See TracChangeset for help on using the changeset viewer.