Whenever you have felt the need of handling collections of objects, you
never began by developing your own arraylist; you implement the collection API
(application programming interface). Similarly, whenever you need a simple Web
application or a transactional or a distributed
application which is secure and interoperable, you never develop all the low-level APIs: all you do is use the
Enterprise Edition of Java. We know that Java Standard Edition (Java SE) supplies us an
API to handle collections, similarly Java EE supplies us a standard way to handle messaging with Java Message Service (JMS), transactions with Java Transaction API (JTA), or persistence with Java Persistence API (JPA). Java EE is nothing more than a set
of specifications intended to be used while developing enterprise applications. It is an
extension of Java SE to some extent which facilitates the development of distributed, powerful, robust, and highly reliable applications.
Java EE 7 has turned out to be a very valuable asset as it follows the principles of Java EE 6 by ensuring that the development
model is easy, but it also includes newer specifications. New functionalities have been added to existing specifications as well. We can say that, Context and Dependency Injection
(CDI) is integrating all these new specifications. Java EE 7 has the advantages of the Java language with
experience gained over the last 13 years as its release coincides with 13th anniversary of Java EE. Java EE is a well-documented platform .It has large number of experienced developers, an extremely large and welcoming community, and many live applications
running on servers of various companies. Java EE is a collection of APIs used to
build standard component-based multitier applications. Components need to be deployed in different containers offering a variety of services.
No comments:
Post a Comment