nmco
commented
6 years ago Iurie Maxim 24/4/2017: Most probably the issue is not related to Geoserver but is related to complex features and/or transformers (such as app-schema or FME). Complex features are handled in Geoserver trough app-schema. App-schema was not designed for data editing, but only for data reading and transormation. Depending on the database structure, in most cases if data is transformed, it cant be edited (ex: if two fields are concatenated into one then it is not possible to edit one field in order to edit two fields). This is the reason why it is not possible to edit trough app-schema. On the other hand for complex features, as they are based on multiple features, it means than in a corectly designed database the data of a complex feature is stored in more than one table and usually has one-to-many or even many-to-many relationships. Therefore for complex features, in order to edit the data, in most cases the data need to be edited in more than one table (tables are linked trough primary and foreign keys that are not exposed in the GML of the complex feature). For better understanding the editing of complex features it should be understood that it is simmilar to the SQL views or simple Microsoft Access Querries that are not allowing to edit the data if the data is transformed or if it is coming from more than one table. Therefore editing must be made directly in the tables trough specific mechanisms that knows how the data is stored in the database and what triggers need to be made in order to insert, edit or delete a record. A general issue is related to the fact that in INSPIRE it is not imposed a certain database structure and will never be imposed such a fixed structure (as for example ESRI is providing in ArcGIS for INSPIRE extension), simply because each data provider has different data and the INSPIRE model tries to accomodate most of these data models trough a single data model.
Currently in GeoServer WFS transactional is only supported for simple features.