Jave Enterprise Edition in Egypt By AMIT Learning
There is a great demand for experienced J2EE professionals now in the market and students and programmers from other languages want to know whether J2EE is Java at all or something else.
With the Java Platform, Enterprise Edition (Java EE), development of Java enterprise applications has never been easier or faster. The aim of the Java EE platform is to provide developers a powerful set of APIs while reducing development time, reducing application complexity, and improving application performance.
To truly understand J2EE and how it can help you do your job, it is important to know exactly what it is and how it came to be. Once you have done that, then understanding the architecture and technology of J2EE makes much more sense.
Building from that knowledge, we can then examine the architecture of J2EE—how applications should be architected using this technology. This Introduction covers these basic architectural concepts, building on the technical discussion of J2EE and progressing to an architectural view.
J2EE leaped onto the scene in 1999. Considering the historical context of this product release you find that the cost of creating, deploying, and maintaining PC-based client/server software was becoming increasingly expensive. Partly in response to this, interest in the Internet and Web applications had been gathering steam for several years.
The Java Development Kit (JDK) is split into three parts: Java 2 Standard Edition (J2SE), Java 2 Enterprise Edition (J2EE), and the Java 2 Micro Edition (J2ME). This split provided a convenient repackaging of the myriad APIs that was Java. What is confusing in relation to J2EE is that the J2SE is part of the J2EE release. In order to run the J2EE, the J2SE must be installed. To avoid this confusion, you should think of the J2SE as the core Java installation component. J2EE is built on the J2SE.
J2EE includes a number of APIs; the most important and the ones most frequently associated with J2EE are EJBs (Enterprise JavaBeans), JSPs, and servlets. The EJB specification preceded the J2EE specification and was no doubt partly intended to improve the portability of these components.
J2EE Architecture consists of following technologies:
· Java Database Connectivity (JDBC)
· Java Naming and Directory Interface (JNDI)
· Enterprise Java Beans (EJB)
· Java Server Pages (JSP)
· Java Servlets
· Remote Method Invocation (RMI)
· Java IDL/CORBA
AMIT Learning , aided with its experienced instructors, tries to provide real work experience in the java EE world. Our courses follow the standard track from oracle which guarantees the professionalism and effectiveness of its courses.
for more information contact us:
01096971990 - 27507627
There is a great demand for experienced J2EE professionals now in the market and students and programmers from other languages want to know whether J2EE is Java at all or something else.
With the Java Platform, Enterprise Edition (Java EE), development of Java enterprise applications has never been easier or faster. The aim of the Java EE platform is to provide developers a powerful set of APIs while reducing development time, reducing application complexity, and improving application performance.
To truly understand J2EE and how it can help you do your job, it is important to know exactly what it is and how it came to be. Once you have done that, then understanding the architecture and technology of J2EE makes much more sense.
Building from that knowledge, we can then examine the architecture of J2EE—how applications should be architected using this technology. This Introduction covers these basic architectural concepts, building on the technical discussion of J2EE and progressing to an architectural view.
J2EE leaped onto the scene in 1999. Considering the historical context of this product release you find that the cost of creating, deploying, and maintaining PC-based client/server software was becoming increasingly expensive. Partly in response to this, interest in the Internet and Web applications had been gathering steam for several years.
The Java Development Kit (JDK) is split into three parts: Java 2 Standard Edition (J2SE), Java 2 Enterprise Edition (J2EE), and the Java 2 Micro Edition (J2ME). This split provided a convenient repackaging of the myriad APIs that was Java. What is confusing in relation to J2EE is that the J2SE is part of the J2EE release. In order to run the J2EE, the J2SE must be installed. To avoid this confusion, you should think of the J2SE as the core Java installation component. J2EE is built on the J2SE.
J2EE includes a number of APIs; the most important and the ones most frequently associated with J2EE are EJBs (Enterprise JavaBeans), JSPs, and servlets. The EJB specification preceded the J2EE specification and was no doubt partly intended to improve the portability of these components.
J2EE Architecture consists of following technologies:
· Java Database Connectivity (JDBC)
· Java Naming and Directory Interface (JNDI)
· Enterprise Java Beans (EJB)
· Java Server Pages (JSP)
· Java Servlets
· Remote Method Invocation (RMI)
· Java IDL/CORBA
AMIT Learning , aided with its experienced instructors, tries to provide real work experience in the java EE world. Our courses follow the standard track from oracle which guarantees the professionalism and effectiveness of its courses.
for more information contact us:
01096971990 - 27507627
