Before I go into the details I have to report that I downloaded the stable version today via http://downloads.sourceforge.net/geoserver/geoserver-2.1.1-war.zip - http://downloads.sourceforge.net/geoserver/geoserver-2.1.1-war.zip.
Though it didn't want to work at all from scratch using a PostGIS DB as the PostGIS library was missing. The PostgreSQL library was present though. I was getting the following exception "The class class org.postgis.PGbox3d does not implement org.postgresql.util.PGobject" without the PostGIS library. Adding the PostGIS library manually fixed that problem.
In case this is another bug on it's own, let me know so I can create a detailed bug report for it.
If a feature definition contains a column that is a defined as a domain type, the column is excluded from the feature definition. No error is given,
The domain type I used and tested it with (both an int and real:
CREATE DOMAIN posreal
CONSTRAINT posreal_check CHECK ((VALUE >= (0)::real));
CREATE DOMAIN posint
CONSTRAINT posint_check CHECK ((VALUE >= 0));
If I change to column to a regular int or real type it works as it should. According to [https://jira.codehaus.org/browse/GEOS-1430" title="Column using domain types are silently ignore in feature definitions" class="issue-link" data-issue-key="GEOS-1430"><del>GEOS-1430</del> it's already fixed a while back.