avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <dona...@apache.org>
Subject Re: [Excalibur] ExcaliburComponentSelector.hasComponent() query
Date Tue, 31 Jul 2001 13:21:19 GMT
On Tue, 31 Jul 2001 22:47, Berin Loritsch wrote:
> Stuart Roebuck wrote:
> > I'm trying to pin down a problem with components in Cocoon 2 at the
> > moment and was trying to get to grips with Avalon.  I ran across the
> > following code which didn't look like what I was expecting...
> >
> > "hasComponent()" which seems like a benign test, has the side-effect of
> > 'releasing' a component and appears to rely on "release()" not raising an
> > exception as the basis for determining the component's existence:
>
> It relies on the select() or lookup() function to not throw an exception. 
> It could be rewritten to take advantage of the internal structure, 

+1000 ;)
Mainly as select/lookup may mean excessive resource usage when 
ComponentManager is acting as a factory, a prototype factory or sometype of 
component pooling mechanism. But then again I don't use 
ExcalibutComponentManager so ... ;)

Cheers,

Pete

*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |
*-----------------------------------------------------*

---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org


Mime
View raw message