Namespace field not updated if there's only on workspace configured
-------------------------------------------------------------------
Key: GEOS-3514
URL: http://jira.codehaus.org/browse/GEOS-3514
Project: GeoServer
Issue Type: Bug
Components: Wicket UI
Affects Versions: 2.0-RC1
Reporter: Gabriel Roldán
Assignee: Gabriel Roldán
Priority: Critical
Fix For: 2.0-RC2
From the mailing list:
{quote}
I'm using 2.0-RC1 as well as an older nightly build of 2.0-beta2 (07/29/09). In both I found that if I have only one workspace, namespaces get confused through the user-interface.
Here's what I did:
1) Extract the .war, set it up to run through Tomcat
2) Connect to the web-based UI and remove all the pre-installed workspaces.
3) Create a new workspace, define the namespace.
4) When building a PostGIS NG datastore, I can only choose that single workspace from the picklist. However, picking it does not populate the namespace further down the form. Nothing shows up there. I fill out all the other elements, and submit the datastore. If I look at the datastore.xml that was built, it lists the incorrect namespace -- it uses the topp URI. I can change the namespace to what it should be in the file, however the next time I use the UI to look at the datastore properties it gets reset to the incorrect namespace.
5) Create a layer from the new datastore.
6) WFS requests to the layer fail, because it looks for topp:<my layer name> instead of the prefix defined for my workspace.
While working with the 2.0-beta2 install, I noticed that if I create two workspaces, then things work better. While I'm building the datastore it allows me to pick between the two workspaces, and the namespace element appears appropriately depending on which workspace I choose.
For any of the Geoserver releases (latest, nightly, stable, whatever), do you ever create a package that does not include any sample data?
Thanks,
Ryan
{code}
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira