Hi Ben :-) It is great to have you working in this space - I only wish
you were working on trunk (since this is an active area of development).
> I had originally intended to use one dynamic proxy class for each
> function, because FilterCapabilities has a one-class to one-function
> mapping, bu
Jody Garnett wrote:
> A couple things; executing any sql function is not a good thing from a
> security standpoint (but you know this).
Indeed.
> You should be able to advertise
> additional functions on a data store by datastore basis using the filter
> capabilities data structure. You are th
Hi Emily; I decided to go ahead and figure out the problem - so you
would not have to have a frustrating day.
Turns out two things:
1. You saw the null checks being needed in the SLDTransformer thing
2. The SLDParser parser code can be done better when an expression is
expected...see what follows
Rob Atkinson wrote:
> hmm - IMHO not having to get a WFS change request is starting small.
> Just accepting that we can get the functionality working and work out
> how to advertise it later (i.e. there isnt really much point
> advertising it if its feature specific) seems to me a much lower bar
I am looking into sld handling on trunk; since udig is starting to make
use of raster symbolizer.
A couple of things;
- A lot of this code will need to be rewritten to account for recent
style mutability decisions; we need to make note of that in the change
proposal; even if a JAXB parser is us
hmm - IMHO not having to get a WFS change request is starting small. Just
accepting that we can get the functionality working and work out how to
advertise it later (i.e. there isnt really much point advertising it if its
feature specific) seems to me a much lower bar. Getting the big picture
righ
[EMAIL PROTECTED] wrote:
> Ahh! Herein lies a quandry. WFS doesnt allow per feature functions to be
> advertised, and most interesting features have implicit or explicit
> operations that would be nice to advertise per feature as functions.
> Ideally, those functions are only allowed on those f
Rob Atkinson wrote:
> There is nothing intrinsically postgis about the solution, we envisage
> it a JDBC capability.
I agree :-)
> A parameter with a sensible default could advertise the table or
> function that would be interrogated to find functions intended to be
> advertised.
>
> My could a
There is nothing intrinsically postgis about the solution, we envisage it a
JDBC capability.
A parameter with a sensible default could advertise the table or function
that would be interrogated to find functions intended to be advertised.
My could attempt to call a function
getRegisteredFunctions
Ciao Martin,
as I promised during this evening IRC I have spared some time to put
together an isolated test case to show the behavior I was talking
about.
The code is here http://pastebin.com/m53e6a6a8 , it is a simple
modification of the testCrop so it is pretty easy to play with in
order to spar
DecoratingFeatureCollection.accepts() implementation for GeoAPI FeatureVisitor
and FeatureCollection
Key: GEOT-1931
URL: http://jira.codehaus.org/browse/GEOT-1931
Meeting starting up now; please stop by...
0) chat (mostly Converters and ClassChanger duplication)
1) what is up
2) follow up to OSGeo graduation
3) gridrange/gridenvelope
> Apparently I forgot the new meeting time; can I ask someone to post a
> reminder for the next couple of weeks?
>
> ---
Apparently I forgot the new meeting time; can I ask someone to post a
reminder for the next couple of weeks?
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applica
I noticed go has now been removed? Is this the end of go-1 project? Or
is it just going to take a different shape.
Jody
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux ba
A couple things; executing any sql function is not a good thing from a
security standpoint (but you know this). You should be able to advertise
additional functions on a data store by datastore basis using the filter
capabilities data structure. You are the first person to want to do this
so pl
I have written a prototype for "registered function" support in WFS
filter queries, in which functions not implemented in GeoServer are
passed to the database for execution. This allows complex or expensive
domain-specific queries to be performed on the database server side.
Please comment if y
Registered functions support permits all database functions to be called
Key: GEOT-1930
URL: http://jira.codehaus.org/browse/GEOT-1930
Project: GeoTools
Issue Type: Bug
17 matches
Mail list logo
