[jira] [Commented] (CAMEL-17571) camel-main - Allow to bean inject beans from @Inject and other similar annotations

["Grzegorz Grzybek (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-17571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612240#comment-17612240 ] 

Grzegorz Grzybek commented on CAMEL-17571:
------------------------------------------

CAMEL-18555 is about replacing Shrinkwrap with pure maven-resolver. However, because of MRESOLVER-157 we can no longer use convenient {{org.eclipse.aether.impl.DefaultServiceLocator}} and we need actual DI solution working with JSR-330 annotation ({{@javax.inject.Inject}}).
I'm checking if the work done for this issue can be used to configure maven-resolver's {{org.eclipse.aether.RepositorySystem}}.

> camel-main - Allow to bean inject beans from @Inject and other similar annotations
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-17571
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17571
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-main
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.16.0
>
>
> When running Camel standalone (not spring boot / quarkus / camel-k) but also with jbang, then it can be good if we can also allow to discover bean injections via @Inject and similar annotations. You can use Camels own @BeanInject but you may build a prototype and run standalone, and then later want to move this over to SB / Camel-K or Quarkus and then its easier if some of their annotations is already supported.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)