Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Endpoint with enabled Outbox but disabled Sagas fails to start #266

Closed
SzymonPobiega opened this issue Mar 12, 2018 · 0 comments
Closed

Endpoint with enabled Outbox but disabled Sagas fails to start #266

SzymonPobiega opened this issue Mar 12, 2018 · 0 comments
Labels
Bug
Milestone
3.0.6

Comments

@SzymonPobiega
Copy link
Member

Symptoms

When Sagas feature is explicitly disabled via endpointConfig.DisableFeature<T> API but the Outbox is enabled the endpoint fails to start.

Who's affected

Users that would like to run the endpoint in the configuration described above

Workaround

Do not disable the Sagas feature explicitly. Instead make sure that no saga classes are included in the assembly scanning.
@SzymonPobiega SzymonPobiega added this to the 3.0.6 milestone Mar 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug
Projects
None yet
Milestone
3.0.6
Development

No branches or pull requests
1 participant
@SzymonPobiega