[Geoserver-devel] Re: [jira] Commented: (GEOS-58) Ability to turn off Transactions

GeoServer GeoServer Developer
1

Yes, I like the semantic, and it is consistent with what I put in 1.1.1.
It currently just does Basic and non-basic, so the transaction/complete is
a fine addition. Are you planning on featureType level support at this
time? Or control over individual transactions (like update and insert,
but not delete)? Both have been requested, and would be nice to support,
or at least think about while we're on this issue.

The following comment has been added to this issue:

     Author: Jody Garnett
    Created: Tue, 10 Feb 2004 1:32 PM
       Body:
2.3.4 Configure Level of WFS Support

GeoServer is compliant with the full "Transactional Web Feature Server" level ofservice as defined by the OGC. The ability to limit the capabilities of GeoServer has been frequently requested.

The OGC defines two levels of service that a Web Feature Server may provide and still remain compliant:
- Basic WFS:
  GetCapabilities, DescribeFeatureType and GetFeature
- Transactional WFS:
  Transaction operation, with optional LockFeature

To meet user requests we propose adding a service level tag to the configuration process.

Intended modification to services.xml:
<service type="WFS">
  <title> My WFS </title>
  ...
  <serviceLevel>Basic</serviceLevel>
  ...
</service>

The following defines our recommended level of Service.

Basic
-----
Operations: GetCapabilities
            DescribeFeatureType
            GetFeature
OGC: Basic Web Feature Server

Transactional
-------------
Opperations: Transaction
OGC: Transactional Web Feature Server

Complete
--------
Opperations: LockFeature

This recommendation does not interact with the Validation Processor. The Validation Processor, if configured, will be used for all Transaction operations regardless of level of service.
---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=GEOS-58&page=comments#action_16628

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=GEOS-58

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GEOS-58
    Summary: Ability to turn off Transactions
       Type: New Feature

     Status: Open
   Priority: Major

Original Estimate: 40 minutes
Time Spent: Unknown
  Remaining: 40 minutes

    Project: GeoServer
Components:
             Configuration
             Transactions/Locking
   Fix Fors:
             1.2-beta
   Versions:
             1.1.0

   Assignee: Jody Garnett
   Reporter: Chris Holmes

    Created: Mon, 19 Jan 2004 1:31 PM
    Updated: Tue, 10 Feb 2004 1:32 PM

Description:
Users have requested the ability to turn 'off' transaction capabilities, so that users of their WFS's can not modify their databases. I'm not sure if this is in 1.2 yet or not, but we should get the fix in there, and in a 1.1.1 bug fix release. It should be pretty easy to implement, just have a configuration setting to turn it off, and transactions check with that global value before letting a transaction go through.

Actually, a slightly more elegant approach could be to allow admins to lock all their tables, to make that happen from the web admin interface. Though that would need more testing than just not allowing any access.

---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

--