Peter Donald wrote:
> On Tue, 27 Aug 2002 07:13, Nicola Ken Barozzi wrote:
>
>>This is IMNSHO a wrong way of using a context.
>>context has been casted to BlockContext, a thing that should be done
>>only on objects given by a ServiceManager.
>>
>>In fact, a service is gotten by role, a Context is given as-is.
>>
>>It's plain wrong that a Context be cast, it should be used only via keys.
>>
>>Seeing all the commented out methods of Blockcontext, I think Phoenix
>>developers agree.
>
>
> Actually - no ;)
>
> The commented out methods are there to indicate future evolution
paths. ie
> When we integrate the interceptors we will need the proxy methods.
When we
> integrate "protected" blocks we will need some way to get at MBean
server
> (though I don't think it will be via that method). etc.
I don't understand, sorry.
As I said above, any cast to a context is a big mistake IMO.
Please explain why you nead methods.
Are interceptors things that act when a method is called?
Then you can intercept the get and dispatch using the attribute.
>> > The attribute documentation over
>> > on excalibur/container/src/xdocs/attributes.xml provides a good
>> > picture of what's needed on common context keys.
>>
>>Let's standardize on these.
>>
>>Like lifecycle interfaces get a stamp of approval when there is a valid
>>use-case for them, so we should do with Context attributes.
>>
>>Proposals?
>
> Wait a while and I will commit the ones that are going to be
integrated into
> Phoenix.
Ha.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
