### XFire Home Bug/Issue Reporting Download FAQ Get Involved License News Stack Comparison Support User's Guide XFire Team ### M5 Javadocs Reports ### M6-SNAPSHOT Javadocs Reports ### Developers Developer Space CVS Building Architecture Interesting Projects Release Process | Please read the overview to get a general grasp of XFire concepts. Thanks – XFire Team ## Using XFire in Applications XFire is a next-generation java SOAP framework. At its core is a light STAX based message processing model used to interact with SOAP messages. On top of this XFire supports a variety of binding mechanisms, containers, and transports. ### Usage Scenarios:
XFire API | You can use the XFireFactory or create your own XFire instances to process soap messages. Not only is this great for HTTP, but also for processing messages within your application, unit testing, or a myriad of other things. See Using the XFire API for information on this.
XML Configuration | Configure your services with an xml descriptor.
## Bindings Bindings are ways to map XML to java objects. Currently XFire supports several different bindings:
[Aegis] | Aegis is the default binding mechanism in XFire. It is very fast, utilizes small amounts of memory and is very easy to use. It allows you to map POJOs and to XML.
XMLBeans | Uses XMLBeans to parse the request and format the response.
MessageBinding | The MessageBinding allows you to easily work with XML documents instead of objects.
## Container Support XFire strives to be a first class citizen with different containers. Containers provide component management and configuration to XFire. If your container isn't supported yet, please help us and integrate XFire with it!
Plexus | Plexus can provide configuration support for nearly any scenario (in a servlet container, embedded, etc).
Spring | Spring is a popular framework for managing components.
PicoContainer | "PicoContainer is a lightweight embeddable container for components that honour Dependency Injection."
Loom | Coming soon.
### Transports XFire is built on a an XML messaging layer made up of Transports which provide Channels for communication.
HTTP Transport | A standard SOAP over HTTP transport.
XMPP/Jabber Transport | XMPP is an asynchronous messaging protocol which can be used for SOAP.