Hi Daniel.
To be honest I don’t know which use case does not work for you. Are you trying to invoke the use case ending with "201 Created” or "400 Bad Request”? I guess you are trying to get 201 but get 400. And I expect you already tracked via ContainerResponseFilter that your resource method already returned 201 response. Right?
GAE has some classes on black list. May be it is that case. But more information is needed. May you set more verbose logging of Jersey? I have found out short blog post about logging configuration:
http://www.mkyong.com/google-app-engine/configure-logging-in-google-app-engine/ <
http://www.mkyong.com/google-app-engine/configure-logging-in-google-app-engine/>. Or may you create simplified GAE project shared on Gist for example to reproduce the problem?
Thanks,
Libor
> On 21 Jan 2015, at 09:28, Rindt, Daniel <drindt_at_viselabs.com> wrote:
>
> Hello everyone,
>
> i am using jersey 2.14 with json-processing 2.15 to nicely send JSON
> responses back to the client. The whole thing runs in google
> appengine. In case that something is wrong with the call i return a
> Status.BAD_REQUEST instead of
> Response.status(Status.CREATED).entity(component).build();.
> This works on my local dev environment as expected. If i deploy to
> appengine and use exact the same client with same parameter scenario
> to check the error behavior i get a html page with bad request.
> I build to check what happened a ordinary HttpServlet which accept
> post and set the response code to 400 just to ensure that appengine is
> not intercepting my response body. But this is working local and
> remote as expected. So i came back to jersey to find out what happened
> and add a ContainerResponseFilter just to see whats going into the
> response. But everything is into as expected.
> I have no idea where to start investigating it further. Your advise is
> very welcome.
>
> Thank you in advance,
> --
> Daniel Rindt
> Viselabs e. K.
> mobile software solutions
> Berlin, Germany
>
> phone: +4930202368410
> fax: +4930202368411
>
> entered in the commercial register at the local court of Berlin under HRA 46662B