Added load order dependency with hibernate, gorm #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added load order dependency with hibernate and gorm to ensure the methods they add to the domain classes are already present by the time activiti loads, in case a task fired at start-up will need them.
limcheekin
added a commit
that referenced
this pull request
Jun 24, 2014
Added load order dependency with hibernate, gorm
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added load order dependency with hibernate and gorm to ensure the methods they add to the domain classes are already present by the time activiti loads, in case a task fired at start-up will need them.
This can happen if we have a timer-triggered task with a timer that is overdue when the plug-in starts (i.e. because the application was down when it was programmed to fire). As soon as the plugin loads, the overdue timer is triggered and the task/process attached to it fire. If the task happens to call a method that uses a GORM-autogenerated method (
findBy*, etc.) and the gorm/hibernate plugins haven't loaded yet, the call to the method will fail.