Hi Karen-
Yes, beans created in blueprint can be exported as an OSGi service via
blueprint. Likewise, other beans exposed as a service may be used by other
beans in a blueprint definition.
Register a service from bean:
<service id="serviceOne" ref="account"
interface="org.apache.aries.simple.Account" />
Reference a service for use by a blueprint-created bean:
<bean id="accountClient" class="...">
<property name="account" ref="accountRef" />
</bean>
<reference id="accountRef" interface="org.apache.aries.simple.Account" />
-Matt Pavlovich
> On Mar 31, 2025, at 8:57 AM, Karen Dolan <[email protected]> wrote:
>
> Hi JB & Matthias,
>
> I’m also interested in Aries Blueprint, specifically to support
> aries-blueprint-spring, ultimately in Karaf.
>
> I’m curious if Camel features/services/libraries can be a-la-carte exported
> in a Karaf environment to support a non-Camel application that needs access
> to those upgraded libraries?
>
> Regards,
> Karen
>
>
>> On Mar 31, 2025, at 9:14 AM, Jean-Baptiste Onofré <[email protected]> wrote:
>>
>> Hi Matthias
>>
>> Aries Blueprint is not dead but slow development. I did the
>> camel-blueprint support, and happy to update in camel-karaf if there
>> are requests.
>>
>> If you don't want to use blueprint anymore, a good alternative is SCR.
>> Another option would be to add new DSL support in camel-karaf
>> (native).
>>
>> Regards
>> JB
>>
>> On Wed, Mar 26, 2025 at 2:32 PM Matthias Leinweber
>> <[email protected]> wrote:
>>>
>>> Hi Karaf-Users,
>>>
>>> I'm curious how everyone is managing blueprints in Karaf. We rely heavily
>>> on blueprint camel, but Camel's rapid development is outpacing aries. Some
>>> Camel features, like creating beans from scriptFiles, aren't available.
>>>
>>> Given this, is Aries Blueprint dead? Should we explore bundling a Camel
>>> spring XML loader for Karaf?
>>>
>>> Best regards,
>>> Matthias
>>>
>
>
>
>
>
>
