Description:
When using jmslibrary without jar files available in configured path, an Exception is raised when calling robot --dryrun.
An Exception is also raised when calling command libdoc JMS list or similar to get libdoc documentation using CLI.
Analysis:
When robot --dryrun or libdoc JMS list is called, constructor of JMS class is called. It tries
to import Java classes, which should be available in configured path for jar files, and to create a ConnectionFactory from them.
Solution:
Move import and creation of ConnectionFactory to existing keyword (i.e. create_connection(..)) or create new keyword to
initialize the lib. In both cases do not raise an Exception, but let the keyword fail instead with proper error message.
Description:
When using jmslibrary without jar files available in configured path, an Exception is raised when calling
robot --dryrun.An Exception is also raised when calling command
libdoc JMS listor similar to get libdoc documentation using CLI.Analysis:
When
robot --dryrunorlibdoc JMS listis called, constructor of JMS class is called. It triesto import Java classes, which should be available in configured path for jar files, and to create a ConnectionFactory from them.
Solution:
Move import and creation of ConnectionFactory to existing keyword (i.e.
create_connection(..)) or create new keyword toinitialize the lib. In both cases do not raise an Exception, but let the keyword fail instead with proper error message.