I was going to say lets just fix the problem ... treat literals as they
are String literals. We can certerntly provide convience methods toInt
toDouble etc... so we don't perform caching multiple times.
I want to smack the filter code at somepoint (to allow breathing room
for Filter 1.1), if
> Yes, the filter-and-literal stuff was poorly designed.
well, I didn't want to go to such lengths - but it's definitely a flaw.
>
> Basically, what needs to happen is the actual filter class should just
> store the literals as strings, and the filter evaluation code should do
> any necessary conv
Jürgen,
Yes, the filter-and-literal stuff was poorly designed.
I've put a bunch of patches in to minimize the damage and considered
hiring a dutch boy to stick his finger in the cracks.
Basically, what needs to happen is the actual filter class should just
store the literals as strings, and the
Chris,
thanks for your quick reply. I'm using a geotools version checked out
from svn on October 9th.
I will check in the next few days whether there are any fixes done
recently. Maybe Dave can give a hint?
Is there yet a timeline for the redesign? Any volunteers yet?
Though we can use some di
Quoting [EMAIL PROTECTED]:
> Our intention is to develop a web application that investigates and
> expands (if necessary) an OGC filter attached to a request.
>
> We assume to use the following filter:
> http://www.opengis.net/gml";>
>
> myValue
> 10
>
