I'm trying to integrate Spring with Tapestry and I'm stuck on applying the objectDefinitionSyntax of my filterInvocationInterceptor to Tapestry's URL conventions (i.e. when everything is of the form /app?page=xxx)
Would it be a Bad Idea to extend the org.acegisecurity.intercept.web.FilterInvocationDe finitionSourceEditor to support the following "PUBLIC" vs "SECURE" syntax...the idea being that if the string matches PUBLIC, don't add the URL to the source.
Is there a better way to do this? I don't see how Tapestry & Acegi integrate easily without this...
Thanks in advance!