Date: 2004-07-23T08:30:44
Editor: UgoCei <[EMAIL PROTECTED]>
Wiki: Cocoon Wiki
Page: ButterflyManifesto
URL: http://wiki.apache.org/cocoon/ButterflyManifesto
no comment
Change Log:
------------------------------------------------------------------------------
@@ -24,6 +24,16 @@
* integrates well with other useful technologies (Hibernate, JDO, OJB,
EJB, Struts, JMS, AOP ...) instead of trying to replace them
* fits perfectly in J2EE environments, where we expect Cocoon to be often
deployed.
+=== Build or buy? ===
+
+Even if the initial implementation will use Spring, some valid concerns have
been raised on the developers' mailing list. Basing our core on a framework
that is being developed elsewhere carries a certain amount of risk. If the
Spring community evaporates, goes down in flames like the Avalon one or takes a
road that is incompatible with our needs, we risk finding ourselves in the same
situation we are now. Moreover, Spring is not an ASF project.
+
+On the other hand, consider:
+
+ 1. The benefits that Spring can give.
+ 1. The fact that Spring's core is relatively small and thus maintaining a
fork wouldn't be unthinkable.
+ 1. The fact that Spring's design promotes a design whereby components do not
have dependencies upon the framework and thus could be moved to a different
container, as long as it supports Type 2 and Type 3 IoC, at least in principle.
+
== Design principles ==
1. Simplicity
