Hi Jean-Charles,
This is perfectly fine. As long as you define the KiFilter in web.xml, you
can externalize your Apache Ki config in a ki.ini file at the root of the
classpath.
For example:
<filter>
<filter-name>KiFilter</filter-name>
<filter-class>org.apache.ki.web.servlet.KiFilter</filter-class>
</filter>
Then just make sure that ki.ini is at the root of the classpath, and it will
still work.
This allows the config to be externalized, which might be preferable if you
don't want to bloat web.xml and/or you share configuration across one or
more .war files.
Cheers,
Les
On Thu, Apr 30, 2009 at 8:00 AM, jcvidal <[email protected]> wrote:
>
> Hi
>
> I said in a previous post i'm implementing Ki with an external conf file
> instead of the ini-file-like in the web.xml. So, there is no config for the
> filter and OnePerRequestFilter.setFilterConfig() trap (about line #80) !
>
> So this is my code :
>
> public void setFilterConfig(FilterConfig filterConfig) {
> this.filterConfig = filterConfig;
> if (this.filterConfig != null) {
> setServletContext(filterConfig.getServletContext());
> }
> }
>
>
> It's weird, but Ki seems to work even if the servletContext is no set :)
>
>
> Best regards
>
> Jean-Charles
>
> --
> View this message in context:
> http://n2.nabble.com/I-don%27t-know-where-to-post-this-tp2746641p2746641.html
> Sent from the JSecurity User mailing list archive at Nabble.com.
>
>
