GUI and Web Frameworks

Anchors in Oracle Forms control positioning relative to a parent object in both vertical AND horizontal directions. The statement incorrectly claims anchors only determine vertical positioning, when in fact anchors can be set for horizontal positioning as well.

A form in Oracle Forms does not require a main canvas. Forms can exist without canvases, or use only stacked canvases, tab canvases, or canvases of different types. While most forms have a content canvas for layout, it is not a technical requirement that a form must have at least one main canvas.

Menu attachment in Oracle Forms is done at the FORM level using the Menu Module property, not at the block level. Blocks cannot have their own menu attachments. The statement incorrectly claims the menu can be attached at block level.

In Oracle Forms Layout Editor, Confine mode restricts object movement so they stay within their frame boundaries. When Confine is ON, you cannot move objects outside the frame - this is the 'confining' or 'locking' behavior. Flex mode is different - it controls whether objects snap to grid.

Custom transformations can be either active or passive based on a user-configurable property. Active transformations change the number of rows passing through them, while passive transformations do not. The transformation type is not determined by algorithms, API functions, nor are they always active.

Action classes in Struts 2 do NOT have to extend ActionSupport. They only need to implement the Action interface (which has one method: execute()). ActionSupport is a convenient base class that provides default implementations and utility methods, but it's optional. You can even use plain POJOs as actions.

Declarative validation in Struts 2 works through XML validation files that are named based on the Action class, not whether the class extends ActionSupport. Any class can have declarative validation as long as the validation XML follows the naming convention (ClassName-validation.xml). The ActionSupport extension is not required.

In JSF, only components that extend UIInput can have their submitted values validated during the Process Validations phase. UIOutput components are for display only and don't receive user input, UICommand is for action events like button clicks, and UIOutputLink renders navigation links without accepting user input.

JSF validators are designed to validate individual component values, not multiple fields simultaneously. Cross-field validation requires workarounds like using phase listeners, custom validators that access other components via UIComponent.findComponent(), or Bean Validation (JSR 303/380) annotations with class-level constraints.

In ASP.NET, all .aspx pages inherit from the Page class located in the System.Web.UI namespace. The full namespace path is System.Web.UI.Page, which provides the base functionality for web pages including lifecycle events, request/response handling, and control management.

The System.Web.Security namespace provides classes for implementing ASP.NET security features, including forms authentication (FormsAuthentication class), membership providers, and role management. The other namespaces are for UI, configuration, and web services respectively.

To enable compilation of debugging symbols and present detailed debugging information in ASP.NET pages, the Debug="true" attribute must be set in the page directive (<%@ Page Debug="true" %>). Setting Trace to true enables execution tracing, but does not compile debug symbols.

The DropDownList control in ASP.NET uses the SelectedIndexChanged event to detect when a user selects a different item. This event fires after the selection changes and the page posts back. The Click event (option A) is for button controls, and the other options are invented names that don't exist in the DropDownList control's event model.

In ASP.NET web applications, configuration settings including custom error pages and error message settings are defined within the Web.config XML file under the `section. Other files likeError.configorApplication.config` are not standard configuration files for this purpose.

RadioButton controls are designed for mutually exclusive selection within a group - only one radio button can be selected at a time. CheckBox controls allow multiple selections. TabControl is for organizing content into tabbed pages, and Button is for triggering actions. For mutually exclusive choices, RadioButtons are the standard UI control.