[Geoserver-devel] [jira] Created: (GEOS-184) Layer level transaction configuration

GeoServer GeoServer Developer
1

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/GEOS-184

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GEOS-184
    Summary: Layer level transaction configuration
       Type: Improvement

     Status: Open
   Priority: Major

Original Estimate: Unknown
Time Spent: Unknown
  Remaining: Unknown

    Project: GeoServer
   Fix Fors:
             1.2.1
   Versions:
             1.2.0-rc2
             1.2.0

   Assignee: Chris Holmes
   Reporter: Chris Holmes

    Created: Sat, 26 Jun 2004 2:20 PM
    Updated: Sat, 26 Jun 2004 2:20 PM

Description:
Right now the transaction level can only be set globally. It's an all or nothing affair. GeoServer should allow different layers to have different transaction settings. We also should allow more configuration options, like updates but not deletes and inserts. This is done in the backend, but there's no user interface for it currently.

---------------------------------------------------------------------
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

2

jira@anonymised.com wrote:

Right now the transaction level can only be set globally. It's an all or nothing affair. GeoServer should allow different layers to have different transaction settings. We also should allow more configuration options, like updates but not deletes and inserts. This is done in the backend, but there's no user interface for it currently.

At a global level there is separate control for insert, delete, update.

At a low technical level this is not quite true. You could choose your GeoServerFeatureSource/Store wrapper when you set up your global.Data object. This would control read/write access since the TransactionResponse class will correctly error out if write access is not available.

But the intent of this message is sound, extend the fine grained insert, delte, update access control down to the FeatureType level.

Jody