What the Spring likelihood Framework will be

Are you the Spring* Framework advocator? We can explore those common parts, whichever the Spring* are implemented by Java, dotNET, Ruby or others.

 

1. Spirited community (No matter it is Generic Programing Language or Dynamic Language), you should bet more guys will be interested in that for the future growing.
2. Inversion of Control - You are allowed to define the blue prints for wiring classes together. Considering using XML configuration to decorate them.
3. Aspect Oriented Programming - You can wrap advices and objects by this way, the smart usage are about remoting, debugger, and performance tracing.
4. Data Access - Reading from the database requires a monotonous cycle of opening cursors, reading rows and closing cursors, along with exception handlers. With the template class, SQL query is just enough.
5. Transaction Management - It can provides multiple ways to more readily manage wrapping business logic with transactions.
6. Security - It should provide plug-in support security interceptors to lock down access to your methods.
7. Remoting - It is easy to convert your local application into a distributed one, if you have already built your client and server pieces using the IoC container, then rely on the configuration change to go from local to distributed.
8. Plug-ins: Use the plug-in system designed to help you rapidly develop applications.