Yeah, as soon as I'd rebuild the test suite piece by piece it became very
clear what the culprit was going to be.

I wasn't complaining about anything specifically, there just seems to be a
lot of "unspecific" errors in OSGI land that us newbies have to contend
with, but I suspect a lot are caused by side effects of the dynamic nature
of OSGI so there is probably not a great deal that can be done.

Thanks for the help Achim.

Tom

On Tue, Dec 15, 2015 at 7:23 AM, Achim Nierbeck <[email protected]>
wrote:

> sorry to hear you had a hard time,
> but I think with Pax-Exam we have some sort of conflicting bundle in use
> concerning Inject.
> Actually it's more like Karaf is using the conflicting one, as the
> official API bundle is already OSGi aware we shouldn't be in need of the
> servicemix one anymore.
> In that case the dependency=true flag on features helps a lot too :-)
>
> regards, Achim
>
>
> 2015-12-15 0:48 GMT+01:00 Tom Barber <[email protected]>:
>
>> Transpires I was pulling in javax.inject which it was taking a deep
>> disliking to.
>>
>> You live and learn. My one bug bear with OSGI is the amount of completely
>> random or unrelated error messages that make debugging harder than it could
>> be.
>>
>> Anyway, mystery solved.
>>
>> Thanks
>>
>> Tom
>>
>> On Mon, Dec 14, 2015 at 8:40 PM, Tom Barber <[email protected]>
>> wrote:
>>
>>> Hmm I don't think that works because the error occurs when trying to
>>> bootstrap Cellar not during the PAX Exam test.
>>>
>>>
>>> https://github.com/OSBI/meteorite-core/blob/master/meteorite-core-itests/src/test/java/bi/meteorite/core/security/TestSecurity.java#L146
>>>
>>> I did attempt to block it up but the error already exists in the logs at
>>> this point.
>>>
>>> Weird how it works in manual mode.
>>>
>>> Tom
>>>
>>> On Mon, Dec 14, 2015 at 7:29 PM, Tom Barber <[email protected]>
>>> wrote:
>>>
>>>> Thanks Achim I thought I shipped most of them I'll double check.
>>>>
>>>> Tom
>>>>
>>>> On Mon, Dec 14, 2015 at 7:17 PM, Achim Nierbeck <
>>>> [email protected]> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> just recently I discovered that a custom distribution just using
>>>>> featuresBoot is lacking certain libs, which a std.
>>>>> Karaf distribution contains. [1]
>>>>> Does your custom Distribution also contain those libraries?
>>>>>
>>>>> After that you should have a distribution comparable to a manual
>>>>> installed Karaf.
>>>>>
>>>>> Regarding the ConfigurationAdmin Service, you'll might run into some
>>>>> sort of race-condition.
>>>>> In that case make sure your test also injects the Configuration Admin
>>>>> Service and waits for it to show up.
>>>>>
>>>>> [1] -
>>>>> https://github.com/apache/karaf/blob/master/assemblies/apache-karaf/pom.xml#L157-L201
>>>>>
>>>>> 2015-12-14 15:19 GMT+01:00 Tom Barber <[email protected]>:
>>>>>
>>>>>> Hello folks
>>>>>>
>>>>>> I have a custom distro and as boot features I have:
>>>>>>
>>>>>> featuresBoot=aries-blueprint, bundle, cellar, config, cxf, deployer,
>>>>>> diagnostic, feature, http-whiteboard, instance, jaas, kar, log, 
>>>>>> management,
>>>>>> package, service, shell, spring, spring-web, ssh, system,
>>>>>> wrap,exam,test-dependencies
>>>>>>
>>>>>> But when I run it in PAX Exam Cellar seems to get upset and complains
>>>>>> about:
>>>>>>
>>>>>> java.lang.IllegalStateException: Configuration Admin service has been
>>>>>> unregistered
>>>>>> at
>>>>>> org.apache.felix.cm.impl.ConfigurationAdminImpl.getConfigurationManager(ConfigurationAdminImpl.java:301)[3:org.apache.felix.configadmin:1.8.8]
>>>>>> at
>>>>>> org.apache.felix.cm.impl.ConfigurationAdminImpl.getConfiguration(ConfigurationAdminImpl.java:152)[3:org.apache.felix.configadmin:1.8.8]
>>>>>> at
>>>>>> org.apache.karaf.cellar.hazelcast.HazelcastGroupManager.init(HazelcastGroupManager.java:72)[89:org.apache.karaf.cellar.hazelcast:4.0.0
>>>>>>
>>>>>> Anyone got any good ideas as to how to bootstrap Cellar.
>>>>>>
>>>>>> I looked at the Cellar ITests but they use a "manual" installation of
>>>>>> Cellar not a boot time spin up.
>>>>>>
>>>>>> I also started the PAX Exam test instance and all the bundles seemed
>>>>>> to be installed and running normally when I start it from ./bin/karaf.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Tom
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> 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
>
>

Reply via email to