custom XML renderer

[Patrick Kranzlmueller]

I'm mainly dealing with the terms of nodes (e.g. root or list-items) and I plan to change these names to more declarative ones.

I'm having something like this in mind:

http://www.campaignmonitor.com/api/subscribers/

Has anyone implemented a custom XML renderer? If so, any hints on what's the best practice?

I want to avoid writing a different XML renderer for every model I'm using but I currently don't see an easy way to a) have an abstract renderer and b) achieve declarative nodes.

Maybe more declarative nodes are not even necessary for an API (and they just look good)?

Thx,

Patrick

[Hassan Shamim]

Sorry for reviving a dead thread, but did you ever find a decent solution for this?  Or did you end up having to write a custom XML renderer for all your endpoints?

[Patrick Kranzlmueller]

I simply gave up on this issue ... please let me know if you find a decent solution.

Thanks,

Patrick