[jira] [Closed] (ARIES-1785) Application without JAX_RS_EXTENSION_SELECT fetchs Extension
[ https://issues.apache.org/jira/browse/ARIES-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bischof closed ARIES-1785. - Resolution: Fixed Hi Carlos, it work for me as explained. Thank you. > Application without JAX_RS_EXTENSION_SELECT fetchs Extension > > > Key: ARIES-1785 > URL: https://issues.apache.org/jira/browse/ARIES-1785 > Project: Aries > Issue Type: Bug > Components: jax-rs-whiteboard >Affects Versions: jax-rs-whiteboard-1.0.0 >Reporter: Stefan Bischof >Priority: Major > Attachments: test.txt > > > Hi, > an application without any JAX_RS_EXTENSION_SELECT property fetchs a > extention. > see the attached test for more information. > (could be paste into org.apache.aries.jax.rs.itests test.JaxrsTest.java) > regards -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ARIES-1754) Application an Ressource CachingServiceReference can't be got
[
https://issues.apache.org/jira/browse/ARIES-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bischof closed ARIES-1754.
-
Resolution: Fixed
@ComponentPropertyType Annotations just work with newer versions of bnd.
Thank you and close this issue
> 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
(v7.6.3#76005)
[jira] [Resolved] (ARIES-1761) Provide support for camel-spring from blueprint-spring
[ https://issues.apache.org/jira/browse/ARIES-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved ARIES-1761. Resolution: Fixed Fix Version/s: blueprint-spring-camel-1.0.0 > Provide support for camel-spring from blueprint-spring > -- > > Key: ARIES-1761 > URL: https://issues.apache.org/jira/browse/ARIES-1761 > Project: Aries > Issue Type: New Feature > Components: Blueprint >Affects Versions: blueprint-spring-camel-1.0.0 >Reporter: Freeman Fang >Assignee: Guillaume Nodet >Priority: Major > Fix For: blueprint-spring-camel-1.0.0 > > Attachments: ARIES-1761.patch > > > With the old spring-dm, there's a "BundleContextAware" interface, any bean > implements this interface can get BundleContext injected. > With the new aries-blueprint-spring, we should follow similar pattern, like > check if a bean has setBundleContext method, if so, just inject the > BundleContext into the bean, so that the application bundles with work with > spring-dm can also work with aries-blueprint-spring -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ARIES-1761) Provide support for camel-spring from blueprint-spring
[ https://issues.apache.org/jira/browse/ARIES-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372663#comment-16372663 ] ASF subversion and git services commented on ARIES-1761: Commit 1825044 from [~gnt] in branch 'aries/trunk' [ https://svn.apache.org/r1825044 ] [ARIES-1761] Provide support for camel-spring from blueprint-spring > Provide support for camel-spring from blueprint-spring > -- > > Key: ARIES-1761 > URL: https://issues.apache.org/jira/browse/ARIES-1761 > Project: Aries > Issue Type: New Feature > Components: Blueprint >Affects Versions: blueprint-spring-camel-1.0.0 >Reporter: Freeman Fang >Assignee: Guillaume Nodet >Priority: Major > Fix For: blueprint-spring-camel-1.0.0 > > Attachments: ARIES-1761.patch > > > With the old spring-dm, there's a "BundleContextAware" interface, any bean > implements this interface can get BundleContext injected. > With the new aries-blueprint-spring, we should follow similar pattern, like > check if a bean has setBundleContext method, if so, just inject the > BundleContext into the bean, so that the application bundles with work with > spring-dm can also work with aries-blueprint-spring -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ARIES-1761) Provide support for camel-spring from blueprint-spring
[ https://issues.apache.org/jira/browse/ARIES-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated ARIES-1761: --- Issue Type: New Feature (was: Bug) > Provide support for camel-spring from blueprint-spring > -- > > Key: ARIES-1761 > URL: https://issues.apache.org/jira/browse/ARIES-1761 > Project: Aries > Issue Type: New Feature > Components: Blueprint >Affects Versions: blueprint-spring-camel-1.0.0 >Reporter: Freeman Fang >Assignee: Guillaume Nodet >Priority: Major > Attachments: ARIES-1761.patch > > > With the old spring-dm, there's a "BundleContextAware" interface, any bean > implements this interface can get BundleContext injected. > With the new aries-blueprint-spring, we should follow similar pattern, like > check if a bean has setBundleContext method, if so, just inject the > BundleContext into the bean, so that the application bundles with work with > spring-dm can also work with aries-blueprint-spring -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ARIES-1761) Provide support for camel-spring from blueprint-spring
[ https://issues.apache.org/jira/browse/ARIES-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated ARIES-1761: --- Affects Version/s: (was: blueprint-spring-0.5.0) blueprint-spring-camel-1.0.0 > Provide support for camel-spring from blueprint-spring > -- > > Key: ARIES-1761 > URL: https://issues.apache.org/jira/browse/ARIES-1761 > Project: Aries > Issue Type: Bug > Components: Blueprint >Affects Versions: blueprint-spring-camel-1.0.0 >Reporter: Freeman Fang >Assignee: Guillaume Nodet >Priority: Major > Attachments: ARIES-1761.patch > > > With the old spring-dm, there's a "BundleContextAware" interface, any bean > implements this interface can get BundleContext injected. > With the new aries-blueprint-spring, we should follow similar pattern, like > check if a bean has setBundleContext method, if so, just inject the > BundleContext into the bean, so that the application bundles with work with > spring-dm can also work with aries-blueprint-spring -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ARIES-1761) Provide support for camel-spring from blueprint-spring
[ https://issues.apache.org/jira/browse/ARIES-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned ARIES-1761: -- Assignee: Guillaume Nodet > Provide support for camel-spring from blueprint-spring > -- > > Key: ARIES-1761 > URL: https://issues.apache.org/jira/browse/ARIES-1761 > Project: Aries > Issue Type: Bug > Components: Blueprint >Affects Versions: blueprint-spring-0.5.0 >Reporter: Freeman Fang >Assignee: Guillaume Nodet >Priority: Major > Attachments: ARIES-1761.patch > > > With the old spring-dm, there's a "BundleContextAware" interface, any bean > implements this interface can get BundleContext injected. > With the new aries-blueprint-spring, we should follow similar pattern, like > check if a bean has setBundleContext method, if so, just inject the > BundleContext into the bean, so that the application bundles with work with > spring-dm can also work with aries-blueprint-spring -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ARIES-1761) Provide support for camel-spring from blueprint-spring
[ https://issues.apache.org/jira/browse/ARIES-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated ARIES-1761: --- Summary: Provide support for camel-spring from blueprint-spring (was: ensure we inject BundleContext to the beans which need it) > Provide support for camel-spring from blueprint-spring > -- > > Key: ARIES-1761 > URL: https://issues.apache.org/jira/browse/ARIES-1761 > Project: Aries > Issue Type: Bug > Components: Blueprint >Affects Versions: blueprint-spring-0.5.0 >Reporter: Freeman Fang >Priority: Major > Attachments: ARIES-1761.patch > > > With the old spring-dm, there's a "BundleContextAware" interface, any bean > implements this interface can get BundleContext injected. > With the new aries-blueprint-spring, we should follow similar pattern, like > check if a bean has setBundleContext method, if so, just inject the > BundleContext into the bean, so that the application bundles with work with > spring-dm can also work with aries-blueprint-spring -- This message was sent by Atlassian JIRA (v7.6.3#76005)
