THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Spec | Purpose | Support |
|---|---|---|
WS-Security | Authentication, Encryption, Digital Signature | Yes, for HTTP and CXF binding components and subsequent authentication/authorization |
WS-RM | Reliable Messaging | Yes, for CXF binding component |
WS-Addressing | Addressing | |
WS-Policy | Policy Management | Yes, for CXF binding component |
WS-Notification | Events | Yes, see the WS-Notification documentation |
WS-TX | Transactions | No, though WS-TX headers can be passed through as normalized message headers for services to handle |
WSDM | Management | No, JMX is used instead |
WS-Management | Management | Not directly, JMX is used instead. A connector However, a bridge from JMX to WS-Management is being developed. See : see https://ws-jmx-connector.dev.java.net/ for more informationsinformation. |
Does ServiceMix support plain XML messages?
...
Of course, you would want to coordinate changes to routing, transformation, or orchestration that depend on changes to the service's WSDL. (This is easiest for anything deployed in the same Service Assembly as the service in question.)
What options are available for building composite services (or business processes)?
The typical solution is a BPEL process to wire multiple individual services together. While ServiceMix does not ship with a BPEL engine, Apache Ode provides a drop-in JBI component for ServiceMix.
Other options, depending on the level of integration necessary, would include using #Routing & Transformation and other Enterprise Integration Patterns to connect individual services. You could also use a Script or Java Bean to integrate several services.