GUI and Web Frameworks

The Toolkit in AWT provides an interface between the abstract window layer and the native windowing system implementation. It enables platform-specific GUI operations while maintaining a consistent Java API.

WebSphere Portal (WPS) requires enabling transcoding services to launch the WML (Wireless Markup Language) device emulator. Transcoding converts web content to formats suitable for different wireless devices, including WML for early mobile browsers.

For Struts portlets in WPS, the initial view for VIEW mode is configured using the viewMode.page preference in portlet.xml. This portlet-specific approach allows each portlet to define its own default view, which is more flexible than application-wide welcome file lists.

In Rational Application Developer's Page Editor, all draggable components including Enhanced Faces Components (JSF components) are located in the Palette view. The Palette is the standard design-time UI for adding visual components to pages in RAD.

Composite applications in WPS are fundamentally built on Templates and Applications. Templates define reusable application structures, relationships, and wiring between components, while Applications are instances created from those templates.

The Lifecycle interface in composite application frameworks (like IBM WebSphere Portal) contains methods for managing component lifecycle, including creation with supported parameters. This interface defines the contract for initializing, configuring, and managing business components throughout their lifecycle. The Membership, Templatable, and DisplayInfo interfaces serve different purposes related to access control, templating, and UI display respectively.

The Client UI Identifier is used at runtime to lookup the task page definition for portal business processes (option A). This identifier maps to the appropriate UI page or portlet that should display the task. The process template name (B) defines the process structure, not the UI. The task instance ID (C) identifies a specific task instance but doesn't specify the UI layout. Staff activity ID (D) relates to activity assignment, not UI resolution.

AWT stands for Abstract Window Toolkit, which is Java's original platform-dependent GUI toolkit. Option B is correct. Option A 'Advanced' is incorrect, Option C 'Adjust' is incorrect, and Option D is wrong because B is the correct answer.

Reusable actions can be invoked multiple times within a test and from other tests, promoting modularity. They cannot be merely copied as independent actions nor are they uncallable; thus the other statements are false.

When 'Fetch New Shared Model' is executed, it performs a fetch operation on all components that depend on the current component. This means any component that relies on this component will be updated with the latest version, ensuring dependency chains remain synchronized.

Component implementations are NOT visible to other components. This is a fundamental principle of CBD - only the interface is exposed, while the internal implementation remains hidden. This encapsulation allows components to be developed and modified independently as long as they adhere to the interface contract.

Xalan-J and Saxon are both XSLT transformation processors that can be integrated with JSP to generate multiple views from XML source data. They apply XSLT stylesheets to produce different output formats (HTML, WML, PDF, XML) from the same content, enabling view separation. Jdk1.5 is a Java development kit, not a view-generation tool.

In UML and software architecture, components are modular units that interact through well-defined interfaces, meaning components can have interfaces. Additionally, dependencies can be defined between components to show relationships. Components and classes are distinct concepts, and components typically reside within a workspace.

JavaScript opens new windows with window.open(). Option A shows the correct syntax. Option B uses a non-existent window.new(), option C treats window as a function (it's an object), and option D invents openwindow().

The browser status bar text is set via window.status property. Option A is correct. Option B invents a status() function, option C references a non-existent statusbar variable, and option D treats status as a method instead of a property.