> From: Berin Loritsch [mailto:[EMAIL PROTECTED]
>
> In this case, Phoenix would be able to recognize the
> components as requiring functionality it can't deliver, and
> then refuse to deploy it. This addresses both Stephen's and
> my concerns.
Wait wait wait wait wait...
If a tag has to be explicitely recognized by all containers, i.e.
the container must do this:
if (tag.equals ("lifecycle")) {
fail ("I don't support that tag.");
}
instead of just defaulting:
if (!supportedTags.contains (tag)) {
fail ("I don't support that tag.");
}
Then it should be in the avalon namespace.
Why? Well, in the first case, a container must test for the
tag whether or not it supports it. In the second
case you just get a "sorry, can't do that".
So what is the score with Phoenix now? Does Phoenix
read any tags? If yes, what will it do with a component that
has a lifecycle tag?
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
