You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Michiel Kalkman (JIRA)" <ji...@apache.org> on 2008/10/24 12:55:44 UTC
[jira] Created: (CONFIGURATION-343)
JNDIConfiguration::recursiveGetKeys goes out of stack (2)
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.
[jira] Commented: (CONFIGURATION-343)
JNDIConfiguration::recursiveGetKeys goes out of stack (2)
Posted by "Oliver Heger (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CONFIGURATION-343)
JNDIConfiguration::recursiveGetKeys goes out of stack (2)
Posted by "Oliver Heger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger updated CONFIGURATION-343:
---------------------------------------
Fix Version/s: 1.7
Setting fix version to 1.7. However, it is possible that a fix will only be provided in 2.0. Nevertheless, patches are welcome.
> 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
> Fix For: 1.7
>
>
> 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.