Descrepency with parameter order for services implimenting interfaces

[John Martin <pb...@gmail.com>]

We are in the process of implementing an XML-RPC client to call ofBiz and
noticed a strange behavior and didn't know if anybody would consider this a
bug?

If you look at the authenticationInterface interface, you'll notice that the
userLogin and locale appear at the bottom of the argument list.  The
userLogin service which implements the interface, the userLogin and locale
parameters are the first arguments.

This normally isn't a problem since typically the service is invoked via
mapped arguments but in the case of XML-RPC, it can be invoked by argument
position.  Programmers coding against the Interface will run into problems
because of this behavior.  One would expect that the argument list of the
service implementing the interface would match.

Any thoughts?

Thanks,

John