weiqingy commented on code in PR #714:
URL: https://github.com/apache/flink-agents/pull/714#discussion_r3328357774
##########
docs/content/docs/development/workflow_agent.md:
##########
@@ -490,6 +490,51 @@ To use async execution on JDK 21+, user should append jvm
option `--add-exports=
{{< /tab >}}
{{< /tabs >}}
+### Cross-language Actions
+
+An action declared in one language can dispatch its body to the other language
by setting a `target` on the decorator/annotation. The decorated function or
annotated method then acts as a stub — it should raise so direct calls outside
the framework fail loud.
Review Comment:
The three other cross-language sections — chat models (`chat_models.md`),
embedding models, and vector stores — each carry the same caveat:
*"Cross-language resources are currently supported only when running in Flink,
not in local development mode."* The Java-from-Python action path documented
here goes through the same Pemja bridge inside `ActionExecutionOperator`
(`CrossLanguageActionRuntimeTest` exercises it via the Flink operator harness,
not local mode). Does that same local-dev limitation apply to cross-language
actions? If so, a matching one-line note here would save users a confusing
local-mode failure — and there's no general caveat elsewhere in this page that
already covers it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
