[jira] Created: (XBEAN-130) Resolving references shoudl supply name and context

Resolving references shoudl supply name and context
---------------------------------------------------

                 Key: XBEAN-130
                 URL: https://issues.apache.org/jira/browse/XBEAN-130
             Project: XBean
          Issue Type: Bug
          Components: naming
    Affects Versions: 3.5, 3.6
            Reporter: David Jencks
            Assignee: David Jencks
             Fix For: 3.6


We call NamingManager.getObjectInstance(object, name, context, env) to resolve non-SimpleReferences.  Currently we're calling it with null for name and context.

Sun javadoc is incomprehensible but clearly indicates that name and context are optional.  IBM javadoc clearly indicates that name is not optional.  We found someone who wants the name and possibly the context.... guess we'd better supply them.  Not sure about env, leaving it empty for now.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/XBEAN-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712323#action_12712323 ]

David Jencks commented on XBEAN-130:
------------------------------------

Likely fix in rev 777752.

> Resolving references shoudl supply name and context
> ---------------------------------------------------
>
>                 Key: XBEAN-130
>                 URL: https://issues.apache.org/jira/browse/XBEAN-130
>             Project: XBean
>          Issue Type: Bug
>          Components: naming
>    Affects Versions: 3.5, 3.6
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.6
>
>
> We call NamingManager.getObjectInstance(object, name, context, env) to resolve non-SimpleReferences.  Currently we're calling it with null for name and context.
> Sun javadoc is incomprehensible but clearly indicates that name and context are optional.  IBM javadoc clearly indicates that name is not optional.  We found someone who wants the name and possibly the context.... guess we'd better supply them.  Not sure about env, leaving it empty for now.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/XBEAN-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks updated XBEAN-130:
-------------------------------

    Summary: Resolving references should supply name and context  (was: Resolving references shoudl supply name and context)

> Resolving references should supply name and context
> ---------------------------------------------------
>
>                 Key: XBEAN-130
>                 URL: https://issues.apache.org/jira/browse/XBEAN-130
>             Project: XBean
>          Issue Type: Bug
>          Components: naming
>    Affects Versions: 3.5, 3.6
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.6
>
>
> We call NamingManager.getObjectInstance(object, name, context, env) to resolve non-SimpleReferences.  Currently we're calling it with null for name and context.
> Sun javadoc is incomprehensible but clearly indicates that name and context are optional.  IBM javadoc clearly indicates that name is not optional.  We found someone who wants the name and possibly the context.... guess we'd better supply them.  Not sure about env, leaving it empty for now.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/XBEAN-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed XBEAN-130.
------------------------------

    Resolution: Fixed

People stopped complaining, so apparently the fix worked.

> Resolving references should supply name and context
> ---------------------------------------------------
>
>                 Key: XBEAN-130
>                 URL: https://issues.apache.org/jira/browse/XBEAN-130
>             Project: XBean
>          Issue Type: Bug
>          Components: naming
>    Affects Versions: 3.5, 3.6
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.6
>
>
> We call NamingManager.getObjectInstance(object, name, context, env) to resolve non-SimpleReferences.  Currently we're calling it with null for name and context.
> Sun javadoc is incomprehensible but clearly indicates that name and context are optional.  IBM javadoc clearly indicates that name is not optional.  We found someone who wants the name and possibly the context.... guess we'd better supply them.  Not sure about env, leaving it empty for now.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.