Java Enterprise and Web Technologies

In Struts 1.x, ActionServlet serves as the Front Controller - it's the single entry point that receives all HTTP requests and delegates them to appropriate Action classes based on the struts-config.xml mapping. Action classes handle business logic, ActionForm holds form data, but ActionServlet is the centralized dispatcher implementing Front Controller.

Struts was originally developed by Craig McClanahan over a long holiday weekend in 2000 as a way to solve common web application development problems. It was not developed through an online exchange (A), not as a commercial package (C), and was donated to the Apache Software Foundation.

The Application Resources file (which contains i18n messages) is configured via the servlet init-param named 'application' in web.xml. This parameter specifies the base name of the resource bundle. Options B, C, and D are incorrect parameter names for this configuration.

The 'validating' init-param of ActionServlet controls whether Struts validates its configuration file against the DTD. When set to true, it bypasses this validation (option B). It does NOT bypass ActionForm validation (A) - that's controlled differently. Option C is incorrect as message key errors are handled separately.

In Struts 1.x, to create a default/fallback ActionMapping that handles requests not matching any other mapping, you set the 'unknown' property to true on that mapping (option C). This is commonly used for 404-style handling. Option A is incorrect, B uses wrong property name, and D references a non-existent init-param.

In Struts 1.1, the form population mechanism was moved from ActionForm to RequestProcessor. To customize how forms are populated, you override the processPopulate() method of RequestProcessor (option B). Option A is incorrect - ActionForm doesn't have a populate method, and C references a non-existent method.

JSP's key advantage over Servlets is the ability to embed Java code directly within HTML pages using special tags like <% %>. This makes JSP pages more natural for web designers and separates presentation from business logic more cleanly. While JSP does offer platform independence and can create database-driven applications, these are not unique advantages over Servlets. Server-side programming is common to both.

JSP has three lifecycle methods: jspInit() is called when the JSP is first initialized (similar to servlet init), jspService() is called for each request (the _jspService method handles the actual processing), and jspDestroy() is called when the JSP is being taken out of service. There is no jspEnd() method in the JSP lifecycle specification.

xhrPost (note: typically lowercase in Dojo documentation) is a function for making asynchronous HTTP POST requests to a server, sending data as part of the request. It's used for AJAX-style form submissions and data transmission. Option A correctly describes this. Option B describes dojo/console, Option C describes the parser module.

Adapter pattern is called Wrapper because it wraps an existing class with a new interface, allowing incompatible interfaces to work together. A Proxy controls access, Surrogate is another name for Proxy, and Token is unrelated to structural adaptation.

Bridge pattern is also known as Handle/Body because it separates abstraction (handle) from implementation (body), allowing them to vary independently. This decoupling prevents the permanent binding between abstraction and implementation that occurs with monolithic designs.

The question asks to select SR types from the list. Application Support, Program Change, and Emergency Change are standard service request categories. Fixed Variable and Variable are not SR types. The 'All of the Above' option is logically incorrect because D and E should not be selected.

JAX-RPC provides three invocation models for calling web services: static stubs generated from WSDL by tools, the Dynamic Invocation Interface (DII) for runtime calls without compile-time stubs, and dynamic proxies that combine type safety with runtime flexibility. These models give developers different trade-offs between convenience and flexibility when invoking services.