Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: security-0.3.1
-
Fix Version/s: security-0.4.1
-
Component/s: security
-
Labels:None
-
Environment:Tapestry: 5.2.4
-
Number of attachments :
Description
Tapestry uses an url scheme of specifying localization after context-path.
Like /page, /en/page, /fi/page
Currently(I believe) tapestry-security is not page-aware.
It would be good if it was possible to specify PAGES instead of urls so that localization would no be lost.
Probably some users would still need the option of specifying a resource. This could be a standard servlet or jsp.
One suggestion: could pages perhaps be specified in a tapestryish way by using a prefix...
configuration.add(SecuritySymbols.SUCCESS_URL, "page:welcome");
configuration.add(SecuritySymbols.LOGIN_URL, "/login.jsp");
To elaborate, the url protecting scheme of tapestry-security isn't Tapestry/page aware at the moment. Use annotations for page-specific protection. In any case though, I agree we can make the url-based protection more Tapestry aware.