avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <blorit...@apache.org>
Subject Re: Fortress and Cornerstone Components
Date Wed, 30 Apr 2003 20:51:07 GMT
Peter Royal wrote:
> On Wednesday, April 30, 2003, at 04:00  PM, Stephen McConnell wrote:
> 
>> Preamble - dealing with Phoenix components required a certain degree 
>> of effort on behalf of a container.  I have expressed on the user list 
>> my opinion that the Fortress container is not there yet in terms of 
>> providing this support.  This is based on my experience in supporting 
>> Phoenix based components in a non-Phoenix environment for over a year. 
>>  Note that this is a transient position - the code to support Phoenix 
>> semantics is in place within Merlin - all that is needed to 
>> collaboration to move this into Fortress or move Fortress 
>> functionality into Merlin/Phoenix.
> 
> 
> Assuming that the components do not use the BlockContext interface, all 
> that is needed for fortress is:
>  * Any required context entries
>  * A manual declaration in a roles file specifying the thread-safe 
> component handler for the block.
> 
> Is this not correct?

Actually, using Fortress's ANT task, you can gather that information
(and assume the components are ThreadSafe as is the case with meta
info generated components).  This is already done.  We can easily
create a test to prove it.



-- 
"You know the world is going crazy when the best
rapper is a white guy, the best golfer is a black guy,
The Swiss hold the America's Cup, France is
accusing the US of arrogance, and Germany doesn't want
to go to war. And the 3 most powerful men in America
are named 'Bush', 'Dick', and 'Colon' (sic)".

-----Chris Rock


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Mime
View raw message