title: Null content-type when migrating from Jersey to RESTEasy.
body: <p>So I wrote a sample REST resource that works like a charm in Jersey/Tomcat, but when I take it to RestEASY/Tomcat it blows. I mean really? what happened to working out of the box. Anyway a little frustrated. I get this error when trying to access the resource(<a href="http://localhost:7070/mg/mytest" rel="nofollow noreferrer">http://localhost:7070/mg/mytest</a>)</p>
  
  <p><strong>"content-type was null and expecting to extract a body"</strong></p>
  
  <p>7842 [http-7070-2] ERROR com.loyalty.mg.rest.exception.MGExceptionMapper - Error caught in the exception mapper - 
  org.jboss.resteasy.spi.BadRequestException: content-type was null and expecting to extract a body
      at org.jboss.resteasy.core.MessageBodyParameterInjector.inject(MessageBodyParameterInjector.java:131)
      at org.jboss.resteasy.core.MethodInjectorImpl.injectArguments(MethodInjectorImpl.java:98)
      at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:121)
      at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:247)
      at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:212)
      at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:202)</p>
  
  <pre><code>@Path("/mytest")
  public class TestResource  {
  
      @GET
      public Response getData()
  </code></pre>
  
  <p>I guess the question also is - is RestEASY any better than Jersey, this is just the start and I am getting errors. Should I just stick to Jersey?</p>
  
  <p>Also already tried this as well :)</p>
  
  <pre><code>&lt;context-param&gt;
    &lt;param-name&gt;resteasy.media.type.mappings&lt;/param-name&gt;
    &lt;param-value&gt;json : application/json, xml : application/xml&lt;/param-value&gt; 
  &lt;/context-param&gt;
  </code></pre>