Enable Multi-App Run for Java HTTP bindings quickstart

[AdepuSriCharan]

Fixes #962

Description

This PR updates the Java HTTP bindings quickstart to use Dapr Multi-App Run as the default execution method.

Previously, users had to manually build and start the application using a long command:

dapr run --app-id batch-http --app-port 8080 --resources-path ../../../components -- java -jar target/BatchProcessingService-0.0.1-SNAPSHOT.jar

Now the quickstart can be started with a single command:

dapr run -f .

This improves the onboarding experience and makes the quickstart reproducible for first-time users.

---

Changes

Added

bindings/java/http/dapr.yaml

• Defines app id, directory, port, command and component resources

Updated

bindings/java/http/README.md

• Replaced manual dapr run command with dapr run -f .
• Removed separate Maven build steps
• Added prerequisites (Java 17+, Maven, dapr init)
• Clarified execution flow (Cron → Service → PostgreSQL)
• Uses docker compose up -d for CI compatibility

---

Verification

Tested locally

1. Start database

cd bindings/db
docker compose up -d

2. Run the quickstart

cd bindings/java/http
dapr run -f .

Observed

• Spring Boot app starts successfully
• Dapr sidecar initializes
• Cron binding triggers every 10 seconds
• Orders inserted into PostgreSQL

Verified with

docker exec -it postgres psql -U postgres -d orders -c "SELECT * FROM orders;"

Records increase over time, confirming the full end-to-end flow.