camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-3295) camel-blueprint - Dependency Injection seems not working
Date Tue, 07 Dec 2010 14:59:09 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Guillaume Nodet resolved CAMEL-3295.
------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Future)
                   2.6.0

> camel-blueprint - Dependency Injection seems not working
> --------------------------------------------------------
>
>                 Key: CAMEL-3295
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3295
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-blueprint
>    Affects Versions: 2.5.0
>            Reporter: Edstrom Johan
>            Assignee: Guillaume Nodet
>            Priority: Minor
>             Fix For: 2.6.0
>
>
> This is just a placeholder - things like this should work.
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
>            xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0"
>            xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0"
>            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>            xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
>             http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd">
>     <camelContext xmlns="http://camel.apache.org/schema/blueprint" id="camelBlueprint">
>         <route>
>             <from uri="jms:queue"/>
>             <to uri="mock:result"/>
>         </route>
>     </camelContext>
>     <bean id="jms" class="org.apache.camel.component.jms.JmsComponent">
>         <property name="connectionFactory" ref="jmsConnectionPool"/>
>     </bean>
>     <reference id="jmsConnectionPool" interface="javax.jms.ConnectionFactory"/>
> </blueprint>
> {code}
> Currently the jmsConnectionPool is not at all passed to the JmsComponent.
> The usage of JmsTemplate as debated on the mailinglists I think is of a (currently) much
lesser concern.
> Especially comparing a little to the ProducerCode in the servicemix-jms components.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message