[Geoserver-devel] [jira] Created: (GEOS-4154) Allow new or edit layer page to recover from minor problems retrieving attribute information
Allow new or edit layer page to recover from minor problems retrieving attribute information Key: GEOS-4154 URL: http://jira.codehaus.org/browse/GEOS-4154 Project: GeoServer Issue Type: Bug Components: UI Affects Versions: 2.1-beta1 Environment: all Reporter: Tara Athan Assignee: Andrea Aime Priority: Minor Attachments: LayerPageWorkaroundForAppSchema.patch Without this fix, the New or Edit Layer page throws a null pointer exception while trying to determine attribute information for an app-schema datastore. While in the long term, it would be best to track down and fix the source of the problem, which appears to be related to complex features, in the meantime we can work around the problem by the submitted simple fix. There is a big gain from this as it allows the layer.xml file to be generated by the GUI for app-schema layers, and then the GML3 option becomes enabled in layer preview, which is helpful for debugging mappings files. Put this together with a change of convention to not store the mappings file in the same directory as the datstore.xml file, and we have partial GUI support for app-schema, so only the mappings file and schema need to be hand-coded -- (once the gui support for Data Access returns.) -- 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 -- Virtualization is moving to the mainstream and overtaking non-virtualized environment for deploying applications. Does it make network security easier or more difficult to achieve? Read this whitepaper to separate the two and get a better understanding. http://p.sf.net/sfu/hp-phase2-d2d ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [jira] Created: (GEOS-3980) Add examples for REST interface with PHP/cURL
Add examples for REST interface with PHP/cURL - Key: GEOS-3980 URL: http://jira.codehaus.org/browse/GEOS-3980 Project: GeoServer Issue Type: Improvement Components: Documentation Reporter: Tara Athan Assignee: Andrea Aime Priority: Minor Attachments: rest-config-examples-java.patch adding a page containing some PHP scripts for accessing the REST interface. This is somewhat of a stub. The PUT example is missing because I have been having trouble getting it to work correctly. Also, it would be nice to have some PHP functions for calling particular REST tasks or better yet a PHP REST object: this is becoming more like code rather than documentation... -- 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 -- ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [jira] Created: (GEOS-3911) keywords missing from rest configuration for FeatureType
keywords missing from rest configuration for FeatureType - Key: GEOS-3911 URL: http://jira.codehaus.org/browse/GEOS-3911 Project: GeoServer Issue Type: Bug Components: REST Affects Versions: 2.0.1 Environment: not applicable Reporter: Tara Athan Assignee: Andrea Aime Priority: Minor the FeatureType class does not contain properties to hold the keywords. This has a major effect that using the updateFeatureTypes method of the class FeatureTypeConfigClient will clear all keywords from the FeatureType. In addition, the functionality to add, delete or change keywords is missing. It appears that the same also applies to FeatureType metadata, and a number of xml elements that appear in the Coverage Rest output. The way this code is set up, if any new elements are added to the xml that were not there when the code was written, this problem will come up. I would propose that the code be set up to keep all unexpected xml elements the same. That way an update would not misconfigure the record. Then the extra functionality to update new elements could be added as convenient. -- 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 -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [jira] Created: (GEOS-3894) error when trying to open to a particular coveragestore from the layers dialogue
error when trying to open to a particular coveragestore from the layers dialogue Key: GEOS-3894 URL: http://jira.codehaus.org/browse/GEOS-3894 Project: GeoServer Issue Type: Bug Affects Versions: 2.0.0 Environment: unknown Reporter: Tara Athan Assignee: Andrea Aime Priority: Minor Attachments: jira.txt noticed this while running a metadata extraction with the rest interface, the GET for coverages from a particular coveragestore yielded an empty xml document the coverage store exists, and its configuration form can be opened from the stores dialogue, but not the layers dialogue. -- 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 -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
