Tim Perrett wrote: > >> So, there's a bug is ESME (or maybe it's in the NGINX/Jetty bridge... I have >> to research it)... that doesn't mean you can't do stuff in Lift. >> >> If you respond to a request with: >> XmlResponse(<mytag>....</mytag>) >> The headers will be set correctly. >> > > Of course not - im not suggesting lift is broken or anything! Just > trying to "do the right thing" :) > > On my local XML api it works and send the text/xml content-type, i > must have missed this before. Doh! Just reviewing the api docs and I > see we also have JsonResponse, what would stop me creating something > similar to XMLApiHelper for JSON which uses JsonResponse? > > Did you see my note earlier in this thread about re-factoring the > net.liftweb.http.rest package to make a generic rest helper then > specific sub-classes for xml and json (and any other one etc)? > I did see the thread. It's a non-trivial problem and the best bet is to leave things the way they are until we figure out how to build a generic JSON/XML data holder.
> Cheers > > Tim > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
