Docker: qtSwordPluginWorker ability never gets added to the worker
|Google Code Legacy ID:||Tested version:||2.4, 2.5|
The qtSwordPlugin is disabled and its classes are not being loaded by default. When the plugin is enabled through the GUI, the classes are loaded and, after restarting the worker, the qtSwordPluginWorker ability is added to the worker.
That's true in an installation where the application and the worker are in the same machine, but it's not the case in the Docker environment, where both things are in different containers.
As a quick solution, and an option for a long term fix, the qtSwordPlugin could be enabled by default, by adding it to the initial plugins array:
#1 Updated by Dan Gillean about 1 month ago
- Assignee set to José Raddaoui Marín
- Requires documentation set to Yes
Personally, I think that enabling the SWORD worker by default sounds like an acceptable solution if it will resolve this issue. Users can always choose to disable it after installation if desired. We could add a note to that effect in the documentation.
#3 Updated by José Raddaoui Marín about 1 month ago
Related thread from the user forum: https://groups.google.com/forum/#!topic/ica-atom-users/GCIhtN4LsDg