G
greg.kujawa
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
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