← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 676517] [NEW] xmlrpc interface: inconsistent default arguments

 

Public bug reported:

for overloaded orm methods, default arguments are varying which make some basic xmlrpc calls to fail for some objects and succeed for others.
For instance, "name_search" is declared in orm.py as:
 /
| name_search(self, cr, user, name='', args=None, operator='ilike', context=None, limit=100):
 \
so basically:
 /
| OBJ.xmlrpclib.ServerProxy("http://%s:%u/xmlrpc/object"%(HOST,PORT))
| OBJ.execute(BASE,UID,PASS,NAME,"name_search")
 \
should work for any object name (NAME) in the system, unfortunately, it's not, as some overloaded name_search method don't set all the default values (e.g. 3rd arg name).

Some other calls are also probably affected. This is not a critical
issue, but the behavior should be consistent (either _no_ defaults or
same defaults everywhere).

** Affects: openobject-server
     Importance: Undecided
         Status: New

-- 
xmlrpc interface: inconsistent default arguments
https://bugs.launchpad.net/bugs/676517
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Server: New

Bug description:
for overloaded orm methods, default arguments are varying which make some basic xmlrpc calls to fail for some objects and succeed for others.
For instance, "name_search" is declared in orm.py as:
 /
| name_search(self, cr, user, name='', args=None, operator='ilike', context=None, limit=100):
 \
so basically:
 /
| OBJ.xmlrpclib.ServerProxy("http://%s:%u/xmlrpc/object"%(HOST,PORT))
| OBJ.execute(BASE,UID,PASS,NAME,"name_search")
 \
should work for any object name (NAME) in the system, unfortunately, it's not, as some overloaded name_search method don't set all the default values (e.g. 3rd arg name).

Some other calls are also probably affected. This is not a critical issue, but the behavior should be consistent (either _no_ defaults or same defaults everywhere).





Follow ups

References