[FIX] db: restore xmlrpc in web service example

[xpl-odoo]

This commit partially reverts 36fb624,
indeed the JSON-2 API only exists starting 19.0

[robodoo]

[xpl-odoo]

@robodoo up to 18.0

[robodoo]

Forward-porting to '18.0'.

[Julien00859]

Commit title and message should be:

[FIX] <title>: restore xmlrpc in web service example

This commit partially reverts <hash of broken commit>, indeed the JSON-2 API only exists starting 19.0

I don't know for the title

[AntoineVDV]

@robodoo r+

Should probably be up to 18.4

[Julien00859]

I think JSON-2 landed in 18.4... but in all cases xmlrpc was deprecated only in 19, and I don't know if internal enabled JSON-2 in 18.4. So up to 18.4 it is 👍

@robodoo up to 18.4

[robodoo]

@Julien00859 you can't up to 18.4.

[Julien00859]

@robodoo up to saas-18.4

[robodoo]

@Julien00859 you can't up to saas-18.4.

[AntoineVDV]

@Julien00859 how do you dare up to 18.4??

@robodoo up to saas-18.4

[robodoo]

Forward-porting to 'saas-18.4'.

[robodoo]

@Julien00859 you can't up to I-am-a-stupid-bot-and-nobody-likes-me.

[AntoineVDV]

@robodoo talk to me like that @Julien00859

[robodoo]

@AntoineVDV unknown command 'talk'.

For your own safety I've ignored everything in your entire comment.

Currently available commands:

command
help	displays this help
r(eview)+	approves the PR, if it's a forwardport also approves all non-detached parents
r(eview)=<number>	only approves the specified parents
r(eview)-	removes approval of a previously approved PR, if the PR is staged the staging will be cancelled
retry	re-tries staging a PR in the "error" state
fw=no	does not forward-port this PR
fw=default	forward-ports this PR normally
fw=skipci	does not wait for a forward-port's statuses to succeed before creating the next one
fw=skipmerge	does not wait for the source to be merged before creating forward ports
up to <branch>	only ports this PR forward to the specified branch (included)
merge	integrate the PR with a simple merge commit, using the PR description as message
rebase-merge	rebases the PR on top of the target branch the integrates with a merge commit, using the PR description as message
rebase-ff	rebases the PR on top of the target branch, then fast-forwards
squash	squashes the PR as a single commit on the target branch, using the PR description as message
delegate+	grants approval rights to the PR author
delegate=<...>	grants approval rights on this PR to the specified github users
nice	only stages the PR if there's room in the batch after default PRs
default	stages the PR normally
priority	tries to stage this PR first, then adds default PRs if the staging has room
alone	stages this PR only with other PRs of the same priority
cancel=staging	automatically cancels the current staging when this PR becomes ready
check	fetches or refreshes PR metadata, resets mergebot state
remindme:<branch>=<message>	When the PR gets forward-ported to , ping you with . can be quoted if it needs spaces.

Note: this help text is dynamic and will change with the state of the PR.