Fix the route filter order in express route circuit constructor

arm-network/2016-12-01/swagger/expressRouteCircuit.json

@@ -1099,10 +1099,6 @@
           "$ref": "#/definitions/ExpressRouteCircuitPeeringConfig",
           "description": "The Microsoft peering configuration."
         },
-        "routeFilter": {
-          "$ref": "./routeFilter.json#/definitions/RouteFilter",
-          "description": "The reference of the RouteFilter resource."
-        },
         "stats": {
           "$ref": "#/definitions/ExpressRouteCircuitStats",
           "description": "Gets peering stats."
@@ -1116,8 +1112,12 @@
           "description": "The GatewayManager Etag."
         },
         "lastModifiedBy": {
-          "type": "string",
-          "description": "Gets whether the provider or the customer last modified the peering."
+            "type": "string",
+            "description": "Gets whether the provider or the customer last modified the peering."
+        },
+        "routeFilter": {
+          "$ref": "./routeFilter.json#/definitions/RouteFilter",
+          "description": "The reference of the RouteFilter resource."
         }
       }
     },

arm-network/compositeNetworkClient.json

@@ -17,6 +17,7 @@
     "./2016-09-01/swagger/virtualNetworkGateway.json",
     "./2016-12-01/swagger/expressRouteCircuit.json",
     "./2016-12-01/swagger/routeFilter.json",
-    "./2016-12-01/swagger/serviceCommunity.json"	
+    "./2016-12-01/swagger/serviceCommunity.json",
+    "./2016-12-01/swagger/network.json"	
   ]
 }