Date: 2004-03-02T18:56:40
Editor: AaronFarr <[EMAIL PROTECTED]>
Wiki: Apache Avalon Wiki
Page: AvalonRoadmap
URL: http://wiki.apache.org/avalon/AvalonRoadmap
initial list of concerns taken from recent email threads -farra
Change Log:
------------------------------------------------------------------------------
@@ -1,6 +1,6 @@
-= Avalon Roadmap =
+= Avalon 5 (Spearhead) Roadmap =
-Here's an effort to define Avalon for 2004. Please join in!
+Here's an effort to define Avalon 5 (once codenamed Spearhead). Please join in!
The '''process''':
@@ -16,7 +16,41 @@
== Concerns and Goals ==
-Okay, here's your chance to be heard! What's important to '''you'''? Where do you
see Avalon in a year or two from now? What itches do you want scratched?
+Okay, here's your chance to be heard! What's important to '''you'''? Where do you
see Avalon in a year or two from now? What itches do you want scratched? ''These are
in '''no''' particular order!''
+
+ * "Put Avalon4 into maintenance and get on with Avalon5"
+ * Create an Avalon TCK, or set of TCK's including specs and tools (only worry
about A5 for now?)
+ * One scalable container solution per language. ie- a real reference implementation
+ * Define Fortress as the Avalon 4 reference implementation. Promote Merlin as the
eventual Avalon 5 reference implementation.
+ * Define an Avalon security model (include support for JAAS?)
+ * automated component publishing
+ * Container facilities: http, jmx, jms, iiop, rmi (altrmi)
+ * Support various IoC "types" (isn't that Avalon PI?)
+ * Cross container interoperability ( A5 should support A4 via adaptors. )
+ * publisher federation technologies (''uh, what is this? :)'')
+ * Single meta format (between A4 and A5?)
+ * Service Availability contract in the framework
+ * Circular dependency handling
+ * JCA client for/in Avalon
+ * Full Tutorial
+ * Update of "Developing With Avalon"
+ * Cooperation with the Repository/Depot folks and our own repository code
+ * Better (re)use and cooperation with Jakarta Commons -- stop reinventing code,
prefer Commons solutions to home grown when possible
+ * Make A5 "simplier" -- less axioms to learn, more intuitive
+ * Unit Tests!
+ * IDE plugins (like Merlin Developer)
+ * "Codenames"
+ * Merlin = Avalon 5 container (should support A4 -- ECM/Fortress)
+ * Fortress = the Avalon 4 reference implementation
+ * Spearhead = ??? (enhancements, adjustments to the actual framework?)
+ * For Avalon 5 nothing should be sacred. Depricate or actually drop marker
interfaces, etc.
+ * Better documentation of Merlin's decomposition -- how it works together, what's
the absolute smallest container you could build from it
+ * An Avalon "kitchen sink" distribution -- a full fledges Avalon app server like
EnterpriseObjectBroker
+ * Cooperation and discussion with the larger IoC Community -- get ideas and
discussions with JContainer people, Pico, Spring, etc.
+ * Component libraries -- what to do with Cornertone and Excalibur? What stays in
Avalon, what goes to Commons or elsewhere. Will Avalon host a Component
library/registry?
+ * Migration tools and documentation from A4 to A5
+ * A JSR?
+ * ... ''add more by editing this page'''
== Roadmap Milestones ==
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
