Von: riena-dev-bounces@xxxxxxxxxxx
[mailto:riena-dev-bounces@xxxxxxxxxxx] Im Auftrag von ekkehard
Gesendet: Dienstag, 11. November 2008 10:24
An: Riena Developers list
Betreff: Re: [riena-dev] Riena Logging
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
hi stefan,
just switched to M5
I've seen your concept of ExtensionPoints for Logging
and found in riena.core that there are examples for extensions,
but commented
so I hoped nothing was logged from riena - only from my logging bundle
but there are still outputs from riena core to console:
DEBUG - 18:26:48 [B: org.eclipse.riena.core] - published web service.
protocol=hessian, url="">
DEBUG - 18:26:48 [B: org.eclipse.riena.core] - web service count: 1.
DEBUG - 18:26:48 [B: org.eclipse.riena.core] - service endpoints count: 1.
ekke
Stefan Liebig schrieb:
Hallo Ekkehard,
You might try the current version from CVS. All the issues that you mentioned
in your blog (http://ekkes-corner.org/)
should be fixed.
Tschüß,
Stefan
ekkehard wrote:
Stefan Liebig schrieb:
Hallo Ekkehard,
....
If you like I can notify you when my refactored logging is ready for testing,
so can grab riena.core from CVS.
yes, of course.
if I'm finding the time I'll test it
ciao
ekke
Tschüß,
Stefan
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev
