Justin
There are a couple discussion threads about the ConverterService
(http://www.mail-archive.com/[email protected]/
msg01773.html), but I still don't understand its advantages or how to
implement it. I find myself writing the same type of code in the
getRepresentation methods for all of my resources to expose them as
HTML, JSON, and XML. Would the converter service simplify/centralize
this? What about handling metadata (for example when building an HTML
representation) beyond just the raw entity that's being serialized?
Could I use the ConverterService in concert with Resource-level
representation handling? For example to serialize/deserialize JSON
and XML generically, but define HTML representations at the resource
level. Any help would be greatly appreciated.
- ConverterService Justin Makeig
- RE: ConverterService Jerome Louvel
- Re: ConverterService Sumit Lohia
- Re: ConverterService Justin Makeig
- RE: ConverterService Jerome Louvel
- Re: ConverterService Rob Heittman
- Re: ConverterService Sumit Lohia
- RE: ConverterService Jerome Louvel

