Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixed bug causing PropertyIsNil filter to fail if ResponsePaging is activated #678

Merged
merged 1 commit into from
Aug 17, 2016
Merged

Fixed bug causing PropertyIsNil filter to fail if ResponsePaging is activated #678

merged 1 commit into from
Aug 17, 2016

Conversation

dstenger
Copy link
Contributor

PropertyIsNil filter fails if ResponsePaging is activated:

<ows:Exception exceptionCode="NoApplicableCode">
    <ows:ExceptionText>Encoding of operator subtype COMPARISON is not supported yet!</ows:ExceptionText>
  </ows:Exception>
</ows:ExceptionReport>

This bug was fixed by adding the missing encoding of PropertyIsNil to Filter200XMLEncoder.

@dstenger dstenger added bug error issue and bug (fix) in progress labels Feb 12, 2016
@tfr42 tfr42 added this to the 3.4 milestone Jul 7, 2016
@copierrj copierrj merged commit 4ea7653 into deegree:master Aug 17, 2016
@lgoltz lgoltz deleted the fixEncodingOfPropertyIsNil-395 branch December 8, 2022 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
bug error issue and bug (fix)
Projects
None yet
Milestone
3.4
Development

Successfully merging this pull request may close these issues.
4 participants
@dstenger @tfr42 @copierrj @lgoltz