GitHub user davinash opened a pull request:
https://github.com/apache/incubator-geode/pull/303
GEODE-1984: Fix Issue Make GatewaySender destroy a public API
1. Making destory API public
2. Added a new gfsh WAN command destroyGatewaySender
3. Impleted GatewaySenderDestroyFunction, which first stop gatewaysender
and then call destroy on the same.
4. Added a WAN Rest Controller for destroy gatewaysender
5. Removed the need of explicit casting of sender to
AbstractGatewaySender for calling
destroy API
6. Renamed Test WanCommandCreateGatewaySenderDUnitTest to
WanCommandCreateDestroyGatewaySenderDUnitTest
7. Each applicable test now also calls destroy gfsh command and verfies
the result
8. Minor changes in the logging for each tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davinash/incubator-geode bugfix/GEODE-1984
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-geode/pull/303.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #303
----
commit 610b620e12b3b8f4198238cd562d5c3f0d8cd669
Author: adongre <[email protected]>
Date: 2016-12-03T14:08:39Z
GEODE-1984: Fix Issue Make GatewaySender destroy a public API
1. Making destory API public
2. Added a new gfsh WAN command destroyGatewaySender
3. Impleted GatewaySenderDestroyFunction, which first stop gatewaysender
and then call destroy on the same.
4. Added a WAN Rest Controller for destroy gatewaysender
5. Removed the need of explicit casting of sender to
AbstractGatewaySender for calling
destroy API
6. Renamed Test WanCommandCreateGatewaySenderDUnitTest to
WanCommandCreateDestroyGatewaySenderDUnitTest
7. Each applicable test now also calls destroy gfsh command and verfies
the result
8. Minor changes in the logging for each tests
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
