You just set up your security context as usual with spring. Define the beans
you need for userDetailsService (or other authenticationProvider),
saltSource, encoder, rememberMe etc. and fire up the spring security
namespace config. This is described in great detail in the Spring security
docs as wel
gger instance. Requests for static resources are
>> >> handled at a higher level, so
>> >> * this filter will only be invoked for Tapestry related requests.
>> >> *
>> >> *
>> >> * Service builder methods are usefu
ization.
> In
> >> most cases,
> >> * use the static bind() method instead.
> >> *
> >> *
> >> * If this method was named "build", then the service id would be
> >> taken from the
> >>
gt;> already defines
>> * a service named "RequestFilter" we use an explicit service id that
>> we can reference
>> * inside the contribution method.
>> */
>> public RequestFilter buildTimingFilter(final Logger log)
>> {
>>
> // The responsibility of a filter is to invoke the
> corresponding method
> // in the handler. When you chain multiple filters
> together, each filter
> // received a handler that is a bridge to the next
> f
// received a handler that is a bridge to the next
filter.
return handler.service(request, response);
}
finally
{
long elapsed = System.currentTimeMillis() - startTime;
log.info
