Skills required for Sun test CX310-081

Skills required for Sun test CX310-081

Rating:

Sun has specified more than 42 objectives for Sun test CX310-081 (Sun Certified Web Component Developer for the Java 2 Platform, Enterprise Edition 1.4). These objectives are grouped under 11 topics. Before taking the test, an individual should possess a good command over the following areas:

• Using the HTTP methods such as GET, POST, HEAD, and so on, and identifying the HttpServlet method that corresponds to the HTTP Method. Describing the purpose and event sequence of the Servlet life cycle.
  
Using the HttpServletRequest interface for writing code to retrieve HTML form parameters from the request, retrieving HTTP request header information, and retrieving cookies from the request. Using the HttpServletResponse interface for writing code to set an HTTP response header, setting the content type of the response, acquiring a text stream for the response, acquiring a binary stream for the response, redirecting an HTTP request to another URL, and adding cookies to the response.

• Constructing the file and directory structure of a Web Application that may contain (a) static content, (b) JSP pages, (c) Servlet classes, (d) the deployment descriptor, (e) tag libraries, (f) JAR files, and (g) Java class files. Describing how to protect resource files from HTTP access. Describing the purpose and semantics of the deployment descriptor and constructing the correct structure of the deployment descriptor. Describing the purpose and contents of a WAR file.
  
• Writing Servlet code to access initialization parameters and creating the deployment descriptor elements to declare initialization parameters. Writing Servlet code for using various attribute scopes (request, session, and context) for adding, retrieving, and removing attributes. Describing the use of a filter and a wrapper and writing code to configure them.
  
• Describing the life cycle of a listener, creating and configuring a listener, and for a given scenario, identifying proper attribute listeners to use. Writing Servlet code to create a request dispatcher, and to forward and include the target resource. Writing Servlet code to store objects into a session object, retrieving objects from a session object, and describing the mechanisms used to destroy the session object.
  
• Using session listeners, writing code to respond to an event when an object is added to a session, and writing code to respond to an event when a session object migrates from one VM to another.
  
• Given a scenario, describing which session management mechanism the Web container could employ, how cookies might be used to manage sessions, how URL rewriting might be used to manage sessions, and writing Servlet code to perform URL rewriting.
  
  
• Describing the following security mechanisms: (a) authentication, (b) authorization, (c) data integrity, and (d) confidentiality. Writing code to use these mechanisms. Writing deployment descriptor elements to declare a security constraint, a Web resource, the transport guarantee, the login configuration, and a security role. Comparing the following authentication types: BASIC, DIGEST, FORM, and CLIENT-CERT.
  
• Writing JSP code for the following elements: (a) template text, (b) scripting elements (comments, directives, declarations, scriptlets, and expressions), (c) standard and custom actions, and (d) expression language elements. Writing code to use the following directives: page, include, and taglib.
  
• Describing the event sequence of the JSP page life cycle as follows: (1) JSP page translation, (2) JSP page compilation, (3) load class, (4) create instance, (5) call the jspInit method, (6) call the _jspService method, and (7) call the jspDestroy method and, for a given scenario, using the appropriate implicit objects: (a) request, (b) response, (c) out, (d) session, (e) config, (f) application, (g) page, (h) pageContext, and (i) exception.
  
• Configuring the deployment descriptor for deactivating the evaluation language, and deactivating the scripting language. Writing code for including a JSP segment in another page and the appropriate inclusion mechanism (the include directive or the jsp:include standard action).
  
• Writing EL code that accesses the following implicit variables: pageScope, requestScope, sessionScope, and applicationScope, param, and paramValues, header and headerValues, cookie, initParam and pageContext. Writing EL code that uses the property access (the . operator) and collection access (the [] operator).
  
• Writing EL code that uses the following operators: arithmetic operators, relational operators, and logical operators. Writing EL code that uses a function and configuring the EL function in a tag library descriptor.
  
• Writing code using the following standard actions: jsp:useBean (with attributes: 'id', 'scope', 'type', and 'class'), jsp:getProperty, jsp:setProperty (with all attribute combinations), jsp:include, jsp:forward, and jsp:param.
  
• Creating the taglib directive for a JSP page and writing custom tag for a given design goal. Using an appropriate JSP Standard Tag Library (JSTL v1.1) tag from the core tag library.
  
  
• Describing the semantics of the "Classic" custom tag event model and describing what is returned when each event method (doStartTag, doAfterBody, and doEndTag) is executed.
  
• Using the PageContext API for writing tag handler code to access the JSP implicit variables and accessing Web application attributes.
  
• Writing a tag handler code to access the parent tag and an arbitrary tag ancestor. Describing the semantics of the simple custom tag event model when the event method (doTag) is executed.
  
• Describing the semantics of the Tag File model, writing a tag file, and explaining the constraints on the JSP content in the body of the tag.
  
  
• Matching design patterns with statements describing potential benefits that accrue from the use of the following patterns: Intercepting Filter, Model-View-Controller, Front Controller, Service Locator, Business Delegate, and Transfer Object.

Rating: