Forage¶

Opinionated bean factories for Apache Camel.

Forage eliminates manual Java bean instantiation by providing factory classes configurable through properties files, environment variables, or system properties. Write your Camel routes — Forage handles the wiring.

Why Forage?¶

Apache Camel components often require manually creating and registering Java beans — data sources, connection factories, AI models, transaction managers. Forage replaces that boilerplate with a configuration-driven approach:

# "ordersDb" becomes a named bean — use it in routes as #ordersDb
forage.ordersDb.jdbc.db.kind=postgresql
forage.ordersDb.jdbc.url=jdbc:postgresql://localhost:5432/orders
forage.ordersDb.jdbc.username=admin
forage.ordersDb.jdbc.password=secret

No Java code. No Spring @Bean methods. No Quarkus producers. Just properties. The name you choose (e.g. ordersDb) registers a bean in the Camel registry, ready to reference in your routes as #ordersDb.

Features¶

Runtime Support¶

Forage works with all major Camel runtimes:

Quick Example¶

A complete AI agent with tool use in just two files:

- route:
    from:
      uri: timer:agent
      parameters:
        repeatCount: 1
      steps:
        - setBody:
            constant: "give details of user 123"
        - to:
            uri: langchain4j-agent:myGraniteAgent
            parameters:
              agent: "#myGraniteAgent"
        - log: "${body}"

# "myGraniteAgent" — pick any name, then reference it in routes as #myGraniteAgent
forage.myGraniteAgent.agent.model.kind=ollama
forage.myGraniteAgent.agent.model.name=granite4:3b
forage.myGraniteAgent.agent.base.url=http://localhost:11434

Versions¶

Forage publishes two release streams so you can match your Apache Camel version:

Pick the stream that matches the Camel version you use, then follow the Getting Started guide.

Getting Started¶

Ready to dive in? Head to the Getting Started guide.

Looking for working examples? Check out the Examples gallery.