[
http://jira.magnolia.info/browse/MAGNOLIA-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829#action_17829
]
Ralf Hirning commented on MAGNOLIA-2343:
----------------------------------------
Hi Greg,
I try to understand what you wrote and try to compile this with just a few
words...
Did I get it right that "deprecate" just means that the usage of
Resource.getSelector() is deprecated, but we still can use selectors in the
URIs? So instead of using Resource.getSelector() we just could write our own
method MyProject.getSelector() to get the selector from the original URI. And
everything works as before. Then I do not have any problems with the
deprecation.
But anyway, I do not see the impact of the usage/deprecation of
Resource.getSelector() on the future of Magnolia.
> Selectors can be deprecated, virtual uri mappings can do a better job
> ---------------------------------------------------------------------
>
> Key: MAGNOLIA-2343
> URL: http://jira.magnolia.info/browse/MAGNOLIA-2343
> Project: Magnolia
> Issue Type: Task
> Components: core, templating
> Reporter: Gregory Joseph
> Assignee: Gregory Joseph
> Fix For: 3.6.2
>
> Attachments: Picture 1.png
>
>
--
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://documentation.magnolia.info/
----------------------------------------------------------------
