It seems to be the issue discussed at
http://fernandoribeiro.eti.br/2011/01/10/issues-with-routes-in-progress-fuse-4-2/.
Let me know if it the case. Thanks.
On Wed, Mar 30, 2011 at 6:31 PM, Donald Whytock wrote:
> Okay...I bundled camel-core-osgi separately, created a bundle that
> instantiates
Okay...I bundled camel-core-osgi separately, created a bundle that
instantiates OsgiDefaultCamelContext on activation then registers
ContextUtil as a service to provide the instance as a singleton, and
created another bundle called Sender that uses a ServiceTracker to
wait until ContextUtil is regi
I'd think it doesn't get any easier than having both bundles depending on
the third, isn't it? Thanks.
On Tue, Mar 29, 2011 at 4:11 PM, Claus Ibsen wrote:
> On Tuesday, March 29, 2011, Fernando Ribeiro
> wrote:
> > Out of curiosity, did I get it right that the code is going to continue
> in
> >
On Tuesday, March 29, 2011, Fernando Ribeiro
wrote:
> Out of curiosity, did I get it right that the code is going to continue in
> the camel-spring and camel-blueprint even when the camel-core-osgi is there?
> If so, why? Thanks.
>
This allow us to easily have common osgi code to share for spring
Out of curiosity, did I get it right that the code is going to continue in
the camel-spring and camel-blueprint even when the camel-core-osgi is there?
If so, why? Thanks.
On Tue, Mar 29, 2011 at 2:52 AM, Willem Jiang wrote:
> It's harmless to provide the bundle of camel-core-osgi in camel.
> I j
It's harmless to provide the bundle of camel-core-osgi in camel.
I just created a JIRA[1] of it, we will provide a bundle of
camel-core-osgi in Camel 2.8.0.
[1]https://issues.apache.org/jira/browse/CAMEL-3814
Willem
On 3/29/11 1:17 PM, Donald Whytock wrote:
Thanks, I'll try that.
Shall I as
Thanks, I'll try that.
Shall I assume this is going to be the standard architecture? As in,
if/when there's a 2.8, I should expect to need to re-bundle
camel-core-osgi again?
Don
On Mon, Mar 28, 2011 at 11:10 PM, Willem Jiang wrote:
> As we shipped the camel-spring and camel-blueprint at the s
As we shipped the camel-spring and camel-blueprint at the same time, so
the org.apache.camel.core.osgi is not exported as public class.
The reason that we don't create another bundle of camel-core-osgi, is
camel-spring bundle detect OSGi and no-OSGi environment rightly. Which
means we could let
You can create a customer bundle which use bnd to add the
camel-core-osgi into your bundle, then you can create a
OsgiDefaultCamelContext yourself without any help of Spring or Blueprint.
Willem
On 3/26/11 3:05 AM, Scott England-Sullivan wrote:
If a project doesn't use Spring or Blueprint how
Okay...added camel-blueprint-2.7.0.jar, which required
org.apache.aries.blueprint-0.3.jar, which required
org.apache.aries.proxy-0.3.jar, which required
org.apache.aries.util-0.3.jar, asm-3.3.1.jar and
org.apache.felix.configadmin-1.0.4.jar.
Tried creating an OsgiDefaultCamelContext, which worked
If a project doesn't use Spring or Blueprint how do you create a CamelContext
in an OSGi container programmatically?
Thanks,
Scott
Scott England-Sullivan
C. (217) 390-3058
H. (952) 440-4568
Sent from my iPhone
On Mar 25, 2011, at 1:05 PM, Claus Ibsen wrote:
> On Fri, Mar 25, 2011 at 3:52 PM
On Fri, Mar 25, 2011 at 3:52 PM, Donald Whytock wrote:
> Okay. Where is the OSGi version? Is that in a different jar?
>
Yes
camel-spring if using spring-dm
camel-blueprint if using blueprint
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.co
Okay. Where is the OSGi version? Is that in a different jar?
On Fri, Mar 25, 2011 at 8:45 AM, Claus Ibsen wrote:
> Yeah you need to use the Osgi version of CamelContext.
>
> But generally is much much easier to just use Apache Karaf (or
> ServiceMix) and features to use Camel with OSGi.
>
>
> O
Yeah you need to use the Osgi version of CamelContext.
But generally is much much easier to just use Apache Karaf (or
ServiceMix) and features to use Camel with OSGi.
On Fri, Mar 25, 2011 at 1:01 PM, Donald Whytock wrote:
> Is this a recent change? I was able to use it with
> camel-core-2.4.0.
Is this a recent change? I was able to use it with
camel-core-2.4.0.jar. This stacktrace is a result of changing to
camel-core-2.6.0.jar.
The code is:
import org.apache.camel.impl.DefaultCamelContext;
public class ContextUtil
{
static org.apache.camel.CamelContext context = null;
static
Hi
How did you start the DefaultCamelContext ?
You can not use it directly in OSGi, you may consider to use
CamelContextFactory instead.
Willem
On 3/25/11 5:59 AM, Donald Whytock wrote:
Running Camel in an OSGi environment under Felix, with
camel-core-2.6.0.jar as a bundle. I'm getting a st
Tried with camel-core-2.7.0.jar and got the same error.
On Thu, Mar 24, 2011 at 5:59 PM, Donald Whytock wrote:
> Running Camel in an OSGi environment under Felix, with
> camel-core-2.6.0.jar as a bundle. I'm getting a stacktrace when I try
> to call start() on the DefaultCamelContext singleton I
17 matches
Mail list logo
