Thanks for your answer Andrea!

So, as long as I don't have a solution with GeoServer, I will try do it  
with GeoExt itself.

What I think to do now with GeoExt is to call my layers according to their  
GeoServer workspace. One of these workspaces would be called "wms" and the  
other "wfs". With GeoExt, I will store the layers in two stores: the "wms  
store" and the "wfs store". And then, I think I'm going to resolve the  
layer subject issue with the keywords layers. In GeoServer, each layer  
will get a keyword according their subject. Then, with GeoExt, I will scan  
all the layers in both stores and put them into several new stores  
according to their keyword. I know, it's not a question that concerns only  
GeoServer, but do you think it is a good way to do it like this?

Geoffrey





On Thu, 07 Jul 2011 10:53:07 +0200, Andrea Aime  
<[email protected]> wrote:

> On Thu, Jul 7, 2011 at 10:30 AM, gbrun <[email protected]> wrote:
>
>> Hi everybody!
>>
>> I want to request all my layers configured in GeoServer with GeoExt. I
>> have two important stuffs for my layers configuration: they must be
>> arranged depending on their subject (environment, urbanism, etc.), and
>> also depending on their editable status (so WFS or not WFS). I can  
>> easily
>> manage one of this stuff by putting in GeoServer my layers into  
>> different
>> workspaces (wfs, wms OR environment, urbanism, etc.). But I can't  
>> combine
>> these both things!
>>
>> So what I chose is to arrange my layers in different workspaces  
>> according
>> to their subject. But then, the point is that, when I request my layers  
>> in
>> GeoExt, some layers are called twice: in WMS and in WFS. I'd like to  
>> avoid
>> this double-occurrence!
>>
>> So, my real question is: is it possible to force the web-service type  
>> (WMS
>> or WFS) for each layer in GeoServer?
>>
>
> You mean, having some layers not show up in WFS capabilities at all,
> while they show up in WMS?
> It's not possible at the moment.
>
> This could be treated as a configuration problem or a security problem.
>
> Config problem: I want to specify which service can see a certain layer,
> this will be the same for everybody, there is no security involved.
> I think there was a jira asking for this, but can't find it at the  
> moment.
>
> Security problem: some combinations of layer + service are not available
> to the general public.
> We have the machinery to do this code wise, but so far no open source
> implementation to actually have the administrator configure it.
>
> Long story short, both are doable with changes to the GeoServer code,
> but are not possible without.
> One possibility sometimes people use is to download the capabilities
> documents, hand modify them, and publish the modified version
> on apache for people to use instead of the original ones.
>
> Cheers
> Andrea
>
>


-- 
Using Opera's revolutionary email client: http://www.opera.com/mail/

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to