Mailing-List: contact xbean-dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: xbean-dev@geronimo.apache.org
Message-ID: <266239649.1252343937627.JavaMail.jira@brutus>
Date: Mon, 7 Sep 2009 10:18:57 -0700 (PDT)
From: "David Jencks (JIRA)" <jira@apache.org>
To: xbean-dev@geronimo.apache.org
Subject: [jira] Closed: (XBEAN-130) Resolving references should supply name
 and context
In-Reply-To: <487169172.1243038405541.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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.