Bryan Hunt

Here is all that is needed. I'd do a PR, but still can't figure out the build. ``` java import org.osgi.framework.BundleActivator; import org.osgi.framework.BundleContext; import org.osgi.framework.ServiceRegistration; import com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider; public class Activator...

Users could always add the Jackson bundles externally if you want to keep those private.

Forgot to mention that not all of the needed Jackson bundles are included in the jersey.all.jar, you need external Jackson bundles to get this to work.

After some additional research, here is the proper way to include Jackson: ``` java import org.glassfish.jersey.jackson.JacksonFeature; import org.osgi.framework.BundleActivator; import org.osgi.framework.BundleContext; import org.osgi.framework.ServiceRegistration; public class Activator implements BundleActivator { @SuppressWarnings("rawtypes") private...

Thanks. BTW, if there were contributing docs that explained importing the projects into Eclipse, fixing the missing Maven connector, setting up the target platform, adding a provider, running tests, etc,...

@dzmitry-kankalovich Have you tried using the jersey-min bundle?

I run this framework all the time and I haven't seen this problem.

I use the following: ```java try { ... } catch (Exception e) { log(LogService.LOG_ERROR, "Unexpected exception", e); throw new InternalServerErrorException(e); } ```

That's how all of my REST endpoints look ... ```java @POST public Response handlePost() { try { ... } catch (Exception e) { log(LogService.LOG_ERROR, "Unexpected exception", e); throw new InternalServerErrorException(e);...

In general, if you have to set a specific start order for your bundles, something is wrong. If someone wants to dig into this and provide a PR, I'll give...