jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • GeoServer
  • GEOS-831

Problem with custom schema.xml for defining FeatureType

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Cannot Reproduce
  • Affects Version/s: 1.4.0
  • Fix Version/s: None
  • Component/s: Configuration
  • Labels:
    None
  • Environment:
    Linux Fedora Core 4, Tomcat 5.5, Java 1.5

Description

The problem arised when configuring a feature type with a custom schema.xml file.

I follow the procedure explained in the documentation, in page "Geoserver config files": I have a PostGIS table in my datastore, I don't create the FeatureType with the web admin but create a directory with the proper name in the data directory, then put into it the info.xml and schema.xml files (handwritten), with a custom GML Schema. Then I open Geoserver's web admin and hit "Load". All works fine: it loads the new configuration, I can see the new feature type and the WFS DescribeFeatureType request returns the right schema. I tested the WMS and WFS interfaces on these datas and all works perfectly, so I'm confident my info.xml and schema.xml files are correct.

Then I use the web admin to edit another already existent feature type (I change a trivial parameter, like the bounding box), hit "Apply", then "Save". Geoserver takes the new parameter correctly, but my custom schema.xml file is rewritten. If I repeat the DescribeFeatureType request I still get the correct result, but only because Geoserver has it in some cache: if I hit "Load" or restart Tomcat, the response gets corrupted.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Andrea Aime added a comment - 04/Dec/09 4:54 AM

Should have been fixed in 1.7.x. Can you try to reproduce?

Show
Andrea Aime added a comment - 04/Dec/09 4:54 AM Should have been fixed in 1.7.x. Can you try to reproduce?
Hide
Permalink
Gabriel Roldán added a comment - 05/Feb/12 11:49 AM

closing, cannot reproduce. Too old an issue, most probably fixed when moved from the monolithic 1.x configuration to the 2.0 one

Show
Gabriel Roldán added a comment - 05/Feb/12 11:49 AM closing, cannot reproduce. Too old an issue, most probably fixed when moved from the monolithic 1.x configuration to the 2.0 one

People

  • Assignee:
    Gabriel Roldán
    Reporter:
    Fabio Da Soghe
Vote (0)
Watch (2)

Dates

  • Created:
    04/Jan/07 11:19 AM
    Updated:
    05/Feb/12 11:49 AM
    Resolved:
    28/Jan/12 2:18 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.