Older versions of GeoNode had a bug where they would create empty keywords in GeoServer - not an empty keyword list, but a keyword that was literally "". When some enhancements were made to GeoServer's keyword handling for GeoServer 2.1.x, the keyword validation in GeoServer was made stricter, making these keywords unallowed.
You will need to manually modify your GeoServer configuration to remove the empty keywords. While I generally don't condone using 'sed' to modify XML files, the following snippet should work with GeoServer's config files thanks to GeoServer's consistent indentation of the config files. find /var/lib/geoserver/geonode-data/workspaces/ -name '*.xml' | \ > xargs sed -i '\!<keywords>!,\!<\/keywords>! s!<string>\s*</string>!!' Your path may differ. Please also make sure to shut down tomcat before running this command and not restart it until after it finishes. -- David Winslow OpenGeo - http://opengeo.org/ On Tue, Feb 21, 2012 at 11:42 AM, MartÃn Rouaux <[email protected]> wrote: > I moved to 1.1 geonode version today. I'm getting the following error > > 2012-02-21 13:35:15,498 WARN [org.geoserver] - Failed to load feature type > 'Comisarias' > com.thoughtworks.xstream.converters.ConversionException: does not match > regular expression: > ([^\\]+)(?:\\@language=([^\\]+)\\;)?(?:\\@vocabulary=([^\\]+)\\;)? : does > not match regular expression: > ([^\\]+)(?:\\@language=([^\\]+)\\;)?(?:\\@vocabulary=([^\\]+)\\;)? > ---- Debugging information ---- > message : does not match regular expression: > ([^\\]+)(?:\\@language=([^\\]+)\\;)?(?:\\@vocabulary=([^\\]+)\\;)? > cause-exception : java.lang.IllegalArgumentException > cause-message : does not match regular expression: > ([^\\]+)(?:\\@language=([^\\]+)\\;)?(?:\\@vocabulary=([^\\]+)\\;)? > class : org.geoserver.catalog.impl.FeatureTypeInfoImpl > required-type : org.geoserver.catalog.Keyword > line number : 11 > ------------------------------- > > > any ideas? >
