What should we do?
Lift ChatModelHttpProxySupport out of framework/langchain4j/ to a provider-neutral package and expose a plain java.net.http.HttpClient (in addition to the existing AWS Apache and Azure shapes) for native vendor SDKs to consume. Each native chat model API factory should build its SDK client through this shared utility so that proxy configuration set via the connector runtime applies on day one — the same way today's LangChain4j implementations do.
Why should we do it?
We rely on JDK proxy support today and need to preserve it in the native impls without re-implementing the configuration plumbing per SDK.
Existing util at connectors/agentic-ai/src/main/java/io/camunda/connector/agenticai/aiagent/framework/langchain4j/ChatModelHttpProxySupport.java.
What should we do?
Lift
ChatModelHttpProxySupportout offramework/langchain4j/to a provider-neutral package and expose a plainjava.net.http.HttpClient(in addition to the existing AWS Apache and Azure shapes) for native vendor SDKs to consume. Each native chat model API factory should build its SDK client through this shared utility so that proxy configuration set via the connector runtime applies on day one — the same way today's LangChain4j implementations do.Why should we do it?
We rely on JDK proxy support today and need to preserve it in the native impls without re-implementing the configuration plumbing per SDK.
Existing util at
connectors/agentic-ai/src/main/java/io/camunda/connector/agenticai/aiagent/framework/langchain4j/ChatModelHttpProxySupport.java.