Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 23.2

Beehive
Beehive Technology

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: Beehive, formerly known as BEA Beehive, is an open-source set of ease-of-use frameworks for enterprise Java applications. Beehive is comprised of the following;
Net User Interface (UI): An annotation-driven web application programming framework that is built atop Struts. NetUI centralizes navigation logic, state, metadata, and exception handling in a single encapsulated and reusable Page Flow Controller class. In addition, NetUI provides a set of JavaServer Pages (JSP) tags for rendering Hypertext Markup Language (HTML) / Extensible HyperText Markup Language (XHTML) and higher-level UI constructs such as data grids and trees and has first-class integration with JavaServer Faces and Struts.
Controls: A lightweight, metadata-driven component framework for building that reduces the complexity of being a client of enterprise resources. Controls provide a unified client abstraction that can be implemented to access a diverse set of enterprise resources using a single configuration model.
Web Service Metadata (WSM): An implementation of JSR 181 which standardizes a simplified, annotation-driven model for building Java web services.
In addition, Beehive includes a set of system controls that are abstractions for low-level Java Platform Enterprise Edition (J2EE) resource Application Programming Interface (APIs) such as Enterprise Java Beans (EJB), Java Message Service (JMS), Java Database Connectivity (JDBC), and web services.
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:
Decision: Prohibited. This entry is not (currently) permitted to be used under any circumstances.
Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v14.2
Decision Date: 02/28/2014
Introduced By: Extended Tool List (ETL)
Vendor Name: Apache Software Foundation (ASF)
- The information contained on this page is accurate as of the Decision Date (02/28/2014).