XY get swapped after a WFS-T 1.1.0 Update with EPSG:3007 in the Update srsName attribute

Description

When using a CRS with northing,easting with a WFS-T update, the axis get swapped when crs style identifier is "EPSG:xxxx".

According to Gabriel Rolan this shouldn't happen:
Using the "EPSG:xxx" crs style identifier to mean "force X/Y lon/lat axis order"

Point INSERT with "EPSG:3007" results in XY readback in PostgreSQL --> Correct !
Point INSERT with "urn:ogc:def:crs:EPSG::3007" results in YX readback in Postgresql --> Correct !

Point UPDATE with "EPSG:3007" results in Y'X' readback in PostgreSQL --> Fail !
Point UPDATE with "urn:ogc:def:crs:EPSG::3007" results in Y'X' readback in PostgreSQL --> Correct !

More info can be found in this thread:
http://osgeo-org.1560.n6.nabble.com/XY-get-swapped-after-WFS-T-Update-with-EPSG-3007-td4667859.html - http://osgeo-org.1560.n6.nabble.com/XY-get-swapped-after-WFS-T-Update-with-EPSG-3007-td4667859.html

The thread provides the following example:

Environment

None

Assignee

Andrea Aime

Reporter

codehaus

Triage

Fix versions

Affects versions

Components

Priority

Medium
Configure