-
Notifications
You must be signed in to change notification settings - Fork 31
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.
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
Registring behaviours for model that are deployed in the same extension fail. #275
Comments
kerkhofsd
pushed a commit
that referenced
this issue
Jan 2, 2020
Reproduced and added some DEBUG logging in an integration test:
Hence it actually looks like the logic to register the model is actually executed before the logic to register the behavior. Looks like issue #197 shares the same root cause: Alfresco adds the model to the |
kerkhofsd
pushed a commit
that referenced
this issue
Jan 3, 2020
kerkhofsd
pushed a commit
that referenced
this issue
Jan 3, 2020
kerkhofsd
pushed a commit
that referenced
this issue
Jan 3, 2020
kerkhofsd
pushed a commit
that referenced
this issue
Jan 3, 2020
kerkhofsd
pushed a commit
that referenced
this issue
Jan 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a ... (check one with "x")
Expected Behavior
Components registered with
@Behaviour
are registered without any problems.They are only registered after the necessary models have already been deployed.
Current Behavior
@Behaviour
annotated components are registered before the models that are present in the same extension are deployed.They log a warning in Alfresco, and the policies are not registered at all the first time that Alfresco starts up.
When Alfresco is restarted, the models have already been deployed to data dictionary, and the policy is registered correctly.
Possible Solution
Re-register failed behaviours after models have been deployed, or register behaviours after models have been deployed.
Steps to Reproduce (for bugs)
WEB-INF/dynamic-extensions/bundles/
)Your Environment
The text was updated successfully, but these errors were encountered: