> -----Original Message-----
> From: Michael McKibben [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, 20 February, 2002 00:10
> To: [EMAIL PROTECTED]
> Subject: Context.put?
>
>
> I've been finding myself wishing for a Context.put(key,value) on the
> Context interface. Why does Context only have a get? It seems that you can
> still support an unmodifiable Context by just throwing an exception (ala
> an unmodifiable java.util.Map). I know supporting this change for the
> immediate future would be bad since this will break any Context impls out
> there (although, in practice don't most people just use DefaultContext?)
Hi Michael:
I pass around either a Context instance or a interface derived from Context.
Typically I construct and populate the context within some implementation
class and use the Context (or derived interface) when exposing it to
anything
else. Concerning DefaultContext - sometime - yes - but I have several
instances
here of objects with an inheritance slot that is already taken up and its
easy to implement the Context interface on an existing class.
Cheers, Steve.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
