Hi Angelo,
Well, let's say I have a filter called CookieLoginRequestFilter that
implements ComponentEventRequestFilter and PageRenderRequestFilter:
public class CookieLoginRequestFilter
implements ComponentEventRequestFilter, PageRenderRequestFilter {
private final CookieLoginService co
Hi Filip S,
Can you show me sample code of doing that? here is my simple code:
public boolean dispatch(Request request, Response response) throws
IOException {
Cookie[] cookies = cookieSource.getCookies();
if (cookies != null) {
for (Cookie c : cookies) {
Angelo,
I do exactly that in the request handling pipeline using a
ComponentEventRequestFilter and a PageRenderRequestFilter. Works
beautifully and let's you get the page name etc. easily from the
supplied parameters. Pretty much doesn't get any easier than that. :)
-Filip
Angelo Chen skrev
hi Howard,
Thanks, cookieDispatcher check if a user cookie already exist, if yes, then
it will log in the user using a login service, I don't know if it works with
request handling pipelines.
A.C.
Howard Lewis Ship wrote:
>
>
> What does CookieDispatcher do? It probably is a better fit for o
The Start page is a special case, and should be relegated to the
"backwards compatibility" scrap heap. Recognizing the Start page is
its own Dispatcher and is probably being processed before your
CookieDispatcher.
What does CookieDispatcher do? It probably is a better fit for one of
the request
