Vincent,
I've taken a look at the FilterChainWrapper class. As far
as I can tell, the setMockFilterChain method appears to be
redundant. If users want to provide a mocked
implementation, they can pass their own mock directly to
the doFilter(request, response, chain) method on the Filter
under test. Since the interface is so small, the only
behavior of the wrapper is to call the doFilter on either
the original filterChain or the mocked filterChain--a
behavior that test cases can easily replicate themselves.
Did you have a reason for defining it the way you did?
Cheers,
Nick
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com
