You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Sriraman Gopalan <sr...@gmail.com> on 2012/08/20 17:31:14 UTC
Unable to deploy a camel route in websphere application server 8.5
Dear All,
Today, I tried to deploy a simple route in Websphere Application Server 8.5
as an Asset (.eba file).
However, while deploying the asset, I got the following error:
org.apache.aries.application.modelling.ModellerException: CWSAL0126E: An
exception occurred while modelling bundle ib-base_0.0.1.SNAPSHOT:
org.apache.aries.application.modelling.ModellerException:
org.osgi.service.blueprint.container.ComponentDefinitionException:
Unsupported node namespace: http://camel.apache.org/schema/blueprint
I use Camel 2.10.0.
My blueprint file snippet is as follows:
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:camel="http://camel.apache.org/schema/blueprint"
xsi:schemaLocation="
http://www.osgi.org/xmlns/blueprint/v1.0.0
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
http://camel.apache.org/schema/blueprint
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd">
<camel:camelContext id="cbrContext" trace="false">
<camel:packageScan>
<camel:package>a.b.c.d</camel:package>
</camel:packageScan>
</camel:camelContext>
</blueprint>
best regards
Sriraman.
--
View this message in context: http://camel.465427.n5.nabble.com/Unable-to-deploy-a-camel-route-in-websphere-application-server-8-5-tp5717720.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Unable to deploy a camel route in websphere application server 8.5
Posted by Charles Moulliard <ch...@gmail.com>.
I don't think that WebSphere 8.5 uses Aries 1.0.0. They should always uses
0.3 release (http://aries.apache.org/downloads/currentrelease.html). You
can verify that by checking in one of the WAS directory the jars files
On Tue, Aug 21, 2012 at 5:47 PM, Sriraman Gopalan <sr...@gmail.com>wrote:
> Dear Willem,
>
> Did some more research. I finally got the eba file deployed to Karaf
> 3.0.0-SNAPSHOT. However, I had to make the following changes in
> camel-parent
> for the aries dependency. Following were the changes:
>
> <aries-blueprint-version>[0.3,)</aries-blueprint-version>
>
> Now, the namespace http://camel.apache.org/schema/blueprint is getting
> resolved without any issues.
>
> Looks like a bug in Websphere. Will post in Websphere forums to see if
> somebody can help me. Since, both Karaf 3.0.0-SNAPSHOT and Websphere 8.5
> use
> Aries 1.0.0, I guess this has something to do with the WebSphere.
>
> best regards
> Sriraman.
>
>
>
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Unable-to-deploy-a-camel-route-in-websphere-application-server-8-5-tp5717720p5717775.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Charles Moulliard
Apache Committer / Sr. Pr. Consultant at FuseSource.com
Twitter : @cmoulliard
Blog : http://cmoulliard.blogspot.com
Re: Unable to deploy a camel route in websphere application
server 8.5
Posted by Willem jiang <wi...@gmail.com>.
In Camel 2.10.0, the version range of aries-blueprint package is [0.2, 2).
I just ran some build with aries-blueprint 1.0.0, it looks good so far.
Please let us know if you hit any issues those camel-blueprint works with aries-blueprint 1.0.0.
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: willemjiang
On Wednesday, August 22, 2012 at 2:31 PM, Sriraman Gopalan wrote:
> Dear Willem,
>
> With the below mentioned change, I think, Camel can support Aries from 0.3
> and above without any issues while addressing the concern of Claus to ensure
> that Camel supports Aries 0.3 and 1.0.0 as well.
>
>
> This is in the camel-parent project's POM.
>
> <aries-blueprint-version>[0.3,)</aries-blueprint-version>
>
>
>
> best regards
> Sriraman.
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Unable-to-deploy-a-camel-route-in-websphere-application-server-8-5-tp5717720p5717820.html
> Sent from the Camel - Users mailing list archive at Nabble.com (http://Nabble.com).
Re: Unable to deploy a camel route in websphere application server
8.5
Posted by Sriraman Gopalan <sr...@gmail.com>.
Dear Willem,
With the below mentioned change, I think, Camel can support Aries from 0.3
and above without any issues while addressing the concern of Claus to ensure
that Camel supports Aries 0.3 and 1.0.0 as well.
This is in the camel-parent project's POM.
<aries-blueprint-version>[0.3,)</aries-blueprint-version>
best regards
Sriraman.
--
View this message in context: http://camel.465427.n5.nabble.com/Unable-to-deploy-a-camel-route-in-websphere-application-server-8-5-tp5717720p5717820.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Unable to deploy a camel route in websphere application
server 8.5
Posted by Willem jiang <wi...@gmail.com>.
Hi Sriraman,
It's good to know you find a way to resolve this issue.
Current camel-blueprint is using aries 0.3.x, I'm not sure if it support the aries 1.0 out of box.
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: willemjiang
On Tuesday, August 21, 2012 at 11:47 PM, Sriraman Gopalan wrote:
> Dear Willem,
>
> Did some more research. I finally got the eba file deployed to Karaf
> 3.0.0-SNAPSHOT. However, I had to make the following changes in camel-parent
> for the aries dependency. Following were the changes:
>
> <aries-blueprint-version>[0.3,)</aries-blueprint-version>
>
> Now, the namespace http://camel.apache.org/schema/blueprint is getting
> resolved without any issues.
>
> Looks like a bug in Websphere. Will post in Websphere forums to see if
> somebody can help me. Since, both Karaf 3.0.0-SNAPSHOT and Websphere 8.5 use
> Aries 1.0.0, I guess this has something to do with the WebSphere.
>
> best regards
> Sriraman.
>
>
>
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Unable-to-deploy-a-camel-route-in-websphere-application-server-8-5-tp5717720p5717775.html
> Sent from the Camel - Users mailing list archive at Nabble.com (http://Nabble.com).
Re: Unable to deploy a camel route in websphere application server
8.5
Posted by Sriraman Gopalan <sr...@gmail.com>.
Dear Willem,
Did some more research. I finally got the eba file deployed to Karaf
3.0.0-SNAPSHOT. However, I had to make the following changes in camel-parent
for the aries dependency. Following were the changes:
<aries-blueprint-version>[0.3,)</aries-blueprint-version>
Now, the namespace http://camel.apache.org/schema/blueprint is getting
resolved without any issues.
Looks like a bug in Websphere. Will post in Websphere forums to see if
somebody can help me. Since, both Karaf 3.0.0-SNAPSHOT and Websphere 8.5 use
Aries 1.0.0, I guess this has something to do with the WebSphere.
best regards
Sriraman.
--
View this message in context: http://camel.465427.n5.nabble.com/Unable-to-deploy-a-camel-route-in-websphere-application-server-8-5-tp5717720p5717775.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Unable to deploy a camel route in websphere application
server 8.5
Posted by Willem jiang <wi...@gmail.com>.
HI Sriraman,
For the issue1, you don't need to install the camel-core-xml, as the camel-blueprint bundle already has classes of camel-core-xml.
As you didn't have chance to play with WebSphere I can not answer the issue2.
But if you look at the camel-blueprint bundle, you should be able find the blueprint handler file there.
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: willemjiang
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Tuesday, August 21, 2012 at 3:12 PM, Sriraman Gopalan wrote:
> Dear Willem,
>
> I did install the camel-blueprint component in the internal bundle
> repository of websphere.
>
> There are 2 issues here.
>
> 1. I am not too sure if the camel-core-xml is also required as it seems to
> be a dependency for the camel-blueprint. However, it is not a valid OSGi
> bundle in the sense, it does not have the Import-Package, Export Package
> entries in its manifest and Websphere refuses to accept it as a valid
> bundle. However, with a small change, I was able to generate the OSGi
> manifest and was successful in adding it to the websphere internal bundle
> repository.
>
> The change was in the pom of the camel-core-xml component as follows:
>
> <packaging>bundle</packaging>
> <properties>
> <camel.osgi.export.pkg>
> org.apache.camel.core.xml.*
> </camel.osgi.export.pkg>
> </properties>
>
> The generated Manifest looked as shown below:
>
> =============================================================
> Manifest-Version: 1.0
> Bnd-LastModified: 1345531716277
> Build-Jdk: 1.6.0_29
> Built-By: sreeraaman
> Bundle-Description: Camel Core XML support
> Bundle-DocURL: http://www.apache.org/
> Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
> Bundle-ManifestVersion: 2
> Bundle-Name: camel-core-xml
> Bundle-SymbolicName: org.apache.camel.camel-core-xml
> Bundle-Vendor: The Apache Software Foundation
> Bundle-Version: 2.10.0
> Created-By: Apache Maven Bundle Plugin
> Export-Package: org.apache.camel.core.xml;uses:="org.apache.camel.impl,o
> rg.apache.camel.util,org.apache.camel,javax.xml.bind.annotation,org.apa
> che.camel.component.properties,org.apache.camel.builder,org.apache.came
> l.processor.interceptor,org.apache.camel.management,org.apache.camel.mo
> del.dataformat,org.slf4j,org.apache.camel.model.config,org.apache.camel
> .model,org.apache.camel.spi,org.apache.camel.processor,javax.xml.bind.a
> nnotation.adapters,org.apache.camel.builder.xml";version="2.10.0",org.a
> pache.camel.core.xml.util.jsse;uses:="org.apache.camel.util.jsse,org.ap
> ache.camel,javax.xml.bind.annotation,org.apache.camel.core.xml";version
> ="2.10.0"
> Implementation-Title: Apache Camel
> Implementation-Version: 2.10.0
> Import-Package: javax.xml.bind.annotation,javax.xml.bind.annotation.adap
> ters,org.apache.camel;version="[2.10,2.11)",org.apache.camel.builder;ve
> rsion="[2.10,2.11)",org.apache.camel.builder.xml;version="[2.10,2.11)",
> org.apache.camel.component.properties;version="[2.10,2.11)",org.apache.
> camel.impl;version="[2.10,2.11)",org.apache.camel.management;version="[
> 2.10,2.11)",org.apache.camel.model;version="[2.10,2.11)",org.apache.cam
> el.model.config;version="[2.10,2.11)",org.apache.camel.model.dataformat
> ;version="[2.10,2.11)",org.apache.camel.processor;version="[2.10,2.11)"
> ,org.apache.camel.processor.interceptor;version="[2.10,2.11)",org.apach
> e.camel.spi;version="[2.10,2.11)",org.apache.camel.util;version="[2.10,
> 2.11)",org.apache.camel.util.jsse;version="[2.10,2.11)",org.slf4j;versi
> on="[1.6,2)"
> Karaf-Info: Camel;camel-core-xml=2.10.0
> Tool: Bnd-1.50.0
> ================================================================
> Also, there were a couple of warning produced while running mvn:package for
> the camel-core-xml component as shown below:
>
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for !org.apache.camel.core.xml.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for com.thoughtworks.xstream.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for freemarker.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for javax.persistence.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for net.sf.flatpack.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for net.sf.saxon.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for org.antlr.stringtemplate.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for org.apache.abdera.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for org.apache.commons.httpclient.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for org.apache.commons.logging.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for org.apache.cxf.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for org.apache.qpid.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for org.apache.velocity.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for org.apache.xmlbeans.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for org.ccil.cowan.tagsoup.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for org.eclipse.jetty.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for org.jivesoftware.smack.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for org.mortbay.cometd.*
> [WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
> find matching referal for org.springframework.*
>
>
>
>
> 2. I tried to check with the websphere application server developer tools to
> see if I can get some insight into what exactly is happening. I was
> surprised to see that we I tried to create a blueprint xml, it had an option
> to add or remove blueprint namespaces and it lists only the following:
>
> a. IBM Blueprint Extension
> b. JPA Blueprint Support
> c. Blueprint Transaction Support
> d. Blueprint Resource Reference support
>
> With all these namespaces selected, the generated blueprint xml looks as
> follows:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
> xmlns:bpext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0"
> xmlns:bpjpa="http://aries.apache.org/xmlns/jpa/v1.0.0"
> xmlns:bptx="http://aries.apache.org/xmlns/transactions/v1.0.0"
>
> xmlns:bpresref="http://www.ibm.com/appserver/schemas/8.0/blueprint/resourcereference">
>
> </blueprint>
>
> I am not too sure, if I can add a custom namespace and attach a URL and a
> namespace handler via tooling in websphere.
>
> I have attached the add/remove blueprint namespace screen from websphere
> developer tools for your reference. (
> http://camel.465427.n5.nabble.com/file/n5717743/blueprintnamespaces.png
> blueprintnamespaces.png )
>
> best regards
> Sriraman.
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Unable-to-deploy-a-camel-route-in-websphere-application-server-8-5-tp5717720p5717743.html
> Sent from the Camel - Users mailing list archive at Nabble.com (http://Nabble.com).
Re: Unable to deploy a camel route in websphere application server
8.5
Posted by Sriraman Gopalan <sr...@gmail.com>.
Dear Willem,
I did install the camel-blueprint component in the internal bundle
repository of websphere.
There are 2 issues here.
1. I am not too sure if the camel-core-xml is also required as it seems to
be a dependency for the camel-blueprint. However, it is not a valid OSGi
bundle in the sense, it does not have the Import-Package, Export Package
entries in its manifest and Websphere refuses to accept it as a valid
bundle. However, with a small change, I was able to generate the OSGi
manifest and was successful in adding it to the websphere internal bundle
repository.
The change was in the pom of the camel-core-xml component as follows:
<packaging>bundle</packaging>
<properties>
<camel.osgi.export.pkg>
org.apache.camel.core.xml.*
</camel.osgi.export.pkg>
</properties>
The generated Manifest looked as shown below:
=============================================================
Manifest-Version: 1.0
Bnd-LastModified: 1345531716277
Build-Jdk: 1.6.0_29
Built-By: sreeraaman
Bundle-Description: Camel Core XML support
Bundle-DocURL: http://www.apache.org/
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-ManifestVersion: 2
Bundle-Name: camel-core-xml
Bundle-SymbolicName: org.apache.camel.camel-core-xml
Bundle-Vendor: The Apache Software Foundation
Bundle-Version: 2.10.0
Created-By: Apache Maven Bundle Plugin
Export-Package: org.apache.camel.core.xml;uses:="org.apache.camel.impl,o
rg.apache.camel.util,org.apache.camel,javax.xml.bind.annotation,org.apa
che.camel.component.properties,org.apache.camel.builder,org.apache.came
l.processor.interceptor,org.apache.camel.management,org.apache.camel.mo
del.dataformat,org.slf4j,org.apache.camel.model.config,org.apache.camel
.model,org.apache.camel.spi,org.apache.camel.processor,javax.xml.bind.a
nnotation.adapters,org.apache.camel.builder.xml";version="2.10.0",org.a
pache.camel.core.xml.util.jsse;uses:="org.apache.camel.util.jsse,org.ap
ache.camel,javax.xml.bind.annotation,org.apache.camel.core.xml";version
="2.10.0"
Implementation-Title: Apache Camel
Implementation-Version: 2.10.0
Import-Package: javax.xml.bind.annotation,javax.xml.bind.annotation.adap
ters,org.apache.camel;version="[2.10,2.11)",org.apache.camel.builder;ve
rsion="[2.10,2.11)",org.apache.camel.builder.xml;version="[2.10,2.11)",
org.apache.camel.component.properties;version="[2.10,2.11)",org.apache.
camel.impl;version="[2.10,2.11)",org.apache.camel.management;version="[
2.10,2.11)",org.apache.camel.model;version="[2.10,2.11)",org.apache.cam
el.model.config;version="[2.10,2.11)",org.apache.camel.model.dataformat
;version="[2.10,2.11)",org.apache.camel.processor;version="[2.10,2.11)"
,org.apache.camel.processor.interceptor;version="[2.10,2.11)",org.apach
e.camel.spi;version="[2.10,2.11)",org.apache.camel.util;version="[2.10,
2.11)",org.apache.camel.util.jsse;version="[2.10,2.11)",org.slf4j;versi
on="[1.6,2)"
Karaf-Info: Camel;camel-core-xml=2.10.0
Tool: Bnd-1.50.0
================================================================
Also, there were a couple of warning produced while running mvn:package for
the camel-core-xml component as shown below:
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for !org.apache.camel.core.xml.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for com.thoughtworks.xstream.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for freemarker.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for javax.persistence.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for net.sf.flatpack.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for net.sf.saxon.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for org.antlr.stringtemplate.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for org.apache.abdera.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for org.apache.commons.httpclient.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for org.apache.commons.logging.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for org.apache.cxf.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for org.apache.qpid.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for org.apache.velocity.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for org.apache.xmlbeans.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for org.ccil.cowan.tagsoup.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for org.eclipse.jetty.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for org.jivesoftware.smack.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for org.mortbay.cometd.*
[WARNING] Bundle org.apache.camel:camel-core-xml:bundle:2.10.0 : Did not
find matching referal for org.springframework.*
2. I tried to check with the websphere application server developer tools to
see if I can get some insight into what exactly is happening. I was
surprised to see that we I tried to create a blueprint xml, it had an option
to add or remove blueprint namespaces and it lists only the following:
a. IBM Blueprint Extension
b. JPA Blueprint Support
c. Blueprint Transaction Support
d. Blueprint Resource Reference support
With all these namespaces selected, the generated blueprint xml looks as
follows:
<?xml version="1.0" encoding="UTF-8"?>
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
xmlns:bpext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0"
xmlns:bpjpa="http://aries.apache.org/xmlns/jpa/v1.0.0"
xmlns:bptx="http://aries.apache.org/xmlns/transactions/v1.0.0"
xmlns:bpresref="http://www.ibm.com/appserver/schemas/8.0/blueprint/resourcereference">
</blueprint>
I am not too sure, if I can add a custom namespace and attach a URL and a
namespace handler via tooling in websphere.
I have attached the add/remove blueprint namespace screen from websphere
developer tools for your reference. (
http://camel.465427.n5.nabble.com/file/n5717743/blueprintnamespaces.png
blueprintnamespaces.png )
best regards
Sriraman.
--
View this message in context: http://camel.465427.n5.nabble.com/Unable-to-deploy-a-camel-route-in-websphere-application-server-8-5-tp5717720p5717743.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Unable to deploy a camel route in websphere application
server 8.5
Posted by Willem jiang <wi...@gmail.com>.
It looks you didn't install the the camel-blueprint bundle rightly?
Can you double check it ?
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: willemjiang
On Monday, August 20, 2012 at 11:31 PM, Sriraman Gopalan wrote:
> Dear All,
>
> Today, I tried to deploy a simple route in Websphere Application Server 8.5
> as an Asset (.eba file).
>
> However, while deploying the asset, I got the following error:
>
> org.apache.aries.application.modelling.ModellerException: CWSAL0126E: An
> exception occurred while modelling bundle ib-base_0.0.1.SNAPSHOT:
> org.apache.aries.application.modelling.ModellerException:
> org.osgi.service.blueprint.container.ComponentDefinitionException:
> Unsupported node namespace: http://camel.apache.org/schema/blueprint
>
> I use Camel 2.10.0.
>
> My blueprint file snippet is as follows:
>
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:camel="http://camel.apache.org/schema/blueprint"
> xsi:schemaLocation="
> http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
> http://camel.apache.org/schema/blueprint
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd">
>
> <camel:camelContext id="cbrContext" trace="false">
> <camel:packageScan>
> <camel:package>a.b.c.d</camel:package>
> </camel:packageScan>
> </camel:camelContext>
> </blueprint>
>
> best regards
> Sriraman.
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Unable-to-deploy-a-camel-route-in-websphere-application-server-8-5-tp5717720.html
> Sent from the Camel - Users mailing list archive at Nabble.com (http://Nabble.com).