What it is

DDC is the sample Java library provided by the European Commission to implement an eDelivery dynamic discovery lookup for an eDelivery party to discover the URLs and metadata of ot

Teams can evaluate Dynamic Discovery Client (DDC) within its category while keeping the implementation, license, and repository signals visible. Confirm the official documentation against your exact workflow before treating it as a production dependency.

Categories: Content & Collaboration
EU domains: Communications
EU catalogue: Code Europa EUStandalone/BackendStable
Tags: communications windows standalone/backend stable eu-oss public-sector
Built with: See repository architecture

Who it’s for — and when to skip it

Knowledge teams

Use it when collaborative content should remain exportable and under your control.

Skip if required editing, permissions, or migration features are missing.

Community operators

Consider it when customization and transparent moderation workflows matter.

Skip if your team cannot run community safety and support operations.

Distributed teams

Evaluate it when shared content and communication need an open deployment path.

Skip if realtime scale or mobile experience is not proven for your use case.

Strengths and trade-offs

Why teams consider it

Automatic participant lookup using SML to locate the SMP service where a network participant published its service capabilities metadata.

SMP metadata retrieval to obtain service metadata such as document types, transport profiles, and endpoint details.

Support for multiple transport profiles (e.g., AS4, AS2, etc.) to enable interoperability with different Access Points.

Source code and EUPL-1.2-or-later license are visible before adoption

Repository metrics are available for independent review

What to validate

A public repository does not automatically guarantee a documented self-hosting path

GitHub popularity is not a security, quality, or product-fit guarantee

The EUPL-1.2-or-later license still needs review against your distribution and commercial model

Support quality, migration effort, and production hardening vary by project

Capabilities and stack fit

01Automatic participant lookup using SML to locate the SMP service where a network participant published its service capabilities metadata.

02SMP metadata retrieval to obtain service metadata such as document types, transport profiles, and endpoint details.

03Support for multiple transport profiles (e.g., AS4, AS2, etc.) to enable interoperability with different Access Points.

04Support for multiple document types and processes to facilitate diverse message exchange scenarios.

Catalog metadata supports discovery, not installation. Verify supported versions, dependencies, deployment topology, and production requirements in the official repository.

Guides for Dynamic Discovery Client (DDC)

No project-specific guide is published yet.

Use the learning library to find a guide by technology, category, or difficulty.

Browse guides

Approved community reviews

No approved review signal yet.

We do not display synthetic testimonials or ratings without sufficient moderated data.

Before you adopt it

01
Read the license and confirm it fits your intended use and distribution model.
02
Review recent commits, open issues, releases, and the maintainer response pattern.
03
Run a small proof of concept with representative data, users, and integrations.
04
Confirm whether an official deployment or self-hosting guide exists.
05
Document an export or migration path before storing critical data.

Dynamic Discovery Client (DDC)