It seems org.glassfish.jersey.internal.ServiceFinder wrongly assumes to be
running in a non-OSGi environment.
Debugging things a bit I found that OsgiRegistry.getInstance() returns null
because it is unable to load the Bundlecontext, which is not surprising as
the jersey-common bundle is not yet active.
I'll try fiddling around with the start levels, but it seems to show the
limitations of this hybrid service registry approach.
Cheers,
Reto
On Fri, Sep 4, 2015 at 11:49 AM, Reto Gmür <reto_at_gmuer.ch> wrote:
> Thanks Adam, I will see if I can create a minimum example.
>
> But right now I've found another problem which is possibly related: it
> seems that none of the ForcedAutoDiscoverable instances are actually
> loaded, at least breakpoint I set at the beginning of the configure-method
> are never hit. I'm using OSGi so I'm guessing the hk2 bits enabling
> ServiceLoader is missing, investigating.....
>
> Cheers,
> Reto
>
> On Thu, Sep 3, 2015 at 6:28 PM, Adam Lindenthal <
> adam.lindenthal_at_oracle.com> wrote:
>
>> Hi Reto,
>>
>> it seems like you are experiencing the same issue as the reporter of
>> https://java.net/jira/browse/JERSEY-2845 a while ago.
>> I tried the described behaviour and did not reproduce it. After a while,
>> it turned out, that the problem was somewhere else on the reporter’s side.
>>
>> Could you give it a look in JIRA and and check, that you are not in
>> similar situation?
>>
>> Regards,
>> Adam
>>
>> On 03 Sep 2015, at 18:17, Reto Gmür <reto_at_gmuer.ch> wrote:
>>
>> Hello,
>>
>> After updating to jersey 2.21 I'm getting 415 responses when submitting
>> forms unless I add a @Consumes("application/x-www-form-urlencoded"). I'm
>> using a method with @FormParam annotations.
>>
>> According to the spec the absence of a @Consumes-Annotation support for
>> any media type (“*/*”) is assumed. How comes Jersey is returning a 415
>> response without this annotation?
>>
>> Cheers,
>> Reto
>>
>>
>>
>>
>>
>