Berin Loritsch wrote:
> The link on the web site:
>
> http://jakarta.apache.org/avalon/excalibur/container/attributes.html
>
> Has two context keys defined an done attribute defined. Obviously this
> is not enough, but we need to get to the proper abstractions. Anyway,
> here are some changes that need to be performed:
>
> CONTEXT
>
> Key Type Description
> ----------- ---------------- -------------------------------------
> avalon:home java.net.URL This is a context directory that may
> contain a bunch of files that a
> component needs to do its work. There
> is NO GUARANTEE that the URL is
> writable.
+1
>
>
> avalon:work java.io.File This is a work directory that the
> component may use as a work area. This
> directory MUST be writable.
+1
>
> avalon:name java.lang.String The name of a component (is this
> really necessary?)
It not "necessary" but it is convinient for two reasons. Firstly it
provides a hook to the component instance name assigned by a container
when having to deal with things like BlockContext. Secondly, it is
useful in error message generation by a component implementation.
Cheers, Steve.
>
>
> ATTRIBUTES
>
> avalon:lifestyle (SINGLETON|THREAD|POOL|TRANSIENT) Currently
> sufficient, but I am awaiting more info
> on Peter's proposals.
>
--
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]>
