Re: [picocontainer-dev] PicoContainer 2.8.1 released

Yup, I'm thinking this is pretty simple to add back :-

     @Deprecated
     public Object resolveInstance(PicoContainer container,  
ComponentAdapter<?> forAdapter, Type expectedType, NameBinding  
expectedNameBinding, boolean useNames, Annotation binding) {
         return resolve(container, forAdapter, null, expectedType,  
expectedNameBinding, useNames, binding).resolveInstance();
     }

     @Deprecated
     public boolean isResolvable(PicoContainer container,  
ComponentAdapter<?> forAdapter, Type expectedType, NameBinding  
expectedNameBinding, boolean useNames, Annotation binding) {
         return resolve(container, forAdapter, null, expectedType,  
expectedNameBinding, useNames, binding).isResolved();
     }

Wherever the impl is needed (and in the interface obviously).

Let me answer later on the verify() question.

Coding this some weeks ago .... I wish that NameBinding  
expectedNameBinding, boolean useNames, Annotation binding were one  
object.  PicoContainer 3.x perhaps.

Regards,

- Paul

On May 21, 2009, at 11:13 AM, Mark Hobson wrote:

> Sure if you want to, I'm migrating my code anyhow.  By the way,
> shouldn't Parameter.verify's signature also be changed to accept an
> injecteeAdapter for consistency?
>
> Mark
>
> 2009/5/21 Paul Hammant <[email protected]>:
>> Yeah, now that you mention it, I forgot to add back the legacy  
>> methods to
>> 'Parameter'.  It should be quite easy, and I can issue a 2.8.2
>>
>> - Paul
>>
>> On May 21, 2009, at 10:54 AM, Mark Hobson wrote:
>>
>>> Note that I've just discovered that the Parameter API has changed
>>> radically in 2.8.1, so perhaps this shouldn't have been a minor
>>> release after all.. ;)
>>>
>>> Mark
>>>
>>> 2009/5/21 Paul Hammant <[email protected]>:
>>>>
>>>> Speed up, I think, is the biggest benefit.
>>>> But see the release news page too : http://picocontainer.org/news.html
>>>>
>>>> Regards,
>>>>
>>>> - Paul
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>>
>>>>  http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>   http://xircles.codehaus.org/manage_email
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>   http://xircles.codehaus.org/manage_email
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>