Computer Knowledge
Java Enterprise and Web Technologies
2,279 Questions
Java enterprise and web technologies questions focus on J2EE architecture, web services like SOAP, and servlet functionalities. These topics frequently appear in IT officer and specialist scale examinations. Regular practice ensures familiarity with enterprise application components.
HttpServlet methodsSOAP and web servicesEJB architecture rolesJ2EE componentsJSP servlet callingUDDI concepts
Java Enterprise and Web Technologies Questions
-
Embedded database
-
External RDBMS
-
File System
-
none
A
Correct answer
Explanation
For lightweight installations like running only the Messaging UI, My webMethods Server can use its embedded database (Apache Derby). External RDBMS is required for production but not for this limited use case.
C
Correct answer
Explanation
AJP13 (Apache JServ Protocol 1.3) is the port connector used to communicate between My webMethods Server and external web servers like Apache. It's the standard for Java application server integration.
-
deployMap.properties
-
phaseProvider.xml
-
mws.xml
-
deploy.xml
-
ConfigurationManagerProperties.xml
B
Correct answer
Explanation
The phaseProvider.xml configuration file controls deployment synchronization settings in MWS, including the deploySynch parameter that enables automatic portlet deployment. This file defines deployment phases and their associated behaviors.
-
Basic Components for Java
-
Basic Controller for Java
-
Business Components for Java
-
Business Controller for Java
C
Correct answer
Explanation
BC4J (Business Components for Java) is Oracle's framework for building J2EE business applications. It provides a layer of abstraction over database operations and follows the MVC pattern. Option C correctly identifies this expansion.
-
processRequest
-
processFormRequest
-
processRequest and processFormRequest
-
processDataRequest
A
Correct answer
Explanation
In OAF Controller, processRequest is the method where you programmatically hide beans, fields, buttons, or regions during initial page rendering. This is done before the page is displayed to the user. processFormRequest handles form submission processing. Option A is correct.
-
View Layer/Presentation Layer
-
Java Bean
-
Controller
-
Model Layer
-
In ASP.NET 4, new configuration elements have been added to Web.config and Web.Config size has increased
-
A new auto-start feature in ASP.NET 4.0 lets you perform expensive application initialization prior to processing the first HTTP request
-
ASP.NET 4 allow to extend output caching by enabling you to configure one or more custom output-cache providers that can use any storage mechanisms
-
ASP.NET 4 introduces a new compression option for Session State Compression for both out-of-process State Server & SQL Server session state providers to improve the performance
A
Correct answer
Explanation
ASP.NET 4.0 actually simplified the default Web.config by moving many configuration elements to machine.config, reducing rather than increasing the file size. Options B, C, and D correctly describe ASP.NET 4.0 improvements: auto-start feature, extensible output caching, and session state compression.
-
request
-
session
-
context
-
page
C
Correct answer
Explanation
JSP implicit objects are: request, response, pageContext, session, application, out, config, page, and exception. 'context' is NOT a valid JSP implicit object - pageContext exists, but not 'context' alone.
-
request
-
session
-
context
-
page
C
Correct answer
Explanation
JSP implicit objects are: request, response, pageContext, session, application, out, config, page, and exception. 'context' is NOT a valid JSP implicit object - pageContext exists, but not 'context' alone.
-
request
-
session
-
context
-
page
C
Correct answer
Explanation
JSP implicit objects are: request, response, pageContext, session, application, out, config, page, and exception. 'context' is NOT a valid JSP implicit object - pageContext exists, but not 'context' alone.
-
request
-
session
-
context
-
page
-
error
-
exception
C
Correct answer
Explanation
JSP implicit objects are: request, response, pageContext, session, application, out, config, page, exception. 'context' is NOT an implicit object - the correct name is 'application' for the ServletContext reference.
-
request
-
session
-
context
-
page
-
error
-
exception
C
Correct answer
Explanation
JSP implicit objects are automatically available in JSP pages without declaration. The standard implicit objects are: request, response, pageContext, session, application (not 'context'), out, config, page, and exception (only in error pages). 'context' is not a valid implicit object name - the correct names are 'application' for servlet context and 'pageContext' for page context.
-
GenericServlet is for servlets that might not use HTTP, like for instance FTP service.
-
As of only Http is implemented completely in GenericServlet.
-
The GenericServlet has a service() method that gets called when a client request is made.
-
GenericServlet is called by both incoming requests and the HTTP requests are given to the servlet as they are.
A,C,D
Correct answer
Explanation
GenericServlet is a protocol-independent servlet class. It defines a lifecycle method service() called for all client requests. Unlike HttpServlet, it does not implement HTTP-specific behavior directly. The marked options correctly describe its protocol-neutral design and request handling workflow.
-
Separation of dynamic and static content.
-
Support for scripting and tags
-
Reuse of components and tags.
-
Web access layer for N-tier enterprise application architecture
A,B,C,D
Correct answer
Explanation
JSP technology provides all four listed advantages: separation of dynamic/static content through its template mechanism, support for scripting and custom tag libraries, component/tag reuse through JavaBeans and custom tags, and serving as the presentation layer in N-tier enterprise architecture.
-
Objects with application scope are accessible from pages processing requests that are in the same application as they one in which they were created.
-
All references to the object shall be released when the runtime environment reclaims the ServletContext.
-
Objects with application scope can be defined (and reached) from pages that are not session-aware
-
References to objects with application scope are stored in the application object associated with a page activation
A,B,C,D
Correct answer
Explanation
All four statements correctly describe application scope in JSP. Objects with application scope are accessible across the entire application (all requests/sessions), persist until the ServletContext is destroyed/reclaimed, can be accessed from non-session-aware pages, and are stored in the implicit application object.