9

There seems to be two options for using in normal :

  • javax.xml.rpc - seems more complicated but is a part of standard jdk (or is it?)
  • org.apache.xmlrpc - seems more easy to use, but i have to attach the library in my jar (or do i?)

Which one should I use for a dektop Java app? Or maybe there is another one that is really good and I have no idea it exists?

Dreen
  • 6,976
  • 11
  • 47
  • 69
  • 1
    JAX-RPC was replaced by by JAX-WS back in Java EE 5. – bdoughan Nov 27 '12 at 11:25
  • 1
    @BenTaliadoros: Unfortunately not, as its communicating with a non-jvm system. – Dreen Nov 27 '12 at 11:32
  • @BlaiseDoughan: How does JAX-WS compare to Apache's XMLRPC ? – Dreen Nov 27 '12 at 11:33
  • 1
    I recommend sticking with standards based solution unless the alternative provides enough value to go the proprietary path. The latest Apache XMLRPC binaries haven't been updated since 2010 so it may no longer be under active development. – bdoughan Nov 27 '12 at 12:08
  • Maybe development has halted, but it works. The development stopped because there is simply little to add, its stable. – Gimby Nov 27 '12 at 12:53
  • 2
    It's an old question but a critical vulnerability has been found in the apache library. It is not maintained so the vuln won't be fixed: https://nvd.nist.gov/vuln/detail/CVE-2019-17570 – Guillaume Dec 22 '20 at 11:37

1 Answers1

4

I ended up going with org.apache.xmlrpc, predominantly because my server does not send a WSDL file at all. This is not to say it would be impossible with JAX-WS. I am actually quite certain that JAX-WS is a more robust solution with many more features than Apache XMLRPC. However, the simple fact of the matter is I spent about 4 hours trying to implement user login to Drupal through JAX-WS with no results, after which I turned to Apache XMLRPC and had a working case in 10 minutes.

Kenly
  • 24,317
  • 7
  • 44
  • 60
Dreen
  • 6,976
  • 11
  • 47
  • 69