Re: New release of Aries Component DSL 1.2.0
+1 from my side. Regards JB On 18/06/2018 18:06, Carlos Sierra Andrés wrote: > Hello all, > > I would like to make a new release 1.2.0 of Aries Component DSL. > > Four JIRA tickets have been closed: > > * ARIES-1810 > > * ARIES-1811 > > * ARIES-1812 > > * ARIES-1813 > > some of which can be considered severe bugs that could prevent usage in > some scenarios. > > If no one opposes I will open a vote in the next days. > > Thanks. > > Carlos. > > -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
New release of Aries Component DSL 1.2.0
Hello all, I would like to make a new release 1.2.0 of Aries Component DSL. Four JIRA tickets have been closed: * ARIES-1810 * ARIES-1811 * ARIES-1812 * ARIES-1813 some of which can be considered severe bugs that could prevent usage in some scenarios. If no one opposes I will open a vote in the next days. Thanks. Carlos.
[jira] [Resolved] (ARIES-1810) `onClose` does not execute the action in the correct order
[
https://issues.apache.org/jira/browse/ARIES-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sierra resolved ARIES-1810.
--
Resolution: Fixed
Fix Version/s: component-dsl-1.2.0
> `onClose` does not execute the action in the correct order
> --
>
> Key: ARIES-1810
> URL: https://issues.apache.org/jira/browse/ARIES-1810
> Project: Aries
> Issue Type: Bug
> Components: Component DSL
>Affects Versions: component-dsl-1.1.0
>Reporter: Carlos Sierra
>Priority: Major
> Fix For: component-dsl-1.2.0
>
>
> It executed the _on leave_ action in the opposite order to {{effects}} which
> creates inconsistencies.
> Actually onClose should be deprecated in favor of effects
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ARIES-1812) `once` should support updates
[
https://issues.apache.org/jira/browse/ARIES-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sierra resolved ARIES-1812.
--
Resolution: Fixed
Fix Version/s: component-dsl-1.2.0
> `once` should support updates
> -
>
> Key: ARIES-1812
> URL: https://issues.apache.org/jira/browse/ARIES-1812
> Project: Aries
> Issue Type: Bug
> Components: Component DSL
>Affects Versions: component-dsl-1.1.0
>Reporter: Carlos Sierra
>Priority: Minor
> Fix For: component-dsl-1.2.0
>
>
> {{once}} is normally used to test the existance of a given service or
> configuration with certain properties. When there is only one tracked
> instance and that instance is updated, {{once}} will retract the program
> associated to the instance and publish the instance again. This is usually
> unnecessary and {{once}} should support update operations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ARIES-1811) `effects` is not unwinding properly when exceptions occur
[
https://issues.apache.org/jira/browse/ARIES-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sierra resolved ARIES-1811.
--
Resolution: Fixed
Fix Version/s: component-dsl-1.2.0
> `effects` is not unwinding properly when exceptions occur
> -
>
> Key: ARIES-1811
> URL: https://issues.apache.org/jira/browse/ARIES-1811
> Project: Aries
> Issue Type: Bug
> Components: Component DSL
>Affects Versions: component-dsl-1.1.0
>Reporter: Carlos Sierra
>Priority: Major
> Fix For: component-dsl-1.2.0
>
>
> {{effects}} does not execute the _on leave_ action if an exception occur.
> This can leave the system in an inconsistent state, event if {{recover}} or
> {{recoverWith}} have been correctly used.
> It should make sure the _on leave_ action is always executed *if and only if*
> the _on adding_ action has been executed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ARIES-1813) `effects` must allow more effect execution points
[
https://issues.apache.org/jira/browse/ARIES-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sierra resolved ARIES-1813.
--
Resolution: Fixed
Fix Version/s: component-dsl-1.2.0
> `effects` must allow more effect execution points
> -
>
> Key: ARIES-1813
> URL: https://issues.apache.org/jira/browse/ARIES-1813
> Project: Aries
> Issue Type: Bug
> Components: Component DSL
>Affects Versions: component-dsl-1.1.0
>Reporter: Carlos Sierra
>Priority: Major
> Fix For: component-dsl-1.2.0
>
>
> There are two events that DSL nodes must handle: a new instance arrives and
> an instance leaves. For both these two events there exist two possible
> effects execution points: before and after, just like an aspect.
> {{effects}} must allow to specify all four execution points, although this
> has implications with error handling since not every execution point has the
> same impact in the execution of the program.
> For simplicity the two parameter {{effects}} will remain and will mean
> correspond to {{before adding}} and {{after removal}}. Any other combination
> must be specified with the four parameter version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARIES-1813) `effects` must allow more effect execution points
[
https://issues.apache.org/jira/browse/ARIES-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515534#comment-16515534
]
ASF subversion and git services commented on ARIES-1813:
Commit 1833695 from csie...@apache.org in branch 'aries/trunk'
[ https://svn.apache.org/r1833695 ]
[ARIES-1813] Add effects execution places
> `effects` must allow more effect execution points
> -
>
> Key: ARIES-1813
> URL: https://issues.apache.org/jira/browse/ARIES-1813
> Project: Aries
> Issue Type: Bug
> Components: Component DSL
>Affects Versions: component-dsl-1.1.0
>Reporter: Carlos Sierra
>Priority: Major
>
> There are two events that DSL nodes must handle: a new instance arrives and
> an instance leaves. For both these two events there exist two possible
> effects execution points: before and after, just like an aspect.
> {{effects}} must allow to specify all four execution points, although this
> has implications with error handling since not every execution point has the
> same impact in the execution of the program.
> For simplicity the two parameter {{effects}} will remain and will mean
> correspond to {{before adding}} and {{after removal}}. Any other combination
> must be specified with the four parameter version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARIES-1811) `effects` is not unwinding properly when exceptions occur
[
https://issues.apache.org/jira/browse/ARIES-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515530#comment-16515530
]
ASF subversion and git services commented on ARIES-1811:
Commit 1833692 from csie...@apache.org in branch 'aries/trunk'
[ https://svn.apache.org/r1833692 ]
[ARIES-1811] Always execute onRemoving action
> `effects` is not unwinding properly when exceptions occur
> -
>
> Key: ARIES-1811
> URL: https://issues.apache.org/jira/browse/ARIES-1811
> Project: Aries
> Issue Type: Bug
> Components: Component DSL
>Affects Versions: component-dsl-1.1.0
>Reporter: Carlos Sierra
>Priority: Major
>
> {{effects}} does not execute the _on leave_ action if an exception occur.
> This can leave the system in an inconsistent state, event if {{recover}} or
> {{recoverWith}} have been correctly used.
> It should make sure the _on leave_ action is always executed *if and only if*
> the _on adding_ action has been executed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARIES-1810) `onClose` does not execute the action in the correct order
[
https://issues.apache.org/jira/browse/ARIES-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515531#comment-16515531
]
ASF subversion and git services commented on ARIES-1810:
Commit 1833693 from csie...@apache.org in branch 'aries/trunk'
[ https://svn.apache.org/r1833693 ]
[ARIES-1810] Deprecate onClose
> `onClose` does not execute the action in the correct order
> --
>
> Key: ARIES-1810
> URL: https://issues.apache.org/jira/browse/ARIES-1810
> Project: Aries
> Issue Type: Bug
> Components: Component DSL
>Affects Versions: component-dsl-1.1.0
>Reporter: Carlos Sierra
>Priority: Major
>
> It executed the _on leave_ action in the opposite order to {{effects}} which
> creates inconsistencies.
> Actually onClose should be deprecated in favor of effects
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARIES-1812) `once` should support updates
[
https://issues.apache.org/jira/browse/ARIES-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515533#comment-16515533
]
ASF subversion and git services commented on ARIES-1812:
Commit 1833694 from csie...@apache.org in branch 'aries/trunk'
[ https://svn.apache.org/r1833694 ]
[ARIES-1812] Add update support to once
> `once` should support updates
> -
>
> Key: ARIES-1812
> URL: https://issues.apache.org/jira/browse/ARIES-1812
> Project: Aries
> Issue Type: Bug
> Components: Component DSL
>Affects Versions: component-dsl-1.1.0
>Reporter: Carlos Sierra
>Priority: Minor
>
> {{once}} is normally used to test the existance of a given service or
> configuration with certain properties. When there is only one tracked
> instance and that instance is updated, {{once}} will retract the program
> associated to the instance and publish the instance again. This is usually
> unnecessary and {{once}} should support update operations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARIES-1813) `effects` must allow more effect execution points
Carlos Sierra created ARIES-1813:
Summary: `effects` must allow more effect execution points
Key: ARIES-1813
URL: https://issues.apache.org/jira/browse/ARIES-1813
Project: Aries
Issue Type: Bug
Components: Component DSL
Affects Versions: component-dsl-1.1.0
Reporter: Carlos Sierra
There are two events that DSL nodes must handle: a new instance arrives and an
instance leaves. For both these two events there exist two possible effects
execution points: before and after, just like an aspect.
{{effects}} must allow to specify all four execution points, although this has
implications with error handling since not every execution point has the same
impact in the execution of the program.
For simplicity the two parameter {{effects}} will remain and will mean
correspond to {{before adding}} and {{after removal}}. Any other combination
must be specified with the four parameter version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
