-
Notifications
You must be signed in to change notification settings - Fork 355
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
SseEventSource cannot see the JAXRS_DEFAULT_SSE_BUILDER in OSGI #4649
Comments
Basically, we have two possible options:
I wonder if there is more OSGi catches like that throughout Jersey |
This was referenced Jun 26, 2021
Merged
This was referenced Jul 6, 2021
This was referenced Aug 5, 2021
This was referenced Aug 30, 2021
1 task
This was referenced Oct 4, 2021
This was referenced Mar 7, 2022
This was referenced Mar 15, 2022
This was referenced Apr 17, 2022
This was referenced May 3, 2022
Closed
1 task
Closed
1 task
1 task
This was referenced Oct 19, 2022
Closed
1 task
This was referenced Feb 11, 2023
Closed
1 task
This was referenced May 11, 2023
This was referenced Jun 15, 2023
This was referenced Jul 6, 2023
1 task
This was referenced Apr 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because the package org.glassfish.jersey.media.sse.internal is not exported in the jersey-media-sse bundle,e.g. the JaxRs client is not able to load the default SSE builder.
This is a constellation that will never work.
A possible solution could be to introduce a factory in the SSE that can be instanciated reflectivley and then create the builder instance in the javax.ws.rs.ext.sse.FactoryFinder#find call
There is an initial issues at the JaxRs-api repository that is related to this, because I believe SSE and API are involved in that problem:
jakartaee/rest#925
The text was updated successfully, but these errors were encountered: