Excerpt |
---|
For CXF up to 2.0.x |
Why Aegis?
Aegis is a fast, StAX based, data-binding that makes developing code first services as simply as possible. It is able to handle most classes and create intelligent schemas for them.
Features include:
- No annotations are needed to expose classes
- Support for interfaces
- Support for collections including Maps
- Support for a wide variety of datatypes
CXF 2.1 Documentation
There are some significant changes to Aegis in CXF 2.1. See Aegis (2.1).
Details on How It Works
This Page, which is a work in progress, explains some of the modularity of Aegis. You may find it helpful in understanding Aegis' behavior and in developing customizations.
...
Most people who use Aegis use the 'Simple' front end.
Code Block | ||||
---|---|---|---|---|
| ||||
<simple:server id="pojoservice" serviceClass="demo.hw.server.HelloWorld" address="/hello_world"> <simple:serviceBean> <bean class="demo.hw.server.HelloWorldImpl" /> </simple:serviceBean> <simple:dataBinding> <bean class="org.apache.cxf.aegis.databinding.AegisDatabinding" /> </simple:dataBinding> <!-- Use this property only for XFire compatibility -- this version for 2.0.x ... <property name="serviceConfigurations"> <list> <bean class="org.apache.cxf.jaxws.support.JaxWsServiceConfiguration"/> <bean class="org.apache.cxf.aegis.databinding.AegisServiceConfiguration"/> <bean class="org.apache.cxf.service.factory.DefaultServiceConfiguration"/> </list> </property> --> </simple:server> </bean> |
You can also use Aegis with JAX-WS. Here's a Spring configuration example for that.
Code Block | ||||
---|---|---|---|---|
| ||||
<bean id="aegisBean" class="org.apache.cxf.aegis.databinding.AegisDatabinding" scope="prototype"/> <bean id="jaxws-and-aegis-service-factory" class="org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean" scope="prototype"> <property name="dataBinding" ref="aegisBean"/> <!-- Use this property only for XFire compatibility -- this version for 2.0.x ... <property name="serviceConfigurations"> <list> <bean class="org.apache.cxf.jaxws.support.JaxWsServiceConfiguration"/> <bean class="org.apache.cxf.aegis.databinding.AegisServiceConfiguration"/> <bean class="org.apache.cxf.service.factory.DefaultServiceConfiguration"/> </list> </property> --> <!-- Use this property only for XFire compatibility -- this version for 2.1 <property name="serviceConfigurations"> <list> <bean class="org.apache.cxf.jaxws.support.JaxWsServiceConfiguration"/> <bean class="org.apache.cxf.aegis.databinding.XFireCompatibilityServiceConfiguration"/> <bean class="org.apache.cxf.service.factory.DefaultServiceConfiguration"/> </list> </property> --> </bean> <jaxws:endpoint id="my_service_endpoint" implementor="#my-service" address="/MyIndex"> <jaxws:serviceFactory> <ref bean='jaxws-and-aegis-service-factory' /> </jaxws:serviceFactory> </jaxws:endpoint> |
Java configuration
Here's a Java configuration using the Simple front end.
...
XFire had/has a different convention for generating namespace URI values from Java package names. It added an additional '/' character.
If you need to interoperate with XFire, you need to enable compatibility with this behavior. You enable this compatibility by adding
an additional service configuration class to your service configuration: XFireCompatibilityServiceConfiguration (in 2.0.x, AegisServiceConfiguration).
The spring example above shows the necessary configuration in a comment. For the client side in Java, you need to add the service configuration to the service factory
as follows:
Code Block | ||||
---|---|---|---|---|
| ||||
import org.apache.cxf.aegis.databinding.AegisServiceConfiguration; // for 2.0.x sf.getServiceFactory().getServiceConfigurations().add(0, new AegisServiceConfiguration()); // for 2.1 sf.getServiceFactory().getServiceConfigurations().add(0, new XFireCompatibilityServiceConfiguration()); |
...
Info | ||
---|---|---|
| ||
You can find an XML Schema for Aegis mapping files here. |
Supported Types
...
- Basic types: int, double, float, long, byte\[\], short, String, BigDecimal
- Arrays
- Collections - including Maps
- Dates: java.util.Date, java.util.Calendar, java.sql.Timestamp, java.sql.Date, java.sql.Time
- XML: org.w3c.dom.Docmument, org.jdom.Element, XMLStreamReader, Source
- Complex types which are aggregations of the above
...