Seems like I have to put that blueprint.xml in the resources folder. It
worked!
Regards,
Jothi
On Tue, Feb 26, 2013 at 4:47 PM, Joe San <codeintheo...@gmail.com> wrote:
> Good. the upgrade landed me in an another error as below:
>
> java.io.FileNotFoundException: Cannot find resource in classpath for URI:
> blueprint.xml
>
> @Override
> protected String getBlueprintDescriptor() {
> return "blueprint.xml";
> }
>
> the blueprint.xml is in the same location where my blueprint test class is
> located.
>
> Regards,
> Jothi
>
>
> On Tue, Feb 26, 2013 at 4:03 PM, Claus Ibsen <claus.ib...@gmail.com>wrote:
>
>> I suggest to upgrade to a newer 2.10.x release, as we have fixed osgi
>> stuff since.
>>
>>
>> On Tue, Feb 26, 2013 at 3:45 PM, Joe San <codeintheo...@gmail.com> wrote:
>> > Is there anything that I have to set so that I could use the
>> > camel-blueprint-test support? When I tried running my camelContext
>> > configured in the blueprint.xml, I get the following error:
>> >
>> > I'm using 2.10.0 versions of the camel-xxx libraries.
>> >
>> > java.lang.NoClassDefFoundError: org.osgi.vendor.framework property not
>> set
>> > at
>> > org.osgi.framework.FrameworkUtil$ImplHolder.run(FrameworkUtil.java:69)
>> > at java.security.AccessController.doPrivileged(Native Method)
>> > at
>> >
>> org.osgi.framework.FrameworkUtil$ImplHolder.<clinit>(FrameworkUtil.java:59)
>> > at
>> org.osgi.framework.FrameworkUtil.createFilter(FrameworkUtil.java:127)
>> > at
>> >
>> de.kalpatec.pojosr.framework.launch.ClasspathScanner.scanForBundles(ClasspathScanner.java:44)
>> > at
>> >
>> org.apache.camel.test.blueprint.CamelBlueprintHelper.getBundleDescriptors(CamelBlueprintHelper.java:222)
>> > at
>> >
>> org.apache.camel.test.blueprint.CamelBlueprintHelper.createBundleContext(CamelBlueprintHelper.java:90)
>> > at
>> >
>> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:41)
>> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>> > at
>> >
>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>> > at
>> >
>> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>> > at
>> >
>> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>> > at
>> >
>> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
>> > at
>> >
>> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
>> > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:47)
>> > at org.junit.rules.RunRules.evaluate(RunRules.java:18)
>> > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
>> > at
>> >
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
>> > at
>> >
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
>> > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
>> > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
>> > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
>> > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
>> > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
>> > at
>> >
>> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
>> > at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
>> > at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
>> > at
>> >
>> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:76)
>> > at
>> >
>> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:195)
>> > at
>> > com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:63)
>> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>> > at
>> com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
>> >
>> > Regards,
>> > Jothi
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cib...@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>
>
