You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "Raymond Augé (JIRA)" <ji...@apache.org> on 2018/08/20 15:05:00 UTC

[jira] [Closed] (ARIES-1807) SPI-Fly's weaving hook is subject to start ordering

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

Raymond Augé closed ARIES-1807.
-------------------------------
       Resolution: Duplicate
    Fix Version/s: spifly-1.0.14

> SPI-Fly's weaving hook is subject to start ordering
> ---------------------------------------------------
>
>                 Key: ARIES-1807
>                 URL: https://issues.apache.org/jira/browse/ARIES-1807
>             Project: Aries
>          Issue Type: Bug
>          Components: SPI Fly
>            Reporter: Raymond Augé
>            Assignee: Raymond Augé
>            Priority: Major
>             Fix For: spifly-1.0.14
>
>
> SPI-Fly is subject to start ordering constraints. This is because weaving hooks are not retroactive in the framework, they only take effect at the moment they are registered. As such they do not operate on previous possible candiates.
> It would be nice if SPI-Fly could trigger a refresh on already installed bundles such that weaving would take affect on them. This would eliminate the start ordering problem. Making this a configurable feature would also probably be a good idea.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)