[jira] [Commented] (IGNITE-17915) Generalize support for inversion of control mechanisms
[
https://issues.apache.org/jira/browse/IGNITE-17915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682020#comment-17682020
]
Semyon Danilov commented on IGNITE-17915:
-
The PR seems good to me, however I need a second opinion from [~mmuzaf]
> Generalize support for inversion of control mechanisms
> ---
>
> Key: IGNITE-17915
> URL: https://issues.apache.org/jira/browse/IGNITE-17915
> Project: Ignite
> Issue Type: Improvement
> Components: spring
>Affects Versions: 2.14
>Reporter: Łukasz Dywicki
>Assignee: Łukasz Dywicki
>Priority: Major
> Labels: patch-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Current inversion of control support for Ignite is bound to Spring framework
> and Spring ApplicationContext interface which is used to lookup beans by type
> or name.
> Above lookup criteria are fairly generic and can be used to first - extract,
> second - generalize support for foreign injections within Ignite itself. With
> little work it is possible to open this for further extensions. This is known
> pattern used in other Apache projects, ie.
> [{{BeanRepository}}|https://github.com/apache/camel/blob/camel-3.19.0/core/camel-api/src/main/java/org/apache/camel/spi/BeanRepository.java]
> and
> [{{Registry}}|https://github.com/apache/camel/blob/camel-3.19.0/core/camel-api/src/main/java/org/apache/camel/spi/Registry.java].
> Main motivation is Ignite running under OSGi which does not host Spring
> (Spring framework dropped support for OSGi a while ago), and has alternative
> ways to provide similar functionality. For OSGi there are mechanisms such as
> OSGi Blueprint and OSGi Service Registry itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17915) Generalize support for inversion of control mechanisms
[
https://issues.apache.org/jira/browse/IGNITE-17915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17676388#comment-17676388
]
Maxim Muzafarov commented on IGNITE-17915:
--
[~ldywicki] I've added you to the Contributors list. Please, check that you're
able to assign the issue.
> Generalize support for inversion of control mechanisms
> ---
>
> Key: IGNITE-17915
> URL: https://issues.apache.org/jira/browse/IGNITE-17915
> Project: Ignite
> Issue Type: Improvement
> Components: spring
>Affects Versions: 2.14
>Reporter: Łukasz Dywicki
>Priority: Major
> Labels: patch-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Current inversion of control support for Ignite is bound to Spring framework
> and Spring ApplicationContext interface which is used to lookup beans by type
> or name.
> Above lookup criteria are fairly generic and can be used to first - extract,
> second - generalize support for foreign injections within Ignite itself. With
> little work it is possible to open this for further extensions. This is known
> pattern used in other Apache projects, ie.
> [{{BeanRepository}}|https://github.com/apache/camel/blob/camel-3.19.0/core/camel-api/src/main/java/org/apache/camel/spi/BeanRepository.java]
> and
> [{{Registry}}|https://github.com/apache/camel/blob/camel-3.19.0/core/camel-api/src/main/java/org/apache/camel/spi/Registry.java].
> Main motivation is Ignite running under OSGi which does not host Spring
> (Spring framework dropped support for OSGi a while ago), and has alternative
> ways to provide similar functionality. For OSGi there are mechanisms such as
> OSGi Blueprint and OSGi Service Registry itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17915) Generalize support for inversion of control mechanisms
[
https://issues.apache.org/jira/browse/IGNITE-17915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17676366#comment-17676366
]
Łukasz Dywicki commented on IGNITE-17915:
-
[~mmuzaf] since I am not contributor in project I can not update issue. Feel
free to change assignee to me if needed.
> Generalize support for inversion of control mechanisms
> ---
>
> Key: IGNITE-17915
> URL: https://issues.apache.org/jira/browse/IGNITE-17915
> Project: Ignite
> Issue Type: Improvement
> Components: spring
>Affects Versions: 2.14
>Reporter: Łukasz Dywicki
>Priority: Major
> Labels: patch-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Current inversion of control support for Ignite is bound to Spring framework
> and Spring ApplicationContext interface which is used to lookup beans by type
> or name.
> Above lookup criteria are fairly generic and can be used to first - extract,
> second - generalize support for foreign injections within Ignite itself. With
> little work it is possible to open this for further extensions. This is known
> pattern used in other Apache projects, ie.
> [{{BeanRepository}}|https://github.com/apache/camel/blob/camel-3.19.0/core/camel-api/src/main/java/org/apache/camel/spi/BeanRepository.java]
> and
> [{{Registry}}|https://github.com/apache/camel/blob/camel-3.19.0/core/camel-api/src/main/java/org/apache/camel/spi/Registry.java].
> Main motivation is Ignite running under OSGi which does not host Spring
> (Spring framework dropped support for OSGi a while ago), and has alternative
> ways to provide similar functionality. For OSGi there are mechanisms such as
> OSGi Blueprint and OSGi Service Registry itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17915) Generalize support for inversion of control mechanisms
[
https://issues.apache.org/jira/browse/IGNITE-17915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17676364#comment-17676364
]
Maxim Muzafarov commented on IGNITE-17915:
--
I will take a look within the next few weeks.
[~ldywicki] you can assign the issue to yourself and set the right status.
> Generalize support for inversion of control mechanisms
> ---
>
> Key: IGNITE-17915
> URL: https://issues.apache.org/jira/browse/IGNITE-17915
> Project: Ignite
> Issue Type: Improvement
> Components: spring
>Affects Versions: 2.14
>Reporter: Łukasz Dywicki
>Priority: Major
> Labels: patch-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Current inversion of control support for Ignite is bound to Spring framework
> and Spring ApplicationContext interface which is used to lookup beans by type
> or name.
> Above lookup criteria are fairly generic and can be used to first - extract,
> second - generalize support for foreign injections within Ignite itself. With
> little work it is possible to open this for further extensions. This is known
> pattern used in other Apache projects, ie.
> [{{BeanRepository}}|https://github.com/apache/camel/blob/camel-3.19.0/core/camel-api/src/main/java/org/apache/camel/spi/BeanRepository.java]
> and
> [{{Registry}}|https://github.com/apache/camel/blob/camel-3.19.0/core/camel-api/src/main/java/org/apache/camel/spi/Registry.java].
> Main motivation is Ignite running under OSGi which does not host Spring
> (Spring framework dropped support for OSGi a while ago), and has alternative
> ways to provide similar functionality. For OSGi there are mechanisms such as
> OSGi Blueprint and OSGi Service Registry itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-17915) Generalize support for inversion of control mechanisms
[
https://issues.apache.org/jira/browse/IGNITE-17915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17657081#comment-17657081
]
Evgeny Stanilovsky commented on IGNITE-17915:
-
[~ldywicki] plz change status, [~mmuzaf] can you review it ?
> Generalize support for inversion of control mechanisms
> ---
>
> Key: IGNITE-17915
> URL: https://issues.apache.org/jira/browse/IGNITE-17915
> Project: Ignite
> Issue Type: Improvement
> Components: spring
>Affects Versions: 2.14
>Reporter: Łukasz Dywicki
>Priority: Major
> Labels: patch-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Current inversion of control support for Ignite is bound to Spring framework
> and Spring ApplicationContext interface which is used to lookup beans by type
> or name.
> Above lookup criteria are fairly generic and can be used to first - extract,
> second - generalize support for foreign injections within Ignite itself. With
> little work it is possible to open this for further extensions. This is known
> pattern used in other Apache projects, ie.
> [{{BeanRepository}}|https://github.com/apache/camel/blob/camel-3.19.0/core/camel-api/src/main/java/org/apache/camel/spi/BeanRepository.java]
> and
> [{{Registry}}|https://github.com/apache/camel/blob/camel-3.19.0/core/camel-api/src/main/java/org/apache/camel/spi/Registry.java].
> Main motivation is Ignite running under OSGi which does not host Spring
> (Spring framework dropped support for OSGi a while ago), and has alternative
> ways to provide similar functionality. For OSGi there are mechanisms such as
> OSGi Blueprint and OSGi Service Registry itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
