Date: 2004-10-01T11:40:00 Editor: HamiltonVerissimo <[EMAIL PROTECTED]> Wiki: Incubator Wiki Page: CastleProposal URL: http://wiki.apache.org/incubator/CastleProposal
no comment Change Log: ------------------------------------------------------------------------------ @@ -8,6 +8,104 @@ Temporary name. -=== Item === +=== Rationale === + +A empty space lies in the open source community for those who happens to use CLI +running on Windows (.Net Framework from MS) and|or Linux (Mono). This empty space refers to a model which set the example, as reference of how to build a Good Application (tm) from the developer's point of view. + +Of course there are several aspects that contribute to create a Good Application, and from our standpoint one them is Inversion of Control, which deserves attention. However the usage of Inversion of Control is a matter of taste, and people should not feel obligate to use, or might disagree with the benefits. + +Castle's goal is to provide a set of standalone tools and an Inversion of Control implementation that provide a rendezvous point for these tools - and possible other - although they are totally independent. Initially our set of tools will consist of: + +* Aspect# +* DynamicProxy +* ManagedExtensions +* Castle Microkernel + +And the container + +* Windsor + + +'''Aspect#''' + +AOP is an AOP framework for CLI. It uses dynamic proxies to generate new types on the fly which implements your aspect rules. Aspect# gained attention since the first day it was released. It's easy to say why: its based on simplicity. We don't rely on creepy xml configuration files, instead a simple configuration language (inspired by Ruby) was conceived. +Aspect# extends an application providing mixins and method interceptors easily. Within a few months of existence, Aspect# had more than one thousand downloads. + + +'''DynamicProxy''' + +DynamicProxy generates proxies for interfaces or classes on the fly through the generation of IL code, just like Java proxies, which is unavailable in CLI. +It's been used by Aspect#, NHibernate project and Castle and we already had some nice testemonials and some suggestions for the next version. + +'''ManagedExtensions''' + +ManagedExtensions is an application extension inspired by Java Management Extensions. As JMX it directs the overall application architecture but simplify some other aspect like remoting access to applications, configuration and service invocation. + +'''Castle Microkernel''' + +If one only wants a very simple - almost naive - Inversion of Control container to set up and assemble his application he can rely on Castle Microkernel to do so. +The microkernel is easily extensible orthogonally, which means that features can be plugged and transparently combined to achieve a major goal. + +'''Castle Windsor ''' + +If one wants a more complex container it can uses the Windsor container which extends the Microkernel to provide a more complex solution. It aims to provide external configuration, configuration overriding, subcontainers and a profile concept that will allow the user to switch to different configurations modes, ie 'production', 'development', 'profiling'. + +The profile only defines a set of service implementation and facilities configurations. + +Castle's goal is to serve as an umbrella for some problem-resolution stardards and default implementation of these standards - for the CLI world. Meanwhile it will provide a simple yet powerfull inversion of control container. + +----- + +'''More Orthogonal extensions''' + +We're are concern to not reinvent the wheel, so we plan to offer adapters to existent open source solutions provided that licenses are compatible with ASF. We plan to support, for instance: + +* PersistenceLayer + + - Ibatis.Net + - NHibernate + - OJB.Net + - Prevayler + +* SecurityLayer + + - To be analyzed + +* PresentationLayer + + - Maverick.Net + - NVelocity + - ASP.Net (possibly not available due to Microsoft license, to be analyzed) + + +'''Plans for the future''' + +Inspired by Ruby language and concepts we're going to provide a more easily way of configure and use applications, in an attempt to avoid XML descriptors, complex deployments, complex setup and steep learning curve. This is subject to research, but should be constantly in our minds when planning and coding. + + +==== Criteria ==== + +===== Meritocracy ===== + +We've been living in meritocracy environment with the project we've been involved to and even from our work environment. We plan to support meritocracy by all means, setting the example with every message posted to the list. + +===== Community ===== + +The Aspect# project have three developers involved, and the Castle container has only one. This incubation process has the objective of attract more contributors, new ideas, new perceptions and even new use cases that will drive our roadmap. + + +===== Core Developers ===== + +Currently only the people that are already involved with these projects. People that are involved with this project as user may be invited to join our efforts as well. + + +===== Alignment ===== + +We're concern in not delivering only Microsoft CLI compatible code so the project must be tested against Mono before being release. For logging purposes we're going to use log4net available through the ASF Logging TLP. +For building purposes we're currently using NAnt, which is a port of Apache ANT, but its licensed as GPL. Test cases are implemented using NUnit, a port of JUnit, another standard and is currently licensed as zlib/libpng License. + + +==== Warning Signs ==== + -=== Second item === --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
