Re: [digester] question about CallMethodRule behaviour

[robert burrell donkin]

i suspect that this is just the way that the API evolved but maybe 
scott or craig would like to jump in here with a solid reason...

- robert

On 5 Apr 2004, at 10:16, Simon Kitching wrote:

Hi,

I have noticed that CallMethodRule currently behaves like this:

(a)
Method takes exactly 1 parameter and that parameter is not
available --> target method not called.
(b)
Method takes >1 parameter, then the target method is always called,
regardless of whether the parameter values were found or not.
This appears to be deliberate; in particular, test case
"testPrimitiveReading" in class CallMethodRuleTestCase verifies this
behaviour.
What exactly is the reason behind this?

Regards,

Simon

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]