julianhyde at speakeasy.net
Tue May 29 15:05:28 EDT 2007
That validator is basically a mock object - because a validator is
needed in order to convert a UnresolvedFunCall to a ResolvedFunCall.
It's only used in one place.
If you add a call to canConvert, I have a feeling that the validator
will need to know the types of the arguments - which means you'll need
to implement other methods in the validator.
> -----Original Message-----
> From: mondrian-bounces at pentaho.org
> [mailto:mondrian-bounces at pentaho.org] On Behalf Of Anton Nikitin
> Sent: Tuesday, May 29, 2007 6:45 AM
> To: 'Mondrian developer mailing list'
> Subject: [Mondrian] Util.createSimpleValidator()
> Are there any objective reasons why mondrian.olap.Util.
> createSimpleValidator() method returns validator which
> doesn't implement
> canConvert() properly (the same way as StackValidator does - by using
> Mondrian mailing list
> Mondrian at pentaho.org
More information about the Mondrian