That is correct, WFS is stateless - hence the lack of a session to control
the JDBC transaction.
Jody Garnett
On Fri, Jun 20, 2014 at 12:10 AM, electrotype <[email protected]> wrote:
> Sadly, GeoServer is not the place where our business logic /validation
> will reside. We have some web services which receive requests in a custom
> format, we validate them using our business logic, modify them, and some
> WFS requests are sent to GeoServer during this process.
>
> So, to resume : controlling the underlying JDBC transaction used by
> Geoserver is not possible for a client. So no begin / commit / rollback
> available for the client . But it may be possible to add some validation,
> as plugins, *on the Geoserver side*.
>
> Thanks a lot for your help Jody!
>
> Julien
>
>
>
> On 6/18/2014 7:07 PM, Jody Garnett wrote:
>
>
> Here, action #3 local validation failed, so the previous actions
>> (action #1 and action #2) must be rollbacked.
>>
>
> You will not get back the "response" for action#3 in order to test
> against your own local business rules. Any validation must occur on the
> server side.
>
>
>> Is it possible to achieve that with Geoserver?
>>
>> With a single "<wfs:Transaction>" request, it's not possible to
>> programatically validate action #3 , with local business rules, if this
>> validation requires to check the results of the application of the previous
>> actions.
>>
>
>
> This is the case for "validating web feature service" functionality[1]
> where you teach GeoServer your "local business rules so it can enforce them
> during wfs:Transaction.
>
> The code to do this is no longer hooked up (to my knowledge) as the
> module lacked a chamption/funding.
> It is however still in the GeoTools[2] / GeoServer codebase and if you
> wire it up against we would be grateful.
>
> What makes me think that it may be possible to achieve such "external"
>> transaction controle, is that the Geotools client seems to do it. Is it?
>>
>
> The GeoTools client holds the changes locally (as a "diff" which it uses
> to filter any incoming requests), when you call commit in GeoTools it
> issues a single Transaction request as described previously.
> --
> Jody
>
> [1] http://vwfs.refractions.net
> [2]
> https://github.com/geotools/geotools/tree/master/modules/extension/validation
> [3]
> https://github.com/geoserver/geoserver/tree/master/src/extension/validation
>
>
>
>
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> Geoserver-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
