[
https://issues.apache.org/jira/browse/CONFIGURATION-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642623#action_12642623
]
Oliver Heger commented on CONFIGURATION-343:
--------------------------------------------
In the configuration2 branch
([http://svn.apache.org/viewvc/commons/proper/configuration/branches/configuration2_experimental/])
there is a complete new implementation of JNDIConfiguration which also
supports the maxDepth feature:
[http://svn.apache.org/viewvc/commons/proper/configuration/branches/configuration2_experimental/src/main/java/org/apache/commons/configuration2/JNDIConfiguration.java?view=log].
Is it possible for you to check out whether this implementation fits your needs?
> JNDIConfiguration::recursiveGetKeys goes out of stack (2)
> ---------------------------------------------------------
>
> Key: CONFIGURATION-343
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-343
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 1.5
> Reporter: Michiel Kalkman
> Priority: Minor
>
> See http://issues.apache.org/jira/browse/CONFIGURATION-281.
> I think the maxDepth feature should be implemented.
> The reason for this is that in WebSphere it seems possible that some contexts
> seem te be generated on the fly, like
> thisNode.cell -->
> thisNode.cell.cell -->
> ...-->
> thisNode.cell.cell.cell.cell.cell.cell.cell.cell.cell.cell.cell.cell.cell
> etc.
> (anybody any idea why this is so ?)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
