Because the only public way we have of destroying a jdbc-mapping is a gfsh command. All those other examples also have public apis that let you remove the other thing. Although at least some of your examples do not prevent a region from being destroyed (cache writer and loader; I don't know about cqs and indexes). The goal here is to help the gfsh user but not the api user.
[ Full content available at: https://github.com/apache/geode/pull/2950 ] This message was relayed via gitbox.apache.org for notifications@geode.apache.org
