Hi Michael,
You can use these boolean system properties:
equinox.ds.debug - Turns on/off debugging of SCR
equinox.ds.print - Specifies that logged entries
should be printed to the framework runtime console
equinox.ds.perf - Enables generating and printing logs about the time
performance of the operations executed by the SCR (Useful when the user is
interested in the time that is spent in the bind, activate, deactivate methods
of his components)
I would recommend you to use both equinox.ds.debug and
equinox.ds.print properties set to "true" because you will see the debug
messages printed in the console. If you turn on only the equinox.ds.debug
property, the debug messages will be sent only to the LogService if
available.
Stoyan
----- Original Message -----
Sent: Monday, April 14, 2008 9:03
PM
Subject: [equinox-dev] SCR debug
output
Hi,
I frequently find myself in a
position of trying to debug why my declarative services are not running. Is
there debug output from the SCR that I could be taking advantage of to help
this process?
If so, what combination of bundles
and settings are required to see it?
Thanks,
-Mike
Furtak
THIS MESSAGE IS INTENDED FOR THE USE OF THE PERSON TO WHOM IT IS
ADDRESSED. IT MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL AND
EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If you are not the intended
recipient, your use of this message for any purpose is strictly prohibited. If
you have received this communication in error, please delete the message and
notify the sender so that we may correct our records.
__________
NOD32 3025 (20080414) Information __________
This message was checked
by NOD32 antivirus system. http://www.eset.com
_______________________________________________ equinox-dev mailing
list equinox-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/equinox-dev
__________
NOD32 3025 (20080414) Information __________
This message was checked
by NOD32 antivirus system. http://www.eset.com
|