-
Notifications
You must be signed in to change notification settings - Fork 9
ESB-915 - fix LangManager bean injection in Content Scheduler plugin #322
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
Conversation
|
PUBLICATION for COMMIT ID `` |
|
PUBLICATION for COMMIT ID `` |
|
PUBLICATION for COMMIT ID `` |
|
PUBLICATION for COMMIT ID `` |
|
PUBLICATION for COMMIT ID `` |
|
PUBLICATION for COMMIT ID `` |
| } | ||
| return false; | ||
| } | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ffalqui Come si comporta se cambia il driver del database? I vari driver usano la stessa identica eccezione e usano il medesimo messaggio?
Potrebbe valere la pena di controllare direttamente lo stato SQL allegato all'eccezione, che è uno standard JDBC se non ricordo male
…cate key exception in versioning plugin
MEM2677
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
|
PUBLICATION for COMMIT ID `` |
|
|
PUBLICATION for COMMIT ID `` |




No description provided.