I have no personal experience with either XML-RPC, SOAP or REST (DB
Developer, Web-GUI needs covered by Vaadin), but this guy expresses a
different (seemingly pragmatic) opinion (and he is using Groovy ;-) ):
https://sites.google.com/a/athaydes.com/renato-athaydes/posts/thereturnofrpc-orhowrestisnolongertheonlyrespectablesolutionforapis
(Generally speaking, in modern software development especially the web
development domain to me seems to suffer from an overabundance of "this
is the /absolute /right way to do things !" - until a newer/hipper/...
(or simply different ?-) ) approach comes along the next year...; I mean
I am not saying there is no improvement in some areas, but it took the
web guys how many decades to rediscover configurable, encapsulated GUI
components as a general concept ?-) )
Cheers,
mg
On 24.07.2018 12:33, Russel Winder wrote:
I suspect XML-RPC is pure legacy. It evolved into SOAP and that is pure
legacy.
All the Web Services folk I know are now using RESTful HTTP/HTTPS
microservices.
On Sat, 2018-07-21 at 16:50 +0200, Jacques Le Roux wrote:
Hi Bernhard,
Actually XML-RPC is no longer maintained, last fix in3.1.3 is for
http://www.openwall.com/lists/oss-security/2011/10/05/10
And there are CVEs pending :
https://0ang3el.blogspot.com/2016/07/beware-of-ws-xmlrpc-library-in-y
our.html
Other TLPs might be affected, I guess Archiva has been picked because
being the 1st in alphabetical order...
HTH
Jacques
Le 19/07/2018 à 17:25, Bernhard Donaubauer a écrit :
Hello,
I think about replacing an old xml-rpc service written in perl with
groovy.
There are examples using groovy-xmlrpc like here:
https://gist.github.com/bjfish/370521
But I wonder if this module is still maintained. While I can find
the
jar files in the repositories I can't find the according project or
sources.
Regards,
Bernhard Donaubauer
