Hi,
If I have understood it correctly, there is no problem with such methods.
Here is example from the site:
Object[] params = new Object[]{new Integer(33), new Integer(9)};
Integer result = (Integer) client.execute("Calculator.add", params);
Also execute method takes parameters in the Object[] object. And then
this array object is translated to XML RPC as param1, param2, ...
paramX (not one parameter of array type!). And that is exactly what
you want, isn't it?
BR
Stano
On Tue, Jul 15, 2008 at 17:15, Elam Daly <[EMAIL PROTECTED]> wrote:
> I agree Jochen, but this is the client's already implemented specification
> and I don't have control over changing it at this point.
>
> Browsing the archives, it seems that a Filter is not the best choice to
> correct this though.
>
> - Elam
>
>
> On Tue, Jul 15, 2008 at 11:11 AM, Jochen Wiedmann <[EMAIL PROTECTED]>
> wrote:
>
>> On Tue, Jul 15, 2008 at 3:51 PM, Elam Daly <[EMAIL PROTECTED]> wrote:
>>
>> > We have a client who is expecting us to create an XML-RPC service with a
>> > dynamic number of variables, ie myRPC(var_1,var_2, var_x);
>> >
>> > Considering the static nature of the ws-xmlrpc library, I don't see how I
>> > can achieve this without using a Filter or something similar.
>>
>> Why not simply using an Object[] or a List?
>>
>> Jochen
>>
>> --
>> Look, that's why there's rules, understand? So that you think before
>> you break 'em.
>>
>> -- (Terry Pratchett, Thief of Time)
>>
>
