Loading content
Apache CXF is an established open-source Java web service framework covering SOAP and REST, implementing JAX‑WS/JAX‑RS standards. It provides tooling for WSDL handling, interceptors, security integration and transport customization, making it suitable for service-oriented integration scenarios in enterprise environments.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Apache CXF is a Java framework for building, publishing, and integrating web services with SOAP and REST. It combines JAX-WS/JAX-RS, WSDL processing, and extensions for transports, interceptors, and security.
Apache CXF originated in 2006 at the Apache Software Foundation as a merger of Celtix, developed by IONA Technologies, and XFire, a project hosted by CodeHaus. The aim was a single Java web services framework that could unify SOAP tooling, WSDL-driven development, and later REST and WS-* extensions in one platform.
Think of CXF as a mediation layer between the service contract and live communication. At the top, WSDL or Java annotations define the interface for SOAP and REST. CXF turns that into client and server endpoints, passes messages through an interceptor chain, binds them to data models, and moves them over transports such as HTTP or JMS. Security and WS-* features plug in as additional processing steps in the same pipeline.
The XML-based messaging protocol is one of CXF's central integration modes.
These Java APIs describe and publish SOAP and REST endpoints in the Java ecosystem.
The service contract is defined first; server and client artifacts can then be derived from it.
Processing steps before and after message exchange enable cross-cutting concerns such as logging, validation, or authentication.
HTTP, JMS, and other transport layers carry messages between participating systems at runtime.
WS-Security, policy, and related extensions add protection and trust rules to the service.
CXF is a good fit when enterprise systems need SOAP interoperability, WSDL-first development, mixed SOAP/REST interfaces, or integration into existing Java stacks. It is strong on standards, transport variety, and security integration, but it also adds more configuration and conceptual depth than lightweight REST-only frameworks. For simple CRUD APIs without WS-* requirements, it can be overkill.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.