[
https://issues.apache.org/jira/browse/ARIES-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240447#comment-16240447
]
Carlos Sierra commented on ARIES-1754:
--------------------------------------
Hey Stefan.
On friday I uploaded a new snapshot version of the whiteboard including some
changes like CachindServiceReference that solved a series of bugs. Nevertheless
all tests in the suite seem to be passing and many (more than before) in the
OSGi CT suite are passing.
Could you upload the code you are having problem with? Because there should be
no reason for a user of the whiteboard to see CachingServiceReference at all,
as far as I understand.
Thanks.
Carlos.
> Application an Ressource CachingServiceReference can't be got
> -------------------------------------------------------------
>
> Key: ARIES-1754
> URL: https://issues.apache.org/jira/browse/ARIES-1754
> Project: Aries
> Issue Type: Bug
> Components: jax-rs-whiteboard
> Affects Versions: jax-rs-whiteboard-1.0.0
> Environment: Framework Felix
> Reporter: Stefan Bischof
> Priority: Blocker
>
> 1.
> with the newest snapshot from Friday 10.11.2017
> All reference of Applications ans Ressources without the .defaule Application
> can't be got from org.apache.aries.osgi.functional.CachingServiceReference
> 14:52:54.740 [Timer-0] WARN
> org.apache.aries.jax.rs.whiteboard.internal.Whiteboard - Application from
> reference org.apache.aries.osgi.functional.CachingServiceReference@5369019f
> can't be got
> 14:52:54.745 [Timer-0] WARN
> org.apache.aries.jax.rs.whiteboard.internal.Whiteboard - Resource from
> reference org.apache.aries.osgi.functional.CachingServiceReference@464309e7
> can't be got
> (2.)
> Can you tell me with bundles so i need to let the Annotations work
> @JaxrsName(OpenApiApplication.APPLICATION_NAME)
> @JaxrsApplicationBase("/" + OpenApiApplication.APPLICATION_NAME)
> 3.
> I got a null pointer by loading the getRuntimeDTO() when there war a Filter
> without name gegisteres. Will report it again, if this problem is solved
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
