Peter,

>>>>1) Merlin includes phoenix-client.jar and provides alternate
>>>>implemetations of the BlockContext interface.
>>>>        
>>>>
>>>Thats the only real solution at this stage.
>>>      
>>>
>>There could be some reason why that is not possible.
>>    
>>
>
>It will become a lot more difficult in the future when classLoader and 
>interceptor stuff get integrated but it should be possible to no-op those 
>features - not sure. 
>
Well let's tackle future features in the future.  For now though I think 
that useing a Phoenix jar to be Phoenix compatible is perfectly possible.

>>>>2) Change cornerstone comps to use Context as is, and access things via
>>>>'Object get(Object)'
>>>>        
>>>>
>>>This may work for somethings but the key will change in the future. This
>>>wont work for somethings - especially once interceptors are integrated
>>>properly.
>>>      
>>>
>>The key will change one the Attribute thread/discussion is completed?
>> If yes, then that is not too far away right?
>>    
>>
>
>It will happen when I integrate containerkit into Phoenix. That will happen 
>when it is ready. There is still a bit of work to do before that happens 
>(mainly experimentation). I want to get at least the skeleton of HPs CSF 
>structure in place and tested (mainly hierarchial Partiions and associated 
>execution contexts). 
>  
>
OK, We'll look forward to the attribute designs..

>>Personally I like this solution best. Why? I have beans with EOB, and if
>>I get back to it Jesktop-applets that could also be contextualizable.
>> JAMES has maillets and one day newslets.  FtpServer might one day have
>>FtpLets.  If all these were Contextualizable woulldn't it be nice is one
>>Component could run in multiple containers, and adapt its duties to that
>>container.  For example a single comp that was both a Mailet and a
>>EOB-Bean.  Maybe I'm guilty of dreaming up something that has no proven
>>need.
>>    
>>
>
>It is a goal and thats what I am moving towards with the ContainerKit stuff. 
>  
>
Bllimey, I thought'd you'd shoot that down as inpossible dream ;-)

- Paul


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to