[gotoxu]

What is the purpose of the change

Close #718

Brief changelog

将 provider.newSimpleConsumerBuilder() 的返回值直接赋值给变量 consumerBuilder，而不再单独创建局部变量

Verifying this change

XXXX

Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

• Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist.
• Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

[RockteMQ-AI]

Issue Evaluation

Category: question | Status: Answered

Yes, rocketmq-spring-boot-starter 2.3.3 supports ordered (sequential) messages.

Usage:
Add selectorExpression = "*" and set the message key to your ordering key (e.g., order ID). Use @RocketMQMessageListener with the selectorExpression attribute, and send messages with the same hash key:

// Producer: send with ordering key
rocketMQTemplate.syncSendOrderly("topic-name", message, "order-id-123");

Messages with the same hashKey will be sent to the same queue and consumed in order.

Note: The issue body appears to contain a PR template rather than a question. If you intended to submit a PR, please use the PR creation flow instead.

---

Automated evaluation by RockteMQ-AI