At 03:40 AM 7/2/2002 +0200, you wrote:
>Our developer understands that he/she has to provide additional
>information at the assembly level
Wrong. The person who does assembling is unlikely to "provide additional
information" for context ever. They may declare how the container maps it
but it is the container provding context data.
If it is user provided data then it goes in via
Configurable/Parameterizable, if it is user supplied service then it comes
in via ServiceManager/ComponentManager.
>2. Several Phoenix based components directly reference the context
>interface BlockContext and will need to declare this interface dependency
>and the corresponding context creation criteria - or - remain bound to
>Phoenix and no other container.
Bingo!
Just in case you did not get it the last 2 times I have already said it in
this thread:
Use BlockContext, remain bound to Phoenix and no other container.
>Please - please - explain how this will be addressed - I'm totally lost in
>trying to figure out your objections here .It the issue is technical -
>please explain what you see the problem being - if the issue if
>architectural - please explain what the impact is that I'm obviously
>missing. If the issue is something else - please explain it because I just
>not getting it.
It is not something that will be implemented in other containers and
ComponentMetaData can be customized by Merlin. Thus why put it in
containerkit?
Besides your misuse of Context is a stupid and ill advised. You can't
expect us to endorse it can you?
Cheers,
Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Faced with the choice between changing one's mind,
and proving that there is no need to do so - almost
everyone gets busy on the proof."
- John Kenneth Galbraith
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
