Il fait beau. C’est super chaud!! Quelle chaleur! Après avoir fait les choses sur mon agenda, j’ai commencé à toucher un p’tit peu le J2EE. C’est parti.

Two types of components deployed, managed, and executed on a J2EE Server.

  • Web Components (Servlet and JSP)
  • EJB Components
    • Session EJB: mapping business process flow
    • Entity EJB: maps a combination of data (usually based on an underlying data store and will be created based on that data within it)
    • Message-Driven EJB: very similar in concept to a session EBJ, but is only activated when an asynchronous message arrives.

A J2EE application will consist of the following:

  • Zero or more Web components packaged as Web Archives (WAR files)
  • Zero or more EJB components packaged as EJB-JAR files
  • Zero or more client components packaged as JAR files
  • Zero or more connectors packaged as Resource Archives (RAR files)

To this end, all of the components in a J2EE application are stored in a particular type of JAR file called an Enterprise Application Archive or EAR.

So far so good, a J2EE application server, like WebLogic, plus a database (DB2, Oracle, SyBase, MySQL, Access… whatever), and a SP maybe, this solution fit for the current trend in today’s enterprise program development and n-tier frameworks aimed at delivering applications that are secure, scalable, and availab.e