Java Web Technologies and Enterprise Portals

In portal architecture (specifically BEA/Oracle WebLogic Portal), a 'desktop' is the top-level container that defines a collection of books, pages, and portlets - essentially defining the service collection for a user. Books organize pages, pages contain portlets, and portlets are the actual service components. Option A is correct.

In portal architecture, 'books' control the navigation menus. Books contain pages and portlets, and their hierarchical structure defines the menu/navigation tree. Options A, B, and D are incorrect - pages display content, portlets are service components, and desktops are top-level containers, not menu controllers.

In Pega Portal architecture, pages are the containers that display portlets. A book contains pages, and a portal contains books. The desktop is the top-level container for the entire portal structure.

The desktop is the foundational container in Pega Portal architecture and must be created first. It serves as the top-level parent for all other portal elements - portals, books, pages, and portlets are added to it hierarchically.

Backing files in portal frameworks serve as initialization and lifecycle management resources. They are commonly used to perform authentication checks when a portlet is accessed, as well as to handle context initialization and cleanup. The other options describe different mechanisms: backing up portal contexts uses different utilities, JNDI resource loading occurs through configuration, and database connections use connection pools or datasources.

Customizing the skeleton or structure of a portal requires JSP (JavaServer Pages) resources. JSP files define the HTML markup, layout, and structural elements that form the portal's framework. JavaScript handles client-side behavior, CSS manages styling, and XML is for configuration. The skeleton is the structural markup layer, which JSP provides.

Customizing the skin or visual appearance of a portal requires CSS (Cascading Style Sheets) resources. CSS controls colors, fonts, spacing, and all visual styling aspects. JavaScript handles interactivity, JSP manages structure, and XML handles configuration. Skin refers specifically to the visual presentation layer.

JPF (Java Page Flow) files serve as the controller component in MVC (Model-View-Controller) architecture used by portal frameworks. They contain the logic that coordinates between the model (data/business logic) and view (presentation), handling request processing, navigation, and workflow. Models represent data, views are the presentation layer (JSPs), and actions are specific controller methods.

Event Handlers are the preferred and recommended mechanism for implementing Inter-Portlet Communication (IPC) in modern portal frameworks. They provide a decoupled, event-driven architecture where portlets can publish and subscribe to events without direct dependencies. Backing files are for lifecycle management, onRefresh is a specific lifecycle method, and listenTo portlet property is an older, less flexible approach.

Content repositories in portal and content management systems store two primary things: content types (definitions, schemas, metadata) and the actual content items (instances of those types). 'Types and content' captures this duality. Segments and profiles relate to personalization, elements and nodes is too generic, and nodes and resources doesn't capture the type definition aspect.

Local variables in Java must be initialized before use. Variable i is declared but never assigned a value before i = i + 5 attempts to read it. This violates Java's definite assignment rules, causing compile-time error.

Java main method must be static, but public is not strictly required (though runtime looks for public). Variations: A is standard, B is valid static main without args (compile-time valid, though JVM won't call it), C is valid non-public static main, D is invalid syntax (void must come before method name, not after).

J2EE (Java 2 Enterprise Edition) is built on Java's "write once, run anywhere" philosophy, making it platform-independent. J2EE applications can run on any operating system with a compatible JVM.

EJB (Enterprise JavaBeans) are specifically designed as business components in Java EE architecture. They encapsulate business logic. Servlets handle web requests/responses, JSP handles presentation - neither are business components.

web.xml is the standard deployment descriptor for Java web applications. It contains configuration for servlets, filters, welcome files, and other web application settings. While context.xml exists (in Tomcat), web.xml is the universal deployment descriptor.

Servlets are server-side programs that run in a web container. They handle client requests, typically HTTP requests, and generate dynamic responses. They do NOT run on the client side.

Context parameters (defined in web.xml) are application-wide and accessible globally via ServletContext to all servlets and filters in the application. Unlike servlet-specific init parameters, context parameters are shared across the entire application.

XML is designed for storing and transporting structured data, while HTML is designed for displaying data on web pages. XML does not replace HTML; rather, they serve different primary purposes and often complement each other. Thus, the statement is false.