Less is more.
In the list below I don't see why we need component, partition and
application seperation - these notions are container specific.
I would prefer to the subset :
avalon:home.dir
avalon.work.dir
avalon::common.classloader <-- but question on this
avalon::name
I've included the avalon:name entry because without it you will not be
able to resolve all of the Phoenix portability issues. 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 ?
Cheers, Steve.
Nicola Ken Barozzi wrote:
>
> Nicola Ken Barozzi wrote:
>
>>
>> Leo Simons wrote:
>>
>>> On Tue, 2002-08-27 at 23:28, Peter Donald wrote:
>>>
>>>> Im not so sure it is to use "context" as the namespace -esepcially
>>>> given that these attributes are scoped. The way these three are
>>>> named in what I am doing is the following
>>>>
>>>> component:home.dir=
>>>> component:work.dir=
>>>> component:common.classloader=
>>>> partition:home.dir=
>>>> partition:work.dir=
>>>> partition:common.classloader=
>>>> application:home.dir=
>>>> application:work.dir=
>>>> application:common.classloader=
>>>>
>>>> And it cascades up. This allows much more scalable usage patterns
>>>> and it also uses the same terminology as in Phoenix, TC, and other
>>>> containers.
>>>
>>>
>>
>> +1
>>
>
> BTW, what name and package shall I give to the class that will hold
> these reference keys?
>
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
