>>>
>>> Sorry if that explanation was overkill.
>>>
>>> You asked "is there some general documentation about the extradata
>>> parameter in the FilterVisitor interface?"
>>>
>>> The reason there's isn't much that&
that's useful is that it's a pretty general
>> mechanism, that's meant to be abused by whichever particular algorithm
>> decides to implement FilterVisitor.
>>
>> --saul
>>
>>
>> -Original Message-
>> From: [EMAIL PROTECTED]
> in the FilterVisitor interface?"
>
> The reason there's isn't much that's useful is that it's a pretty general
> mechanism, that's meant to be abused by whichever particular algorithm
> decides to implement FilterVisitor.
>
> --saul
's useful is that it's a pretty general
mechanism, that's meant to be abused by whichever particular algorithm decides
to implement FilterVisitor.
--saul
-Original Message-
From: [EMAIL PROTECTED] on behalf of Cory Horner
Sent: Thu 4/5/2007 11:20 AM
To: geotools list
Cc: R
Rob Atkinson wrote:
> in FilterToSQL
>
>public Object visit(Literal expression, Object context) throws
> Class target = (Class)context;
If I remember correctly, the context (extraData) parameter is optional
and is basically whatever you want it to be. A null/instanceof check
shou
got some pain in this process ..
in FilterToSQL
public Object visit(Literal expression, Object context) throws
RuntimeException {
LOGGER.finer("exporting LiteralExpression");
//type to convert the literal to
Class target = (Class)context;
//J
