This modified code sends the shapefile downstream, I suppose to the ShapefileImportService, using the same parameters as the original upload service. I don't see where the ShapefileUploadService deletes the uploaded zipfile; what am I missing?

More fully, if we want to publish both the exploded and the original shapefile, we'll need to make the ShapefileUploadService handle more than one input zip in the upload directory (and change the shape name in the exploded shapefile). This is, I think, a simple change. Will it break anything else?

The relevant parameter is requestMap["file-token"], which is interpreted by the ShapefileUploadService as the directory to search for zipfiles to import; it currently only processes the first one.