Implement aggregate lifecycle helper functions

[zambrovski]

fix #71

[smcvb]

What is provided looks fine, but I am uncertain why you haven't added the other static operations from the AggregateLifecycle class with it. So, things like isLive, getVersion and markDeleted. Especially the last one is pretty important if the life cycle of an aggregate actually ends.

[zambrovski]

What is provided looks fine, but I am uncertain why you haven't added the other static operations from the AggregateLifecycle class with it. So, things like isLive, getVersion and markDeleted. Especially the last one is pretty important if the life cycle of an aggregate actually ends.

Since the methods isLife() and getVersion() and markDeleted() are static methods of AggregateLifecycle class, they can still be called from Kotlin by providing a static import and they neither collide with any Kotlin functions nor creating aliases would add any value (no reified classes, no functional support).

So in Kotlin code it will look like:

import org.axonframework.modelling.command.AggregateLifecycle.*

class MyAggregate {

    @CommandHandler
    fun someHandler(cmd: SomeCommand) {
        
        if (isLive()) {
            val version = getVersion()
            // do something
        }
    }
    
    @EventSourcingHandler
    fun on(evt: SomeEvent) {
        // process event
        markDeleted()
    }
}

I see no value in providing the same functions and just change the import.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

No Coverage information
0.0% Duplication

[smcvb]

Aaaah gotcha, I completely missed the point of collision in your original issue description. Could be me, could be the description; in the end it doesn't matter, as I feel that what you've done is fine as is. Thanks for clarifying @zambrovski.

[smcvb]

My concerns have been addressed, hence approving.

[sandjelkovic]

Looks good!