Release of the first beta of a Camel component for Petals ESB
Hi, Just for your information, we released yesterday version 4.3 of the Petals ESB that includes our first beta of a service engine for Apache Camel: http://petals.ow2.org/index.html In a few words, you can now deploy Camel routes into the service bus and make them consumes and provides Petal services (JBI). If you are interested, there is the documentation of the service engine here: https://doc.petalslink.com/display/petalscomponents/Petals-SE-Camel+0.5.0-SNAPSHOT Unfortunately, Petals 4.3 is using Java 6 so we had to settle for Camel 5.12.x, but the next version of Petals (v5) will use Java 7. Thanks for your help until now :) Victor @ Linagora
Re: Is there way to parse in camel cxf endpoint for empty tag's as name/name
No buddy, name is of the element in the response. If we dont pass any data to elements CXF is parsing it as name/ but i need the empty tag's like this name/name -- View this message in context: http://camel.465427.n5.nabble.com/Is-there-way-to-parse-in-camel-cxf-endpoint-for-empty-tag-s-as-name-name-tp5767301p5767408.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Using shared Netty configuration with Rest DSL
You can setup the endpoint property just like this
restConfiguration component=netty4-http”
camel:componentProperty key=“configuration value=#configuration/
camel:endpointProperty key=“nettySharedHttpServer
value=#sharedNettyHttpServer/
camel:endpointProperty key=“securityConfiguration
value=“#securityConfiguration/
/restConfiguration
BTW, you need to create the securityConfiguration yourself.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On May 22, 2015 at 3:06:20 AM, Alex Soto (alex.s...@envieta.com) wrote:
I would like to reuse the same Netty Service that is configured outside of
the Rest DSL.
For example I have the Netty and SSL configuration:
type=JKS provider=SUN/
type=JKS provider=SUN/
init-method=start destroy-method=stop
Now in my Camel Context I declare the Rest DSL:
However, it does not seem to be picking up the shared configuration. Log file
shows:
BootstrapFactory on port 0 is using bootstrap configuration:
[NettyServerBootstrapConfiguration{protocol='tcp',
host=‘X.local', port=0, broadcast=false, sendBufferSize=65536,
receiveBufferSize=65536,
receiveBufferSizePredictor=0, workerCount=0, bossCount=1, keepAlive=true,
tcpNoDelay=true,
reuseAddress=true, connectTimeout=1, backlog=0,
serverInitializerFactory=org.apache.camel.component.netty4.http.HttpServerInitializerFactory@2db0d008,
nettyServerBootstrapFactory=null, options=null, ssl=false, sslHandler=null,
sslContextParameters='null', needClientAuth=false,
enabledProtocols='TLSv1,TLSv1.1,TLSv1.2,
keyStoreFile=null, trustStoreFile=null, keyStoreResource='null',
trustStoreResource='null',
keyStoreFormat='JKS', securityProvider='SunX509', passphrase='null',
bossGroup=null,
workerGroup=null, networkInterface='null’}]
I could not find any examples of how to accomplish this. Any hints?
Best regards,
Alex soto
Re: camel-parent pom properties
Hi,
I would advice to keep Camel BOM imported and import also Spring BOM. Keep
in mind that the order is important here - Spring BOM first, Camel BOM
second. This is actually pretty common approach - to import Spring and
Camel BOMs at the same time. Works like a charm - I'm using this approach
myself. :)
In particular this approach is recommended when working with
camel-spring-boot. The end user should choose his/her Spring stack version
of choice and then just add Camel to the mix.
Cheers!
czw., 21.05.2015 o 16:51 użytkownik Ronny Aerts ronny.ae...@intris.be
napisał:
Hello,
This works very fine for everything which has to do with camel (as
groupid) itself but not for dependencies with other groupid like the one
below:
dependencies
dependency
groupIdorg.springframework.ws/groupId
artifactIdspring-ws-security/artifactId
version${spring-ws-version}/version
/dependency
/dependencies
--
vriendelijke groeten,
Ronny Aerts – Intris nv – Wapenstilstandlaan 47, 2600 Berchem, België
RD Integration Architect
Prince II certified – ITIL certified
Tel: +32-3-326.50.75
-Original Message-
From: Henryk Konsek [mailto:hekon...@gmail.com]
Sent: vrijdag 15 mei 2015 17:23
To: users@camel.apache.org
Subject: Re: camel-parent pom properties
Hi,
The better practice is to import Camel parent as BOM:
dependencyManagement
dependnecies
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-parent/artifactId
version${camel.version}/version
typepom/type
scopeimport/scope
/dependency
/dependnecies
/dependencyManagement
And then simply:
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-core/artifactId
/dependency
Cheers!
pt., 15.05.2015 o 15:24 użytkownik Ronny Aerts ronny.ae...@intris.be
napisał:
Hello camel community,
I'm interested in using the maven properties which are defined in the
camel-parent pom.xml. In order to inherit these maven properties, I need to
set the parent in my projects to the camel-parent. The point is that my
projects use other version numbers than those of camel and this results in
unresolvable camel-core references because the camel-parent uses the
${project.version} variable in its dependencies (which is not 2.15.2 in my
projects).
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-core/artifactId
version${project.version}/version
/dependency
Is there a workaround for this?
--
vriendelijke groeten,
Ronny Aertsmailto:ronny.ae...@intris.be - Intris nv -
Wapenstilstandlaan 47, 2600 Berchem, België RD Integration Architect
Prince IIhttp://nl.wikipedia.org/wiki/PRINCE2 certified - ITIL
http://nl.wikipedia.org/wiki/Information_Technology_Infrastructure_Library
certified
Tel: +32-3-326.50.75
Intris nv
Wapenstilstandlaan 47
B-2600 Berchem Tel. +32 3 326 50 75
Fax +32 3 326 42 23
www.intris.behttp://www.intris.be/ [
http://www.intris.be/mail/AEO_Sticker_108pxRGB.jpg] http://www.intris.be
DISCLAIMER
This is an e-mail from Intris. The information contained in this
communication is intended solely for use by the individual or entity to
whom it is addressed.
Use of this communication by others is prohibited. If the e-mail message
was sent to you by mistake, please notify supp...@intris.bemailto:
supp...@intris.be, destroy it without reading, using, copying or
disclosing its contents to any other person.
We accept no liability for damage related to data and/or documents which
are communicated by electronic mail.
Intris nv
Wapenstilstandlaan 47
B-2600 Berchem Tel. +32 3 326 50 75
Fax +32 3 326 42 23
www.intris.behttp://www.intris.be/[
http://www.intris.be/mail/AEO_Sticker_108pxRGB.jpg] http://www.intris.be
DISCLAIMER
This is an e-mail from Intris. The information contained in this
communication is intended solely for use by the individual or entity to
whom it is addressed.
Use of this communication by others is prohibited. If the e-mail message
was sent to you by mistake, please notify supp...@intris.bemailto:
supp...@intris.be, destroy it without reading, using, copying or
disclosing its contents to any other person.
We accept no liability for damage related to data and/or documents which
are communicated by electronic mail.
Local XSD Schema into CamelContext File
Hello everyone, In my camel-context file i would use a local XSD schema. Today my camel-context start with: beans xmlns=http://www.springframework.org/schema/beans; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:camel=http://camel.apache.org/schema/spring; xsi:schemaLocation= http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.0.xsd http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring-2.14.1.xsd; I tried to copy XSD files into follow folders but i don't have success: - Into META-INF - Into META-INF/spring - Into project root . Can you help me? Note: i am using camel with a standalone JAR Best Regards -- View this message in context: http://camel.465427.n5.nabble.com/Local-XSD-Schema-into-CamelContext-File-tp5767414.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: camel-parent pom properties
To be exact:
dependencyManagement
dependencies
!-- BOMs --
dependency
groupIdorg.springframework.boot/groupId
artifactIdspring-boot-dependencies/artifactId
version${spring-boot.version}/version
typepom/type
scopeimport/scope
/dependency
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-parent/artifactId
version${camel.version}/version
typepom/type
scopeimport/scope
/dependency
...
Regarding Spring version for Camel - just check which version of Spring is
used with the given version of Camel. Unfortunately we can't just import
Spring BOM into Camel BOM, because for example OSGi deployments might go
crazy.
Cheers.
pt., 22.05.2015 o 16:41 użytkownik Ronny Aerts ronny.ae...@intris.be
napisał:
Hello,
I understand your answer about importing the spring bom. I assume you
import it as follows:
dependency
groupIdorg.springframework/groupId
artifactIdspring-framework-bom/artifactId
version4.1.6.RELEASE/version
/dependency
The point with this is that you have to choose the spring version yourself
while camel also made a choice about the spring version which I would like
to follow.
--
vriendelijke groeten,
Ronny Aerts – Intris nv – Wapenstilstandlaan 47, 2600 Berchem, België
RD Integration Architect
Prince II certified – ITIL certified
Tel: +32-3-326.50.75
-Original Message-
From: Henryk Konsek [mailto:hekon...@gmail.com]
Sent: vrijdag 22 mei 2015 9:56
To: users@camel.apache.org
Subject: Re: camel-parent pom properties
Hi,
I would advice to keep Camel BOM imported and import also Spring BOM. Keep
in mind that the order is important here - Spring BOM first, Camel BOM
second. This is actually pretty common approach - to import Spring and
Camel BOMs at the same time. Works like a charm - I'm using this approach
myself. :)
In particular this approach is recommended when working with
camel-spring-boot. The end user should choose his/her Spring stack version
of choice and then just add Camel to the mix.
Cheers!
czw., 21.05.2015 o 16:51 użytkownik Ronny Aerts ronny.ae...@intris.be
napisał:
Hello,
This works very fine for everything which has to do with camel (as
groupid) itself but not for dependencies with other groupid like the
one
below:
dependencies
dependency
groupIdorg.springframework.ws/groupId
artifactIdspring-ws-security/artifactId
version${spring-ws-version}/version
/dependency
/dependencies
--
vriendelijke groeten,
Ronny Aerts – Intris nv – Wapenstilstandlaan 47, 2600 Berchem, België
RD Integration Architect Prince II certified – ITIL certified
Tel: +32-3-326.50.75
-Original Message-
From: Henryk Konsek [mailto:hekon...@gmail.com]
Sent: vrijdag 15 mei 2015 17:23
To: users@camel.apache.org
Subject: Re: camel-parent pom properties
Hi,
The better practice is to import Camel parent as BOM:
dependencyManagement
dependnecies
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-parent/artifactId
version${camel.version}/version
typepom/type
scopeimport/scope
/dependency
/dependnecies
/dependencyManagement
And then simply:
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-core/artifactId
/dependency
Cheers!
pt., 15.05.2015 o 15:24 użytkownik Ronny Aerts ronny.ae...@intris.be
napisał:
Hello camel community,
I'm interested in using the maven properties which are defined in the
camel-parent pom.xml. In order to inherit these maven properties, I
need to set the parent in my projects to the camel-parent. The point
is that my projects use other version numbers than those of camel and
this results in unresolvable camel-core references because the
camel-parent uses the ${project.version} variable in its dependencies
(which is not 2.15.2 in my projects).
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-core/artifactId
version${project.version}/version
/dependency
Is there a workaround for this?
--
vriendelijke groeten,
Ronny Aertsmailto:ronny.ae...@intris.be - Intris nv -
Wapenstilstandlaan 47, 2600 Berchem, België RD Integration Architect
Prince IIhttp://nl.wikipedia.org/wiki/PRINCE2 certified - ITIL
http://nl.wikipedia.org/wiki/Information_Technology_Infrastructure_Lib
rary
certified
Tel: +32-3-326.50.75
Intris nv
Wapenstilstandlaan 47
B-2600 Berchem Tel. +32 3 326 50 75
Fax +32 3 326 42 23
www.intris.behttp://www.intris.be/ [
http://www.intris.be/mail/AEO_Sticker_108pxRGB.jpg]
http://www.intris.be
DISCLAIMER
This is an e-mail from Intris. The information contained in this
communication is intended solely for use by the individual or entity
to whom it is addressed.
Use of this communication by others is prohibited. If the e-mail
message was sent to you by mistake, please notify supp...@intris.be
mailto:
supp...@intris.be, destroy it without reading, using, copying or
disclosing its contents to any other person.
We accept no liability for damage related to data and/or documents
which are communicated by electronic mail.
Intris nv
Wapenstilstandlaan 47
B-2600
Camel XQuery 3.0
Hi, I would like to use the group by functionality provided with XQuery 3.0, along with some other features. Even though Camel 2.15.2 seems to be using Saxon 9.5.1-5 HE which supports XQuery 3.0, I'm getting this exception: Caused by: net.sf.saxon.trans.XPathException: 'group by' is not supported in XQuery 1.0 at net.sf.saxon.query.QueryParser.grumble(QueryParser.java:453) at net.sf.saxon.expr.parser.ExpressionParser.grumble(ExpressionParser.java:226) at net.sf.saxon.expr.parser.ExpressionParser.grumble(ExpressionParser.java:213) at net.sf.saxon.query.QueryParser.parseGroupByClause(QueryParser.java:2389) at net.sf.saxon.query.QueryParser.parseFLWORExpression(QueryParser.java:2091) at net.sf.saxon.expr.parser.ExpressionParser.parseExprSingle(ExpressionParser.java:499) at net.sf.saxon.expr.parser.ExpressionParser.parseExpression(ExpressionParser.java:464) at net.sf.saxon.query.QueryParser.parseQuery(QueryParser.java:365) at net.sf.saxon.query.QueryParser.makeXQueryExpression(QueryParser.java:168) at net.sf.saxon.query.StaticQueryContext.compileQuery(StaticQueryContext.java:526) at org.apache.camel.component.xquery.XQueryBuilder$1.createQueryExpression(XQueryBuilder.java:242) at org.apache.camel.component.xquery.XQueryBuilder.initialize(XQueryBuilder.java:660) at org.apache.camel.component.xquery.XQueryBuilder.evaluateAsString(XQueryBuilder.java:198) at org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:120) ... 92 more Digging further, it seems XQuery 3.0 needs to be explicitly enabled with Saxon. Is there any way I can do this, or a possible workaround? Thanks -- View this message in context: http://camel.465427.n5.nabble.com/Camel-XQuery-3-0-tp5767434.html Sent from the Camel - Users mailing list archive at Nabble.com.
Exchange setBody not working with Camel 2.15.2
Hi,
I'm upgrading some programs from Camel 2.9.3 to 2.15.2 and I'm having all
sort of issues.
One of them is that I'm filtering out messages with Null body, but the new
version of Camel doesn't think that the body is Null.
The route is really simple e.g.
from(DirectRoutes.MyRoute)
.id(getClass().getSimpleName())
.transacted()
.process(myProcessor)
.log(Body ${in.body})
.filter(body().isNotNull())
.log(Message not filtered out)
...
And inside myProcessor I'm setting the body to null depending on some
conditions:
exchange.getIn().setBody(null)
With Camel 2.9.3 the message is filtered out correctly e.g.
[22-May-2015 11:22:45.908] [INFO] [Camel (camel-1) thread #2 -
file://src/data/] MyRoute : Body
But with Camel 2.15.2 the body doesn't appear to be null, so it's not
filtered out:
[22-May-2015 11:22:45.908] [INFO] [Camel (camel-1) thread #2 -
file://src/data/] MyRoute : Body {I AM THE MESSAGE IN INPUT}
[22-May-2015 11:22:45.908] [INFO] [Camel (camel-1) thread #2 -
file://src/data/] MyRoute : Message not filtered out
--
View this message in context:
http://camel.465427.n5.nabble.com/Exchange-setBody-not-working-with-Camel-2-15-2-tp5767420.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Exchange setBody not working with Camel 2.15.2
Also the official API doc says using getIn() is fine: http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Exchange.html If your Processor is not producing a different Message but only needs to slightly modify the in, you can simply update the in Message returned by getIn(). So how comes this is not supported by Camel 2.15.2? -- View this message in context: http://camel.465427.n5.nabble.com/Exchange-setBody-not-working-with-Camel-2-15-2-tp5767420p5767422.html Sent from the Camel - Users mailing list archive at Nabble.com.
Meaning of synchronous for a from()
Hi, I have trouble of understanding the meaning of synchronous parameter on a from() in a route. Does it mean the whole route will be execute with the syncronous API? I ask because from the few tests I did, it seems that even though the first call goes through calls to process() without AsyncCallback, then the following ones in a route seems to be going through process() with AsyncCallback! I'm developing a component and I'm not sure what to write in the documentation about the effect of synchronous on the consumer :) For now I just call the processor with the non-async API: https://github.com/petalslink/petals-se-camel/blob/master/camel-petals/src/main/java/org/ow2/petals/camel/component/PetalsCamelConsumer.java#L67 Thanks! Victor
Re: Exchange setBody not working with Camel 2.15.2
I've found a way to fix the issue by using getOut() instead of getIn() i.e. exchange.getOut().setBody(null); but I'm not happy: 1) the headers of the message are not exactly the same, so now I will have to add code to copy the headers 2) I should not need to change the code. Using getIn() should be perfectly fine as described in the Camel documentation in the section Consider using getIn: http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html What am I doing wrong? -- View this message in context: http://camel.465427.n5.nabble.com/Exchange-setBody-not-working-with-Camel-2-15-2-tp5767420p5767421.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Using shared Netty configuration with Rest DSL
It is working now. Thanks!
Best regards,
Alex soto
On May 22, 2015, at 3:53 AM, Willem Jiang willem.ji...@gmail.com wrote:
You can setup the endpoint property just like this
restConfiguration component=netty4-http”
camel:componentProperty key=“configuration value=#configuration/
camel:endpointProperty key=“nettySharedHttpServer
value=#sharedNettyHttpServer/
camel:endpointProperty key=“securityConfiguration
value=“#securityConfiguration/
/restConfiguration
BTW, you need to create the securityConfiguration yourself.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On May 22, 2015 at 3:06:20 AM, Alex Soto (alex.s...@envieta.com) wrote:
I would like to reuse the same Netty Service that is configured outside of
the Rest DSL.
For example I have the Netty and SSL configuration:
type=JKS provider=SUN/
type=JKS provider=SUN/
init-method=start destroy-method=stop
Now in my Camel Context I declare the Rest DSL:
However, it does not seem to be picking up the shared configuration. Log
file shows:
BootstrapFactory on port 0 is using bootstrap configuration:
[NettyServerBootstrapConfiguration{protocol='tcp',
host=‘X.local', port=0, broadcast=false, sendBufferSize=65536,
receiveBufferSize=65536,
receiveBufferSizePredictor=0, workerCount=0, bossCount=1, keepAlive=true,
tcpNoDelay=true,
reuseAddress=true, connectTimeout=1, backlog=0,
serverInitializerFactory=org.apache.camel.component.netty4.http.HttpServerInitializerFactory@2db0d008,
nettyServerBootstrapFactory=null, options=null, ssl=false, sslHandler=null,
sslContextParameters='null', needClientAuth=false,
enabledProtocols='TLSv1,TLSv1.1,TLSv1.2,
keyStoreFile=null, trustStoreFile=null, keyStoreResource='null',
trustStoreResource='null',
keyStoreFormat='JKS', securityProvider='SunX509', passphrase='null',
bossGroup=null,
workerGroup=null, networkInterface='null’}]
I could not find any examples of how to accomplish this. Any hints?
Best regards,
Alex soto
RE: camel-parent pom properties
Hello,
I understand your answer about importing the spring bom. I assume you import it
as follows:
dependency
groupIdorg.springframework/groupId
artifactIdspring-framework-bom/artifactId
version4.1.6.RELEASE/version
/dependency
The point with this is that you have to choose the spring version yourself
while camel also made a choice about the spring version which I would like to
follow.
--
vriendelijke groeten,
Ronny Aerts – Intris nv – Wapenstilstandlaan 47, 2600 Berchem, België
RD Integration Architect
Prince II certified – ITIL certified
Tel: +32-3-326.50.75
-Original Message-
From: Henryk Konsek [mailto:hekon...@gmail.com]
Sent: vrijdag 22 mei 2015 9:56
To: users@camel.apache.org
Subject: Re: camel-parent pom properties
Hi,
I would advice to keep Camel BOM imported and import also Spring BOM. Keep in
mind that the order is important here - Spring BOM first, Camel BOM second.
This is actually pretty common approach - to import Spring and Camel BOMs at
the same time. Works like a charm - I'm using this approach myself. :)
In particular this approach is recommended when working with camel-spring-boot.
The end user should choose his/her Spring stack version of choice and then just
add Camel to the mix.
Cheers!
czw., 21.05.2015 o 16:51 użytkownik Ronny Aerts ronny.ae...@intris.be
napisał:
Hello,
This works very fine for everything which has to do with camel (as
groupid) itself but not for dependencies with other groupid like the
one
below:
dependencies
dependency
groupIdorg.springframework.ws/groupId
artifactIdspring-ws-security/artifactId
version${spring-ws-version}/version
/dependency
/dependencies
--
vriendelijke groeten,
Ronny Aerts – Intris nv – Wapenstilstandlaan 47, 2600 Berchem, België
RD Integration Architect Prince II certified – ITIL certified
Tel: +32-3-326.50.75
-Original Message-
From: Henryk Konsek [mailto:hekon...@gmail.com]
Sent: vrijdag 15 mei 2015 17:23
To: users@camel.apache.org
Subject: Re: camel-parent pom properties
Hi,
The better practice is to import Camel parent as BOM:
dependencyManagement
dependnecies
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-parent/artifactId
version${camel.version}/version
typepom/type
scopeimport/scope
/dependency
/dependnecies
/dependencyManagement
And then simply:
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-core/artifactId
/dependency
Cheers!
pt., 15.05.2015 o 15:24 użytkownik Ronny Aerts ronny.ae...@intris.be
napisał:
Hello camel community,
I'm interested in using the maven properties which are defined in the
camel-parent pom.xml. In order to inherit these maven properties, I
need to set the parent in my projects to the camel-parent. The point
is that my projects use other version numbers than those of camel and
this results in unresolvable camel-core references because the
camel-parent uses the ${project.version} variable in its dependencies
(which is not 2.15.2 in my projects).
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-core/artifactId
version${project.version}/version
/dependency
Is there a workaround for this?
--
vriendelijke groeten,
Ronny Aertsmailto:ronny.ae...@intris.be - Intris nv -
Wapenstilstandlaan 47, 2600 Berchem, België RD Integration Architect
Prince IIhttp://nl.wikipedia.org/wiki/PRINCE2 certified - ITIL
http://nl.wikipedia.org/wiki/Information_Technology_Infrastructure_Lib
rary
certified
Tel: +32-3-326.50.75
Intris nv
Wapenstilstandlaan 47
B-2600 Berchem Tel. +32 3 326 50 75
Fax +32 3 326 42 23
www.intris.behttp://www.intris.be/ [
http://www.intris.be/mail/AEO_Sticker_108pxRGB.jpg]
http://www.intris.be
DISCLAIMER
This is an e-mail from Intris. The information contained in this
communication is intended solely for use by the individual or entity
to whom it is addressed.
Use of this communication by others is prohibited. If the e-mail
message was sent to you by mistake, please notify supp...@intris.bemailto:
supp...@intris.be, destroy it without reading, using, copying or
disclosing its contents to any other person.
We accept no liability for damage related to data and/or documents
which are communicated by electronic mail.
Intris nv
Wapenstilstandlaan 47
B-2600 Berchem Tel. +32 3 326 50 75
Fax +32 3 326 42 23
www.intris.behttp://www.intris.be/[
http://www.intris.be/mail/AEO_Sticker_108pxRGB.jpg]
http://www.intris.be
DISCLAIMER
This is an e-mail from Intris. The information contained in this
communication is intended solely for use by the individual or entity
to whom it is addressed.
Use of this communication by others is prohibited. If the e-mail
message was sent to you by mistake, please notify supp...@intris.bemailto:
supp...@intris.be, destroy it without reading, using, copying or
disclosing its contents to any other person.
We accept no liability for damage related to data
Re: HttpProducer to ignore response body avoiding stream caching
yes that's exactly what I'd need. Should I open a JIRA issue? Best, Marco -- View this message in context: http://camel.465427.n5.nabble.com/HttpProducer-to-ignore-response-body-avoiding-stream-caching-tp5767260p5767416.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Exchange setBody not working with Camel 2.15.2
Hi, Maybe a little Maven example demonstrating the issue? That would encourage us to debug your problem :) . Cheers! pt., 22.05.2015 o 13:33 użytkownik geppo geppore...@gmail.com napisał: Also the official API doc says using getIn() is fine: http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Exchange.html If your Processor is not producing a different Message but only needs to slightly modify the in, you can simply update the in Message returned by getIn(). So how comes this is not supported by Camel 2.15.2? -- View this message in context: http://camel.465427.n5.nabble.com/Exchange-setBody-not-working-with-Camel-2-15-2-tp5767420p5767422.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Release of the first beta of a Camel component for Petals ESB
Hi Victor, I guess that you meant Camel 2.12.x (not 5.12.x ;)). Thanks for the update ! Regards JB On 05/22/2015 11:04 AM, Victor NOËL wrote: Hi, Just for your information, we released yesterday version 4.3 of the Petals ESB that includes our first beta of a service engine for Apache Camel: http://petals.ow2.org/index.html In a few words, you can now deploy Camel routes into the service bus and make them consumes and provides Petal services (JBI). If you are interested, there is the documentation of the service engine here: https://doc.petalslink.com/display/petalscomponents/Petals-SE-Camel+0.5.0-SNAPSHOT Unfortunately, Petals 4.3 is using Java 6 so we had to settle for Camel 5.12.x, but the next version of Petals (v5) will use Java 7. Thanks for your help until now :) Victor @ Linagora -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Synchronous one time use of endpoint
I would like to leverage the endpoint abstraction Camel provides, but I don't necessarily need a route. My use case is to simply read a file from an FTP server. Is there a way to leverage Camel either through the API or a route to synchronously leverage a Camel consumer endpoint? For example, I would like to do something like this: Message message = from(sftp://u...@someserver.com/dir/file.txt;); I understand that I could do something like: from(sftp://u...@someserver.com/dir/file.txt;).to(someBean); However, that would be asynchronous, and potentially consume more than one file. I could, in theory, spin up a dynamic route, collect messages, and then spin it down, but that would require a lot of management. Another way to ask the question would be, can I leverage Camel's URI abstraction of the JSCH API without actually creating routes? ~Justin CONFIDENTIALITY NOTICE: The information in this message, and any attachment, is intended for the sole use of the individual and entity to whom it is addressed. This information may be privileged, confidential, and protected from disclosure. If you are not the intended recipient you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it, or its contents, is strictly prohibited. If you think that you have received this message in error please notify the sender and destroy all copies of this communication and any attachments. Thank you.
