From 3d0ec509abfffddfb6c618e645e9f3f88d1a7bcf Mon Sep 17 00:00:00 2001 From: Sam Brannen Date: Thu, 11 Apr 2019 16:46:50 +0200 Subject: [PATCH] Document mock JNDI support deprecation in the Reference Manual See gh-22779 --- src/docs/asciidoc/testing.adoc | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/src/docs/asciidoc/testing.adoc b/src/docs/asciidoc/testing.adoc index eed948f5573..035990641fd 100644 --- a/src/docs/asciidoc/testing.adoc +++ b/src/docs/asciidoc/testing.adoc @@ -77,12 +77,16 @@ out-of-container tests for code that depends on environment-specific properties. [[mock-objects-jndi]] ==== JNDI -The `org.springframework.mock.jndi` package contains an implementation of the JNDI SPI, -which you can use to set up a simple JNDI environment for test suites or stand-alone +The `org.springframework.mock.jndi` package contains a partial implementation of the JNDI +SPI, which you can use to set up a simple JNDI environment for test suites or stand-alone applications. If, for example, JDBC `DataSource` instances get bound to the same JNDI names in test code as they do in a Java EE container, you can reuse both application code and configuration in testing scenarios without modification. +WARNING: The mock JNDI support in the `org.springframework.mock.jndi` package is +officially deprecated as of Spring Framework 5.2 in favor of complete solutions from third +parties such as https://github.com/h-thurow/Simple-JNDI[Simple-JNDI]. + [[mock-objects-servlet]] ==== Servlet API