Cape Clear SOA Assembly
SOA applications need to combine a set of artefacts:
For more information:
- The Service implementation itself (BPEL, Java, DB);
- Multiple ways to reach it (transports);
- Transformations into and out of relevant formats;
- Manipulation of message parts;
- Application of routing, splitting and load-balancing rules;
- Handling of Error conditions;
For the first time, Cape Clear 7.5 offers a unified, Spring-based, graphical means to describe, develop and deploy Assemblies which span all the above areas.
Assemblies are defined and manipulated in the SOA Assembly Editor, which is part of Cape Clear Studio:
Advantages of an Assembly Approach:
- Ease of configuration—single Spring file
- Ease of deployment—one-click for a whole WSAR
- Simplicity—wiring model is quick & easy
- Flexible—re-use services multiple ways
- Consistent—mix’n’match all the main artefacts as you like
- Open—Spring-based framework
- Scheduled—Quartz makes it simple
- RESTful—no assumption of SOAP in transports
- Scalability—Mediations are stateless
- Customizable—anything can be added as a Spring bean
