[RestEasy] @FormParam params reset to null 2.0 RC3 . Works fine in 1.0.15

[ucfstevie]

I use a RestEasy implementation and pass params to the server using POST.
My Java Script Code:

function loginUser(userName,password){
$.ajax({
  type: "POST",
  contentType : 'application/x-www-form-urlencoded',
  url: getLogonUrl(),
  data: { "userName": userName, "password" : password },
  success: function(msg){
  handleLogonSuccess(msg,userName);      
  },
  error: function(xhr, textStatus, errorThrown) {
    console.log("error :" + xhr.responseText);
    console.log("status code :" + xhr.status);
    showLoginMessage(xhr.responseText,'red');
  }
});
}

Server Side Code:

   @POST
   @Securable
   @Path("doLogon")
   @Produces("text/plain")
   public Response  logonUser(@FormParam("userName") String userName, @FormParam("password")String password,@Context HttpServletRequest servletRequest){
            System.out.println("userName :" + userName);
            System.out.println("password:" + password);
}

Using 1.0.15 my username/password params work fine. Upgrading to 2.0 RC3 the username/password are always null.

[ucfstevie]

Sad to say this is still an issue with the latest build. I did some debugging it and it seems the problem is in AtmosphereFramework configureRequestRespons(AtmosphereRequest req, AtmosphereResponse res).

The Problem is the call to Map<String, String> headers = configureQueryStringAsRequest(req);. That method depends on the AtmosphereRequest queryString being set. This is not set until further down in configureRequestResponse. Because of this, the headers always return as empty.

[jfarcand]

Seems like an issue only with RestEasy. With Jersey, it works as expected. The sample use @FormParam

[jfarcand]

OK now properly fixed. Sorry for that.

[ucfstevie]

Retested and issue has been resolved. Thank you