jersey-2.0

...if the instance needs to be constructed manually, perhaps by a 3rd party factory class? Previously, (Jersey 1.x), you would do something like this: public class MyInjectableProvider extends PerRequestTypeInjectableProvider<Context, MyInjectable> { public MyInjectableProvider() { super(MyInjectable.class); } @Override public Injectable<MyInjectable> getInjectable(ComponentContext ic, Context context) { MyInjectable myInjectableInstance = //... return new Injectable<MyInjectable>() { @Override public MyInjectable getValue() { return myInjectableInstance; } }; } } The anonymous local class is

When in jersey server I have server 500 error: In server response don´t have stack trace or some info. In Eclipse console don´t have exception stack trace I try to catch exception in server and print trace in console, but nothing happens How can I get the stack trace when 500 server error happens? Most of the time, a generic ExceptionMapper will do the trick. @Provider public class DebugMapper implements ExceptionMapper<Throwable> { @Override public Response toResponse(Throwable t) { t.printStackTrace() return Response.serverError() .entity(t.getMessage()) .build(); } } Then just register it

I have a problem trying to inject a contract with two services bound to it. I'm using Jersey, and extending ResourceConfig to configure my app, where I'm binding two different implementations (classes FooImpl1 and FooImpl2 ) to a same contract (interface Foo ), ranking them differently. Each of these implementations is annotated with @Named and its name. In one of my controllers I want to have access to both implementations, so I inject an IterableProvider<Foo> fooProvider . If I do not specify anything, the implementation with the highest rank is injected always, which is what I want. The

I am using a Jersey StreamingOutput that was working just fine until we upgraded to Jersey 2.16. Here's the thing. My StreamingOuput produces output very slowly in some circumstances. I do write data regularly, but I write it pretty slowly and just a little of it at a time. I call flush() on the OutputStream passed to StreamingOutput.write() every time I write any bytes, but the flush() appears to have no effect. Nothing is sent over the wire until 8K has been written to the OutputStream . Unfortunately, in some circumstances, by the time 8K has been written, the client has timed out. I

I have been trying to know if JacksonFeature.class is still needed for Jersey 2.17. I can't see any difference between the outputs between codes that JacksonFeature.class is registered or not. Then, I forked a code from codingpedia codingpedia , removed JacksonFeature.class, upgraded to Spring 4.1.2 and jersey 2.17, updated the codes and the test still passed. So I created a very simple web service to test this again github link , having in mind to remove all the moving parts and still worked. So do we still need to register JacksonFeature? Yeah I don't know why that tutorial they are using

I am having problems with creating a mock Response object to use with my unit tests. I am using org.glassfish.jersey.core.jersey-client version 2.3.1 to implement my RESTful client and mockito version 1.9.5 to help me with mock objects. Here is my test's code: @Test public void testGetAll() throws IOException { // Given String expectedResource = "expectedResource" final Response expectedRes = Response.ok(expectedResource, MediaType.APPLICATION_JSON).build(); String receivedResource; BDDMockito.given(this.client.getSimpleClient().getAllWithResponse()).willReturn(expectedRes); // When