[GitHub] aries pull request: Performance improvements for service invocatio...
Github user netudima closed the pull request at: https://github.com/apache/aries/pull/25 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [VOTE] blueprint-parser-1.4.0, org.apache.aries.blueprint.core-1.5.0,
+1 (binding) Regards JB On 12/14/2015 04:47 PM, Christian Schneider wrote: I've staged some releases for vote. blueprint-parser-1.4.0 Repository: https://repository.apache.org/content/repositories/orgapachearies-1054 Release Notes https://issues.apache.org/jira/browse/ARIES/fixforversion/12334350 ** New Feature * [ARIES-1456] - Spring support blueprint-core-1.5.0 Repository: https://repository.apache.org/content/repositories/orgapachearies-1055 Release Notes https://issues.apache.org/jira/browse/ARIES/fixforversion/12334309 ** Bug * [ARIES-1467] - Blueprint creates unnecessary prototype bean instances * [ARIES-1477] - NPE in NamespaceHandlerRegistryImpl * [ARIES-1478] - Avoid possible IllegalStateException when registering a service org.apache.aries.blueprint.spring-0.1.0 org.apache.aries.blueprint.spring.extender-0.1.0 Repository: https://repository.apache.org/content/repositories/orgapachearies-1056 Release Notes https://issues.apache.org/jira/browse/ARIES/fixforversion/12334353 ** New Feature * [ARIES-1456] - Spring support * [ARIES-1480] - Complete spring extender support https://issues.apache.org/jira/browse/ARIES/fixforversion/12334351 ** New Feature * [ARIES-1456] - Spring support Please review and vote: [ ] +1 Release the above artifacts [ ] -1 Do not Here is my +1 Cheers, Christian -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
[jira] [Commented] (ARIES-1383) Provide option to disable the provisioning of dependencies at install time.
[ https://issues.apache.org/jira/browse/ARIES-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058133#comment-15058133 ] John Ross commented on ARIES-1383: -- Also http://svn.apache.org/viewvc?rev=1720173&view=rev and http://svn.apache.org/viewvc?rev=1720174&view=rev. I forgot to do a Git interactive rebase before svn dcommit. > Provide option to disable the provisioning of dependencies at install time. > --- > > Key: ARIES-1383 > URL: https://issues.apache.org/jira/browse/ARIES-1383 > Project: Aries > Issue Type: Improvement > Components: Subsystem >Affects Versions: subsystem-2.0.6, subsystem-2.0.8 >Reporter: John Ross >Assignee: John Ross > > PROBLEM > - > The Subsystems specification states that all dependencies of a subsystem must > have been installed in order to attain the INSTALLED state. If required > dependencies are not found, the installation must fail. > This functionality was described in order to achieve fail-fast functionality. > If an environment cannot support the dependencies of a subsystem, it is > rejected right away. > However, there are deployment situations where it is valuable to delay the > installation of dependencies. For example, you may wish to independently and > simultaneously install a suite of subsystems whose contents have interleaving > dependencies. This is currently not possible because the local repository of > one subsystem is not available to others. The resources will not be available > to others until they become part of the System Repository (assuming a > compatible sharing policy) once the INSTALLED state is acquired. In the > meantime, the other subsystems fail installation. > There are three potential workarounds to this issue, none of which may be > acceptable to a particular Subsystems consumer. > (1) Provide all content as part of a remote repository. Note that this would > require the Subsystem-Content header to be computed by the subsystem provider > and not by the implementation. > (2) Package all subsystems into a single ESA and make use of parent-child > relationships. > (3) Manage the install order manually. Note that this would not handle the > case of circular dependencies. > A solution that will allow for the independent and simultaneous installation > of multiple subsystems with interleaving content dependencies, thus giving a > deployer more flexibility, is desirable. > PROPOSED SOLUTION > - > A custom directive is introduced: apache-aries-provision-dependencies. The > possible values are "install" and "resolve", which indicate the time at which > dependency provisioning should occur. The default value is "install" which > results in the current behavior. This directive may be specified as part of > the Subsystem-Type header. A value of "resolve" indicates that dependencies > should not be provisioned at installation time. Rather, this step will occur > when the subsystem is resolved which typically happens as part of the start > process. > A subsystem with apache-aries-provision-dependencies:=resolve will remain in > the INSTALLING state until it is started. This is an indication to > administration programs monitoring subsystems via the service registry that > the subsystem has not yet had its dependencies provisioned. When the > subsystem is started, the transition from INSTALLING to INSTALLED will then > occur as it does today. Assuming the provisioning of dependencies succeeds, > the subsystem will then immediately transition into the RESOLVING state and > proceed as normal. > State transitions when apache-aries-provision-dependencies:=start: > install() : -> INSTALLING > -> INSTALLING -> INSTALL_FAILED -> UNINSTALLING > -> UNINSTALLED (if installation fails for some reason other than dependency > provisioning) > start() : INSTALLING -> INSTALLED -> RESOLVING -> RESOLVED -> STARTING > -> ACTIVE >INSTALLING -> INSTALLING (if provisioning of dependencies > fails) > INSTALLING -> INSTALLED -> RESOLVING -> INSTALLED (if > runtime resolution fails) > >INSTALLING -> INSTALLED -> RESOLVING -> RESOLVED -> > STARTING -> RESOLVED (if starting fails) > Child scoped subsystems inherit the apache-aries-provision-dependencies value > of the first scoped ancestor unless explicitly overridden. Unscoped > subsystems always inherit the apache-aries-provision-dependencies value of > the first scoped ancestor and may not override the value. The root subsystem > always has a value of apache-aries-provision-dependencies:=install. > ALTERNATIVE SOLUTIONS > - > (1) Make the local repositories o
[jira] [Commented] (ARIES-1383) Provide option to disable the provisioning of dependencies at install time.
[ https://issues.apache.org/jira/browse/ARIES-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058123#comment-15058123 ] ASF subversion and git services commented on ARIES-1383: Commit 1720175 from [~jwr...@us.ibm.com] in branch 'aries/trunk' [ https://svn.apache.org/r1720175 ] [ARIES-1383] Provide option to disable the provisioning of dependencies at install time. Composites in the INSTALLING state and having apache-aries-provision-dependencies:=resolve must have their export sharing policies set in order for any offered capabilities to be considered valid as part of computing the dependencies of another subsystem having the same state and directive value. Currently, a brute force method is used whereby all composites fitting the above criteria will have their export policies temporarily enabled. Any that did not end up offering a capability used to resolve the other subsystem will have their policies rolled back. Plus test. > Provide option to disable the provisioning of dependencies at install time. > --- > > Key: ARIES-1383 > URL: https://issues.apache.org/jira/browse/ARIES-1383 > Project: Aries > Issue Type: Improvement > Components: Subsystem >Affects Versions: subsystem-2.0.6, subsystem-2.0.8 >Reporter: John Ross >Assignee: John Ross > > PROBLEM > - > The Subsystems specification states that all dependencies of a subsystem must > have been installed in order to attain the INSTALLED state. If required > dependencies are not found, the installation must fail. > This functionality was described in order to achieve fail-fast functionality. > If an environment cannot support the dependencies of a subsystem, it is > rejected right away. > However, there are deployment situations where it is valuable to delay the > installation of dependencies. For example, you may wish to independently and > simultaneously install a suite of subsystems whose contents have interleaving > dependencies. This is currently not possible because the local repository of > one subsystem is not available to others. The resources will not be available > to others until they become part of the System Repository (assuming a > compatible sharing policy) once the INSTALLED state is acquired. In the > meantime, the other subsystems fail installation. > There are three potential workarounds to this issue, none of which may be > acceptable to a particular Subsystems consumer. > (1) Provide all content as part of a remote repository. Note that this would > require the Subsystem-Content header to be computed by the subsystem provider > and not by the implementation. > (2) Package all subsystems into a single ESA and make use of parent-child > relationships. > (3) Manage the install order manually. Note that this would not handle the > case of circular dependencies. > A solution that will allow for the independent and simultaneous installation > of multiple subsystems with interleaving content dependencies, thus giving a > deployer more flexibility, is desirable. > PROPOSED SOLUTION > - > A custom directive is introduced: apache-aries-provision-dependencies. The > possible values are "install" and "resolve", which indicate the time at which > dependency provisioning should occur. The default value is "install" which > results in the current behavior. This directive may be specified as part of > the Subsystem-Type header. A value of "resolve" indicates that dependencies > should not be provisioned at installation time. Rather, this step will occur > when the subsystem is resolved which typically happens as part of the start > process. > A subsystem with apache-aries-provision-dependencies:=resolve will remain in > the INSTALLING state until it is started. This is an indication to > administration programs monitoring subsystems via the service registry that > the subsystem has not yet had its dependencies provisioned. When the > subsystem is started, the transition from INSTALLING to INSTALLED will then > occur as it does today. Assuming the provisioning of dependencies succeeds, > the subsystem will then immediately transition into the RESOLVING state and > proceed as normal. > State transitions when apache-aries-provision-dependencies:=start: > install() : -> INSTALLING > -> INSTALLING -> INSTALL_FAILED -> UNINSTALLING > -> UNINSTALLED (if installation fails for some reason other than dependency > provisioning) > start() : INSTALLING -> INSTALLED -> RESOLVING -> RESOLVED -> STARTING > -> ACTIVE >INSTALLING -> INSTALLING (if provisioning of dependencies > fails) > INSTALLING -> INSTALLED -> RESOLVING -> INSTALLED
Re: [VOTE] blueprint-parser-1.4.0, org.apache.aries.blueprint.core-1.5.0,
+1 (non-binding) tested with camel-test-blueprint regards Grzegorz Grzybek 2015-12-14 22:35 GMT+01:00 Sergey Beryozkin : > +1 > > Sergey > > On 14/12/15 15:47, Christian Schneider wrote: >> >> I've staged some releases for vote. >> >> >> blueprint-parser-1.4.0 >> >> Repository: >> https://repository.apache.org/content/repositories/orgapachearies-1054 >> >> Release Notes >> https://issues.apache.org/jira/browse/ARIES/fixforversion/12334350 >> >> ** New Feature >> * [ARIES-1456] - Spring support >> >> >> blueprint-core-1.5.0 >> >> Repository: >> https://repository.apache.org/content/repositories/orgapachearies-1055 >> >> >> Release Notes >> https://issues.apache.org/jira/browse/ARIES/fixforversion/12334309 >> >> ** Bug >> * [ARIES-1467] - Blueprint creates unnecessary prototype bean >> instances >> * [ARIES-1477] - NPE in NamespaceHandlerRegistryImpl >> * [ARIES-1478] - Avoid possible IllegalStateException when >> registering a service >> >> >> org.apache.aries.blueprint.spring-0.1.0 >> org.apache.aries.blueprint.spring.extender-0.1.0 >> >> Repository: >> https://repository.apache.org/content/repositories/orgapachearies-1056 >> >> Release Notes >> https://issues.apache.org/jira/browse/ARIES/fixforversion/12334353 >> ** New Feature >> * [ARIES-1456] - Spring support >> * [ARIES-1480] - Complete spring extender support >> >> https://issues.apache.org/jira/browse/ARIES/fixforversion/12334351 >> ** New Feature >> * [ARIES-1456] - Spring support >> >> Please review and vote: >>[ ] +1 Release the above artifacts >>[ ] -1 Do not >> >> Here is my +1 >> >> Cheers, >> Christian >> > > > -- > Sergey Beryozkin > > Talend Community Coders > http://coders.talend.com/
