Using CDI Beans in Camel Routes The Camel component provides a convenient and powerful mechanism for routing between SwitchYard services using Java DSL or XML routing definitions. When creating these routes, it's often necessary to add logic t... 
Create service tests using Forge You can now create unit tests for SwitchYard services using a simple forge command : create-service-test. This command is available once you install the "switchyard" facet in your forge project. Generating... SwitchYard AS7 Camel Integration Adding additional Camel components At times you would like to leverage the vast component libraries offered by Camel. Say you would like to use the routes of ftp://, sftp:// etc., SwitchYard by default offers core and... 
SwitchYard AS7 Development Modules everywhere AS7 is so modular, that each organization's project artifact is deployed as a seperate module. Each module comes with one or more jars accompanied by a module.xml. A typical module.xml looks like th... SwitchYard Tooling List This is a rough and growing list of SwitchYard tooling requirements. Feel free to add anything you would like to see. Integration with Savara tooling to generate a SwitchYard project. This could t... SwitchYard Milestone 1 Notes Using this page to document/track our thoughts on Milestone 1 functionality. The related forum discussion can be found here. The goal for M1 is a basic end-to-end service implementation and composition s... Transformation Overview Transformation represents a change to the format and/or representation of a message's content. The representation of a message is simply the Java contract (interface or class) used to access the underly... Exchanging Messages Overview In the SOA world, services interact through the exchange of messages. A service can declare the message exchange pattern that it supports for a given operation, which defines the order, direction, and c... Error and Fault Handling Overview As described previously, a service invocation consists of an exchange of messages described by a message exchange pattern (or MEP). Lots of errors can occur during the course of a message exchang... Context Overview Context is essentially a bag of properties with a well-defined lifecycle. public interface Context { Object getProperty(String name); Map<String, Object> g... Service Domains Overview A ServiceDomain represents a collection of services with a shared set of resources, configuration, and policy definitions. The ServiceDomain API is used by software components to provide an... Messages Overview A Message represents an individual input or output of a service, the content of which is interpreted by service implementation logic. A Message does not carry context specific to a service invocation, w...
Log in to follow, share, and participate in this community.