Paul Hammant wrote:
> Vincent,
>
>> Paul,
>>
>> I'm really interested in your approach. IIUC correctly, we're trying to
>> share common mechanism by inheritance and have different component
>> "front
>> ends" to support different containers. I have been thinking recently
>> on the
>> best way to make the AAA framework both Pico and Avalon compatible. I
>> was
>> hoping we could support both containers in a single implementation (as
>> opposed to having PicoContainer and Avalon implementations), for the
>> sake of
>> simplicity, and that's the path I have investigated. The downside of
>> it is
>> that as we add support for different containers, it might not always be
>> possible, so I don't know if this is something we would like to do. You
>> surely have think of this before.
>>
>>
> I like the style I have done as it reduces the jar bloat of a for
> users of teh frameworks in question. For example, Pico users would
> not like to see avalon-framework.jar as a requirement for using
> directory/ldapd
This is a function of the container - for example, Merlin users don't
see avalon or merlin - they see services.
Cheers, Steve.
--
Stephen J. McConnell
mailto:mcconnell@apache.org
|------------------------------------------------|
| Magic by Merlin |
| Production by Avalon |
| |
| http://avalon.apache.org/merlin |
| http://dpml.net/ |
|------------------------------------------------|
|