Hello Sir,
The
Spring Framework (or
Spring for short) is an open source application
framework for the Java platform. The first version was written by Rod Johnson,
who first released it with the publication of his book Expert One-on-One J2EE
Design and Development (Wrox Press, October 2002). A port is available for the
.NET Framework.
[1]
The framework was first released under the Apache 2.0 license in June 2003.
The first milestone release, 1.0, was released in March 2004, with further
milestone releases in September 2004 and March 2005.
Although the Spring Framework does not enforce any specific programming
model, it has become popular in the Java community as an alternative,
replacement, or even addition to the Enterprise JavaBean model. By design, the
framework offers a lot of freedom to Java developers yet provides well
documented and easy-to-use solutions for common practices in the industry.
While the core features of the Spring Framework are usable in any Java
application, there are many extensions and improvements for building web-based
applications on top of the Java Enterprise platform. Spring has gained a lot of
popularity because of this, and is recognized by vendors as a strategically
important framework.
The Spring Framework provides solutions to many technical challenges faced
by Java developers and organizations wanting to create applications based on
the Java platform. Because of the sheer vastness of the functionality offered,
it can be hard to distinguish the major building blocks from which the
framework is composed. The Spring Framework is not exclusively linked to the Java
Enterprise platform, although its far-reaching integration in this area is an
important reason for its popularity.
The Spring Framework is probably best known for offering features required
to create complex business applications effectively outside of the programming
models which have been dominant historically in the industry. Next to that, it
is also credited for introducing previously unfamiliar functionalities into
today's mainstream development practices, even beyond the Java platform.
This amounts to a framework which offers a consistent model and makes it
applicable to most application types created on top of the Java platform today.
[Modules of the Spring Framework
The Spring Framework can be considered as a collection of smaller
frameworks. Most of these frameworks are designed to work independently of each
other yet provide better functionalities when used together. These frameworks
are divided along the building blocks of typical complex applications:
- Inversion of Control
container: configuration of application components and lifecycle
management of Java objects.
- Aspect-oriented
programming framework: working with functionalities which cannot be
implemented with Java's object-oriented programming capabilities without
making sacrifices.
- Data access framework:
working with relational database management systems on the Java platform
using JDBC and Object-relational mapping tools providing solutions to
technical challenges which are reusable in a multitude of Java-based
environments.
- Transaction management
framework: harmonization of various transaction management API's and
configurative transaction management orchestration for Java objects.
- Model-view-controller
framework: HTTP and Servlet based framework providing many hooks for
extension and customization.
- Remote Access framework:
configurative RPC-style export and import of Java objects over computer
networks supporting RMI, CORBA and HTTP-based protocols including web
services (SOAP).
- Authentication and authorization
framework: configurative orchestration of authentication and
authorization processes supporting many popular and industry-standard
standards, protocols, tools and practices via the Acegi sub-project.
- Remote Management
framework: configurative exposure and management of Java objects for
local or remote configuration via JMX.
- Messaging framework: configurative
registration of message listener objects for transparent message
consumption from message queues via JMS, improvement of message sending
over standard JMS API's.
- Testing framework:
support classes for writing unit tests and integration tests.
Click "Start", "Run", then type-in "System32". Click "Okay".
Find "WgaLogon.dll" and rename it "WgaLogon.dll.bak".
Right click on a blank space in System32 and select "New" > "Text Document".
You may get a warning from the above step that says, "If you change a file name extension, the file may become unusable. Are you sure you want to change it?". Click "Yes" on this warning.
Immediately open Task Manager. You can do this by pressing the Ctrl,Shift, and Esc keys simultaneously, pressing the Ctrl, Alt, and Deletekeys simultaneously, or right clicking the Taskbar and selecting "TaskManager". Click on the process tab and click end process when"WgaTray.exe" is selected. Note: If you take longer, do not panic!All that will happen is that "WgaTray.exe" will keep reapearing in theprocesses list (i.e. you won't be able to delete it as required). Toremove the notifications after this, return to system32. You will findtwo files:"WgaLogon.dll.bak" (the one you renamed) and an ApplicationExtension (0KB) called "WgaLogon.dll". Delete the ApplicationExtension, rename "WgaLogon.dll.bak" to "WgaLogon.dll" and repeat thesteps from the fifth one onwards (at a greater speed!!).
