Chances are you've heard the term service-oriented architecture (SOA). It
describes a software architecture in which reusable services are deployed
onto application servers and then consumed by clients in different
applications or business processes. If you've tried to find information on
SOAs, the chances are also good that you found a description that includes
Web services, often exclusively. This might have led you to the conclusion
that if you aren't using Web services, you have no need for SOAs. This
couldn't be further from the truth.
The problem starts with the definition. SOAs are designed to decouple the
implementation of a software service from the interface that calls that
service. This allows clients of a service to rely on a consistent interface
regardless of the implementation technology of the service. Instead of
building big, monolithic applications... (more)
As the Java 2 Enterprise Edition (J2EE) platform continues to grow and gain
ground in corporations and the battle between Java and Microsoft .NET
intensifies, more and more companies are looking for help in building their
J2EE applications.
With the large number of standard technologies available, all being exposed
at the programming interface or metadata level, making sense of what, when,
and how to use these technologies is becoming harder.
This problem opens the door for J2EE frameworks tools and applications
that manage much of the complexities of the underlying J2EE data, ... (more)