Sunday, December 18, 2005

Weblogic 8.1 SP2 and Acegi framework

Here is a Workaround for Weblogic 8.1 SP2 with
Acegi framework.
BEA has fixed the problem in SP3..but I did not
have the luxury of upgrading Weblogic in the middle of a deployment..lesson learned(Always develop on the same
version that is in production).I used Spring 1.2.5
DelegatingFilterProx which was "inspired" by the
filterToBean cousin located in the Acegi package.

<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>
     /WEB-INF/applicationContext-acegi-security.xml  
     /WEB-INF/applicationContext.xml
  </param-value>
</context-param>
<filter>
  <filter-name>Acegi Filter Chain Proxy</filter-name>
    <filter-class>
org.springframework.web.filter.DelegatingFilterProxy
    </filter-class>
    <init-param>
      <param-name>targetBeanName</param-name>
      <param-value>filterChainProxy</param-value>
    </init-param>
    <init-param>
      <param-name>init</param-name>
      <param-value>lazy</param-value>
     </init-param>
</filter>
<filter-mapping>
   <filter-name>Acegi Filter Chain Proxy</filter-name>
    <url-pattern>/*</url-pattern>
   </filter-mapping>
<listener>
<listener-class>
   org.springframework.web.context.ContextLoaderListener
  </listener-class>
</listener>
<listener>
   <listener-class>
net.sf.acegisecurity.ui.session.HttpSessionEventPublisher
</listener-class>
</listener>