Do i understand correctly, that at this moment there isn't way to check 
separately each layer is it writable or not? Will the method, proposed by 
Rahkonen, work, or it isn't supported?
I changed geoserver standard sequrity rules fo layers and no it looks like:

*.*.r         *
*.*.w        NO_ONE
Test.*.w   ROLE_DVO

But i still get capabilities document  with strings:
<FeatureTypeList>
<Operations>
<Operation>Query</Operation>
<Operation>Insert</Operation>
<Operation>Update</Operation>
<Operation>Delete</Operation>
<Operation>Lock</Operation>
</Operations><FeatureType>
...

And no any information about suported operations in FeatureType block


23.04.2013, 11:32, "Andrea Aime" <[email protected]>:
> On Thu, Apr 18, 2013 at 9:06 AM, Rahkonen Jukka <[email protected]> 
> wrote:
>> Hi,
>>
>> Is suppose that the standard way would be to advertise the supported 
>> operations for each layer in GetCapabilities in WFS 1.0.0 it would be like
>>
>> <FeatureType><Name>lv:editable_multipoints</Name>
>> <Title>Editable test layer with multipoint geometries</Title>
>> <SRS>EPSG:3067</SRS>
>> <Operations>
>> <Insert/>
>> <Update/>
>> <Delete/>
>> </Operations>
>> <LatLongBoundingBox minx="22.897012" miny="61.978491" maxx="29.155145" 
>> maxy="67.392921"/>
>> </FeatureType>
>>
>> With standard controls Geoserver turns on of of WFS-T for the whole service 
>> and operations are listed at a higher level in FeatureTypeList
>> <FeatureTypeList>
>> <Operations>
>> <Operation>Query</Operation>
>> <Operation>Insert</Operation>
>> <Operation>Update</Operation>
>> <Operation>Delete</Operation>
>> <Operation>Lock</Operation>
>> </Operations><FeatureType>
>>
>> Check the GetCapabities of your secured system and see if the supported 
>> operations are listed for each feature type according to your security 
>> settings. If they are, you have fond the place to look at.
>
> Doing that layer by layer would be possible, but at the same time, might be 
> expensive,
> since we'd have to get each and every layer, gather its data source, and see 
> if it's writable.
> If the store cache is big enough that might work just fine, if not we might 
> end up creating
> and dropping either open files or database connections a lot
>
> Looks to me like good material for a "improvement request" jira ticket.
>
> Cheers
> Andrea
>
> --
> ==
> GeoServer training in Milan, 6th & 7th June 2013!  Visit 
> http://geoserver.geo-solutions.it for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054  Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39  339 8844549
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> ,
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
> ,
> _______________________________________________
> Geoserver-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
-------- Завершение пересылаемого сообщения --------

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to