Skip to content

Conversation

fjtirado
Copy link
Collaborator

@fjtirado fjtirado commented Aug 28, 2025

Fix #744

See list of commits for detailed explanations of changes

Workflow suspend and resume event should be sent regardless a task was
in fact suspended or not. Same applies to workflow status.

Signed-off-by: Francisco Javier Tirado Sarti <[email protected]>
Although already included because jackson-impl depends on it, it is a
good practise to explicitly add API as dependency because this
dependency is an implementation detail and the usage of the reader API
by the exampple is not.

Signed-off-by: Francisco Javier Tirado Sarti <[email protected]>
In some scenarios, users wont need the cloud events to be published.
This allows user to disable publishing at application level.

Signed-off-by: Francisco Javier Tirado Sarti <[email protected]>
There might be more that one EventPublisher

EventPublishers are either added programatically or through service
loader.

There will be only one consumer. If user want to handler more than one
consuming event broker, he should provide an specific implementation
that deals with them.

The one consumer is added programatically (priortiy) or default to
service loader.

If not eventConsumer was provides, InMemoryEvents is used as event
consumer and publisher.

ChatBotIT and LifeCycleEventTest has been changed accordingly.

Signed-off-by: Francisco Javier Tirado Sarti <[email protected]>
Signed-off-by: Francisco Javier Tirado Sarti <[email protected]>
@fjtirado fjtirado merged commit a14cc21 into serverlessworkflow:main Aug 28, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Prerelease improvements
1 participant