WFSContentDataAccess will fail when using HTTP POST
Description
When using the WFSContentDataAccess it’s possible to direct if the HTTP call’s should be made by GET or POST, by setting the parameter WFSDataStoreFactory.PROTOCOL.
This setting will also be used for call’s that isn’t directly related to the WFS calls, like for instance a call for xsd specified in the xml declaration of the resulting xml.
So a workaround is to always use GET set by the PROTOCOL. At the other hand, if you would like to make a Get_feature with a filter. It’s problematic to use GET and you should instead use POST. This causes an exception like this:
When using the WFSContentDataAccess it’s possible to direct if the HTTP call’s should be made by GET or POST, by setting the parameter WFSDataStoreFactory.PROTOCOL.
This setting will also be used for call’s that isn’t directly related to the WFS calls, like for instance a call for xsd specified in the xml declaration of the resulting xml.
So a workaround is to always use GET set by the PROTOCOL. At the other hand, if you would like to make a Get_feature with a filter. It’s problematic to use GET and you should instead use POST. This causes an exception like this: