You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2007/10/30 11:32:50 UTC
[jira] Resolved: (SLING-51) microsling: use OCM mappings, in
addition to direct access to JCR nodes
[ https://issues.apache.org/jira/browse/SLING-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved SLING-51.
--------------------------------------
Resolution: Won't Fix
Setting to won't fix, people seem to agree according to sling-dev discussions. We'll reopen this if we change our collective mind.
> microsling: use OCM mappings, in addition to direct access to JCR nodes
> -----------------------------------------------------------------------
>
> Key: SLING-51
> URL: https://issues.apache.org/jira/browse/SLING-51
> Project: Sling
> Issue Type: Improvement
> Components: microsling
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> As discussed on the list, use Resource.getItem() to access the current JCR Node or Property, and use Resource.getData() to access the OCM-mapped object if there's one.
> OCM can probably be implemented as an additional RequestFilter that comes after the ResourceResolverFilter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.