Configuring Cascaded WFS Layers doesn't capture and store basic layer metadata 
from remote service
--------------------------------------------------------------------------------------------------

                 Key: GEOS-4859
                 URL: https://jira.codehaus.org/browse/GEOS-4859
             Project: GeoServer
          Issue Type: Bug
            Reporter: Jeffrey Johnson
            Assignee: Andrea Aime
            Priority: Minor


When configuring a resource/layer from a remote WFS server using the WFS Store. 
The basic metadata of the service such as the abstract and and keywords are not 
parsed and stored with the new layer in the local geoserver. 

This is similar to http://jira.codehaus.org/browse/GEOS-4775 but in this case 
the metadata is not parsed when configured via the Wicket UI or via the rest 
API.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, 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-novd2d
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to