Activity
From 12/30/2010 to 01/28/2011
01/28/2011
- 05:53 PM Bug #4307: Upgrade Geoserver to prevent Metacat crashes
- I seem to have introduced invalid shapefiles - perhaps when committing them to SVN. Will have to check alternate chec...
- 05:34 PM Bug #4307: Upgrade Geoserver to prevent Metacat crashes
- keeping this opened until additional tasks are completed:
-package geoserver.war (v2.0.2) along with Metacat's knb.wa... - 12:16 PM Bug #4307: Upgrade Geoserver to prevent Metacat crashes
- We are now using Geotools 2.6.4 (from Geoserver 2.0.2) to read/write the shape files.
Geoserver is deployed in a diff... - 05:30 PM Bug #2188: replace web client with OpenLayers
- TODO:
-create a way for skins to reuse the common map rendering but still perform spatial queries with their results ... - 12:19 PM Bug #2188: replace web client with OpenLayers
- Re-implementing the features we have in MapBuilder in OpenLayers:
1. named locations drop down
2. spatial query when ... - 12:25 PM Bug #2180: Make it easier for admin to add new layers
- It's true that Geoserver does all of this except including the new layer in a rendered map in Metacat.We could includ...
- 12:21 PM Bug #4680: Geoserver StringIndexOutOfBoundsException
- We are now using Geotools 2.6.4
01/14/2011
- 10:59 AM Bug #5273: docs with inline-data allow invalid xml into metacat
- People certainly can use CDATA sections within their inline element, in which case escaping would be taken care of. ...
- 09:11 AM Bug #5273: docs with inline-data allow invalid xml into metacat
- is inline data not contained in CDATA? I thought you could put anything in CDATA and have it be ignored by parsers.
01/13/2011
- 09:37 AM Bug #5273 (Resolved): docs with inline-data allow invalid xml into metacat
- If you insert a document with inline-data, the data is stripped out of the document before it is validated. However,...
01/10/2011
- 02:57 PM Bug #2495: Charset bug: Internationalization
- Fro reference: http://wiki.apache.org/tomcat/FAQ/CharacterEncoding
- 02:57 PM Bug #2495: Charset bug: Internationalization
- Current state: use XML encoding in prolog if it existing, otherwise default to UTF-8
Next phase: respect encoding spe...
Also available in: Atom