Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.1.4 broken release, JettyConnectorProvider always throws exception #5491

Closed
rickardoberg opened this issue Dec 6, 2023 · 2 comments
Closed
Milestone

Comments

@rickardoberg
Copy link

It seems like 3.1.4 is a broken release, as the JettyConnectorProvider always throws an exception:


    @Override
    public Connector getConnector(Client client, Configuration runtimeConfig) {
        throw new ProcessingException(LocalizationMessages.NOT_SUPPORTED());
    }
}

I'm going to take a wild guess and say that you probably meant to include a non-exception-throwing version under META-INF/versions/17, but there is no such class. So, the connector simply doesn't work at the moment.

@senivam
Copy link
Contributor

senivam commented Dec 6, 2023

yes, you are right. Fix is being prepared. Meanwhile, you can use jersey-jetty11-connector [module added since 3.1.4 version] which works. The jersey-jetty-connector module which will be fixed in the next release is Jetty 12 based. While jersey-jetty11-connector keeps backwards compatibility for the Jetty 11

@senivam senivam added this to the 3.1.5 milestone Dec 12, 2023
@senivam
Copy link
Contributor

senivam commented Dec 12, 2023

the 3.1.5 is out. The issue is fixed.

@senivam senivam closed this as completed Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants