You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xmlrpc-dev@ws.apache.org by "Jochen Wiedmann (JIRA)" <xm...@ws.apache.org> on 2006/05/07 23:00:21 UTC
[jira] Geschlossen: (XMLRPC-21) de/serialization independence
[ http://issues.apache.org/jira/browse/XMLRPC-21?page=all ]
Jochen Wiedmann closed XMLRPC-21:
---------------------------------
Resolution: Fixed
Assign To: (was: rpc-dev mailing list)
The XML handling has been completely reworked in version 3.
> de/serialization independence
> -----------------------------
>
> Key: XMLRPC-21
> URL: http://issues.apache.org/jira/browse/XMLRPC-21
> Project: XML-RPC
> Type: Bug
> Components: Source
> Versions: unspecified
> Environment: Operating System: Other
> Platform: Other
> Reporter: Reed Esau
>
> 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, reed.esau@pobox.com
> http://xmlrpc.jxta.org
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira