Fabric3 supports defining components using annotations, XML, or a DSL. This section focuses on the details of using Before discussing other aspects of programming with Fabric3, we will provide an overview of working with annotations and the DSL.
Annotation Basics
Fabric3 is a modular runtime that is designed to be configured and deployed based on the specific functional requirements of the services it is hosting. For example, if a runtime is to host a service that requires JAX-RS functionality, an image can be assembled from the Fabric3 kernel and JAX-RS extensions; extensions for other technologies such as JMS or WS-* may be excluded.
...
| Coordinates | Description | ||
|---|---|---|---|
org.fabric3:fabric3-api | The base package containing general annotations and API classes | ||
{{org.fabric3:fabric3-model-api}} | The base package for DSL classes | ||
{{org.fabric3:fabric3-binding-jms-api}} | Package for JMS annotations and DSL classes | ||
{{org.fabric3:fabric3-binding-file-api}} | Package for file binding annotations and DSL classes | ||
{{org.fabric3:fabric3-binding-rs-api}} | Package for JAX-RS annotations and DSL classes | ||
{{org.fabric3:fabric3-binding-ws-api}} | Package for JAX-WS annotations and DSL classes | ||
{{org.fabric3:fabric3-binding-zeromq-api}} | Package for ZeroMQ annotations and DSL classes | ||
{{org.fabric3:fabric3-junit-api}} | Package for JUnit annotations | ||
{{org.fabric3:fabric3-timer-api}} | Package for Timer annotations and DSL classes |
Using the DSL
Components and channels can also be defined using the Fabric3 DSL. To use the DSL, one or more provider classes must be packaged in an application archive under the Java package "f3". Provider classes are invoked by the runtime to programmatically create composites. The following is an example of a provider class:
...