oskari-server

oskari-server copied to clipboard

If a WFS-layer is registered to the application with an URL containing request, version or service parameters some things will break for example the capabilities parser that tries to call request=DescribeFeatureType. This results in calls having something like request=GetCapabilities&request=DescribeFeatureType when fetching the featuretype documentation.

This is first attempt with what I consider the "right places" for doing this:

• MapLayer is used when inserting layers from JSON at the startup and when admin UI is used.
• ServiceConnectInfo is used for fetching capabilities and handles the issue when there are layers in the database that has the problematic parameters on the URL.

However, we might need to support resources:// protocol for urls (used in thematic maps) and regenerating the url is pretty nasty looking at this point (generating arrays and strings for each param).

Related to: https://github.com/oskariorg/oskari-frontend/pull/2569