Daniel Fagerstrom wrote:
Sylvain Wallez skrev:
If the scenario where we have several implementations of a block
interface (e.g. skin)
This is solved by agree before hand which id implementations of this
"interface" should be registered under. Now, this use case is rather
abstract IMO, as we have not developed any way to describe the
"interface" of a skin. So it will be hard to make sure that two
implementations of the same skin interface are interchangeable. But
this problem is of course completely separated from the choice of
component lookup strategy.
Agree. Let's make sure we can wire blocks, we'll see later on how to
specify and control their interfaces :-)
and several instances of a given block (e.g. CSS-Skin) with different
configurations can be handled with a flat central registry,
Using the servlet pattern described above, i.e. using a wiring file as
we have decided long time ago.
<shame>I never had an in-depth look at it...</shame>
Sylvain
--
Sylvain Wallez Anyware Technologies
http://bluxte.net http://www.anyware-tech.com
Apache Software Foundation Member Research & Technology Director
