You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Jean-Pierre Bergamin <ja...@ractive.ch> on 2011/04/18 21:21:27 UTC
Camel as an OSGi bundle in virgo
Hello everyone
We are trying to get camel running as an OSGI bundle in Virgo - more or
less successfully. Our first attempt was to simply add camel-core and
camel-spring as dependencies (version 2.7.1) to the pom.xml of our osgi
web application
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-core</artifactId>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-spring</artifactId>
</dependency>
We put camel-core-2.7.1.jar and camel-spring-2.7.1.jar in Virgo's
repository/usr folder.
When starting the web bundle, we get the following error:
[2011-04-18 20:29:18.246] TCP Connection(2)-127.0.0.1 <DE0002E>
Installation of bundle 'com.example.ui.web' version '0.0.1.SNAPSHOT'
failed.
org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException:
Unable to satisfy dependencies of bundle 'com.example.ui.web' at version
'0.0.1.SNAPSHOT': Cannot resolve: com.example.ui.web
Resolver report:
An Import-Package could not be resolved. Caused by missing
constraint in bundle <com.example.ui.web_0.0.1.SNAPSHOT>
constraint: <Import-Package: org.apache.camel.model;
version="0.0.0">
An Import-Package could not be resolved. Caused by missing
constraint in bundle <org.apache.camel.camel-spring_2.7.1>
constraint: <Import-Package: org.apache.camel;
version="[2.7.1,2.7.2)">
An Import-Package could not be resolved. Caused by missing
constraint in bundle <org.apache.camel.camel-core_2.7.1>
constraint: <Import-Package:
org.fusesource.commons.management; version="[1.0.0,2.0.0)">
at
org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:45)
....
With a lot of experimenting, we managed to get the dependency to
org.fusesource.commons.management resolved by adding the dependency:
<dependency>
<groupId>org.fusesource.commonman</groupId>
<artifactId>commons-management</artifactId>
</dependency>
This jar is found in the repository http://repo.fusesource.com/maven2/.
Question: Why is there a dependency to
org.fusesource.commons.management? Should this dependency maybe optional?
The next problem was that the CamelNamespaceHandler class could not be
found in the webapp:
[2011-04-18 20:44:10.835] start-signalling-5
org.springframework.web.context.ContextLoader
Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: Unexpe
cted exception parsing XML document from ServletContext resource
[/WEB-INF/spring/camel-context.xml]; nested exception is
org.springframework.beans.FatalBeanException: NamespaceHandler class
[org.apache.camel.spring.handl
er.CamelNamespaceHandler] for namespace
[http://camel.apache.org/schema/spring] not found; nested exception is
java.lang.ClassNotFoundException:
org.apache.camel.spring.handler.CamelNamespaceHandler not found from bundle
[com.example.ui.web]
The bundle camel-spring does not get loaded, although it is put in the
repository/usr directory of Virgo. We tried to manually add a dependency
to the web bundle, by adding:
Import-Bundle:
org.apache.camel.camel-spring;version="[2.7.0,2.8.0)",
...
This gives import constraints on org.apache.camel.language:
[2011-04-18 20:50:14.405] TCP Connection(2)-127.0.0.1 <DE0002E>
Installation of bundle 'com.example.ui.web' version '0.0.1.SNAPSHOT'
failed.
org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException:
Unable to satisfy dependencies of bundle 'com.example.ui.web' at version
'0.0.1.SNAPSHOT': Cannot resolve: com.example.ui.web
Resolver report:
An Import-Package could not be resolved. Caused by missing
constraint in bundle <com.example.ui.web_0.0.1.SNAPSHOT>
constraint: <Import-Package: org.apache.camel.language;
version="0.0.0"> constrained to bundle <org.apache.camel.camel-spring>
constrained bundle version range "[2.7.1,2.7.1]"
at
org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:45)
Question: Does the core-spring bundle really need to import
org.apache.camel.language? It contains the package
org.apache.camel.language with just the SpEL.class itself.
We tried to import also the camel-core bundle to provide the
org.apache.camel.language:
Import-Bundle:
org.apache.camel.camel-core;version="[2.7.0,2.8.0)",
org.apache.camel.camel-spring;version="[2.7.0,2.8.0)",
...
Then we got merge errors:
[2011-04-18 20:54:40.715] TCP Connection(2)-127.0.0.1 <DE0002E>
Installation of bundle 'com.example.ui.web' version '0.0.1.SNAPSHOT'
failed. org.eclipse.virgo.kernel.deployer.core.DeploymentException:
Error merging expanded imports for [bundle 'com.example.ui.web' version
'0.0.1.SNAPSHOT' in scope 'null']
at
org.eclipse.virgo.kernel.deployer.core.internal.ImportExpandingTransformer.expandImports(ImportExpandingTransformer.java:112)
...
Caused by: org.eclipse.virgo.kernel.osgi.framework.ImportMergeException:
cannot merge imports of package 'org.apache.camel.language' from sources
'Import-Library 'org.springframework.spring' version
'3.0.5.RELEASE'(null), Import-Bundle 'org.apache.camel.camel-core'
version '2.7.1', Import-Bundle 'org.apache.camel.camel-spring' version
'2.7.1'' because of conflicting values 'org.apache.camel.camel-spring',
'org.apache.camel.camel-core' of attribute 'bundle-symbolic-name'
at
org.eclipse.virgo.kernel.userregion.internal.importexpansion.AbstractTrackedPackageImports.mergeAttributes(AbstractTrackedPackageImports.java:144)
at
org.eclipse.virgo.kernel.userregion.internal.importexpansion.AbstractTrackedPackageImports.mergePackageImport(AbstractTrackedPackageImports.java:119)
...
Is there a way around this?
Finally what made it somehow working was to remove the Import-Bundle
entries and add an Import-Package to the org.apache.camel.spring package
like:
Import-Package:
org.apache.camel.spring;version="[2.7.0,2.8.0)"
...
But now we get "java.lang.ClassNotFoundException:
org.apache.camel.spring.handler.CamelNamespaceHandler" error when
redeploying the web bundle, which is very unconvenient. Funny enough
after redeploying 3 times, the web bundle starts again.
In short:
* Why is there a dependency to org.fusesource.commons.management in
camel-core? Should this dependency maybe optional?
* Does the core-spring bundle really need to import
org.apache.camel.language? The bundle already contains this package with
SpEL.class in it.
* Any ideas why the web bundle does not see the class
CamelNamespaceHandler any more after redeployment? Could this be a bug
in Virgo?
Best regards,
Jean-Pierre Bergamin
Re: Camel as an OSGi bundle in virgo
Posted by Jean-Pierre Bergamin <ja...@ractive.ch>.
Thanks for your answer
I was unsure because the we use maven assembly to collect all
dependencies, but commons-management came not up as a transitive
dependency of camel-core. So we had to manually add it as a dependency
to our project. And I never saw this maven dependency added explicitely
in any example. But anyway.
Best regards,
James
Am 19.04.2011 09:48, schrieb Claus Ibsen:
> Read this FAQ about which JARs
> http://camel.apache.org/what-jars-do-i-need.html
>
>
> On Mon, Apr 18, 2011 at 9:21 PM, Jean-Pierre Bergamin<ja...@ractive.ch> wrote:
>> Hello everyone
>>
>> We are trying to get camel running as an OSGI bundle in Virgo - more or less
>> successfully. Our first attempt was to simply add camel-core and
>> camel-spring as dependencies (version 2.7.1) to the pom.xml of our osgi web
>> application
>> <dependency>
>> <groupId>org.apache.camel</groupId>
>> <artifactId>camel-core</artifactId>
>> </dependency>
>> <dependency>
>> <groupId>org.apache.camel</groupId>
>> <artifactId>camel-spring</artifactId>
>> </dependency>
>>
>> We put camel-core-2.7.1.jar and camel-spring-2.7.1.jar in Virgo's
>> repository/usr folder.
>>
>> When starting the web bundle, we get the following error:
>>
>> [2011-04-18 20:29:18.246] TCP Connection(2)-127.0.0.1<DE0002E>
>> Installation of bundle 'com.example.ui.web' version '0.0.1.SNAPSHOT' failed.
>> org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException:
>> Unable to satisfy dependencies of bundle 'com.example.ui.web' at version
>> '0.0.1.SNAPSHOT': Cannot resolve: com.example.ui.web
>> Resolver report:
>> An Import-Package could not be resolved. Caused by missing constraint
>> in bundle<com.example.ui.web_0.0.1.SNAPSHOT>
>> constraint:<Import-Package: org.apache.camel.model;
>> version="0.0.0">
>> An Import-Package could not be resolved. Caused by missing constraint
>> in bundle<org.apache.camel.camel-spring_2.7.1>
>> constraint:<Import-Package: org.apache.camel;
>> version="[2.7.1,2.7.2)">
>> An Import-Package could not be resolved. Caused by missing constraint
>> in bundle<org.apache.camel.camel-core_2.7.1>
>> constraint:<Import-Package: org.fusesource.commons.management;
>> version="[1.0.0,2.0.0)">
>>
>> at
>> org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:45)
>> ....
>>
>> With a lot of experimenting, we managed to get the dependency to
>> org.fusesource.commons.management resolved by adding the dependency:
>> <dependency>
>> <groupId>org.fusesource.commonman</groupId>
>> <artifactId>commons-management</artifactId>
>> </dependency>
>> This jar is found in the repository http://repo.fusesource.com/maven2/.
>>
>> Question: Why is there a dependency to org.fusesource.commons.management?
>> Should this dependency maybe optional?
>>
>>
>> The next problem was that the CamelNamespaceHandler class could not be found
>> in the webapp:
>>
>> [2011-04-18 20:44:10.835] start-signalling-5
>> org.springframework.web.context.ContextLoader Context
>> initialization failed
>> org.springframework.beans.factory.BeanDefinitionStoreException: Unexpe
>> cted exception parsing XML document from ServletContext resource
>> [/WEB-INF/spring/camel-context.xml]; nested exception is
>> org.springframework.beans.FatalBeanException: NamespaceHandler class
>> [org.apache.camel.spring.handl
>> er.CamelNamespaceHandler] for namespace
>> [http://camel.apache.org/schema/spring] not found; nested exception is
>> java.lang.ClassNotFoundException:
>> org.apache.camel.spring.handler.CamelNamespaceHandler not found from bundle
>> [com.example.ui.web]
>>
>>
>> The bundle camel-spring does not get loaded, although it is put in the
>> repository/usr directory of Virgo. We tried to manually add a dependency to
>> the web bundle, by adding:
>>
>> Import-Bundle:
>> org.apache.camel.camel-spring;version="[2.7.0,2.8.0)",
>> ...
>>
>> This gives import constraints on org.apache.camel.language:
>>
>> [2011-04-18 20:50:14.405] TCP Connection(2)-127.0.0.1<DE0002E>
>> Installation of bundle 'com.example.ui.web' version '0.0.1.SNAPSHOT' failed.
>> org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException:
>> Unable to satisfy dependencies of bundle 'com.example.ui.web' at version
>> '0.0.1.SNAPSHOT': Cannot resolve: com.example.ui.web
>> Resolver report:
>> An Import-Package could not be resolved. Caused by missing constraint
>> in bundle<com.example.ui.web_0.0.1.SNAPSHOT>
>> constraint:<Import-Package: org.apache.camel.language;
>> version="0.0.0"> constrained to bundle<org.apache.camel.camel-spring>
>> constrained bundle version range "[2.7.1,2.7.1]"
>>
>> at
>> org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:45)
>>
>>
>> Question: Does the core-spring bundle really need to import
>> org.apache.camel.language? It contains the package org.apache.camel.language
>> with just the SpEL.class itself.
>>
>>
>> We tried to import also the camel-core bundle to provide the
>> org.apache.camel.language:
>>
>> Import-Bundle:
>> org.apache.camel.camel-core;version="[2.7.0,2.8.0)",
>> org.apache.camel.camel-spring;version="[2.7.0,2.8.0)",
>> ...
>>
>> Then we got merge errors:
>>
>> [2011-04-18 20:54:40.715] TCP Connection(2)-127.0.0.1<DE0002E>
>> Installation of bundle 'com.example.ui.web' version '0.0.1.SNAPSHOT' failed.
>> org.eclipse.virgo.kernel.deployer.core.DeploymentException: Error merging
>> expanded imports for [bundle 'com.example.ui.web' version '0.0.1.SNAPSHOT'
>> in scope 'null']
>> at
>> org.eclipse.virgo.kernel.deployer.core.internal.ImportExpandingTransformer.expandImports(ImportExpandingTransformer.java:112)
>> ...
>> Caused by: org.eclipse.virgo.kernel.osgi.framework.ImportMergeException:
>> cannot merge imports of package 'org.apache.camel.language' from sources
>> 'Import-Library 'org.springframework.spring' version '3.0.5.RELEASE'(null),
>> Import-Bundle 'org.apache.camel.camel-core' version '2.7.1', Import-Bundle
>> 'org.apache.camel.camel-spring' version '2.7.1'' because of conflicting
>> values 'org.apache.camel.camel-spring', 'org.apache.camel.camel-core' of
>> attribute 'bundle-symbolic-name'
>> at
>> org.eclipse.virgo.kernel.userregion.internal.importexpansion.AbstractTrackedPackageImports.mergeAttributes(AbstractTrackedPackageImports.java:144)
>> at
>> org.eclipse.virgo.kernel.userregion.internal.importexpansion.AbstractTrackedPackageImports.mergePackageImport(AbstractTrackedPackageImports.java:119)
>> ...
>>
>> Is there a way around this?
>>
>>
>> Finally what made it somehow working was to remove the Import-Bundle entries
>> and add an Import-Package to the org.apache.camel.spring package like:
>>
>> Import-Package:
>> org.apache.camel.spring;version="[2.7.0,2.8.0)"
>> ...
>>
>> But now we get "java.lang.ClassNotFoundException:
>> org.apache.camel.spring.handler.CamelNamespaceHandler" error when
>> redeploying the web bundle, which is very unconvenient. Funny enough after
>> redeploying 3 times, the web bundle starts again.
>>
>>
>> In short:
>> * Why is there a dependency to org.fusesource.commons.management in
>> camel-core? Should this dependency maybe optional?
>> * Does the core-spring bundle really need to import
>> org.apache.camel.language? The bundle already contains this package with
>> SpEL.class in it.
>> * Any ideas why the web bundle does not see the class CamelNamespaceHandler
>> any more after redeployment? Could this be a bug in Virgo?
>>
>>
>> Best regards,
>> Jean-Pierre Bergamin
>>
>
>
Re: Camel as an OSGi bundle in virgo
Posted by Claus Ibsen <cl...@gmail.com>.
Read this FAQ about which JARs
http://camel.apache.org/what-jars-do-i-need.html
On Mon, Apr 18, 2011 at 9:21 PM, Jean-Pierre Bergamin <ja...@ractive.ch> wrote:
> Hello everyone
>
> We are trying to get camel running as an OSGI bundle in Virgo - more or less
> successfully. Our first attempt was to simply add camel-core and
> camel-spring as dependencies (version 2.7.1) to the pom.xml of our osgi web
> application
> <dependency>
> <groupId>org.apache.camel</groupId>
> <artifactId>camel-core</artifactId>
> </dependency>
> <dependency>
> <groupId>org.apache.camel</groupId>
> <artifactId>camel-spring</artifactId>
> </dependency>
>
> We put camel-core-2.7.1.jar and camel-spring-2.7.1.jar in Virgo's
> repository/usr folder.
>
> When starting the web bundle, we get the following error:
>
> [2011-04-18 20:29:18.246] TCP Connection(2)-127.0.0.1 <DE0002E>
> Installation of bundle 'com.example.ui.web' version '0.0.1.SNAPSHOT' failed.
> org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException:
> Unable to satisfy dependencies of bundle 'com.example.ui.web' at version
> '0.0.1.SNAPSHOT': Cannot resolve: com.example.ui.web
> Resolver report:
> An Import-Package could not be resolved. Caused by missing constraint
> in bundle <com.example.ui.web_0.0.1.SNAPSHOT>
> constraint: <Import-Package: org.apache.camel.model;
> version="0.0.0">
> An Import-Package could not be resolved. Caused by missing constraint
> in bundle <org.apache.camel.camel-spring_2.7.1>
> constraint: <Import-Package: org.apache.camel;
> version="[2.7.1,2.7.2)">
> An Import-Package could not be resolved. Caused by missing constraint
> in bundle <org.apache.camel.camel-core_2.7.1>
> constraint: <Import-Package: org.fusesource.commons.management;
> version="[1.0.0,2.0.0)">
>
> at
> org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:45)
> ....
>
> With a lot of experimenting, we managed to get the dependency to
> org.fusesource.commons.management resolved by adding the dependency:
> <dependency>
> <groupId>org.fusesource.commonman</groupId>
> <artifactId>commons-management</artifactId>
> </dependency>
> This jar is found in the repository http://repo.fusesource.com/maven2/.
>
> Question: Why is there a dependency to org.fusesource.commons.management?
> Should this dependency maybe optional?
>
>
> The next problem was that the CamelNamespaceHandler class could not be found
> in the webapp:
>
> [2011-04-18 20:44:10.835] start-signalling-5
> org.springframework.web.context.ContextLoader Context
> initialization failed
> org.springframework.beans.factory.BeanDefinitionStoreException: Unexpe
> cted exception parsing XML document from ServletContext resource
> [/WEB-INF/spring/camel-context.xml]; nested exception is
> org.springframework.beans.FatalBeanException: NamespaceHandler class
> [org.apache.camel.spring.handl
> er.CamelNamespaceHandler] for namespace
> [http://camel.apache.org/schema/spring] not found; nested exception is
> java.lang.ClassNotFoundException:
> org.apache.camel.spring.handler.CamelNamespaceHandler not found from bundle
> [com.example.ui.web]
>
>
> The bundle camel-spring does not get loaded, although it is put in the
> repository/usr directory of Virgo. We tried to manually add a dependency to
> the web bundle, by adding:
>
> Import-Bundle:
> org.apache.camel.camel-spring;version="[2.7.0,2.8.0)",
> ...
>
> This gives import constraints on org.apache.camel.language:
>
> [2011-04-18 20:50:14.405] TCP Connection(2)-127.0.0.1 <DE0002E>
> Installation of bundle 'com.example.ui.web' version '0.0.1.SNAPSHOT' failed.
> org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException:
> Unable to satisfy dependencies of bundle 'com.example.ui.web' at version
> '0.0.1.SNAPSHOT': Cannot resolve: com.example.ui.web
> Resolver report:
> An Import-Package could not be resolved. Caused by missing constraint
> in bundle <com.example.ui.web_0.0.1.SNAPSHOT>
> constraint: <Import-Package: org.apache.camel.language;
> version="0.0.0"> constrained to bundle <org.apache.camel.camel-spring>
> constrained bundle version range "[2.7.1,2.7.1]"
>
> at
> org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:45)
>
>
> Question: Does the core-spring bundle really need to import
> org.apache.camel.language? It contains the package org.apache.camel.language
> with just the SpEL.class itself.
>
>
> We tried to import also the camel-core bundle to provide the
> org.apache.camel.language:
>
> Import-Bundle:
> org.apache.camel.camel-core;version="[2.7.0,2.8.0)",
> org.apache.camel.camel-spring;version="[2.7.0,2.8.0)",
> ...
>
> Then we got merge errors:
>
> [2011-04-18 20:54:40.715] TCP Connection(2)-127.0.0.1 <DE0002E>
> Installation of bundle 'com.example.ui.web' version '0.0.1.SNAPSHOT' failed.
> org.eclipse.virgo.kernel.deployer.core.DeploymentException: Error merging
> expanded imports for [bundle 'com.example.ui.web' version '0.0.1.SNAPSHOT'
> in scope 'null']
> at
> org.eclipse.virgo.kernel.deployer.core.internal.ImportExpandingTransformer.expandImports(ImportExpandingTransformer.java:112)
> ...
> Caused by: org.eclipse.virgo.kernel.osgi.framework.ImportMergeException:
> cannot merge imports of package 'org.apache.camel.language' from sources
> 'Import-Library 'org.springframework.spring' version '3.0.5.RELEASE'(null),
> Import-Bundle 'org.apache.camel.camel-core' version '2.7.1', Import-Bundle
> 'org.apache.camel.camel-spring' version '2.7.1'' because of conflicting
> values 'org.apache.camel.camel-spring', 'org.apache.camel.camel-core' of
> attribute 'bundle-symbolic-name'
> at
> org.eclipse.virgo.kernel.userregion.internal.importexpansion.AbstractTrackedPackageImports.mergeAttributes(AbstractTrackedPackageImports.java:144)
> at
> org.eclipse.virgo.kernel.userregion.internal.importexpansion.AbstractTrackedPackageImports.mergePackageImport(AbstractTrackedPackageImports.java:119)
> ...
>
> Is there a way around this?
>
>
> Finally what made it somehow working was to remove the Import-Bundle entries
> and add an Import-Package to the org.apache.camel.spring package like:
>
> Import-Package:
> org.apache.camel.spring;version="[2.7.0,2.8.0)"
> ...
>
> But now we get "java.lang.ClassNotFoundException:
> org.apache.camel.spring.handler.CamelNamespaceHandler" error when
> redeploying the web bundle, which is very unconvenient. Funny enough after
> redeploying 3 times, the web bundle starts again.
>
>
> In short:
> * Why is there a dependency to org.fusesource.commons.management in
> camel-core? Should this dependency maybe optional?
> * Does the core-spring bundle really need to import
> org.apache.camel.language? The bundle already contains this package with
> SpEL.class in it.
> * Any ideas why the web bundle does not see the class CamelNamespaceHandler
> any more after redeployment? Could this be a bug in Virgo?
>
>
> Best regards,
> Jean-Pierre Bergamin
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
CamelOne 2011: http://fusesource.com/camelone2011/
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: Camel as an OSGi bundle in virgo
Posted by Jean-Pierre Bergamin <ja...@ractive.ch>.
Am 19.04.2011 09:53, schrieb Willem Jiang:
> On 4/19/11 3:21 AM, Jean-Pierre Bergamin wrote:
>> In short:
>> * Why is there a dependency to org.fusesource.commons.management in
>> camel-core? Should this dependency maybe optional?
> The camel-core user the fusesource management as the default
> management framework and because of the management code is used when
> the camel context is started, I don't think the dependency can be
> optional.
>
>> * Does the core-spring bundle really need to import
>> org.apache.camel.language? The bundle already contains this package with
>> SpEL.class in it.
> No, I don't think so.
> Maybe we should consider to move th SpEL.class into camel-core to
> avoid exporting the same package of org.apache.camel.language twice.
IMHO it would be best to not have a split org.apache.camel.language
package. This also would it allow us to use Require-Bundle for the
camel-spring bundle in our web bundle.
>> * Any ideas why the web bundle does not see the class
>> CamelNamespaceHandler any more after redeployment? Could this be a bug
>> in Virgo?
>
> I guess it's a Virgo's bug, because we never hit this kind of issue
> when we deploy the camel-core and camel-spring with Spring-DM in OSGi.
This really seems to be a bug in virgo.
Best regards,
James
Re: Camel as an OSGi bundle in virgo
Posted by Willem Jiang <wi...@gmail.com>.
On 4/19/11 3:21 AM, Jean-Pierre Bergamin wrote:
> In short:
> * Why is there a dependency to org.fusesource.commons.management in
> camel-core? Should this dependency maybe optional?
The camel-core user the fusesource management as the default management
framework and because of the management code is used when the camel
context is started, I don't think the dependency can be optional.
> * Does the core-spring bundle really need to import
> org.apache.camel.language? The bundle already contains this package with
> SpEL.class in it.
No, I don't think so.
Maybe we should consider to move th SpEL.class into camel-core to avoid
exporting the same package of org.apache.camel.language twice.
> * Any ideas why the web bundle does not see the class
> CamelNamespaceHandler any more after redeployment? Could this be a bug
> in Virgo?
I guess it's a Virgo's bug, because we never hit this kind of issue when
we deploy the camel-core and camel-spring with Spring-DM in OSGi.
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Connect at CamelOne May 24-26
The Open Source Integration Conference
http://camelone.com