kXML-RPC is a Java ME (J2ME) implementation of the XML-RPC protocol built on top of the kXML parser. kXML-RPC empowers Java ME devices with a lightweight mechanism for exchanging data and invoking web services, in a neutral, standardized XML format.
Be the first to post a text review of XML-RPC for Java ME. Rate and review a project by clicking thumbs up or thumbs down in the right column.
Hi everyone, Kyle and I have authored an article/tutorial for DevX.com. Along with a discussion all about kXML-RPC, it has a full downloadable example client and web service. Check it out at: http://www.devx.com/Java/Article/34963 -David
A new release is now available for the XML-RPC for J2ME project. This release includes several important bug fixes, some of which were reported by our community members - so thank you to those people! Here's a summary of the bug fixes: - The two-argument constructor for XmlRpcClient did not correctly handle host locations that included subdirectories. This has been fixed and now allows you to access services located below your host's root directory. - Serializing Array datatype did not implement <data> start and end tags. This now works correctly and is compliant with the XML-RPC specification. - Parsing strings where no <string> tags were used threw an exception. This has been fixed to comply correctly with the XML-RPC specification, where <string> tags can be used to specify a string value, and if no tag is present a string value is assumed. - Date/time values were not implemented to the correct XML-RPC specification in both serialization and parsing. Previously the kobjects implementation of IsoDate (org.kobjects.isodate.IsoDate) was used to parse and serialize dates to conform to ISO.8601 formatting. This was found to be just plain wrong - the XML-RPC spec uses an ISO.8601-like format, but does not conform to it. This has been fixed by replacing the implementation of IsoDate with a brand new one (now found in org.kxmlrpc.util.IsoDate). The next milestone is to deal with parsing responses that may have embedded XML/HTML tags - for example <string> responses with XML tags within the string payload. This should fix the known issue with <fault> responses. In the meantime, if you do have any problems/bug reports with this new release please drop a message into the discussion forum! David
Significant Changes =================== A number of important fixes have been contributed to address the following bugs - The two-argument constructor for XmlRpcClient did not correctly handle host locations that included subdirectories - Serializing Array datatype did not implement <data> start and end tags - Parsing strings where no <string> tags were used threw an exception - Date/time values were not implemented to the correct XML-RPC specification in both serialization and parsing. This has been fixed by providing a new implementation of IsoDate to replace org.kobjects.isodate.IsoDate
Significant Changes =================== A number of important fixes have been contributed to address the following bugs - The two-argument constructor for XmlRpcClient did not correctly handle host locations that included subdirectories - Serializing Array datatype did not implement <data> start and end tags - Parsing strings where no <string> tags were used threw an exception - Date/time values were not implemented to the correct XML-RPC specification in both serialization and parsing. This has been fixed by providing a new implementation of IsoDate to replace org.kobjects.isodate.IsoDate
Significant Changes =================== A number of important fixes have been contributed to address the following bugs - The two-argument constructor for XmlRpcClient did not correctly handle host locations that included subdirectories - Serializing Array datatype did not implement <data> start and end tags - Parsing strings where no <string> tags were used threw an exception - Date/time values were not implemented to the correct XML-RPC specification in both serialization and parsing. This has been fixed by providing a new implementation of IsoDate to replace org.kobjects.isodate.IsoDate
Significant Changes =================== A number of important fixes have been contributed to address the following bugs - The two-argument constructor for XmlRpcClient did not correctly handle host locations that included subdirectories - Serializing Array datatype did not implement <data> start and end tags - Parsing strings where no <string> tags were used threw an exception - Date/time values were not implemented to the correct XML-RPC specification in both serialization and parsing. This has been fixed by providing a new implementation of IsoDate to replace org.kobjects.isodate.IsoDate
Significant Changes =================== A number of important fixes have been contributed to address the following bugs - The two-argument constructor for XmlRpcClient did not correctly handle host locations that included subdirectories - Serializing Array datatype did not implement <data> start and end tags - Parsing strings where no <string> tags were used threw an exception - Date/time values were not implemented to the correct XML-RPC specification in both serialization and parsing. This has been fixed by providing a new implementation of IsoDate to replace org.kobjects.isodate.IsoDate
Be the first person to add a text review.
Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?
Thanks for your review!
Get credit for your review by logging in via OpenID. Click your account provider: