-
Notifications
You must be signed in to change notification settings - Fork 602
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
HTTP Cache Factories do not have correct names in /confMgr #1720
Comments
Nice find kwin, I will try this one. If not, I will have to duplicate the exact same generic OCD 4 times :( |
To me it just seems that the necessary name hints are just missing (e.g. in |
I think your right. I will try this out once I got some time (should be soon) and let you know the result.. if it works we'll use it. |
I cannot get it to work. What about you Konrad? If not, we have to eat copy pasta for dinner I'm afraid. |
🍝 |
Sorry, I was not looking closely enough. This is about reusing the same metatype in the context of 4 different services (not about differentiating the individual instance per factory which would indeed work via name hint). I asked about this now via https://mail.osgi.org/pipermail/osgi-dev/2019-January/007382.html. |
Ah Konrad, many thanks. Not sure how long we can keep the PR unmerged for your ticket. But greatly appreciated. |
Fixed via and closing due to revert back to SCR: #1741 |
Required Information
master
)Expected Behavior
The names in /system/console/confMgr should be accurate and meaningful.
Actual Behavior
The names in /confMgr are the same for several
Steps to Reproduce
Install latest from master and goto /system/console/confMgr
Links
Looks like this is because OCD definitions are shared between impl's. Im not sure how to remedy this without copying the impl and updating the keys. In the case of the
KeyValueConfig
it seems odd these 4 HttpCacheConfigExtension would use the same one; ie I think this is a bug in the move to new OSGi annotations for HTTP Cache. Not sure about the first duplication./cc @niekraaijmakers
The text was updated successfully, but these errors were encountered: