-
Notifications
You must be signed in to change notification settings - Fork 357
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
InjectionManagerFactory not found with OSGi singe bundles #3588
Comments
@pavelbucek Commented org.glassfish.jersey.inject:jersey-hk2:jar:2.26-b06 |
@pavelbucek Commented |
@JohneDoe Commented More Details: |
@pavelbucek Commented |
@JohneDoe Commented is thought that org.glassfish.jersey.inject:jersey-hk2 can require org.glassfish.hk2:osgi-resource-locator and let it run befor jersey starts |
@pavelbucek Commented |
|
I had the exact same problem. jersey/core-common/src/main/java/org/glassfish/jersey/internal/OsgiRegistry.java Lines 93 to 105 in a401695
getBundleContext() returns null (only ACTIVE, STARTING, or STOPPING bundles have a BundleContext). Therefore setOSGiServiceFinderIteratorProvider() does not get invoked and ServiceFinder uses DefaultServiceIteratorProvider instead of OsgiServiceFinder. If you make sure I think |
Thanks @cliffred this really helped me! |
@cliffred Thanks as well - I was hitting a brick wall with getting to the bottom of this problem. Changing the start level for the |
Is it enough to set the |
I think so |
Ok, |
@jansupol Thanks for taking action on this. Just for record: I have patched the MANIFEST.MF in the core-common 2.30.1 jar in our environment and added the |
I am using the 2.31 jersey-common jar inside a karaf container and I still face the same issue with hk2 dependency injection.
|
* github/jnr: make github/jnr/com.github.jnr.ffi_2.1.12/osgi.bnd depend on latest available org.objectweb.asm 8.0.1 * glassfish/hk2: add 'Bundle-ActivationPolicy: lazy' to fix, see eclipse-ee4j/jersey#3588 (comment) * glassfish/jersey: fix dependency versions * glassfish/jersey/org.glassfish.jersey.core.jersey-client_2.30.1: add property to permit use of Require-Bundle * glassfish/jersey/org.glassfish.jersey.core.jersey-common_2.30.1: fix jakarta.annotation-api-version Change-Id: I1dad84fda54c93c7ba6aaa2e9159b5af488c52bb Signed-off-by: Tony Homer <tony.homer@intel.com>
i get same issue InjectionManagerFactory not found (i use 2.30.1) note solution here
|
* IDEMPIERE-4492 update jetty to 9.4.33.v20201020 update atmosphere to 2.5.15 * IDEMPIERE-4492 update jetty to 9.4.33.v20201020 (update configuration) update to default jetty configuration delete unused configuration (alpn, http2,..) * IDEMPIERE-4492 update orbit eclipse repository to 4.17 * IDEMPIERE-4492 update orbit eclipse repository to 4.17 (on parent pom) * IDEMPIERE-4492 update jasper to 6.15.0 * IDEMPIERE-4492 update jasper to 6.15.0 (IDEMPIERE-4504) get rid of bundle "org.w3c.dom.events version 3.0.0" by use old version of org.w3c.dom.smil note: on target platform a bundle has multi version then tycho can pickup correct version define on feature (tab included plugins, field version) but on eclipse when sync launching from .product it don't respect that value, always set highest version to bundle workaround: on target platform manual un-select bundle org.w3c.dom.smil 1.0.1 * IDEMPIERE-4492 update atmosphere to 2.6.4 * IDEMPIERE-4492 refine target platform use targetplatform-dsl to generate target platform https://github.com/eclipse-cbi/targetplatform-dsl + don't need to care update bundle version when update repository + at moment org.idempiere.eclipse.platform-feature include some feature form eclipse repository so target has to include that feature so target platform will include all bundler request by feature and bundle request by plugins of that feature and so on (ever optional so it make target content has more plugins than what we use on project next step will convert include feature to include plugins to define only what we used * IDEMPIERE-4492 refine target platform (continue) don't include framework feature, use include plugins to void load transitive dependency so minimize target flatform remove some unused feature from idempiere product * IDEMPIERE-4492 update c3p0 and database jdbc (patch from Carlos) * IDEMPIERE-4492 improve target platform (continue) provide test bundle require to repository for use on offline remove some unused bundle also fix for IDEMPIERE-4475 * IDEMPIERE-4492 improve target platform (continue IDEMPIERE-4475) add launch for unittest add more require bundle for unit test * IDEMPIERE-4492 fix for rest api refer:eclipse-ee4j/jersey#3588 (comment) * IDEMPIERE-4492 fix for rest api refer:eclipse-ee4j/jersey#3588 (comment)
* IDEMPIERE-4492 update jetty to 9.4.33.v20201020 update atmosphere to 2.5.15 * IDEMPIERE-4492 update jetty to 9.4.33.v20201020 (update configuration) update to default jetty configuration delete unused configuration (alpn, http2,..) * IDEMPIERE-4492 update orbit eclipse repository to 4.17 * IDEMPIERE-4492 update orbit eclipse repository to 4.17 (on parent pom) * IDEMPIERE-4492 update jasper to 6.15.0 * IDEMPIERE-4492 update jasper to 6.15.0 (IDEMPIERE-4504) get rid of bundle "org.w3c.dom.events version 3.0.0" by use old version of org.w3c.dom.smil note: on target platform a bundle has multi version then tycho can pickup correct version define on feature (tab included plugins, field version) but on eclipse when sync launching from .product it don't respect that value, always set highest version to bundle workaround: on target platform manual un-select bundle org.w3c.dom.smil 1.0.1 * IDEMPIERE-4492 update atmosphere to 2.6.4 * IDEMPIERE-4492 refine target platform use targetplatform-dsl to generate target platform https://github.com/eclipse-cbi/targetplatform-dsl + don't need to care update bundle version when update repository + at moment org.idempiere.eclipse.platform-feature include some feature form eclipse repository so target has to include that feature so target platform will include all bundler request by feature and bundle request by plugins of that feature and so on (ever optional so it make target content has more plugins than what we use on project next step will convert include feature to include plugins to define only what we used * IDEMPIERE-4492 refine target platform (continue) don't include framework feature, use include plugins to void load transitive dependency so minimize target flatform remove some unused feature from idempiere product * IDEMPIERE-4492 update c3p0 and database jdbc (patch from Carlos) * IDEMPIERE-4492 improve target platform (continue) provide test bundle require to repository for use on offline remove some unused bundle also fix for IDEMPIERE-4475 * IDEMPIERE-4492 improve target platform (continue IDEMPIERE-4475) add launch for unittest add more require bundle for unit test * IDEMPIERE-4492 fix for rest api refer:eclipse-ee4j/jersey#3588 (comment) * IDEMPIERE-4492 fix for rest api refer:eclipse-ee4j/jersey#3588 (comment)
* IDEMPIERE-4492 update jetty to 9.4.33.v20201020 update atmosphere to 2.5.15 * IDEMPIERE-4492 update jetty to 9.4.33.v20201020 (update configuration) update to default jetty configuration delete unused configuration (alpn, http2,..) * IDEMPIERE-4492 update orbit eclipse repository to 4.17 * IDEMPIERE-4492 update orbit eclipse repository to 4.17 (on parent pom) * IDEMPIERE-4492 update jasper to 6.15.0 * IDEMPIERE-4492 update jasper to 6.15.0 (IDEMPIERE-4504) get rid of bundle "org.w3c.dom.events version 3.0.0" by use old version of org.w3c.dom.smil note: on target platform a bundle has multi version then tycho can pickup correct version define on feature (tab included plugins, field version) but on eclipse when sync launching from .product it don't respect that value, always set highest version to bundle workaround: on target platform manual un-select bundle org.w3c.dom.smil 1.0.1 * IDEMPIERE-4492 update atmosphere to 2.6.4 * IDEMPIERE-4492 refine target platform use targetplatform-dsl to generate target platform https://github.com/eclipse-cbi/targetplatform-dsl + don't need to care update bundle version when update repository + at moment org.idempiere.eclipse.platform-feature include some feature form eclipse repository so target has to include that feature so target platform will include all bundler request by feature and bundle request by plugins of that feature and so on (ever optional so it make target content has more plugins than what we use on project next step will convert include feature to include plugins to define only what we used * IDEMPIERE-4492 refine target platform (continue) don't include framework feature, use include plugins to void load transitive dependency so minimize target flatform remove some unused feature from idempiere product * IDEMPIERE-4492 update c3p0 and database jdbc (patch from Carlos) * IDEMPIERE-4492 improve target platform (continue) provide test bundle require to repository for use on offline remove some unused bundle also fix for IDEMPIERE-4475 * IDEMPIERE-4492 improve target platform (continue IDEMPIERE-4475) add launch for unittest add more require bundle for unit test * IDEMPIERE-4492 fix for rest api refer:eclipse-ee4j/jersey#3588 (comment) * IDEMPIERE-4492 fix for rest api refer:eclipse-ee4j/jersey#3588 (comment)
Any chance to have this merged? Or should we fork and patch this? |
Hi,
if i use a "all-in-one" jersey jar i can use my Servlets.
if i use all the single bundles i got an error
some of the used bundles
The Error:
The text was updated successfully, but these errors were encountered: