It's not a problem, you can have multiple filters, they will be called in
sequence when you hit an URL that matches your filter-mapping. Example for
spring-security :
<filter>
<filter-name>springSecurityFilterChain</filter-name>
<filter-class>org.springframework.web.filter.DelegatingFilterProxy</filter-class>
</filter>
<filter>
<filter-name>wicket</filter-name>
<filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class>
<init-param>
<param-name>applicationFactoryClassName</param-name>
<param-value>
org.apache.wicket.spring.SpringWebApplicationFactory
</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>springSecurityFilterChain</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>wicket</filter-name>
<url-pattern>/*</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>ERROR</dispatcher>
</filter-mapping>
Just add your Cayenne filter in your web.xml and you're done.
2009/10/7 Peter Arnulf Lustig <[email protected]>
> Cayenne needs his own filter.
>
>
>
> ----- Ursprüngliche Mail ----
> Von: Olivier Bourgeois <[email protected]>
> An: [email protected]
> Gesendet: Mittwoch, den 7. Oktober 2009, 10:10:00 Uhr
> Betreff: Re: How do you achieve persistency
>
> Why would you replace the Wicket filter ?
>
> You can have multiple filters defined in your web.xml , they are chained by
> your application server.
>
> 2009/10/7 Peter Arnulf Lustig <[email protected]>
>
>
