DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15216>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15216 de/serialization independence Summary: de/serialization independence Product: XML-RPC Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Source AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] For serialization (object->XML) can XmlWriter be made public? For deserialization (XML->object) can the ContentHandler be separated from XmlRpc, allowing it to be used as an independent SAX handler, with no thread or SaxDriver discovery code inside? Support for SAX2 DefaultHandler would be nice too, but not critical. Use case: where XML-RPC is being used with an alternative transport (JXTA pipes, e.g.) this separation would allow for much cleaner client implementations, where these modules can be used for preparing requests and parsing responses. Much appreciated! Reed Esau, [EMAIL PROTECTED] http://xmlrpc.jxta.org
