Skip to content

Conversation

@tzolov
Copy link
Contributor

@tzolov tzolov commented Oct 28, 2025

Changed DefaultChatClient to store ToolCallbackProvider instances instead of eagerly resolving them during configuration. Providers are now resolved lazily when call() or stream() is invoked.

  • Added toolCallbackProviders field to DefaultChatClientRequestSpec
  • Updated DefaultChatClientUtils to resolve providers at execution time
  • Added tests verifying lazy evaluation behavior

Resolves #4748

Changed DefaultChatClient to store ToolCallbackProvider instances
instead of eagerly resolving them during configuration.
Providers are now resolved lazily when call() or stream() is invoked.

- Added toolCallbackProviders field to DefaultChatClientRequestSpec
- Updated DefaultChatClientUtils to resolve providers at execution time
- Added tests verifying lazy evaluation behavior

Resolves spring-projects#4748

Signed-off-by: Christian Tzolov <[email protected]>
@ericbottard
Copy link
Member

You should add Fixes #4459 as well

@ilayaperumalg ilayaperumalg added this to the 1.1.0.M4 milestone Oct 28, 2025
@tzolov tzolov merged commit 99ccf9b into spring-projects:main Oct 28, 2025
2 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.

ChatClient eagerly retrieves ToolCallbacks during configuration

3 participants