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.

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

Provide DataEntrySenderType 'tx' as configurable option (similar to SenderType 'tx' in TaskpoolSender) #1084

Open
margue opened this issue Feb 11, 2025 · 0 comments · May be fixed by #1086
Open
Assignees
Labels
Prio: Must This feature must be implemented in current milestone. Status: In progress Assignee is working on this issue. Type: enhancement New feature or request

Comments

@margue
Copy link

margue commented Feb 11, 2025

Sender for DataEntryCommands using Tx synchronization sending commands directly.
In doing so, the DataEntryCommand list is collected during the transaction and are sent out by transactional listener. This allows atomicity in sending Task and DataEntry commands.

@zambrovski zambrovski added Type: enhancement New feature or request Status: In progress Assignee is working on this issue. Prio: Must This feature must be implemented in current milestone. labels Feb 11, 2025
margue pushed a commit to margue/camunda-bpm-taskpool that referenced this issue Feb 13, 2025
margue added a commit to margue/camunda-bpm-taskpool that referenced this issue Feb 13, 2025
margue added a commit to margue/camunda-bpm-taskpool that referenced this issue Feb 13, 2025
margue added a commit to margue/camunda-bpm-taskpool that referenced this issue Feb 13, 2025
- adds missing docs to DataEntrySenderConfiguration
- declares simpleDataEntryCommandSender Bean as DataEntrySender
margue added a commit to margue/camunda-bpm-taskpool that referenced this issue Feb 13, 2025
margue added a commit to margue/camunda-bpm-taskpool that referenced this issue Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Prio: Must This feature must be implemented in current milestone. Status: In progress Assignee is working on this issue. Type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants