Jerome Louvel <contact <at> noelios.com> writes: > It seems indeed like this service would help you to centralize your > conversion logic. But nothing is done automatically, you still need to > manually call getEntityAsObject() or setEntity(Object) methods in order to > trigger the converter service. >
But if I need to support both XML and JSON representations, I would need two converter services, right? Or do you see the toRepresentation() method on ConverterService accepting a MediaType/Variant parameter? Thanks. Sumit
