deegree / deegree3

Official deegree repository providing geospatial core libraries, data access and advanced OGC web service implementations
https://www.deegree.org
GNU Lesser General Public License v2.1
146 stars 99 forks source link

Services dispatching too lax on single WFS service #413

Open vog opened 10 years ago

vog commented 10 years ago

When I configure the deegree with a single WFS service "wfs1", the following service URLs work, as expected:

However, any other name behind "services/" works, too:

This effect disappears if I configure at least two WFS services. If "wfs1" and "wfs2" are configured, only the following URLs work, as expected:

In that case, any other service name leads to the expected error "No service with identifier '...' available".

Tested on deegree 3.4-pre15.

tfr42 commented 10 years ago

Can you please provide the deegree configuration files for both services?

vog commented 10 years ago

This can be reproduced without any feature store, database or data sets. The wfs1.xml can contain the following minimal configuration:

<?xml version="1.0" encoding="UTF-8"?>
<deegreeWFS configVersion="3.0.0" xmlns="http://www.deegree.org/services/wfs" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.deegree.org/services/wfs http://schemas.deegree.org/wfs/3.0.0/wfs_configuration.xsd">
  <QueryCRS>urn:ogc:def:crs:EPSG:4326</QueryCRS>
</deegreeWFS>

For the second test, the wfs2.xml can be simply a copy of wfs1.xml.

segoerke commented 10 years ago

I'd expect the same behaviour for any service type.

vog commented 10 years ago

I'd expect this, too, but since I didn't test that, I didn't want to make false claims.

segoerke commented 10 years ago

This is very easy to check, just request one of the deegree demo services with the service endpoint or do the same with the OGC CITE setup of deegree where there are several service types defined and more than one endpoint for each.