Not quite sure Andy, the GML spec does provide some standard (but optional) attributes for name, description, bounds etc… I wonder if one of them snuck out of the encoder at you?
Can you produce this issue with a plain geoserver install? If so you have a solid bug report on your hands. Other than that it would be good to note what data store you are using in case we are looking at a problem there.
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet
This is a plain Geoserver install.
I just threw the 2.6.0-war-File at Tomcat, configured a PostGIS-Data-Source
and plublished some tables.
The string attribute in question showed up once i renamed it from "name" to
"nname" so my guess is that GS has some problem tih attributes called
"name".
Btw. the services a publicly accessible so if somebody wants to check by
themselves, please do.
Andy
PS: I can reproduce the same issue with GS-2.6.1 on my test server
