Skip to content

Issue #13: [spring] Spring Boot integration — ItaraSpring fetch helper Implement ItaraSpring.get(Class) — a fetch helper that returns the wired proxy for a contract interface. The developer calls this in their @Configuration class to create their own bean explicitly.#49

Open
gyorgycsintalan wants to merge 2 commits into
mainfrom
Add_ItaraSpring_fetch_helper

Conversation

@gyorgycsintalan
Copy link
Copy Markdown

No description provided.

gyorgycsintalan and others added 2 commits May 17, 2026 21:50
  Implement ItaraSpring.get(Class) — a fetch helper that returns the
  wired proxy for a contract interface. The developer calls this in
  their @configuration class to create their own bean explicitly.
Comment thread itara-common/src/main/java/io/itara/runtime/ItaraRegistry.java
Copy link
Copy Markdown
Collaborator

@kissgabor94 kissgabor94 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall all good, two small comments that aren't functional issues.

* <p>The returned instance is the Itara-wired proxy that was pre-registered
* by the agent during startup.
*/
public final class ItaraSpring {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know the GitHub Issue required this class, but I'm wondering if we should just skip it. It suggests that this is spring specific, which isn't true, and if we do introduce spring specific support later on, the name will be confusing. Could you remove it and simply call the registry directly instead?

log.info("=".repeat(50));

// Small pause to let the agent's HTTP server start if needed
Thread.sleep(500);
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I forgot to delete this in the other demo code, but it shouldn't be needed anymore, I think you can remove this sleep. When it's manually started, the user handles it, when docker-compose runs it, there is a dependency. It shouldn't be necessary.

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.

2 participants