Hi,
But sometime component don't know at configuration time which components
are needed.
In my case I know the type of needed component but not which instances,
depends of input request. Dataflow, pipeline, seda,... architecture
doesn't predicate at configuration time all dependencies.
It's right (in my case) I could define all potential needed component at
configuration time, but when I code, I don't know the number of intances
(of a type) needed.
It's why I think react is better. An other aspect is what's append with
Merlin, if needed components are remote, ala Jini?
R.
> IOC
>
> The objective is that the container supplies everything the component
> needs. To do this, the component needs to declare this. The big
> diference between Merlin/Phoenix verus Fortress/ECM is that the first
> group know in advance of component instantiation what the solution is
> wheras the Fortress/ECM is reacting to noise from the component. Ok -
> maybe that's a dramatic way of looking at it - but there are big
> advantages in knowing about component dependencies before instantiation:
>
> * build time validation of deployment scenarios
> * substantially reduced risk of runtime exceptions
> * ability to resolve a provider in advance from a set of candidates
> and selection policy
> * ability to control orderly deployment and decommissioning
>
> Stephen.
>
> >
> >Regards,
> >Vjeran
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> >
--
--------------------------------------------------------------
David "Dwayne" Bernard Freelance Developer (Java)
mailto:[EMAIL PROTECTED]
\|/ http://dwayne.java-fan.com
--o0O @.@ O0o-------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
