Peter Donald wrote:
On Tue, 18 Mar 2003 16:21, Berin Loritsch wrote:
I can think of the following *core* attributes:
see avalon-sandbox/info/src/xdocs/xdoclet.xml for what I consider core
attributes.
@avalon.service -- Required for marking role interfaces.
I thought we already decided to use the term "service" to refer to the work
interfaces that a component provides other components. It would be better to
use @avalon.role or @avalon.interface as marker for work interface.
**As long as it is considered a _standard_ name and supported accross
**_all_ our containers: +1
@avalon.scope -- Used to represent the scope of the component,
and consequently the lifestyle. Values are
"container", "thread", and "request"
Not common across avalon and I can think of several more "scopes". So this is
largely container specific and should be in the fortress namespace.
True. I was thinking these would be the "core" set. Additional scopes
like "session" scope or "application" scope or "block" scope are
specific to the containers that use them.
The question is how would you prefer to express component lifestyle?
I would like to get this resolved so that as the user migrates from
Fortress to Merlin to Phoenix they don't have to do a global replace
on all their source files. Set the attribute once, and it will be
automatically used in all the containers.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
