I don't think it's possible to change the log level using command line arguments. The reason is because Jubula bundles initialize their logging based on a logback.xml file contained within the bundle. The code for this can be found in the various Activators for Jubula bundles. For example, ITE / testexec:
(I apologize for the mangled link. I am still not yet permitted to post real, working links in this forum.)
One possible way to change the log level would be to extract the bundle contents and then modify the logback.xml file. You could also submit an enhancement request to make logging configurable from the command line.
I need the log level to trace the submitted SQL statements. I want create a database schema for read only user, which have only the possibility to read and execute the tests. Therefor I want to grant the access rights on the tables to read only.
The problem is, hat the test execution needs write access on reporting, locking and some more tables. That means, I have to differ between the tables for definition and the tables for execution. And I have to find out, which tables are required for text execution with write access.
If I can log the SQL statements on test execution, then I would find out the tables.
Do you know, which logback.xml in which plug-in I have to set to trace level?
I second Achim's comment that those tables are not API and may very well change in the near future, and you should consider very carefully whether to invest effort into this area. You could, for example, submit an enhancement request and work with the Jubula team to implement the functionality you're looking to achieve.
If you still are *sure* you want to log the SQL statements, I'm not sure that modifying the logback.xml file will be sufficient. You probably need to modify the persistence.xml file (in org.eclipse.jubula.client.core/META-INF directory) instead. h ttp://wiki.eclipse.org/EclipseLink/Examples/JPA/Logging contains information and examples for logging in EclipseLink (the JPA provider that is used in Jubula). Sorry for the mangled link, I do not yet have enough posts to be allowed to enter working links in this forum.
Changing the log level to trace in the org.eclipse.jubula.client.core plug-in logs everything but no SQL statements. I think, this is part of the persistence.xml file.
You are right, it's not the best solution to reduce the rights on the database. The user can change values on client side which results into an exception, if the rights are limited to read only.