I've been trying everything I can think of to successfully invoke a remote
REST service and capture the response purely within a spring camel file.
I've got a setup that appears to do everything I need, but for the life of
me I can't figure out how to capture the response.
On top of it all, by se
I am writing a DELETE statement using the JDBC component and want to make
sure there is no SQL injection possibilities. My statement does not have
any input parameters, is basically a table with a few columns including one
called MOD_TIME.
The SQL statement is in a bean
DELETE FROM MY_TABLE WHER
Hello,
i'm pretty new in developing camel routes, so my problem might be easy to
you.
I wanna receive a message from RabbitMQ and if occurs any Exception this
message will be requeued from I received.
Something like a Rollback in the route or just a NAck in my queue.
Is that possible to do with C
Hi All,
We are using the latest version of Camel 2.12.2, CXF 2.7.10, and Tomcat 7.
-- cxf interface
@WebService(name="createSecurityOrder", targetNamespace="http://www.com/";)
@XmlSeeAlso({ObjectFactory.class})
public interface CreateSecurityOrder {
@WebResult(name = "Acknowledgment", target
And the one for the early compendium extension:
https://github.com/OsgiliathEnterprise/net.osgiliath.parent/tree/master/net.osgiliath.framework/net.osgiliath.helpers.parent/net.osgiliath.helpers.camel.cdi.configadmin
Le 30 avr. 2014 15:33, Charles Moulliard a écrit :
>
> Hi Charlie,
>
> The lin
Hi Charles,
Sorry for the link, the framework is evolving at the speed of the light ;).
Here's the link to the integration tested sample:
https://github.com/OsgiliathEnterprise/net.osgiliath.parent/tree/master/net.osgiliath.framework/net.osgiliath.features.karaf-features/net.osgiliath.features.k
Hi,
maybe someone will correct me, but I think thats not an issue of the
camel-cxf component.
Cxf uses jaxb as standard binding and jaxb has a standard schema to java
type mapping:
See the chapter "Schema-to-Java Mapping" of the following link:
http://docs.oracle.com/cd/E19159-01/819-3669/bnazf/i
Hi,
I tried to configure log4.properties in my standalone application, it shows
on console but i am unable to see it in file, following is my code
Main Class:-
public static void main(String[] args) throws Exception {
Main main = new Main();
main.enableHangupSupport();
m
Hi Claus, hi all,
Thank you for explaining why there's no equals in DefaultExchangeHolder's.
If DefaultExchangeHolder is not the representation of a queued Camel
exchange waiting to be processed, what is?
We weren't trying to create new ExchangeHolders or duplicate exchanges.
The problem was simpl
Where should this line be put if you are using Spring DSL? Well keeping it
inside a root will also be not a good idea though.
main.setApplicationContextUri("first_directory/sub_directory/xyz.xml");
--
View this message in context:
http://camel.465427.n5.nabble.com/class-path-resource-ME
Hi Charlie,
The link is wrong. Can you send me the exact url to let me to have a look
please ?
Regards,
On Sun, Apr 6, 2014 at 9:40 PM, Charlie Mordant wrote:
> Hi Camel community (and enjoy to say this to me too :p),
>
> For the Osgi folks, I created a Compedium service component for camel-
How did you set the OperationName header?
Please make sure the message body is match the Operation that you want invoke.
--
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
CaughtExceptionType:java.lang.IllegalArgumentException,
CaughtExceptionMessage:The PayLoad elements cannot fit with the message
parts of the BindingOperation. Please check the BindingOperation and
PayLoadMessage., StackTrace:java.lang.IllegalArgumentException: The PayLoad
elements cannot fit with t
OK. I really get your point. Great answer!
Thanks
On Wed, Apr 30, 2014 at 5:18 PM, Jens Breitenstein wrote:
> onder if performance is really a problem? An object makes handling of your
> business logic in all your camel processors far easier (a map, a business
> related class) in contrast to rep
if you use JMS than your data will be send as ObjectMessage which makes
use of JAVA object serialization thus it's converted to byte stream at
some point in time.
But this serialization only occurs ones when ActiveMQ sends your message
to JMS listeners (regardless if same VM or another one). If
Hi there,
I'm pretty new to camel, however until now it let me do anything I want ,-).
For the last two days, however I struggled with a problem, and hope you can
help.
I am developing a message based application, with several components. Now
there is one component, that is receiving messages wit
Yes, we changed the default setting in Camel-2.12.x to enforce the security
the setting by default.
You can override the setting just as Grzegorz suggested.
--
View this message in context:
http://camel.465427.n5.nabble.com/XMLConstants-FEATURE-SECURE-PROCESSING-feature-setting-in-jboss-fuse-6-
Ah..!
So, in the same JVM, using Java object simply uses an instance
pointer. But if I'm going to produce into an ActiveMQ endpoint, I
should make sure the MQ in the same JVM with vm transport or, I should
marshall into protobuf bytes. The MQ is used for my own system too,
but different physical l
Fuse 6.1 uses Camel 2.12, Fuse 6.0 used Camel 2.10.
Look at https://issues.apache.org/jira/browse/CAMEL-7123 - from Camel 2.11
Camel sets:
factory.setFeature(javax.xml.XMLConstants.FEATURE_SECURE_PROCESSING, true);
if you want to change this behaviour, configure your XSLT endpoint by
referencing
What do you mean by different systems? Different Camel Processors?
You can store your data as body/property and this is a pure instance pointer.
As long the message is not deep cloned/serialized as bytestream there is no
overhead passing this message through the camel routes (in one vm).
Can yo
Hi
This is the Apache Camel user forum.
If you want to discuss JBoss Fuse product then use the jboss forum at
https://community.jboss.org/en/jbossfuse
On Wed, Apr 30, 2014 at 9:09 AM, bharadwaj wrote:
> The solution is not proper.. and it's perfectly working in jboss fuse 6.0
> even with same v
Could you please explain where exactly you made a change?
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-validator-parser-doesn-t-allow-a-maxOccurs-attribute-value-to-be-set-greater-than-the-value-5-0-tp5747680p5750714.html
Sent from the Camel - Users mailing list arch
The solution is not proper.. and it's perfectly working in jboss fuse 6.0
even with same version.
--
View this message in context:
http://camel.465427.n5.nabble.com/XMLConstants-FEATURE-SECURE-PROCESSING-feature-setting-in-jboss-fuse-6-1-tp5750712p5750715.html
Sent from the Camel - Users mailin
Hello Satyam
The problem is related to
https://jaxp.java.net/1.4/JAXP-Compatibility.html#JAXP_security which
defaults to true in JAXP 1.4.
See also this post:
http://camel.465427.n5.nabble.com/camel-validator-parser-doesn-t-allow-a-maxOccurs-attribute-value-to-be-set-greater-than-the-value-5-0-td
24 matches
Mail list logo
