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
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:
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
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
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;
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
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
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)
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().
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
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
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/
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
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.
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:
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:
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
17 matches
Mail list logo