Did you run into the exception on Wink Client or Wink Server? If it happens on the server, it probably means that the "request" doesn't have the correct Content-Type header set.
Thanks, Raymond On Aug 30, 2012, at 2:04 PM, Cindy A McMullen wrote: > Here are the response headers from the service: > > Proxy-Connection: keep-alive > Content-Type: text/html; charset=utf-8 > Server: Microsoft-IIS/7.0 > Content-Length: 66931 > X-AspNet-Version: 2.0.50727 > Date: Thu, 30 Aug 2012 21:18:25 GMT > Cache-Control: private > X-Powered-By: ASP.NET > > > On Aug 30, 2012, at 2:48 PM, Raymond Feng wrote: > >> Are you missing the Content-Type and/or Accept headers? From your message, >> the system is trying to unmarshal text/html into >> org.apache.wink.common.model.atom.AtomFeed. >> >> Can the client set the Content-Type to be "application/atom+xml"? >> Thanks, >> Raymond >> >> On Aug 30, 2012, at 12:57 PM, nedhead wrote: >> >>> I'm getting this exception; >>> >>> A javax.ws.rs.ext.MessageBodyReader implementation was not found for class >>> org.apache.wink.common.model.atom.AtomFeed type and text/html; charset=utf-8 >>> media type. Verify that all entity providers are correctly registered. Add a >>> custom javax.ws.rs.ext.MessageBodyReader provider to handle the type and >>> media type if a JAX-RS entity provider does not currently exist. >>> >>> Which provider package contains the class to accommodate 'text/xml' ? >>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://apache-wink-users.3471013.n2.nabble.com/MessageBodyReader-for-text-xml-tp7572609.html >>> Sent from the Apache Wink Users mailing list archive at Nabble.com. >> >
