Stephen,
>> Hmmm...
>
>
>
> The only issue is for Phoenix to throw the exception
>
> try
> {
> // do classic Phoenix stuff
> }
> catch( ValidationException ve )
> {
> final String error =
> "Sorry, Phoenix isn't as advanced as some other Avalon
> containers."
> + "Phoenix does not support"
> + " * extensions"
> + " * dynamic context"
> + " * default configuration"
> + " * auto assembly";
>
> throw new ValidationFailure( error );
> }
OK, ignoring for the time being that this is a little rude to Phoenix
and its authors, there is something positive here. Especially as you
have in another mail said that Merlin can (or will be soon) be run
inside Phoenix.
Given some basic assumptions:
1) From the laymans point of view, Merlin is apparently an alternate
container to Phoenix providing extensions, dynamic xontext, default
configuration and auto assembly beyong the abilities of Phoenix
2) Phoenix is likely not to support directly those features.
Perhaps we have some positive things to do here:
1) DTD unified, for Merlin specific elements, basic Phoenix refuses
to run with a polite message.
2) Compatibility elements added .xinfo files and assembly.xml.
A euphamism like <avalon-container-compatability> might be good.
3) Merlin coded to have distributions for all of these:
i) standalone
ii) in Phoenix,
iii) replacement Phoenix kernel components (refer kernel.conf).
4) basic Phoenix coded to exlicitly not handle Merlin specific features.
We have a way to placate steve's quest for a new generation, Peter
feeling that phoenix itself should be stable. Please folks if we are
going to shoot this idea/compromise down, could we do so without heated
emotion. Could we also try to do so in a summarial way, with
accompanying detailed explanation: "This will not work because Phoenix
is a bird that rises from the ashes; Refer to mythalogical blah blah
blah blah." Some of us demi-management types want to see a managerial
summary and trust that we don't have to wade through pages of
justification. If the managerial summary is concisely put, and fairly
represents the accompanying explanation, then it is a good point of
reference. This whole Merlin/Phoenix thing has been clouded by too much
detail, that kinda precludes the involvement of those of us who have not
written one of the two or swallowed the "Software architecture for
geniuses". Please -> short, fair and concilliatory chatter from now on?
- Paul
- Paul
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
