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 24.3

Java Data Objects (JDO)
Java Data Objects (JDO) Standard or Specification

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: Java Data Objects (JDO) is a specification defining a standard method to access persistent data in databases through plain old Java objects (POJO). This specification provides an interface-based definition of object persistence for the Java programming language mainly dealing with storing, querying and retrieving database objects. JDO allows developers to persist Java objects into traditional data stores. JDO supports transactions, queries, and the management of an object cache. JDO provides for transparent persistence for Java objects with an Application Programming Interface (API) that is independent of the underlying data store. Additionally, JDO allows developers to store regular Java classes.
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: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v22.11
Decision Date: 11/04/2022 at 01:37:20 UTC
Introduced By: TRMSP
Standards Body: Apache Software Foundation (ASF)
- The information contained on this page is accurate as of the Decision Date (11/04/2022 at 01:37:20 UTC).