On Saturday 17 January 2004 15:45, Leo Simons wrote: > IMHO, it should be about delivering on the promise of reuse, even making > it rather difficult *not* to reuse. The Framework|Container split is so > useful because it allows (in theory; the practice so far has been quite > ugly) to keep the framework intact while replacing the container, and > still being able to use all the components.
YES, the Promise is there, but IMHO, the A-F is too weak. > In our ever-changing development world, we currently have "components" > using type-0, type-1, type-1.1, type-2, type-3, type-4, type-n IoC, > components that aren't IoC at all, javabeans, enterprise beans, eob > beans, corba components, soap services, RPC and XML-RPC services, > mbeans, singletons, static factories, and others. > Jicarilla is about making (potentially) all of these components work > together. And about me being stubborn, ignorant, and arrogant :D You will need a lot of good luck!!! Most of the components listed above doesn't even work between two different implementations of the same type of framework. Cheers, Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
