jersey-container-servlet-core-4.0.0M2 references ServiceFinderBinder from unexpected package in jersey-common

Open Beginner friendly
#6,090 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
java
Domain
backend

Research direction

Start with WebComponent.java in jersey-container-servlet-core-4.0.0-M2 and compare its ServiceFinderBinder reference with the class location in jersey-common-4.0.0-M2. Reproduce the runtime failure using the reported dependency versions, then verify that the servlet core component resolves the ServiceFinderBinder class from the package provided by jersey-common.

Written by the indexing model from the issue text.

Description

Description:

While testing an upgrade from jersey-container-servlet-core-3.1.11 to jersey-container-servlet-core-4.0.0-M2, I encountered what appears to be a package reference inconsistency involving ServiceFinderBinder.

Observed behavior

WebComponent.java in jersey-container-servlet-core-4.0.0-M2 attempts to load:

org.glassfish.jersey.innate.inject.ServiceFinderBinder

However, the class is actually present in:

org.glassfish.jersey.internal.ServiceFinderBinder

within jersey-common-4.0.0-M2.

Comparison with jersey-container-servlet-core-3.1.11

  • jersey-container-servlet-core-3.1.11 references:

    org.glassfish.jersey.internal.ServiceFinderBinder

  • jersey-common-3.1.11 contains:

    org.glassfish.jersey.internal.ServiceFinderBinder

The reference and implementation locations are consistent.

jersey-common-4.0.0

I verified that ServiceFinderBinder is still located in:

org.glassfish.jersey.internal.ServiceFinderBinder

inside jersey-common-4.0.0.

However, jersey-container-servlet-core-4.0.0-M2 appears to look for:

org.glassfish.jersey.innate.inject.ServiceFinderBinder

which results in a runtime failure.

Question

Is this an unintended package reference in jersey-container-servlet-core-4.0.0-M2?

If so, would it be possible to correct the reference in a future milestone/release?

I can provide stack traces, dependency information, and a minimal reproduction if needed.

Dominant language
Java
Stars
730
Forks
382
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-ee4j/jersey

All issues in eclipse-ee4j/jersey

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.