-
Notifications
You must be signed in to change notification settings - Fork 168
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
OSGi: Use declarative service registration instead of programmatic for #4371 #4372
Comments
Hi Denis, does your service not appear at all or is it registered but just not activated? Kind regards, |
Hi, |
Did you check if your service throws any Exceptions within its If you are using felix-scr at runtime for your declarative services then in the gogo shell you could use the scr commands to get more information about the bundles and services they provide and if your service is not found at all or registered but not activated. |
I don't have any I think I missed something trying But thank you for helping with this anyway! |
Just for the reference: If you don't have implementation bundles in your OSGi container then this declarative registration won't work. In our felix tests currently no implementation is deployed so that's the reason why it doesn't work. |
I've been trying to register a service using OSGi
@Component
annotation instead of using bundle activator and programmatic registration. But I'm failed: the service for some reason doesn't appear as a registered in theflow-client
bundle.It would be nice (though not necessary) to use declarative OSGi service registration instead of programmatic.
This is just an enhancement and is not a top priority. We may live without this.
The text was updated successfully, but these errors were encountered: