Hi,
Tasmania_cities is an odd shapefile for a demo data. The shapefile is of type multipoint and it contains exactly one feature.
I wonder if this is intentional.
How did you move the “tasmania_cities.shp” into Postgis and have you checked what datatype it has now while in PostGIS? If it is still a multipoint layer that could explain why inserting points fails.
-Jukka Rahkonen-
···
Lähettäjä: Hakala Oiva (MTT) [mailto:oiva.hakala@anonymised.com]
Lähetetty: 25. lokakuuta 2013 15:41
Vastaanottaja: Rahkonen Jukka; ‘GeoServer Mailing List List’
Aihe: VS: [Geoserver-users] WFS-T and database
My problem is easy to repeat
Just move tasmania_cities to database, and see what happens. I am not experienced enough to solve this alone. Something is WRONG with the wfs-t demo app. I can easily add data to that table with another wfs-t app. However it uses Openlayers 2.1.2, Geoext 1.1 and Ext 3.4. This wfs-t app uses openlayers that comes with Geoserver and won’t even work with 2.1.2 openlayers.js.
The reason for all this is, that I would like to use this sample wfs-t app as a base of my own app, including attribute form. There is nothing wrong with the database. Geoserver WFS-level is set to complete. The only problem is this sample app. Don’t know why 
Oiva
Lähettäjä: Rahkonen Jukka [jukka.rahkonen@anonymised.com]
Lähetetty: 25. lokakuuta 2013 15:17
Vastaanottaja: ‘GeoServer Mailing List List’
Aihe: Re: [Geoserver-users] WFS-T and database
Hi,
I think that the message about the input format “inputFormat = text/xml; subtype=gml/3.1.1”
that comes after sending the demo request “WFS_transactionInsert.xml” is not true.
The transaction is really successful and both the geometry and attribute are inserted so I believe that Geoserver is doing the right thing and with WFS 1.0.0 it is awaiting geometries expressed as GML 2.1.2. It would be amazing to pass the CITE tests if it did not do that. Can we say this is a bug? Client is sending GML2 and Geoserver takes it as GML2 but prints that it was GML 3.1.1 and at least this is misleading information for newbie debuggers.
The demo request contains a weird EPSG:4326 geometry but Geoserver does accept it. I made GEOS-6115 because of this.
The log info that Oiva sent does not contain valuable information. I think that we need the POST data that was used when Geoserver made a successful insert but no geometry was really inserted.
-Jukka Rahkonen-
Hakala Oiva wrote:
Restart GeoServer and have your client do and edit. Look in the logs for the Transaction XML,
post it here. At least we can see what is the client doing
Cheers
Andrea
Maybe I could edit web.xml right. Anyway, here is the log just after transaction trial.
WFS 1.0.0, but GML 3.1.1
Oiva
Request: getServiceInfo
2013-10-25 13:32:57,794 INFO [geoserver.gwc] - DataStoreChange: {http://localhost:8080/geoserver}tasmania_cities PreInsert
2013-10-25 13:32:57,816 INFO [geoserver.gwc] - DataStoreChange: {http://localhost:8080/geoserver}tasmania_cities PostInsert
2013-10-25 13:32:57,897 INFO [geoserver.wfs] -
Request: transaction
service = WFS
version = 1.0.0
baseUrl = http://localhost:8080/geoserver/
group[0] = wfs:insert=net.opengis.wfs.impl.InsertElementTypeImpl@anonymised.com (feature: [SimpleFeatureImpl:tasmania_cities=[SimpleFeatureImpl.Attribute: gid=0, SimpleFeatureImpl.Attribute: city_name<city_name id=fid–2c919365_141ef2c92a5_-8000>=Test-town, SimpleFeatureImpl.Attribute: admin_name<admin_name id=fid–2c919365_141ef2c92a5_-8000>=Tasmania, SimpleFeatureImpl.Attribute: cntry_name<cntry_name id=fid–2c919365_141ef2c92a5_-8000>=null, SimpleFeatureImpl.Attribute: status=null, SimpleFeatureImpl.Attribute: pop_class<pop_class id=fid–2c919365_141ef2c92a5_-8000>=null, SimpleFeatureImpl.Attribute: geom=null]], handle: null, idgen: , inputFormat: , srsName: null)
insert[0]:
feature[0] = SimpleFeatureImpl:tasmania_cities=[SimpleFeatureImpl.Attribute: gid=0, SimpleFeatureImpl.Attribute: city_name<city_name id=fid–2c919365_141ef2c92a5_-8000>=Test-town, SimpleFeatureImpl.Attribute: admin_name<admin_name id=fid–2c919365_141ef2c92a5_-8000>=Tasmania, SimpleFeatureImpl.Attribute: cntry_name<cntry_name id=fid–2c919365_141ef2c92a5_-8000>=null, SimpleFeatureImpl.Attribute: status=null, SimpleFeatureImpl.Attribute: pop_class<pop_class id=fid–2c919365_141ef2c92a5_-8000>=null, SimpleFeatureImpl.Attribute: geom=null]
idgen = GenerateNew
inputFormat = text/xm
inputFormat = text/xml; subtype=gml/3.1.1
releaseAction = ALL