[
https://issues.apache.org/jira/browse/SLING-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3002.
-------------------------------------
Resolution: Fixed
Fix Version/s: Mongo Resource Provider 1.0.0
Thanks for your patch, Dan - i've applied it.
I'm just curious, what are the reasons to subclass the provider? Is this
something we could solve in a general way ootb?
> Make the Mongo Resource Provider easier to subclass
> ---------------------------------------------------
>
> Key: SLING-3002
> URL: https://issues.apache.org/jira/browse/SLING-3002
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: dan mcweeney
> Assignee: Carsten Ziegeler
> Fix For: Mongo Resource Provider 1.0.0
>
> Attachments: enableSubClass.patch
>
>
> The Mongo Provider isn't the easiest thing to extend and specialize. Most of
> the methods are marked as private and once those are loosened up other issues
> came up, like changing the field that ID is stored in etc. Attached is a
> patch to help make subclassing possible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
