You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xbean-dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2008/10/23 01:56:44 UTC
[jira] Created: (XBEAN-115) nameInNamespace not used properly in
NestedSubcontexts
nameInNamespace not used properly in NestedSubcontexts
------------------------------------------------------
Key: XBEAN-115
URL: https://issues.apache.org/jira/browse/XBEAN-115
Project: XBean
Issue Type: Bug
Components: naming
Affects Versions: 3.4.2
Reporter: David Jencks
Assignee: David Jencks
Fix For: 3.4.3, 3.5
See GERONIMO-4375.
If you create a WritableContext with a nameInNamespace, then do a deepBind, then try to rebind.... the rebind doesn't work. The problem appears to be that the root nameInNamespce is not always added to the NestedWritableContext pathWithSlash.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (XBEAN-115) nameInNamespace not used properly in
NestedSubcontexts
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/XBEAN-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642011#action_12642011 ]
David Jencks commented on XBEAN-115:
------------------------------------
Similar change in NestedImmutableContext for constency, although I don't see how the bug could manifest. rev 707230.
> nameInNamespace not used properly in NestedSubcontexts
> ------------------------------------------------------
>
> Key: XBEAN-115
> URL: https://issues.apache.org/jira/browse/XBEAN-115
> Project: XBean
> Issue Type: Bug
> Components: naming
> Affects Versions: 3.4.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 3.4.3, 3.5
>
>
> See GERONIMO-4375.
> If you create a WritableContext with a nameInNamespace, then do a deepBind, then try to rebind.... the rebind doesn't work. The problem appears to be that the root nameInNamespce is not always added to the NestedWritableContext pathWithSlash.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (XBEAN-115) nameInNamespace not used properly in
NestedSubcontexts
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/XBEAN-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed XBEAN-115.
------------------------------
Resolution: Fixed
rev 707227
> nameInNamespace not used properly in NestedSubcontexts
> ------------------------------------------------------
>
> Key: XBEAN-115
> URL: https://issues.apache.org/jira/browse/XBEAN-115
> Project: XBean
> Issue Type: Bug
> Components: naming
> Affects Versions: 3.4.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 3.4.3, 3.5
>
>
> See GERONIMO-4375.
> If you create a WritableContext with a nameInNamespace, then do a deepBind, then try to rebind.... the rebind doesn't work. The problem appears to be that the root nameInNamespce is not always added to the NestedWritableContext pathWithSlash.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (XBEAN-115) nameInNamespace not used properly in
NestedSubcontexts
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/XBEAN-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed XBEAN-115.
------------------------------
only fixed in trunk
> nameInNamespace not used properly in NestedSubcontexts
> ------------------------------------------------------
>
> Key: XBEAN-115
> URL: https://issues.apache.org/jira/browse/XBEAN-115
> Project: XBean
> Issue Type: Bug
> Components: naming
> Affects Versions: 3.4.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 3.5
>
>
> See GERONIMO-4375.
> If you create a WritableContext with a nameInNamespace, then do a deepBind, then try to rebind.... the rebind doesn't work. The problem appears to be that the root nameInNamespce is not always added to the NestedWritableContext pathWithSlash.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.