We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
See - https://github.com/eXist-db/exist/blob/develop/exist-core/src/main/java/org/exist/config/ConfigurationDocumentTrigger.java#L93
The method finish in ConfigurationDocumentTrigger is no longer called. Should it be deleted?
finish
ConfigurationDocumentTrigger
It looks like the code in that method should go into afterDeleteDocument but it is already present in beforeDeleteDocument!
afterDeleteDocument
beforeDeleteDocument
@shabanovd Any thoughts on this please?
The text was updated successfully, but these errors were encountered:
@adamretter if 5.x was released then it should go to 6.x because it's api change, IMHO
Sorry, something went wrong.
@adamretter on code itself, finish was here before triggers refactoring, so it can be safely deleted
No branches or pull requests
See - https://github.com/eXist-db/exist/blob/develop/exist-core/src/main/java/org/exist/config/ConfigurationDocumentTrigger.java#L93
The method
finish
inConfigurationDocumentTrigger
is no longer called. Should it be deleted?It looks like the code in that method should go into
afterDeleteDocument
but it is already present inbeforeDeleteDocument
!@shabanovd Any thoughts on this please?
The text was updated successfully, but these errors were encountered: