Stephen McConnell wrote:
>
> Less is more.
>
> In the list below I don't see why we need component, partition and
> application seperation - these notions are container specific.
That 's what I thought, but...
> I would prefer to the subset :
>
> avalon:home.dir
> avalon.work.dir
> avalon::common.classloader <-- but question on this
> avalon::name
The question is: how can we differentiate between component, partition
and application - level - stuff?
What about:
avalon:home.dir
avalon.work.dir
avalon:common.classloader
avalon:context:name
and
avalon:app.context
avalon:partition.context
?
> I've included the avalon:name entry because without it you will not be
> able to resolve all of the Phoenix portability issues.
IIRC it has already been proposed out of a need somewhere, ok.
> For the home and
> work values - no problem - for the "common.classloader" - what does this
> mean - is it different from a regular classloader supplied to the
> component ?
Can be.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
