View post: JBoss Marshalling Framework 1.0.0.Beta1 Released
Navigation
Recent posts from all feeds
- hSenid - officially certified JBCP partner
- jBPM 3 seam/jsf/richfaces based console
- Help push the open sourcing of a jBPM Migration Tool
- JBUG Munich meets Pete Muir with JSR-299 - Contexts and Dependency Injection for Java EE (06.07.09 at 19:00 PM)
- Javarsovia, static analysis and annotations
- Drools Job requested - Buenos Aires Argentina
- Seam and Web Beans downloads temporarily relocated
- Introducing a new smart forms tool: Drools Advisor
- JBoss Cloud introduction video
- Using rich:colorPicker in RichFaces
- « Back to feed: David M. Lloyd
JBoss Marshalling Framework 1.0.0.Beta1 Released
As a part of the JBoss Remoting project (and hopefully several other projects as well), I've developed a separated marshalling (a.k.a. serialization) framework. This framework was inspired by the need for certain features unavailable with the standardObject*Stream
classes:- Pluggable class resolvers, making it easy to customize classloader policy, by implementing a small interface (rather than having to subclass the
Object*Streamclasses) - Pluggable object replacement (also without subclassing)
- Pluggable predefined class tables, which can dramatically decrease stream size and serialization time for stream types which frequently use a common set of classes
- Pluggable predefined instance tables, which make it easy to handle remote references
- Pluggable externalizers which may be used to serialize classes which are not
Serializable, or for which an alternate strategy is needed - Customizable stream headers
- Each marshaller instance is highly configurable and tunable to maximize performance based on expected usage patterns
- A generalized API which can support many different protocol implementations, including protocols which do not necessarily provide all the above features
- Inexpensive instance creation, beneficial to applications where many short-lived streams are used
- Support for separate class and instance caches, if the protocol permits; useful for sending multiple messages or requests with a single stream, with separate object graphs but retaining the class cache
The default implementation, known as "River", is also available as a separate JAR.
This project does not have a home page, but the binaries have been uploaded to repositry.jboss.org and the Javadocs are available online at docs.jboss.org . The source code may be found in my sandbox repository for now, until it gets a permanent home.
Enjoy!
Post to DZone
Post to del.icio.us
Digg this!
Stumble It!