You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Michael Täschner <m....@gmail.com> on 2014/11/21 14:50:54 UTC
Karaf 2.4.0 with Pax-Logging-Logback
Hi All,
after getting pax-logging-logback implementation running in ServiceMix
5.1.x, based on Karaf 2.3.x, I face issues again in ServiceMix 5.3.0 using
Karaf 2.4.0
I replaced the pax-logging-service bundle inside etc/startup.properties (as
before) but was surprised to see a pax-logging-service bundle running in
the container. Sifting through features.xml to find the root issue
importing pax-logging-service I found:
karaf-standard-features: karaf-framework feature declares bundle
pax-logging-service !! I am puzzled: why are these "core" bundles declared
in a feature if they are explicitly started before the feature deployment
through startup.properties ?? Is this duplicate declaration really helpful
?
How can I proceed to continue using pax-logging-logback with minimal
changes to the karaf configuration? I already customize startup.properties
as stated before but I am hesitant to override the karaf standard features
xml.
On a related note: it would be extremely helpful if we had some kind of
reverse search for features, i.e. search feature by bundle (name/symbolic
name) to find where it is declared.
Thanks and Best Regards,
Michael
Re: Karaf 2.4.0 with Pax-Logging-Logback
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi,
the default etc/org.apache.karaf.features.cfg is defined in the framework
feature. Basically the framework feature is the boot feature per se. [1]
I think it's best you get the latest sources and start playing with your
ideas. I'm not sure there is a better solution for it, though it might be
worth to look at.
regards, Achim
[1] -
https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=blob;f=assemblies/features/framework/src/main/filtered-resources/resources/etc/org.apache.karaf.features.cfg;h=73f3bbf134c067dc955c0f9aadb19b22a907f1df;hb=HEAD
2014-11-24 15:22 GMT+01:00 Michael Täschner <m....@gmail.com>:
> Hi,
>
> sorry to ask again: where are the bootFeatures defined,where is the
> default etc/org.apache.karaf.features.cfg defined ? Reason, I still think
> "karaf-framework" should not be set as bootFeature (in the final assembly)
> as the contained features are started via etc/startup properties.
>
> I think having both: bootFeature=karaf-framework,... and the bundles
> defined in startup.properties is redundant (and irritating).
>
> Your improvement feedback sounds good.
>
> Best Regards,
> Michael
>
> 2014-11-24 13:14 GMT+01:00 Achim Nierbeck <bc...@googlemail.com>:
>
>> Hi,
>>
>> see my comments inline.
>>
>> regards, Achim
>>
>>
>>> so to understand clearly: the "karaf-framework" feature is used to
>>> assemble karaf using karaf-maven-plugin ? As such it should rather be
>>> configured as "installedFeature" instead of "bootFeatures" as the contained
>>> bundles will be managed via startup.properties ? If yes, should I raise a
>>> bug for Karaf 2.4.0 ?
>>>
>>>
>> Yes and no, the framework feature is used as KAR file as it not only
>> contains the feature.xml but also the additional resources like *.sh and
>> *.bat and all of the configurations.
>> Take a look at the corresponding pom [1] and the framework feature module
>> [2].
>> That part is especially tricky and needs special handling.
>>
>> [1] -
>> https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=blob;f=assemblies/apache-karaf/pom.xml;h=6b721ed1c012338a2041b869335ac295aff4e4e9;hb=HEAD
>> [2] -
>> https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=tree;f=assemblies/features/framework;hb=HEAD
>>
>>
>>
>>> Secondly: I get the message about contribution :)
>>>
>>> I suggest raising improvement issue with new goal features:finditem with
>>> bundle-id to display list of features where this bundle is configured.
>>> Question would be what the best match criteria is: by Bundle-Symbolic name
>>> (and version) ? or by location (mvn identifier) ?
>>>
>>
>> yes an improvement issue is always good :)
>> I'd think either the Bundle-Symbolic name or the ID used inside karaf,
>> rather then the mvn: identifier.
>> It should be quite easy to get back to the actual used identifier and
>> from there on it's just grabbing through the installed features ...
>>
>>
>>>
>>> I see if I can come up with something ...
>>>
>>> Cheers,
>>> Michael
>>>
>>> 2014-11-21 15:20 GMT+01:00 Achim Nierbeck <bc...@googlemail.com>:
>>>
>>>> Well actually it's the other way round.
>>>> The never version of Karaf which is build by the karaf-maven-plugin
>>>> you'll need a feature to describe the Karaf container,
>>>> allas the karaf-framework feature.
>>>>
>>>> On a related note: it would be extremely helpful if we had some kind of
>>>>> reverse search for features, i.e. search feature by bundle (name/symbolic
>>>>> name) to find where it is declared.
>>>>
>>>>
>>>> We really, really love contribution :-)
>>>>
>>>> regards, Achim
>>>>
>>>>
>>>> 2014-11-21 15:05 GMT+01:00 Michael Täschner <m....@gmail.com>:
>>>>
>>>>> Hi All,
>>>>>
>>>>> as a workaround I removed "karaf-framework" from the "featuresBoot" in
>>>>> etc/org.apache.karaf.features.cfg and the container runs nicely with no
>>>>> duplicate logging provider.
>>>>>
>>>>> Still curios why "karaf-framework" replicates the entries from
>>>>> etc/startup.properties ?!
>>>>>
>>>>> Best Regards,
>>>>> Michael
>>>>>
>>>>> 2014-11-21 14:50 GMT+01:00 Michael Täschner <m....@gmail.com>:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> after getting pax-logging-logback implementation running in
>>>>>> ServiceMix 5.1.x, based on Karaf 2.3.x, I face issues again in ServiceMix
>>>>>> 5.3.0 using Karaf 2.4.0
>>>>>>
>>>>>> I replaced the pax-logging-service bundle inside
>>>>>> etc/startup.properties (as before) but was surprised to see a
>>>>>> pax-logging-service bundle running in the container. Sifting through
>>>>>> features.xml to find the root issue importing pax-logging-service I found:
>>>>>>
>>>>>> karaf-standard-features: karaf-framework feature declares bundle
>>>>>> pax-logging-service !! I am puzzled: why are these "core" bundles declared
>>>>>> in a feature if they are explicitly started before the feature deployment
>>>>>> through startup.properties ?? Is this duplicate declaration really helpful
>>>>>> ?
>>>>>>
>>>>>> How can I proceed to continue using pax-logging-logback with minimal
>>>>>> changes to the karaf configuration? I already customize startup.properties
>>>>>> as stated before but I am hesitant to override the karaf standard features
>>>>>> xml.
>>>>>>
>>>>>> On a related note: it would be extremely helpful if we had some kind
>>>>>> of reverse search for features, i.e. search feature by bundle
>>>>>> (name/symbolic name) to find where it is declared.
>>>>>>
>>>>>> Thanks and Best Regards,
>>>>>> Michael
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Apache Member
>>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>>>> Committer & Project Lead
>>>> blog <http://notizblog.nierbeck.de/>
>>>> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>>>>
>>>> Software Architect / Project Manager / Scrum Master
>>>>
>>>>
>>>
>>
>>
>> --
>>
>> Apache Member
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
>> & Project Lead
>> blog <http://notizblog.nierbeck.de/>
>> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>>
>> Software Architect / Project Manager / Scrum Master
>>
>>
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: Karaf 2.4.0 with Pax-Logging-Logback
Posted by Michael Täschner <m....@gmail.com>.
Hi,
sorry to ask again: where are the bootFeatures defined,where is the default
etc/org.apache.karaf.features.cfg defined ? Reason, I still think
"karaf-framework" should not be set as bootFeature (in the final assembly)
as the contained features are started via etc/startup properties.
I think having both: bootFeature=karaf-framework,... and the bundles
defined in startup.properties is redundant (and irritating).
Your improvement feedback sounds good.
Best Regards,
Michael
2014-11-24 13:14 GMT+01:00 Achim Nierbeck <bc...@googlemail.com>:
> Hi,
>
> see my comments inline.
>
> regards, Achim
>
>
>> so to understand clearly: the "karaf-framework" feature is used to
>> assemble karaf using karaf-maven-plugin ? As such it should rather be
>> configured as "installedFeature" instead of "bootFeatures" as the contained
>> bundles will be managed via startup.properties ? If yes, should I raise a
>> bug for Karaf 2.4.0 ?
>>
>>
> Yes and no, the framework feature is used as KAR file as it not only
> contains the feature.xml but also the additional resources like *.sh and
> *.bat and all of the configurations.
> Take a look at the corresponding pom [1] and the framework feature module
> [2].
> That part is especially tricky and needs special handling.
>
> [1] -
> https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=blob;f=assemblies/apache-karaf/pom.xml;h=6b721ed1c012338a2041b869335ac295aff4e4e9;hb=HEAD
> [2] -
> https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=tree;f=assemblies/features/framework;hb=HEAD
>
>
>
>> Secondly: I get the message about contribution :)
>>
>> I suggest raising improvement issue with new goal features:finditem with
>> bundle-id to display list of features where this bundle is configured.
>> Question would be what the best match criteria is: by Bundle-Symbolic name
>> (and version) ? or by location (mvn identifier) ?
>>
>
> yes an improvement issue is always good :)
> I'd think either the Bundle-Symbolic name or the ID used inside karaf,
> rather then the mvn: identifier.
> It should be quite easy to get back to the actual used identifier and from
> there on it's just grabbing through the installed features ...
>
>
>>
>> I see if I can come up with something ...
>>
>> Cheers,
>> Michael
>>
>> 2014-11-21 15:20 GMT+01:00 Achim Nierbeck <bc...@googlemail.com>:
>>
>>> Well actually it's the other way round.
>>> The never version of Karaf which is build by the karaf-maven-plugin
>>> you'll need a feature to describe the Karaf container,
>>> allas the karaf-framework feature.
>>>
>>> On a related note: it would be extremely helpful if we had some kind of
>>>> reverse search for features, i.e. search feature by bundle (name/symbolic
>>>> name) to find where it is declared.
>>>
>>>
>>> We really, really love contribution :-)
>>>
>>> regards, Achim
>>>
>>>
>>> 2014-11-21 15:05 GMT+01:00 Michael Täschner <m....@gmail.com>:
>>>
>>>> Hi All,
>>>>
>>>> as a workaround I removed "karaf-framework" from the "featuresBoot" in
>>>> etc/org.apache.karaf.features.cfg and the container runs nicely with no
>>>> duplicate logging provider.
>>>>
>>>> Still curios why "karaf-framework" replicates the entries from
>>>> etc/startup.properties ?!
>>>>
>>>> Best Regards,
>>>> Michael
>>>>
>>>> 2014-11-21 14:50 GMT+01:00 Michael Täschner <m....@gmail.com>:
>>>>
>>>>> Hi All,
>>>>>
>>>>> after getting pax-logging-logback implementation running in ServiceMix
>>>>> 5.1.x, based on Karaf 2.3.x, I face issues again in ServiceMix 5.3.0 using
>>>>> Karaf 2.4.0
>>>>>
>>>>> I replaced the pax-logging-service bundle inside
>>>>> etc/startup.properties (as before) but was surprised to see a
>>>>> pax-logging-service bundle running in the container. Sifting through
>>>>> features.xml to find the root issue importing pax-logging-service I found:
>>>>>
>>>>> karaf-standard-features: karaf-framework feature declares bundle
>>>>> pax-logging-service !! I am puzzled: why are these "core" bundles declared
>>>>> in a feature if they are explicitly started before the feature deployment
>>>>> through startup.properties ?? Is this duplicate declaration really helpful
>>>>> ?
>>>>>
>>>>> How can I proceed to continue using pax-logging-logback with minimal
>>>>> changes to the karaf configuration? I already customize startup.properties
>>>>> as stated before but I am hesitant to override the karaf standard features
>>>>> xml.
>>>>>
>>>>> On a related note: it would be extremely helpful if we had some kind
>>>>> of reverse search for features, i.e. search feature by bundle
>>>>> (name/symbolic name) to find where it is declared.
>>>>>
>>>>> Thanks and Best Regards,
>>>>> Michael
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Apache Member
>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
>>> & Project Lead
>>> blog <http://notizblog.nierbeck.de/>
>>> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>>>
>>> Software Architect / Project Manager / Scrum Master
>>>
>>>
>>
>
>
> --
>
> Apache Member
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>
> Software Architect / Project Manager / Scrum Master
>
>
Re: Karaf 2.4.0 with Pax-Logging-Logback
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi,
see my comments inline.
regards, Achim
> so to understand clearly: the "karaf-framework" feature is used to
> assemble karaf using karaf-maven-plugin ? As such it should rather be
> configured as "installedFeature" instead of "bootFeatures" as the contained
> bundles will be managed via startup.properties ? If yes, should I raise a
> bug for Karaf 2.4.0 ?
>
>
Yes and no, the framework feature is used as KAR file as it not only
contains the feature.xml but also the additional resources like *.sh and
*.bat and all of the configurations.
Take a look at the corresponding pom [1] and the framework feature module
[2].
That part is especially tricky and needs special handling.
[1] -
https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=blob;f=assemblies/apache-karaf/pom.xml;h=6b721ed1c012338a2041b869335ac295aff4e4e9;hb=HEAD
[2] -
https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=tree;f=assemblies/features/framework;hb=HEAD
> Secondly: I get the message about contribution :)
>
> I suggest raising improvement issue with new goal features:finditem with
> bundle-id to display list of features where this bundle is configured.
> Question would be what the best match criteria is: by Bundle-Symbolic name
> (and version) ? or by location (mvn identifier) ?
>
yes an improvement issue is always good :)
I'd think either the Bundle-Symbolic name or the ID used inside karaf,
rather then the mvn: identifier.
It should be quite easy to get back to the actual used identifier and from
there on it's just grabbing through the installed features ...
>
> I see if I can come up with something ...
>
> Cheers,
> Michael
>
> 2014-11-21 15:20 GMT+01:00 Achim Nierbeck <bc...@googlemail.com>:
>
>> Well actually it's the other way round.
>> The never version of Karaf which is build by the karaf-maven-plugin
>> you'll need a feature to describe the Karaf container,
>> allas the karaf-framework feature.
>>
>> On a related note: it would be extremely helpful if we had some kind of
>>> reverse search for features, i.e. search feature by bundle (name/symbolic
>>> name) to find where it is declared.
>>
>>
>> We really, really love contribution :-)
>>
>> regards, Achim
>>
>>
>> 2014-11-21 15:05 GMT+01:00 Michael Täschner <m....@gmail.com>:
>>
>>> Hi All,
>>>
>>> as a workaround I removed "karaf-framework" from the "featuresBoot" in
>>> etc/org.apache.karaf.features.cfg and the container runs nicely with no
>>> duplicate logging provider.
>>>
>>> Still curios why "karaf-framework" replicates the entries from
>>> etc/startup.properties ?!
>>>
>>> Best Regards,
>>> Michael
>>>
>>> 2014-11-21 14:50 GMT+01:00 Michael Täschner <m....@gmail.com>:
>>>
>>>> Hi All,
>>>>
>>>> after getting pax-logging-logback implementation running in ServiceMix
>>>> 5.1.x, based on Karaf 2.3.x, I face issues again in ServiceMix 5.3.0 using
>>>> Karaf 2.4.0
>>>>
>>>> I replaced the pax-logging-service bundle inside etc/startup.properties
>>>> (as before) but was surprised to see a pax-logging-service bundle running
>>>> in the container. Sifting through features.xml to find the root issue
>>>> importing pax-logging-service I found:
>>>>
>>>> karaf-standard-features: karaf-framework feature declares bundle
>>>> pax-logging-service !! I am puzzled: why are these "core" bundles declared
>>>> in a feature if they are explicitly started before the feature deployment
>>>> through startup.properties ?? Is this duplicate declaration really helpful
>>>> ?
>>>>
>>>> How can I proceed to continue using pax-logging-logback with minimal
>>>> changes to the karaf configuration? I already customize startup.properties
>>>> as stated before but I am hesitant to override the karaf standard features
>>>> xml.
>>>>
>>>> On a related note: it would be extremely helpful if we had some kind of
>>>> reverse search for features, i.e. search feature by bundle (name/symbolic
>>>> name) to find where it is declared.
>>>>
>>>> Thanks and Best Regards,
>>>> Michael
>>>>
>>>
>>>
>>
>>
>> --
>>
>> Apache Member
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
>> & Project Lead
>> blog <http://notizblog.nierbeck.de/>
>> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>>
>> Software Architect / Project Manager / Scrum Master
>>
>>
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: Karaf 2.4.0 with Pax-Logging-Logback
Posted by Michael Täschner <m....@gmail.com>.
Hi,
so to understand clearly: the "karaf-framework" feature is used to assemble
karaf using karaf-maven-plugin ? As such it should rather be configured as
"installedFeature" instead of "bootFeatures" as the contained bundles will
be managed via startup.properties ? If yes, should I raise a bug for Karaf
2.4.0 ?
Secondly: I get the message about contribution :)
I suggest raising improvement issue with new goal features:finditem with
bundle-id to display list of features where this bundle is configured.
Question would be what the best match criteria is: by Bundle-Symbolic name
(and version) ? or by location (mvn identifier) ?
I see if I can come up with something ...
Cheers,
Michael
2014-11-21 15:20 GMT+01:00 Achim Nierbeck <bc...@googlemail.com>:
> Well actually it's the other way round.
> The never version of Karaf which is build by the karaf-maven-plugin you'll
> need a feature to describe the Karaf container,
> allas the karaf-framework feature.
>
> On a related note: it would be extremely helpful if we had some kind of
>> reverse search for features, i.e. search feature by bundle (name/symbolic
>> name) to find where it is declared.
>
>
> We really, really love contribution :-)
>
> regards, Achim
>
>
> 2014-11-21 15:05 GMT+01:00 Michael Täschner <m....@gmail.com>:
>
>> Hi All,
>>
>> as a workaround I removed "karaf-framework" from the "featuresBoot" in
>> etc/org.apache.karaf.features.cfg and the container runs nicely with no
>> duplicate logging provider.
>>
>> Still curios why "karaf-framework" replicates the entries from
>> etc/startup.properties ?!
>>
>> Best Regards,
>> Michael
>>
>> 2014-11-21 14:50 GMT+01:00 Michael Täschner <m....@gmail.com>:
>>
>>> Hi All,
>>>
>>> after getting pax-logging-logback implementation running in ServiceMix
>>> 5.1.x, based on Karaf 2.3.x, I face issues again in ServiceMix 5.3.0 using
>>> Karaf 2.4.0
>>>
>>> I replaced the pax-logging-service bundle inside etc/startup.properties
>>> (as before) but was surprised to see a pax-logging-service bundle running
>>> in the container. Sifting through features.xml to find the root issue
>>> importing pax-logging-service I found:
>>>
>>> karaf-standard-features: karaf-framework feature declares bundle
>>> pax-logging-service !! I am puzzled: why are these "core" bundles declared
>>> in a feature if they are explicitly started before the feature deployment
>>> through startup.properties ?? Is this duplicate declaration really helpful
>>> ?
>>>
>>> How can I proceed to continue using pax-logging-logback with minimal
>>> changes to the karaf configuration? I already customize startup.properties
>>> as stated before but I am hesitant to override the karaf standard features
>>> xml.
>>>
>>> On a related note: it would be extremely helpful if we had some kind of
>>> reverse search for features, i.e. search feature by bundle (name/symbolic
>>> name) to find where it is declared.
>>>
>>> Thanks and Best Regards,
>>> Michael
>>>
>>
>>
>
>
> --
>
> Apache Member
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>
> Software Architect / Project Manager / Scrum Master
>
>
Re: Karaf 2.4.0 with Pax-Logging-Logback
Posted by Achim Nierbeck <bc...@googlemail.com>.
Well actually it's the other way round.
The never version of Karaf which is build by the karaf-maven-plugin you'll
need a feature to describe the Karaf container,
allas the karaf-framework feature.
On a related note: it would be extremely helpful if we had some kind of
> reverse search for features, i.e. search feature by bundle (name/symbolic
> name) to find where it is declared.
We really, really love contribution :-)
regards, Achim
2014-11-21 15:05 GMT+01:00 Michael Täschner <m....@gmail.com>:
> Hi All,
>
> as a workaround I removed "karaf-framework" from the "featuresBoot" in
> etc/org.apache.karaf.features.cfg and the container runs nicely with no
> duplicate logging provider.
>
> Still curios why "karaf-framework" replicates the entries from
> etc/startup.properties ?!
>
> Best Regards,
> Michael
>
> 2014-11-21 14:50 GMT+01:00 Michael Täschner <m....@gmail.com>:
>
>> Hi All,
>>
>> after getting pax-logging-logback implementation running in ServiceMix
>> 5.1.x, based on Karaf 2.3.x, I face issues again in ServiceMix 5.3.0 using
>> Karaf 2.4.0
>>
>> I replaced the pax-logging-service bundle inside etc/startup.properties
>> (as before) but was surprised to see a pax-logging-service bundle running
>> in the container. Sifting through features.xml to find the root issue
>> importing pax-logging-service I found:
>>
>> karaf-standard-features: karaf-framework feature declares bundle
>> pax-logging-service !! I am puzzled: why are these "core" bundles declared
>> in a feature if they are explicitly started before the feature deployment
>> through startup.properties ?? Is this duplicate declaration really helpful
>> ?
>>
>> How can I proceed to continue using pax-logging-logback with minimal
>> changes to the karaf configuration? I already customize startup.properties
>> as stated before but I am hesitant to override the karaf standard features
>> xml.
>>
>> On a related note: it would be extremely helpful if we had some kind of
>> reverse search for features, i.e. search feature by bundle (name/symbolic
>> name) to find where it is declared.
>>
>> Thanks and Best Regards,
>> Michael
>>
>
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: Karaf 2.4.0 with Pax-Logging-Logback
Posted by Michael Täschner <m....@gmail.com>.
Hi All,
as a workaround I removed "karaf-framework" from the "featuresBoot" in
etc/org.apache.karaf.features.cfg and the container runs nicely with no
duplicate logging provider.
Still curios why "karaf-framework" replicates the entries from
etc/startup.properties ?!
Best Regards,
Michael
2014-11-21 14:50 GMT+01:00 Michael Täschner <m....@gmail.com>:
> Hi All,
>
> after getting pax-logging-logback implementation running in ServiceMix
> 5.1.x, based on Karaf 2.3.x, I face issues again in ServiceMix 5.3.0 using
> Karaf 2.4.0
>
> I replaced the pax-logging-service bundle inside etc/startup.properties
> (as before) but was surprised to see a pax-logging-service bundle running
> in the container. Sifting through features.xml to find the root issue
> importing pax-logging-service I found:
>
> karaf-standard-features: karaf-framework feature declares bundle
> pax-logging-service !! I am puzzled: why are these "core" bundles declared
> in a feature if they are explicitly started before the feature deployment
> through startup.properties ?? Is this duplicate declaration really helpful
> ?
>
> How can I proceed to continue using pax-logging-logback with minimal
> changes to the karaf configuration? I already customize startup.properties
> as stated before but I am hesitant to override the karaf standard features
> xml.
>
> On a related note: it would be extremely helpful if we had some kind of
> reverse search for features, i.e. search feature by bundle (name/symbolic
> name) to find where it is declared.
>
> Thanks and Best Regards,
> Michael
>