ónio
Jacob Costa
http://www.trikorasolutions.com/
http://linkd.in/ajcin
--
View this message in context:
http://camel.465427.n5.nabble.com/Deploying-route-to-Karaf-fails-with-waiting-for-dependencies-tp5662144p5738947.html
Sent from the Camel - Users mailing list archive at Nabble.com.
> What do you mean with fix the route to use http4?
>
> Thank you in advance.
>
>
>
> -
>
> Best
> regards, Cumprimentos, Un saludo, António
> Jacob Costa
>
> http://www.trikorasolutions.com/
>
> http://linkd.in/ajcin
> --
> View this message i
http://www.trikorasolutions.com/
http://linkd.in/ajcin
--
View this message in context:
http://camel.465427.n5.nabble.com/Deploying-route-to-Karaf-fails-with-waiting-for-dependencies-tp5662144p5738938.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Yes, that is it! Installing camel-http instead of camel-http4 solved this
dependency issue.
Thanks Claus, you saved my day.
-borut
Dne 24. april 2012 16:17 je Claus Ibsen napisal/-a:
> OSGi waits for the http component.
>
> You need to use the camel-http feature, and not camel-http4.
> And/or
OSGi waits for the http component.
You need to use the camel-http feature, and not camel-http4.
And/or fix the route to use http4 if thats the one you want.
On Tue, Apr 24, 2012 at 4:13 PM, Borut Bolčina wrote:
> Hello,
>
> Despite my best efforts I can not get my Camel route to run in Karaf.
>
Hi Borut,
I think that some Camel features are missing.
Did you install camel-http feature ?
karaf@root> features:install camel-http
Regards
JB
On 04/24/2012 04:13 PM, Borut Bolčina wrote:
Hello,
Despite my best efforts I can not get my Camel route to run in Karaf.
Log entry where route fa
Hello,
Despite my best efforts I can not get my Camel route to run in Karaf.
Log entry where route fails to start:
2012-04-24 15:51:43,721 | INFO | rint Extender: 3 | BlueprintContainerImpl
| container.BlueprintContainerImpl 321 | 10 -
org.apache.aries.blueprint - 0.3.1 |
Bundle weat
Blueprint is the easiest way. You can simply define a RouteBuilder bean
in the camelcontext and then do the rest in java.
I think though that it makes sense to provide an easy way to start camel
using a simple Activator. So if it is not yet possible we should
do that for one of the next releases
But I did install the Camel feature, but it does not contain camel-core-osgi!
So the only way to kickstart Camel in Karaf is by using blueprint? I do not
want Spring or any XML configuration files, well blueprint seems inevitable.
Regards,
Borut
Sent from my iPad
On 13. apr. 2012, at 16:55, Cl
Hi
I suggest to install the camel feature, and not camel-core. By install
camel feature, you get Camel support for Spring-DM and Blueprint.
Then you should be able to install and start your bundle out of the box.
If you use another Camel component such as FTP, Velocity etc. Then you
need to insta
I have added/modified some dependencies in my bundle to:
org.osgi
org.osgi.core
4.2.0
org.osgi
org.osgi.compendium
4.2.0
This last one has a package which was reported missing in the Karaf console.
and the build section in pom looks like:
org.apache.felix
maven-bundle-plugin
2.3.7
I tried
karaf@root> osgi:install mvn:org.apache.camel/camel-core-osgi/2.9.1
Bundle ID: 91
and then I get error by starting
karaf@root> osgi:start 91
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.camel.camel-core-osgi [91]: Unable to resolve 91.0:
missing require
inal Message-
> From: Borut Bolčina
> Date: Fri, 13 Apr 2012 12:33:26
> To:
> Reply-To:
> Subject: Re: Deploying route to Karaf
>
> OK, I installed the latest Karaf (2.2.6) and Camel features with
>
> features:chooseurl camel 2.9.1
>
>
> features:instal
As far as I know the camel.core.osgi package is not exported. In fact
the osgi stuff in camel core looks quite strange as it works with
fragment bundles where it could be much simpler.
So I am not sure if this will work.
You can try require bundle instead of import package so you might get
the
, 13 Apr 2012 12:33:26
To:
Reply-To:
Subject: Re: Deploying route to Karaf
OK, I installed the latest Karaf (2.2.6) and Camel features with
features:chooseurl camel 2.9.1
features:install camel-core
Then I installed my bundle into the local maven repo and then to Karaf with
karaf@root
OK, I installed the latest Karaf (2.2.6) and Camel features with
features:chooseurl camel 2.9.1
features:install camel-core
Then I installed my bundle into the local maven repo and then to Karaf with
karaf@root> osgi:install
mvn:com.mycompany/route-weather-current/1.0-SNAPSHOT
Bundle ID: 67
> The blueprint.xml file is then placed in the META-INF/blueprint
> directory. The standard place for that.
Ah sorry I think its OSGI-INF/blueprint/blueprint.xml
The name of the XML file dont have to be blueprint.xml. I think you
can name it myapp.xml, camel.xml, etc. Or what you like.
Anyway th
On Wed, Apr 11, 2012 at 10:24 AM, Borut Bolčina wrote:
> Dne 11. april 2012 09:54 je Claus Ibsen napisal/-a:
>
>> On Wed, Apr 11, 2012 at 9:43 AM, Borut Bolčina
>> wrote:
>> > Thanks for the answers and guidelines Claus.
>> >
>> > I looked into the ServiceMix, but the project seems so abandoned,
Dne 11. april 2012 09:54 je Claus Ibsen napisal/-a:
> On Wed, Apr 11, 2012 at 9:43 AM, Borut Bolčina
> wrote:
> > Thanks for the answers and guidelines Claus.
> >
> > I looked into the ServiceMix, but the project seems so abandoned, I
> decided
> > not to use it. I read some discussions on the u
On Wed, Apr 11, 2012 at 9:43 AM, Borut Bolčina wrote:
> Thanks for the answers and guidelines Claus.
>
> I looked into the ServiceMix, but the project seems so abandoned, I decided
> not to use it. I read some discussions on the user and dev lists which gave
> the impression that ServiceMix has no
Thanks for the answers and guidelines Claus.
I looked into the ServiceMix, but the project seems so abandoned, I decided
not to use it. I read some discussions on the user and dev lists which gave
the impression that ServiceMix has no certain future. Plus, you are bound
to use older versions of Ka
On Wed, Apr 11, 2012 at 8:32 AM, Borut Bolčina wrote:
> So instead of
>
>
> org.apache.camel
> camel-core
> ${camel-version}
>
>
> I use camel-core-osgi and use the OsgiDefaultCamelContext instead and I
> should be safe?
>
> public void start(BundleContext context) throws Exception {
> camel
So instead of
org.apache.camel
camel-core
${camel-version}
I use camel-core-osgi and use the OsgiDefaultCamelContext instead and I
should be safe?
public void start(BundleContext context) throws Exception {
camelContext = new OsgiDefaultCamelContext(context);
...
}
Will this enable me to
Hi
Yeah that is how this can be done with OSGi APIs.
You may want to use the camel-core-osgi JAR and use the
OsgiDefaultCamelContext as the CamelContext instance.
That one knows about the OSGi runtime. Otherwise you may run in trouble.
On Tue, Apr 10, 2012 at 3:02 PM, Borut Bolčina wrote:
> He
Hello,
I was wondering if I am going down the right path. My goal is to deploy a
simple Camel route to an OSGI container, but without the Spring "startup
code".
The route:
public class WeatherCurrentRouteBuilder extends RouteBuilder {
public void configure() {
...
}
}
and to start and stop the
25 matches
Mail list logo
