Floodlight's Static Flow Pusher REST interface expects "posted data"
for DELETE requests. It uses this posted data to identify which entry
should be deleted. However, the RFC 2616 states that resources
to be deleted using the DELETE method should be identified by a
URI (not by posted data):
http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.7

This is a problem when you try to use a spec-compliant framework to
communicate with the REST interface provided by StaticFlowEntryPusher
module. The Restlet framework, that is being used in the implementation
of the module itself, is an example. It prevents you from posting data with
a DELETE method, according to what is specified in the HTTP1.1 RFC.

/wm/staticflowentrypusher/list/{switch}/json
{switch} can be 'all' or a DPID in Hex format, i.e. '00:00:00:00:00:00:00:01'

Make static flow pusher into a service (IStaticFlowEntryPusherService). This will allow other Floodlight modules to push static flows without using the REST API.

Fixed JUnit tests.

Move the switchcluster REST API from /wm/core/controller/switchclusters/json to /wm/topology/switchclusters/json. [#23518013]

First checking for ITopology REST API. Links between OpenFlow switches connected to the controller can now be seen through /wm/topology/links. [#23518013]