[BIG VERY OBJECTIONABLE & FRUSTRATING SNIP]
Leo:
>
> And then you can use om.lookup for objects and components.
> Does this solve your immediate needs? That is, getting
> something working NOW, with not too much crap for future
> cleanups?
Absolutely not!!!!!
I think Paul is going to have to resent that thing about
user requirements! What Paul wants, what I want, and what a bunch
of other people want is simply the following:
public MyClass implements Serviceable
{
public void service( ServiceManager manager )
{
Object object = manager.lookup("MY-SERVICE");
}
}
That's it - that all!
If someone wants a recyclable service all they need to do is:
public MyClass implements Serviceable
{
public void service( ServiceManager manager )
{
ServicePool pool = (ServicePool) manager.lookup("MY-POOL");
Object object = pool.checkout( this, "MY-SERVICE" );
pool.release( object );
}
}
It's that simple.
Please go back and read the proposal.
http://www.mail-archive.com/avalon-dev@jakarta.apache.org/msg06099.html
> Getting the next version may not be possible for
> a while, maybe by summer.
What possible justification!
The solution is already there - you may want to sit around until summertime
contemplating the meaning of life but some of us have more pressing agendas.
Some of us have to deal with the real world - a world where a component is
implemented as an Object - a world where not everything can be passed as
a Component. Please - go back, look at the proposal, keep yourself
constrained to the abstractions defined in the framework and if there
is a problem - please detail what your problem is.
Steve.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
