Closed Aster123 closed 2 years ago
I think this is expected behaviour. If a feature has a reference to the subfeature this must be resolvable.
How did you insert the features? Why the referenced feature is missing?
In the future please ask questions on the mailing list or GIS stackexchange. As mentioned in the guidelines for contributing, we prefer to use GitHub issues only for bugs and enhancements. Please read further in our community support guideline.
We have configured Deegree (3.3.17) and it seemed to be working. When querying http://localhost:8080/wfswms/services?SERVICE=WFS&VERSION=1.1.0&request=GetFeature&TypeName=Ftm&BBOX=106278.201485,445470.3877,109684.259251,450565.950765,EPSG:28992&srsName=EPSG:28992 we received nice results. Then we added queryparameter traversexlinkdepth=* to our request, because we want to see the data of the subfeatures. Then the request crashes with the following error: WebFeatureService:649 - OWS-Exception: Unable to resolve reference to '#Communication_10359663'
With some debugging I found out that what is happening is the following: The query to find all my "Ftm" items is performed. With the data in this query a xlink to the communication query type is created. When this link is followed the exception occurs, because for this id communication does not exist in the database.
I would expect that minOccurs=0 in the element communication specifies that the communication item is optional. Therefore I would expect deegree to do one of the following things:
Relevant part of schema file:
Relevant part of feature type mapping