At 08:38 20/3/01 -0500, Berin Loritsch wrote:
>Peter Donald wrote:
>>
>> Maybe what would be to refactor the *Info into something useful to both
>> Phoenix/Cocoon.
>
>The big thing is that it would have to be part of Avalon--there is no sense
>in including a server with a servlet.
right.
>The framework I created is for Components. It works quite well in that
scope.
>I would be sad to see it deal exclusively with Blocks.
agreed - but I was queriny what he was using it for ;)
>Here is my input: I refactered Cocoon so that Cocoon can have a good
foundation
>for ComponentManagement and Selection. If we move that framework into
Avalon,
>it benefits a wider population. If we move it to Camelot or Pheonix, then we
>again narrow our focus and the classes are of no use to Cocoon--why move
them?
>They _need_ to be in Avalon, and then specializations can be made in Camelot
>or Pheonix. I propose moving the Component framework to Avalon, with a
really
>simple Role tool, and then we can create specializations that would really
>benefit Camelot or Pheonix.
I think you are mistaking camelot (container sub-package in jakarta-avalon)
for cornerstone (separate cvs in jakarta-avalon-cornerstone) ;) Yes it
would not make a lot of sense to move it out of the core framework. As long
as it was simple all projects who use the framework should be able to use
this design.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
