Gap Analysis: `cds-feature-ord` (CAP Java) vs `@cap-js/ord` (Node.js)

[zongqichen]

Background

To ensure consistent ORD support across the CAP ecosystem, we need a systematic comparison between cds-feature-ord (CAP Java, com.sap.cds:cds-feature-ord) and @cap-js/ord (Node.js).

Tasks

1. Deploy & Run a Java CAP App with ORD (End-to-End)

• Set up a Java CAP application with cds-feature-ord enabled
• Verify the ORD document endpoint (/.well-known/open-resource-discovery) works
• Document the setup steps and any issues encountered

2. Integrate Java App into Reference & Test Landscape

• Add a Java-based CAP application to the existing reference demo apps
• Integrate it into the e2e test landscape for automated ORD document validation

3. Gap Analysis: cds-feature-ord vs @cap-js/ord

This is the key deliverable. Document a detailed comparison:

Area	What to compare
ORD Document generation	Structure, completeness, default values
Annotation support	Which @ORD.Extensions annotations are supported
Protocol support	OData V2/V4, REST, GraphQL, MCP
Resource definitions	OpenAPI, AsyncAPI, EDMX generation parity
Custom ORD content	custom.ord.json handling
Authentication	Supported auth flows
Multitenancy	Tenant-aware ORD endpoints
Build-time generation	cds build ORD document output

4. Bridge the Gaps

• Create follow-up issues to close identified gaps
• Prioritize gaps that block real-world adoption

Acceptance Criteria

• Java CAP app deployed and ORD endpoint accessible
• Java app added to reference apps and e2e test landscape
• Gap analysis document completed and shared
• Follow-up issues created for identified gaps

[zongqichen]

Hi @swennemers, could you have a quick look, anything we need to change?