You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Ian Boston (JIRA)" <ji...@apache.org> on 2009/11/07 23:30:32 UTC
[jira] Created: (SLING-1175) Potential Invinite Recursion in
JCRResourceResolver2
Potential Invinite Recursion in JCRResourceResolver2
----------------------------------------------------
Key: SLING-1175
URL: https://issues.apache.org/jira/browse/SLING-1175
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR Resource 2.0.6
Reporter: Ian Boston
Fix For: JCR Resource 2.0.8
In JCRResourceResolver.getProperty if a path resolves to a Synthetic Resource, then unless the Resolution can distinguish between a property and node by name it will recurse forever.
I am not certain what the solution should be, either the provider of the synthetic resource should be more intelligent, or JcrResourceResolver2 should guard against recursion.
around line 752
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1175) Potential Invinite Recursion in
JCRResourceResolver2
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854456#action_12854456 ]
Carsten Ziegeler commented on SLING-1175:
-----------------------------------------
Is this still current?
> Potential Invinite Recursion in JCRResourceResolver2
> ----------------------------------------------------
>
> Key: SLING-1175
> URL: https://issues.apache.org/jira/browse/SLING-1175
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.0.6
> Reporter: Ian Boston
> Fix For: JCR Resource 2.0.8
>
>
> In JCRResourceResolver.getProperty if a path resolves to a Synthetic Resource, then unless the Resolution can distinguish between a property and node by name it will recurse forever.
> I am not certain what the solution should be, either the provider of the synthetic resource should be more intelligent, or JcrResourceResolver2 should guard against recursion.
> around line 752
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1175) Potential Invinite Recursion in
JCRResourceResolver2
Posted by "Ian Boston (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Boston resolved SLING-1175.
-------------------------------
Resolution: Fixed
AFAIK, this issue was removed when we refactored the resolver to use map of maps.
> Potential Invinite Recursion in JCRResourceResolver2
> ----------------------------------------------------
>
> Key: SLING-1175
> URL: https://issues.apache.org/jira/browse/SLING-1175
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 2.0.6
> Reporter: Ian Boston
> Fix For: JCR Resource 2.0.8
>
>
> In JCRResourceResolver.getProperty if a path resolves to a Synthetic Resource, then unless the Resolution can distinguish between a property and node by name it will recurse forever.
> I am not certain what the solution should be, either the provider of the synthetic resource should be more intelligent, or JcrResourceResolver2 should guard against recursion.
> around line 752
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.