Stephen, I'm all for your approach - it certainly is better than what we have now.
But I would like to solve the cases where the context entry is either + a value (like a java.io.File) provided by the container + an interface to the container (should be accessed via serviceManager probably) + something that changes during runtime (a Recontextualizable component) and that has new values depending on runtime parameters completely independent of application profile, such as performance data. /LS -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
