- POJO based REST API to quickly implement REST based services
- SEDA based messaging fabric with integrated CometD
- Messaging fabric obviates the need for traditional thread programming
- Asynchronous processing is natural (inline, queued, and fully concurrent)
- Configurable Producer Flow Control
- Support for text, XML, binary, and AMF0 return types
- Scheduler and Persistent Processing Queue API (Mail Queue provided)
- Fast XML Marshalling API
- Built from the ground up for Terracotta DSO clustering support
- Integrated POJO session management
- Single Servlet install
- Configure using convenience methods; suck in your properties file and go!
- Lightweight AS3 messaging library
- Unified session management with Java cluster
- Native CometD
Swerve SOA is a full stack POJO framework for developing Flex 2 / Java RIA solutions. It has been under development for about a year and has been leveraged in several internal projects within the financial industry. This is the first public release of the codebase. The framework is distributed with full source, ant scripts, sample application (inlcudes Flex 2 / Java). The ant script also supports running Swerve in a cluster leveraging Terracotta; the next release will leverage PojoCache (a JBoss Cache extension) for clustering support with less deployment impact. Swerve SOA provides the following features out of the box:
- Posted by: Travell Perkins
- Posted on: August 21 2007 07:54 EDT
is it legal to use anything that not originated from adobe that deal with the propriatory amf format and the rtmp protocol?
A flavor of this discussion has popped up on the Red5 list recently. This might shed some light: http://osflash.org/red5/fud
Swerve uses Red5 for AMF support (marshalling.) Currently only AMF0 works. I'm hoping that someone will figure out what I might be doing wrong for AMF3. It seems like its broken on the client side.