Skip to main content

Development Roles

The entire Web Development Process has following steps to be followed.

  1. Purchase and installation of J2EE products and tools.
  2. J2EE components can be developed by application component providers.
  3. Assembled by application assemblers.
  4. Deployed by application deployers.


 

J2EE Product Provider

  • Product providers are typically operating system, database system, application server, or web server vendors who implement the J2EE platform according to the Java 2 Platform, Enterprise Edition specification.


 

Tool Provider

  • The tool provider is the company or person who creates development, assembly, and packaging tools used by component providers, assemblers, and deployers.


 

Application Component Provider

  • The application component provider is the company or person who creates web components, enterprise beans, applets, or application clients for use in J2EE applications.


 

Enterprise Bean Developer

  • An enterprise bean developer performs the following tasks to deliver an EJB JAR file that contains the enterprise bean(s):
    • Writes and compiles the source code
    • Specifies the deployment descriptor
    • Packages the .class files and deployment descriptor into the EJB JAR file


 

Web Component Developer

  • A web component developer performs the following tasks to deliver a WAR file
  • containing the web component(s):
    • Writes and compiles servlet source code
    • Writes JSP and HTML files
    • Specifies the deployment descriptor
    • Packages the .class, .jsp, and.html files and deployment descriptor into the WAR file


 

Application Client Developer

  • An application client developer performs the following tasks to deliver a JAR file containing the application client:
    • Writes and compiles the source code
    • Specifies the deployment descriptor for the client
    • Packages the .class files and deployment descriptor into the JAR file


 

Application Assembler

  • The application assembler is the company or person who receives application modules from component providers and assembles them into a J2EE application EAR file. The assembler or deployers can edit the deployment descriptor directly or can use tools that correctly add XML tags according to interactive selections.
    • Assembles EJB JAR and WAR files created in the previous phases into a    J2EE application (EAR) file
    • Specifies the deployment descriptor for the J2EE application
    • Verifies that the contents of the EAR file are well formed and comply with the J2EE specification


 

Application Deployer and Administrator

  • The application deployer and administrator is the company or person who configures and deploys the J2EE application, administers the computing and networking infrastructure where J2EE applications run, and oversees the runtime environment. Duties include such things as setting transaction controls and security attributes and specifying connections to databases.
  • During configuration, the deployer follows instructions supplied by the application component provider to resolve external dependencies, specify security settings, and assign transaction attributes. During installation, the deployer moves the application components to the server and generates the container-specific classes and interfaces.
  • A deployer or system administrator performs the following tasks to install and configure a J2EE application:
    • Adds the J2EE application (EAR) file created in the preceding phase to the J2EE server
    • Configures the J2EE application for the operational environment by modifying the deployment descriptor of the J2EE application
    • Verifies that the contents of the EAR file are well formed and comply with the J2EE specification
    • Deploys (installs) the J2EE application EAR file into the J2EE server
Labels:

Popular posts from this blog

Primitive Obsession with Example

Primitive Obsession is the name of a code smell that occurs when we use primitive data types to represent domain ideas. For example, we use a string to represent a message or an integer to represent an amount of money. For Example: Code with Primitive Obsession // primitiveObsession.java public class primitiveObsession { public static void main ( String args []) { Integer [] cityPopulations = { 13000000 , // London 21903623 , // New York 12570000 , // Tokyo 1932763 , // Stockholm 1605602 , // Barcelona 4119190 // Sydney }; for ( Integer cityPopulation : cityPopulations ) { System . out . println ( cityPopulation ); } } } public class City { private final String name ; private final int population ; private final Continent continent ; public String getName () { return name ; } public int getPopulation () { return population ; } public Continent ge...
Read more

Singleton Pattern

Lazy Initialization :- The instantiation of an object can be delayed until it is actually needed. Usage: This especially beneficial when the constructor is doing a costly job like, accessing a remote database. Example: This code demonstrates how the Singleton pattern can be used to create a counter to provide unique sequential numbers, such as might be required for use as primary keys in a Database:   Sequence.java   public class Sequence { private static Sequence instance; private static int counter; private Sequence() { counter = 0; // May be necessary to obtain // starting value elsewhere... } public static synchronized Sequence getInstance() { if(instance==null) // Lazy instantiation { instance = new Sequence(); } return instance; } public static synchronized int getNext() { return ++counter; } }   Some things to note about this implementation: Synchronized methods are used to ensure that the class is thread-safe. This class cannot be subclassed because the constructor is private ...
Read more

Factory Pattern

This pattern is used when it must be decided at run time which one of several compatible classes is to be instantiated. For example, the abstract Collator class's getInstance() method returns a collation object that is appropriate for the default locale, as determined by java.util.Locale.getDefault() : Like other locale-sensitive classes, you can use the static factory method, getInstance, to obtain the appropriate Collator object for a given locale.  The following example shows how to compare two strings using the Collator for the default locale. Compare two strings in the default locale Collator myCollator = Collator.getInstance(); if( myCollator.compare("abc", "ABC") < 0 ) System.out.println("abc is less than ABC"); else System.out.println("abc is greater than or equal to ABC");
Read more