Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / General / February 2006

Tip: Looking for answers? Try searching our database.

Alternative XML content handler?

Thread view: 
greg.kujawa@gmail.com - 06 Feb 2006 14:23 GMT
I am using a SuperWaba Java implemenation to port an app over to Palm
OS. There is an XMLRPC library I am using for it that doesn't seem to
parse the results passed back from my XMLRPC server. The server is
running a non-Java XMLRPC process that seems to be compatible with
other XMLRPC clients, but not the SuperWaba Java XMLRPC client (which
is based on Apache XMLRPC v1.0). I have narrowed it down to the XML
content handler, which isn't interpreting the results that it's being
provided. The SuperWaba Java implementation is using an XML content
handler based on SAX 2.0, but not entirely SAX 2.0 compliant.

What would be the best method of implementing an alternative XML
content handler on my client? My XMLRPC server is based on Electric XML
(in this case a Ruby off-shoot called REXML). So I would like to try to
substitute Electric XML on the client.

Please be kind, as I'm far from a Java expert :-)
gregarican - 10 Feb 2006 17:49 GMT
For anyone who is interested there appears to be a bug in some of the
Java XML-RPC implementations. Or at least a different in that it breaks
certain functionality found in other language's XML-RPC
implementations. The issue that I saw with this SuperWaba XML-RPC
implementation (http://xmlrpc4sw.sourceforge.net) appears to stem from
the Apache XML-RPC 1.0 library it's based on. See
http://www.xmlrpc.com/discuss/msgReader$2354?mode=day for details. In
short an XML-RPC response that is passed long with the
<array><data><value> structure isn't being parsed correctly. The <data>
tag isn't being interpreted.

Trying a J2ME Midp4Palm1.0 alternative I brought in kXML-RPC
(http://kxmlrpc.objectweb.org) and ran into similar issues. It wasn't
until I added the <data> tag into the source code that the test cases I
coded actually worked. See
http://comments.gmane.org/gmane.comp.java.enhydra.kxmlrpc/36 for
details.

I know this is all a needle in a haystack, but in case anyone goes
through similar problems trying to get some of the Java XML-RPC
implementations to talk to other non-Java XML-RPC servers this might be
of some aid.


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.