Hi, the CookieInterceptor currently looks for all available cookies. Lets say there are cookies x, y, z. Now it would call setX, setY, setZ on the action. In addition it creates a cookie-map which is then injected to the action.
The cookie interceptor does not make sense at a general level so far. You need to have x, y, z in your actions, and so all your actions would need to provide these setters. Also "*" is risky: if you set a cookie for use in Action A it might fail if you have not an appropriate cookie-based Action B. Actually I have tried to implement CookieAware and expected it would populate a map only from which I can take care of the cookies myself. This doesn't work, because an error is thrown when the get/set methods are missing. To overcome this I created a CookieMapInterceptor which does not populate the action but only a Map. For that I have overridden the CookieInterceptor. It was a bit of pain because a few necessary members are private and not protected. That said, I would like to implement one of the following solutions: Option 1) override CookieInterceptor with CookieMapInterceptor and make ACCEPTED_PATTERN, acceptedPattern, cookiesNameSet protected Option 2) add another option to the CookieInterceptor, which is called "skipActionPopulation" (defaults to false). If true, only the map would be created without putting the Cookies on the Action In any way I would love to make ACCEPTED_PATTERN, acceptedPattern, cookiesNameSet protected. Any preferences/objections? Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
