Spring Framework

General Information

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:	Spring is an application framework based on Inversion of Control (IoC). This technology provides a comprehensive programming and configuration model for modern Java-based enterprise applications on any deployment platform. A key element of Spring is infrastructural support at the application level; Spring focuses on the `plumbing` of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments. This technology also serves as the foundation for Spring Integration, Spring Batch, and the rest of the Spring family of projects. This technology does not utilize a database.
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:	This technology has been assessed by the Section 508 Office and found non-conformant. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v22.12
Decision Date:	12/09/2022 at 19:31:03 UTC
Introduced By:	Extended Tool List (ETL)
Vendor Name:	Pivotal

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date
2.0.2	01/08/2007	01/01/2013
2.0.3	03/09/2007
2.0.4	04/10/2007
2.0.5	05/07/2007
2.0.6	06/18/2007
2.0.7	10/01/2007
2.5	11/19/2007
2.5.4	05/01/2008
2.5.6	10/31/2008
3.0.5	10/20/2010
3.1	12/13/2011	01/28/2014
3.2	12/13/2012
4.0	12/01/2013
4.0.4	05/01/2014
4.0.5	05/20/2014
4.0.6	07/08/2014
4.1	09/12/2014
4.2.x	07/31/2015
4.3.x	09/19/2016
5.x	09/28/2017
6.x	11/16/2022

Current Decision Matrix (12/06/2022)

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.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2023

CY2024

CY2025

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

2.5.6

Unapproved

3.0.5

Unapproved

3.1

Unapproved

3.2

Unapproved

4.0.5

Unapproved

4.0.6

Unapproved

4.1

Unapproved

4.2.x

Unapproved

4.3.x

Unapproved

5.x

Approved w/Constraints
[6, 7, 8, 9]

6.x

Approved w/Constraints
[6, 7, 8, 9]

Decision Constraints


[1]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[2]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[3]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[4]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[5]	This technology must use the latest version of Java Development Kit (JDK) - Oracle.

[6]	This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle.

[7]	This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product.

[8]	Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[9]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.

Note:

At the time of writing, version 6.0.2 is the most current version, released 11/24/2022.

References

The following reference(s) are associated with this entry:
Type	Name	Description
Vendor Provided*	GitHub Repository	This webpage outlines the GitHub repository, and open-source documentation for the Spring Framework technology.
Other	Release Notes	This website links to the release notes for this technology.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
.ui	The .ui module contains the support for user interface (UI) layer concepts and applications. This also contains support classes for FreeMarker, JasperReports, and Velocity.
AOP	Spring`s aspect-oriented programming (AOP) module provides an AOP Alliance-compliant AOP implementation. Using Spring`s AOP module allows separation of functionality such as method-interceptors and pointcuts to cleanly decouple code.
Aspects	The Aspects module provides integration with AspectJ.
Beans	This package contains classes to manipulate Java beans. Beans are multiple objects which have been encapsulated into a single object (bean).
Context	The Context module is a means to access objects in a framework-style manner that is similar to a Java Naming and Directory Interface (JNDI) registry.
Core	The Core module provides the fundamental parts of the framework, including the inversion of control (IoC) and Dependency Injection features.
Dao	The Dao module enables error handling irrespective of the data access approach used.
EHCache	The EHCache module contains classes for the open source cache EHCache and allows the user to set up EHCache as a Bean in the Spring framework.
Expression Language	The Expression Language module provides a powerful expression language for querying and manipulating an object graph at runtime.
Instrumentation	The Instrumentation module provides class instrumentation support and classloader implementations to be used in certain application servers.
JDBC	The Java Database Connectivity (JDBC) module provides a JDBC-abstraction layer that removes the need to do JDBC coding and parsing of database-vendor specific error codes.
JMS	The Java Messaging Service (JMS) module contains features for producing and consuming messages.
ORM	The object-relational mapping module provides integration layers for popular object-relational mapping application programming interfaces (API), including Java Persistence API, Java Date Object, Hibernate, and iBatis.
OXM	The object extensible markup language (OXM) module provides an abstraction layer that supports Object extensible markup language (XML) mapping implementations for Java architecture for XML Binding (JAXB), Castor, XMLBeans, JiBX, and XStream.
Test	The Test module supports the testing of Spring components with JUnit or TestNG. It provides consistent loading of Spring ApplicationContexts and caching of those contexts. It also provides mock objects that users can use to test their code in isolation.
Transaction	The Transaction module supports programmatic and declarative transaction management for classes that implement special interfaces.
Web	Spring`s Web module provides basic web-oriented integration features such as multipart file-upload functionality and the initialization of the IoC container using servlet listeners and a web-oriented application context. It also contains the web-related parts of Spring`s remoting support (remote-enabled services such as Remote Method Invocation, Remote Procedure Calls, and Java Message Service).
Web-Portlet	The Web-Portlet module provides the model-view-controller implementation to be used in a portlet environment and mirrors the functionality of Web-Servlet module.
Web-Servlet	The Web-Servlet module contains Spring`s model-view-controller (MVC) implementation for web applications. Spring`s MVC framework provides a clean separation between domain model code and web forms, and integrates with all the other features of the Spring Framework.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Application Technology Development Tools	Development Frameworks

Open Source

This entry is available as an open source technology.

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

JDK - Oracle Java Standard Edition (SE) Development Kit

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology is available at no cost through open-source licensing and supports VA`s open source initiative.
This technology may improve productivity for specific staff whose responsibilities include coding and development.
This technology has a comprehensive set of documentation.

Adoption Risks

This technology relies on Java Development Kit (JDK) - Oracle, which has a rapid release and update schedule.
This technology is available as freeware. As such this technology may be without clearly defined support options which may result in suboptimal enterprise level support.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.nist.gov/vuln/search for more details.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.

Architectural Benefits

This technology is portable as it runs on multiple TRM-approved operating systems.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (12/06/2022)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (12/06/2022)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

EMAIL UPDATES