Introduction to Java 2 Enterprise Edition About myself –Neutrinos, Cancer Research, IT Applications Today’s topic: J2EE –Context –Advantages –Components.
Published byModified over 6 years ago
Presentation on theme: "Introduction to Java 2 Enterprise Edition About myself –Neutrinos, Cancer Research, IT Applications Today’s topic: J2EE –Context –Advantages –Components."— Presentation transcript:
Introduction to Java 2 Enterprise Edition About myself –Neutrinos, Cancer Research, IT Applications Today’s topic: J2EE –Context –Advantages –Components –Architecture Lecture method –Informal, Interactive
Context of J2EE Role of J2EE in IT Applications Brief History –Role of Java in IT Role of Telecommunications Comparison with other technologies –.NET
Advantages Standard architecture, –greater choices in tools, servers, etc Scalability –Distributed computing Developer productivity –Object Oriented language Run-time configurability
Advantages (continued) Portability –Works on many platforms Access to existing systems –JDBC, JNDI, JNI, Connectors Flexibility in security, transactions, etc.
Common Components of J2EE 1.3 HTTP 1.0 and HTTPS (HTTP 1.0 over SSL 3.0) –Existed before, is a Prerequisite JavaServer Pages 1.2 and Servlet 2.3 API –Add dynamism to the web EJB 2.0, Enterprise JavaBeans –Allow partitioning into tiers
Connection APIs JDBC 2.0 –Database operations JNDI 1.2, Java Naming and Directory Interface –Locating resources JCA 1.0, J2EE Connector Architecture –Access to enterprises applications like ERP JavaIDL, –Java 2 access to CORBA services JTA 1.0.1 and JTS, Java Transaction API and Service
Web Services JAXP 1.1, Java API for XML Processing JAX-RPC, Java API for XML-based RPC JAXR, Java API for XML Registries JAXB, Java Architecture for XML Binding JAXM, Java API for XML Messaging
Other Services JAAS 1.0, Java Authentication and Authorization Service JavaMail 1.2 and JAF 1.0 Java RMI JMS 1.0.2, Java Message Service for asynchronous exchanges
MVC Architecture Model –Application Data and Business Rules View –Rendering of model contents Controller –Translate user input to model actions
MVC Actions Model –Notify view about data updates View –Change rendering as needed Controller –Select view to be rendered Based on event notifications and method invocations