Java Server Pages and the Java 2 Enterprise Edition Model - Essay Example

JAVA SERVER PAGES By Java Server Pages (JSP) JavaScript is also known as ECMAScript. It is basically an object oriented scripting language which was originally developed by Netscape Communications (Henderson 2009, p.256). According to Henderson, Java Script is one of the several computing languages that can enable the quick and efficient interaction of Web pages (2009, p. 256). It was first referred to as LiveScript but it then renamed to JavaScript after which it was given a syntax closer to that of the sun Micro System. Technically, this change occurred during the apparent time that NetScape was including the support for java technology in its popular NetScape navigator browser (Henderson 2009, p.256). This change however brought up much confusion since there was absolutely no clear relationship between Java and Java Script. In fact, apart from using some similar syntaxes, their only other similarity is that both languages are usually used comprehensively on the World Wide Web. This type of language is relatively easy to use. It provides an option for addition of other additional features such as 3 Dimensional buttons and pop-up windows. Java Server Pages (JSP) is a technology that offers a simple way of creating lively and attractive web scripts (Horton 2011, p. 2). The JSP employs the use of a component based approach. This approach permits web developers to combine static HTML with Java components easily so as to produce dynamic features. According to Horton, the component-based model is quite simple in its functioning (2011, p. 2). This component is combined with the cross-platform power of Java thereby allowing the development of a web environment that has a huge importance in the running of applications. The Java Server Pages was added to the collection of Enterprise Java tools by Sun Microsystems in the year 1999 (Kogent Solutions Inc. [KSI] 2010, p. 1594). The JSP’s are usually built on top of the Java servlets and are aimed to intensify the effectiveness through which both experienced programmers and nonprogrammers can be able to generate web content. Put simply, JSP refers to a technology that enables one to develop web pages which contains dynamic content. As opposed to a plain HTML page that contains a stationary content, a JSP page usually has the ability to change its content based on any amount of variables (Hall & Brown 2004, p. 343). These variables could include items such as the identification of the handler, the operators browser type, the basic information delivered by the user, different selections made by the user among other aspects. The JSP functionality can therefore be used to in creation of networking applications such as and employee directories and information systems. Just like any other regular web page, a JSP script comprises of ordinary markup language components such as HTML tags (Metlapalli 2007, p. 167). However, it also contains exceptional JSP elements which enables the server to insert dynamic contents in to the script. JSP components have multiple variety of functions, for instance, they can be used in the retrieving information from a database or registering user preferences among others. As soon as the user requests for a JSP page, the server will execute the JSP elements, thereby amalgamating the outcomes with the static parts of the script, and finally it will send the dynamically processed script back to the browser. JSP describes a number of ordinary components that can be useful to any web application such as retrieving JavaBeans components, passing control between scripts and the sharing of information between applications, scripts, and the various operators. Consequently, programmers can also prolong the JSP syntax through the execution of the application precise components that can execute tasks like accessing the databases, sending of emails and the generation of HTML to present the data of a specific application (Zokowski 2006, p. 685-686). The amalgamation of ordinary components and custom components usually allows and facilitates the creation of web applications which are more powerful. The use of the JSP application can provide multiple benefits. During the early years, the Common Gateway Interface (CGI) was the solitary tool that was used in the development of the dynamic web contents. The CGI was however not an effective solution (Chopra, 2005, P. 10). This is so since when using the CGI, every request that is searched will result to the creation of a new operating system process by the web server, thereby making it to load an interpreter and a script. After this it will execute the script then break down again for the results to be posted. This process is quite demanding for the server and it does not measure well there is an increase in the amount of traffic. A couple of CGI substitutions and improvements have been created over the years. These improvements include Fast CGI, Apache’s mod Perl, Netscape’s NSAPI, Microsoft’s ISAPI and lastly Java Servlets from Sun Microsystems (Lane & Dulaney 2006, p.282). Even though these interfaces usually provides an improved performance and scalability, all of these technologies have a mutual problem. They usually create web pages by driving in the HTML straight in to the programming language code. This therefore impulses the creation of a dynamic web script entirely into the programmers’ territory (Chopra, 2005, P. 331). On the other hand however, Java Server Pages overcomes all that. Consequently, an additional benefit of the JSP script is that it is always amassed before it is send to the server to be processed. This is a plus over the older technologies such as CGI which usually necessitate the server to load a translator or an interpreter and the target script every single time that the page has been requested (Chopra, 2005, P. 10). JSP therefore rectifies this problem since it compiles every JSP page into an executable code during the first instance that the page has been requested. It then invokes the ensuing code directly on all the other following requests. The JSP can therefore allow the server to handle the pages much faster as compared to the other technologies. ISRD group points out that the use of JSP has several advantages (2007, p.488). Some of these advantages could include, It usually combines the most important features that are present in the other alternatives such as CGI, mod Pearl, ISAPI among others. It also has the ability to not support scripting but also the component based dynamic content. Furthermore, it usually enables the programmers to come up with customary tagged libraries that will satisfy the specific needs of the application. The JSP scripts can also be precompiled in order to increase the processing effectiveness, speed and the overall efficiency of the server. In addition, the JSP scripts could be used in conjunction with the servlets that have the ability to handle the business logic. Finally, JSP can compete with different applications thus increasing its overall performance and quality. JSP is therefore an integral part of the enterprise applications. Although the JSP has multiple advantages, Brown et al. points out that it also contains a number of disadvantages (2005, p.360-361). Some of its disadvantages include, Java programs are a usually expensive commodities. Accessing of the programs can be therefore a challenge to most of the programmers. Debugging JSP programs is also another key challenge. This is a JSP page is initially converted to a java file before it is compiled JSP has also Security Issues. For instance, when the JavaScript extracts are added to web pages, they execute on the client servers with immediate effect. This can hence be used to exploit the users system. Lastly, the use of different engine blueprints could extract the JavaScript differently thereby resulting in irregularity in the sense of functionality and interface. The Java 2 Enterprise Edition Model The Java 2 Enterprise Edition Model (J2EE) is an assembly of numerous Java APIs that have formerly been offered as separate packages, an Application Programming Model (APM), also known as the J2EE Blueprints, that describes how they can all be combined, and a test suite that J2EE vendors can use to test their products for compatibility. J2EE includes the following enterprise-specific APIs; Java Server Pages ( JSP) Java Servlets Enterprise JavaBeans (EJB) Java Database Connection ( JDBC) Java Transaction API ( JTA) and Java Transaction Service ( JTS) Java Naming and Directory Interface ( JNDI) Java Message Service ( JMS) Java IDL and Remote Method Invocation (RMI) Java XML In addition, all the J2SE APIs can be used when developing a J2EE application. These groups of APIs can be used in several arrangements. The first three APIs, that is, EJB, JSP, and servlets a different set of technologies that are managed by web containers. Usually, servlets and JSP pages are managed by a container which delivers the runtime setting for these components, interpreting requests and responses into ordinary Java objects. Similarly, EJB components are usually controlled by an EJB container. Components in the two types of containers (web and EJB), employ the use of other APIs to access databases, locate numerous resources, and communicate with other server resources such as Java IDL, RMI, and XML. The Enterprise applications are usually divided into a group of tiers. J2EE contains three tiers, they include, the client tier, the middle tier, and lastly the Enterprise Information System (EIS) tier. The middle tier can be further divided into the web tier and the EJB tier. Due to this logical separation and the existence of well-defined interfaces, it is possible to build mountable applications. Primarily, one or more tiers can be running on the same physical server. However, with increased demands, the tiers can be divided and disseminated over several servers using the same code but just by altering the configuration. The client tier contains browsers as well as regular GUI applications. The browser communicates with the web container using HTTP. A standalone application can also use HTTP or communicate directly with the EJB container using RMI or a CORBA protocol. Another type of client that is becoming more and more popular is the extremely thin client, such as a cellular phone or PDA. This type of client typically uses the Wireless Access Protocol (WAP), often converted into HTTP via a gateway, to communicate with the web container. The middle tier provides client services through the web container and the EJB container. A client that communicates through HTTP with the server uses modules in the web container, such as servlets and JSP pages, as entry points to the application. Many applications can be executed solely as web container components. In other applications, the web components just act as an interface to the application logic implemented by EJB components. A standalone application, written in Java or any other programming language, can also communicate directly with the EJB components. Components in this tier can access databases and communicate with other server applications using all of the other J2EE APIs. Lastly, The Enterprise Information System (EIS) tier holds the applications business data. Typically, it consists of a single or multiple relational database management servers, but other types of databases, applications, and mainframe transaction processing systems are also included in this tier. The middle tier uses J2EE APIs to communicate with the EIS tier. The J2EE has various strengths and weaknesses. According to Boone, the J2EE multiple strengths and minimal constraints on the implementation of the server (2003, p.499). These strength and weaknesses are as discussed below. STRENGTHS Contains a simplified architecture and development component based that helps in labor division and change deployment. Has scalability to meet demand variations like transaction support and load-balancing. Has the ability to integrate with existing information systems since it contains the integration APIs for: DBs, mail, CORBA, messaging and directories. It also contains a flexible security model that supports a wide range of security requirements. WEAKNESSES The principal cannot solitarily be used in the determination of the log in ID of the user. There is lack of a vendor independent way to add users to a role through the dynamic user registration. Lastly, the model does not offer support for the web based authentication other than using the password contest or user certificates. Works Cited Boone, K. (2003). Applied Enterprise JavaBeans technology. Upper Saddle River, NJ, Prentice Hall PTR. Print. Brown, S., & Mukhar, K. (2005). Pro JSP 2. Berkeley, CA press. Print. Chopra, V. (2005). Beginning Java Server pages. Indianapolis, Wiley. Print. Hall, M. (2004). Core Servlets and Java Server Pages 1, 1. Upper Saddle River, N.J., Prentice Hall PTR. Print. Henderson, H. (2009). Encyclopedia of computer science and technology. New York. Print. Horton, I., Gregoire, M., & Scherer, A. (2011). Ivor Hortons beginning Java, Java 7 edition. Indianapolis, John Wiley & Sons. Print ISRD Group. (2007). Introduction to object oriented programming through Java. New Delhi, Tata McGraw Hill. Print. Kogent Learning Solutions, Inc. (2010). Java server programming: Java EE5 (J2EE 1.5). New Delhi, India, Dream tech Press. Print. Lane, P. T., Sodeman, W., & Dulaney, E. (2006). CIWTM Foundations Study Guide (Exam 1D0-410). Hoboken, John Wiley & Sons. Print. Metlapalli, P. (2007). Java Server pages illuminated. Sudbury, Mass, Jones and Bartlett Publishers. Print. Zokowski, J. (2006). Mastering Java 2, J2SE 1.4. Hoboken, John Wiley & Sons. Print. Read More