Agree, it doesn't have impact to change the log level to use "simple"
ones, but I don't see a big value.
Regards
JB
On 05/23/2013 11:42 AM, Guillaume Nodet wrote:
Fwiw, having a more fine grained start level helps reducing the log
verbosity at start time and may slightly help with performance too. The
reason is that a correct start order will result in service dependencies
being satisfied correctly for most bundles, thus not having to wait until
those are satisfied later.
At startup, it also helps having the low-level services up and ready early
in the process (pax-logging, pax-url, etc...).
So while reducing the number of start levels should perfectly work, I'm not
sure what the benefit is really.
2013/5/23 Christian Schneider <[email protected]>
I am currently working on:
https://issues.apache.org/**jira/browse/CXF-5030<https://issues.apache.org/jira/browse/CXF-5030>
It seems that we use an incorrect start level and order for the xmlsec
dependency. I have just committed the fix for this.
While correcting this I found that we have a lot of different start
levels. I am quite sure we should not need all of these.
I have created a wiki page with the current start levels and the meaning I
figured out:
https://cwiki.apache.org/**confluence/display/CXF20DOC/**
CXF+feature+for+Apache+Karaf<https://cwiki.apache.org/confluence/display/CXF20DOC/CXF+feature+for+Apache+Karaf>
Could you guys review this? I wonder if we could remove some of the start
levels.
I think we could limit it to just 9,10,20,30.
Another issue is that there are also some duplicates in the bundles. For
example we start the JAXB impls in cxf-specs and cxf-jaxb.
What do you think?
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
