A GetMapOutputFormat implementation is meant to produce one and only one type of content, whose normative MIME-Type is advertised through the {@link #getContentType()} method. Yet, the{@link #getOutputFormatNames()} method is meant to advertise the map format in the capabilitiesdocument and may or may not match the MIME-Type.
To incorporate a new producer specialized in a given output format, there must be a {@code GetMapOutputFormat} registered in the Spring context that can provide instances of thatconcrete implementation, as well as a {@link Response} Spring bean that can encode the produced{@link WebMap}. Hence, it's counterpart {@code Response} implementation{@link Response#canHandle(org.geoserver.platform.Operation) canHandle(Operation)} method must beimplemented in a consistent way with the output format's {@link #getMimeType()} and{@link #getOutputFormatNames()}.
The methods defined in this interface respect the general parse request/produce response/get mime type/write content workflow, so they should raise an exception if are called in the wrong order (which is produceMap -> getContentType -> writeTo)
@author Gabriel Roldan @author Simone Giannecchini, GeoSolutions @version $Id$
|
|
|
|