hi stefan,
I'll debug this later.... (not today)
but did another test:
before I haven't used system property "riena.defaultlogging"
so I tried to run with set to false:
same happens as before
then I set it to true,
now there is a difference:
these outputs only appear if defaultlogging is set to true:
Tue Nov 11 10:13:45 CET 2008 WARNING [DeferredLoggingForwarder]
org.eclipse.riena.internal.core.Activator Defered log event occured on
Tue Nov
11 10:13:45 CET 2008 (1226394825556 ms) in thread [Start Level Event
Dispatcher]:
LogLevel: 2,
Message: Forced <<lazy>> start():
'org.eclipse.riena.communication.factory.hessian' failed but may
succeed
(bundle state is in transition):
State change in progress for bundle "initial@reference:file:../../riena/plugins/org.eclipse.riena.communication.factory.hessian_1.0.0.M5.jar/"
by thread "Start Level Event Dispatcher
......
Tue Nov 11 10:13:45 CET 2008 INFO [Start Level Event Dispatcher]
org.eclipse.riena.communication.core.ssl.SSLConfiguration Configuring
SSL
protocol 'null' with keystore 'null'.
Tue Nov 11 10:13:45 CET 2008 INFO [Start Level Event Dispatcher]
org.eclipse.riena.communication.core.ssl.SSLConfiguration No
configuration
given!.
...
and more
but the other output written for each Service registered with Riena
remote
properties happens always:
DEBUG - 10:18:54 [B: org.eclipse.riena.core] - published web service.
protocol=hessian, url= "">
DEBUG - 10:18:54 [B: org.eclipse.riena.core] - web service count: 80.
DEBUG - 10:18:54 [B: org.eclipse.riena.core] - service endpoints count:
80.
the log output is formatted differently, so perhaps you have an idea
why the
first (Tue Nov 11.......) are not printed with
riena.defaultlogging=false
but the other (DEBUG - 10:18:54....) are printed
ciao
ekke
Liebig, Stefan schrieb:
Hi
Ekke,
To
be honest I have no idea why this happens. Not yet!
If
there are no extensions defining log listeners nothing should
be logged.
Except
when the system property "riena.defaultlogging"
has been set to true.
Than
as a default a log listener logging to the console will be
created.
Could
please set a breakpoint at
LoggerMill.bind(ExtendedLogReaderService
logReaderService)
and
check what happens there?
Thanks,
Stefan