[jira] [Commented] (ARIES-1928) Applications depending on failing extensions should be held undeployed
[ https://issues.apache.org/jira/browse/ARIES-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927738#comment-16927738 ] ASF subversion and git services commented on ARIES-1928: Commit 14d481f5442f54515093e2d702cd5ca0d2d1a7b4 in aries-jax-rs-whiteboard's branch refs/heads/master from Carlos Sierra [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=14d481f ] [ARIES-1928] These are still needed to be able to track which the services that triggered the registrations. > Applications depending on failing extensions should be held undeployed > -- > > Key: ARIES-1928 > URL: https://issues.apache.org/jira/browse/ARIES-1928 > Project: Aries > Issue Type: Bug > Components: jax-rs-whiteboard >Affects Versions: jax-rs-whiteboard-1.0.4 >Reporter: Carlos Sierra >Priority: Major > Fix For: jax-rs-whiteboard-1.0.5 > > > If application depends on a extensions that fails when it is wired to the > application, the application should be held. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (ARIES-1929) Performance optimization
[ https://issues.apache.org/jira/browse/ARIES-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927551#comment-16927551 ] ASF subversion and git services commented on ARIES-1929: Commit 0816520e651c2ba7172720463a118753859b9a00 in aries-jax-rs-whiteboard's branch refs/heads/master from Carlos Sierra [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=0816520 ] [ARIES-1929] Special error handling in the first rewire If we get a wiring error in the first (probably bulk) rewire we need to discard one by one the possible services that are causing it. Since CXF does not inform about which service is causing the error we need to try incrementally. Once we have ruled out the failing services we mark them as such in the runtime and in the extension registry, which might cause some more extensions or services to be unregistered from the application (even the very application). During this process we disable the registrator so we don't get re-entrant rewires and, when finalized, we try to wire the application again. If the application still fails we mark it as failing. > Performance optimization > > > Key: ARIES-1929 > URL: https://issues.apache.org/jira/browse/ARIES-1929 > Project: Aries > Issue Type: Improvement > Components: jax-rs-whiteboard >Affects Versions: jax-rs-whiteboard-1.0.4 >Reporter: Carlos Sierra >Priority: Major > Fix For: jax-rs-whiteboard-1.0.5 > > > Currently the deployment of one application involves a redeployment of the > whole application per service that conforms the application. That means that, > if an application is composed of 20 services it will be rewired 20 times even > if all the services are present when the application is registered. > This should not be necessary and an optimization can be made for the _best > case_, being that all the services are present at the moment of the > application registration so one rewire should be made. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (ARIES-1928) Applications depending on failing extensions should be held undeployed
[ https://issues.apache.org/jira/browse/ARIES-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927557#comment-16927557 ] ASF subversion and git services commented on ARIES-1928: Commit 978eca4ab6906899dddb9530d20292b16e4a4871 in aries-jax-rs-whiteboard's branch refs/heads/master from Carlos Sierra [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=978eca4 ] [ARIES-1928] Add new test > Applications depending on failing extensions should be held undeployed > -- > > Key: ARIES-1928 > URL: https://issues.apache.org/jira/browse/ARIES-1928 > Project: Aries > Issue Type: Bug > Components: jax-rs-whiteboard >Affects Versions: jax-rs-whiteboard-1.0.4 >Reporter: Carlos Sierra >Priority: Major > Fix For: jax-rs-whiteboard-1.0.5 > > > If application depends on a extensions that fails when it is wired to the > application, the application should be held. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (ARIES-1927) Applications registered with higher ranking should shadow other applications even if their extensions dependencies are not met
[ https://issues.apache.org/jira/browse/ARIES-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927554#comment-16927554 ] ASF subversion and git services commented on ARIES-1927: Commit bd50412cf37ae96c76888b72b45cd9ff6ba73f67 in aries-jax-rs-whiteboard's branch refs/heads/master from Carlos Sierra [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=bd50412 ] [ARIES-1927] Change order of checks Application dependencies check must come after shadowing > Applications registered with higher ranking should shadow other applications > even if their extensions dependencies are not met > -- > > Key: ARIES-1927 > URL: https://issues.apache.org/jira/browse/ARIES-1927 > Project: Aries > Issue Type: Bug > Components: jax-rs-whiteboard >Affects Versions: jax-rs-whiteboard-1.0.4 >Reporter: Carlos Sierra >Priority: Major > Fix For: jax-rs-whiteboard-1.0.5 > > > According to the spec any registered application with a higher ranking should > shadow other applications even when the shadowing applications does not have > its extension dependencies fulfilled. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (ARIES-1929) Performance optimization
[ https://issues.apache.org/jira/browse/ARIES-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927552#comment-16927552 ] ASF subversion and git services commented on ARIES-1929: Commit 5e16be26c886e1ea37e8cf240af52caf41aaa8b8 in aries-jax-rs-whiteboard's branch refs/heads/master from Carlos Sierra [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=5e16be2 ] [ARIES-1929] Add test for errors in the initial case > Performance optimization > > > Key: ARIES-1929 > URL: https://issues.apache.org/jira/browse/ARIES-1929 > Project: Aries > Issue Type: Improvement > Components: jax-rs-whiteboard >Affects Versions: jax-rs-whiteboard-1.0.4 >Reporter: Carlos Sierra >Priority: Major > Fix For: jax-rs-whiteboard-1.0.5 > > > Currently the deployment of one application involves a redeployment of the > whole application per service that conforms the application. That means that, > if an application is composed of 20 services it will be rewired 20 times even > if all the services are present when the application is registered. > This should not be necessary and an optimization can be made for the _best > case_, being that all the services are present at the moment of the > application registration so one rewire should be made. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (ARIES-1928) Applications depending on failing extensions should be held undeployed
[ https://issues.apache.org/jira/browse/ARIES-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927555#comment-16927555 ] ASF subversion and git services commented on ARIES-1928: Commit b2149355f401c4f6bc4f774cc6ed1a3e3442fa48 in aries-jax-rs-whiteboard's branch refs/heads/master from Carlos Sierra [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=b214935 ] [ARIES-1928] Track extensions per application Before there was a global registry for extensions. The presence or absence of an extension does not mean anything until it is initialized inside an application. An application depending on extensions should not be deployed until its dependencies have been checked to work. Also, instead of registering the CxfJaxrsServiceRegistrator, we now register the application in a internal registry, which simplifies the extension attaching. > Applications depending on failing extensions should be held undeployed > -- > > Key: ARIES-1928 > URL: https://issues.apache.org/jira/browse/ARIES-1928 > Project: Aries > Issue Type: Bug > Components: jax-rs-whiteboard >Affects Versions: jax-rs-whiteboard-1.0.4 >Reporter: Carlos Sierra >Priority: Major > Fix For: jax-rs-whiteboard-1.0.5 > > > If application depends on a extensions that fails when it is wired to the > application, the application should be held. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (ARIES-1928) Applications depending on failing extensions should be held undeployed
[ https://issues.apache.org/jira/browse/ARIES-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927556#comment-16927556 ] ASF subversion and git services commented on ARIES-1928: Commit 719850452f78833fc86ca8ddd3b8a49547963cec in aries-jax-rs-whiteboard's branch refs/heads/master from Carlos Sierra [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=7198504 ] [ARIES-1928] No need to register the registrators in OSGi registry > Applications depending on failing extensions should be held undeployed > -- > > Key: ARIES-1928 > URL: https://issues.apache.org/jira/browse/ARIES-1928 > Project: Aries > Issue Type: Bug > Components: jax-rs-whiteboard >Affects Versions: jax-rs-whiteboard-1.0.4 >Reporter: Carlos Sierra >Priority: Major > Fix For: jax-rs-whiteboard-1.0.5 > > > If application depends on a extensions that fails when it is wired to the > application, the application should be held. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (ARIES-1929) Performance optimization
[ https://issues.apache.org/jira/browse/ARIES-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927553#comment-16927553 ] ASF subversion and git services commented on ARIES-1929: Commit bdd962c77d86dd5522077cf657e1977bf18300ef in aries-jax-rs-whiteboard's branch refs/heads/master from Carlos Sierra [ https://gitbox.apache.org/repos/asf?p=aries-jax-rs-whiteboard.git;h=bdd962c ] [ARIES-1929] Add support for a ready service for applications It is treated as a raw dependency for the application. It allows to defer application tracking until the ready service is present so the rest of the components can be registered before the application, thus minimizing the number of application rewires. > Performance optimization > > > Key: ARIES-1929 > URL: https://issues.apache.org/jira/browse/ARIES-1929 > Project: Aries > Issue Type: Improvement > Components: jax-rs-whiteboard >Affects Versions: jax-rs-whiteboard-1.0.4 >Reporter: Carlos Sierra >Priority: Major > Fix For: jax-rs-whiteboard-1.0.5 > > > Currently the deployment of one application involves a redeployment of the > whole application per service that conforms the application. That means that, > if an application is composed of 20 services it will be rewired 20 times even > if all the services are present when the application is registered. > This should not be necessary and an optimization can be made for the _best > case_, being that all the services are present at the moment of the > application registration so one rewire should be made. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (ARIES-1926) UpdateSupport is changing effects execution order
[ https://issues.apache.org/jira/browse/ARIES-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927540#comment-16927540 ] ASF subversion and git services commented on ARIES-1926: Commit a86ab9cf1bd3686ae96a4fa859d67a468cd23d86 in aries-component-dsl's branch refs/heads/master from Carlos Sierra [ https://gitbox.apache.org/repos/asf?p=aries-component-dsl.git;h=a86ab9c ] [ARIES-1926] UpdateSupport should not reorder effects So publication of new event should happen after the termination of the deferred terminators when running inside an upgrade operation. > UpdateSupport is changing effects execution order > - > > Key: ARIES-1926 > URL: https://issues.apache.org/jira/browse/ARIES-1926 > Project: Aries > Issue Type: Bug > Components: Component DSL >Affects Versions: component-dsl-1.2.1 >Reporter: Carlos Sierra >Priority: Major > Fix For: component-dsl-1.2.2 > > > When running as a result of an update operation, nodes with update support > where reorganizing the effects because the termination was deferred but not > the following adding event. This caused publication of the new event to > happen before the termination of the previous event. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (ARIES-1929) Performance optimization
Carlos Sierra created ARIES-1929: Summary: Performance optimization Key: ARIES-1929 URL: https://issues.apache.org/jira/browse/ARIES-1929 Project: Aries Issue Type: Improvement Components: jax-rs-whiteboard Affects Versions: jax-rs-whiteboard-1.0.4 Reporter: Carlos Sierra Fix For: jax-rs-whiteboard-1.0.5 Currently the deployment of one application involves a redeployment of the whole application per service that conforms the application. That means that, if an application is composed of 20 services it will be rewired 20 times even if all the services are present when the application is registered. This should not be necessary and an optimization can be made for the _best case_, being that all the services are present at the moment of the application registration so one rewire should be made. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (ARIES-1928) Applications depending on failing extensions should be held undeployed
Carlos Sierra created ARIES-1928: Summary: Applications depending on failing extensions should be held undeployed Key: ARIES-1928 URL: https://issues.apache.org/jira/browse/ARIES-1928 Project: Aries Issue Type: Bug Components: jax-rs-whiteboard Affects Versions: jax-rs-whiteboard-1.0.4 Reporter: Carlos Sierra Fix For: jax-rs-whiteboard-1.0.5 If application depends on a extensions that fails when it is wired to the application, the application should be held. -- This message was sent by Atlassian Jira (v8.3.2#803003)
