[ http://jira.magnolia.info/browse/MAGNOLIA-887?page=all ]
Ralf Hirning updated MAGNOLIA-887:
----------------------------------
Attachment: selector.patch.txt
I attached a patch to allow the usage of selector. The changes are:
- Add static final String SELECTOR = "selector" in class Aggregator
- Add static String getSelector(HttpServletRequest req) in class Resource
- Modify MgnlCmsFilter.collect(HttpServletRequest request) to extract the
selector and store as request attribute
> Introduction of selectors in url
> --------------------------------
>
> Key: MAGNOLIA-887
> URL: http://jira.magnolia.info/browse/MAGNOLIA-887
> Project: magnolia
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.0 Beta 1
> Reporter: Ralf Hirning
> Assigned To: Philipp Bracher
> Fix For: 3.1
>
> Attachments: selector.patch.txt
>
>
> It would be nice to allow selectors in URLs. Selectors are the parts between
> the path (handle) and the extension.
> The idea is to pass additional parameters to the template within the URL (not
> using page.html?X=1 ...) so that the result can be cached.
> The template can decide what to do with these parameters.
> Examples:
> http://localhost/site/form.thanks.html to give feedback to a form
> http://localhost/site/page.en.html to render a page with
> English texts
> http://localhost/site/page.de.html to render a page with German
> texts
> http://localhost/site/page.w-170.h-80.jpg to create a graphic with width 170
> px and height 80px
> The selectors could be provided via API function
> Iterator Resource.getSelectors()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
