If you embeds a service which uses the loadLibrary@Runtime operation the path you set as a parameter will be wrong because the interpreter will consider as a reference path that of the embedder.
Can you provide a test for this?
Old bug, still an issue?
Log in to post a comment.
Can you provide a test for this?
Old bug, still an issue?