XFire

Home
Bug/Issue Reporting
Download
FAQ
Get Involved
License
News
Performance
Stack Comparison
Support
Who uses XFire\?
XFire Team

Documentation

Javadocs
Reports
User's Guide
Release Notes

Quicklinks

Aegis Binding
Client
JAXB 2.0
JSR 181 Annotations
Spring

Developers

Developer Space
CVS
Building
Architecture
Interesting Projects
Roadmap
Release Process
JAX\-WS

SOAP encoding poses a couple issues when implementing:

  • Trying to in such a way where your whole architecture is contimanted
  • Interopability issues - SOAP Encoding is easy in theory. The problem is that vendors have all interpreted the spec differently.

Interop Issues

Need to determine what these are

Implementation

  • Need a RPCEncodedWSDL implementation. From what I recall, the challenge here is that the schema is written differently than with normal schema types.
  • Need different Bean/ArrayType implementations for soap encoding - lets not try to through both doc/lit and the encoded stuff into the same Type classes.
  • Need EncodedReader/Writer implementations. Referenced elements can be loaded lazily through some kind of handle table.