Finally I Found the solution.
here my Service CXf endpoint is
http://www.mit.gov.in/eGov/schema/ConnectorServices/wsdl"/>
than, i have create a header called serviceuri and use
The EntityManager will not automatically join the transaction by using
@Transactional annotation.
You will have to write your transaction management code - and make entity
manager participate in the transaction. Kind of beats the purpose of using
Camel - if you have to take all that pain.
--
Vi
That's not good from c3p0. You can try a different connection pool
altogether.
Apache DBCP is compatible with Hibernate
http://commons.apache.org/proper/commons-dbcp/
Here are some more details on Hibernate connection pooling:
http://www.informit.com/articles/article.aspx?p=353736&seqNum=4
--
hi Mahdava
If you package your camel app. as a war
maybee tweek the weblogic.xml deployment descriptor to to use your war
dependencies instead of app. server libs.
(prefer-web libs something) cant remember from the top of my head.
Then deploy it just as you would any other war file targeting all
Unless I am reading it wrong, stub is not a mock but a seda.
Seems like with seda / stub, can use discardIfNoConsumers=true.
--
View this message in context:
http://camel.465427.n5.nabble.com/Memory-leak-in-stub-component-tp5775851p5775853.html
Sent from the Camel - Users mailing list archive
Yes its by design. See the retain options on the mock endpoint to
limit how many.
On Tue, Jan 5, 2016 at 7:40 PM, dancerjohn wrote:
> We have a system that published to several JMS topics. This system processes
> several million exchanges a day. In our integration environment we are still
> proce
We have a system that published to several JMS topics. This system processes
several million exchanges a day. In our integration environment we are still
processing the same number of exchanges but we don't want to publish to JMS
(or might want to publish to some topics but not others). We way I th
xHi everyone,
this is my nice scenario (Let's dive into it!) :
1. User moves a file into a folder X
2. A complex route is defined on folder X to process the file. The file is
splitted, normalized and inserted into CRM. On completion a report is
displayed to end user and then he could correct some
That's true, I am using 2.14.2, which is what the latest version (2.8.1) of
DDF is using.
I will try updating the Camel libs in DDF to the latest.
Thanks,
Mark
On Tue, Jan 5, 2016 at 11:54 AM, Claus Ibsen wrote:
> You may need to upgrade camel as it may use an old twitter library
> that may n
You may need to upgrade camel as it may use an old twitter library
that may not support latest twitter api. I can see you are on the old
2.14.x release.
On Tue, Jan 5, 2016 at 4:55 PM, Mark wrote:
> I was trying to deploy the camel-example-twitter-websocket-blueprint
> example in DDF 2.8.1 (uses
Thank you for getting back to me regarding this issue. I did verify that I
am using valid account information. I even verified my account information
with the OAuth test page https://dev.twitter.com/apps//oauth
On Tue, Jan 5, 2016 at 11:08 AM, Claus Ibsen wrote:
> You need to use your own t
You need to use your own twitter account, not the one from the source
code, its only for fun and demo.
See the box on this page
http://camel.apache.org/twitter-websocket-example.html
On Tue, Jan 5, 2016 at 4:55 PM, Mark wrote:
> I was trying to deploy the camel-example-twitter-websocket-blueprin
I was trying to deploy the camel-example-twitter-websocket-blueprint
example in DDF 2.8.1 (uses Karaf version 2.4.3) and I get the exception
shown below. I'm not sure if anyone has experienced this and may know how
to get this bundle working inside OSGi with the proper Twitter certificate
informat
To use Spring, you have to stick to Spring DM configuration. Which is not
maintained anymore. So using Spring in OSGi creates more problem than it
solves.
If you want to use Spring I recommend dropping OSGi on the behalf of the
Spring Boot running as fat jar or WAR.
Cheers!
wt., 5.01.2016 o 11:5
Thanks Claus.
--
View this message in context:
http://camel.465427.n5.nabble.com/Exception-from-idempotentConsumer-not-propagating-to-onException-tp5775779p5775795.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Greg,
I've already reviewed this links above.
You can't define a spring bean inside yous OSGI configuration. It won't
work.
Let me first explain to you why I need to do it.
I need to use the Spring JdbcTemplate component because to leverage the
stored procedure abstraction.
I do that because eit
Hi
Thanks for reporting. I have reproduced the issue and logged a ticket
https://issues.apache.org/jira/browse/CAMEL-9480
On Tue, Jan 5, 2016 at 9:27 AM, siddhesh
wrote:
> Hi Claus, Sorry I dint mention Camel version. I am facing this issue on
> 2.10.0 and even on 2.15.2
>
>
>
> --
> View this m
Hi Claus, Sorry I dint mention Camel version. I am facing this issue on
2.10.0 and even on 2.15.2
--
View this message in context:
http://camel.465427.n5.nabble.com/Exception-from-idempotentConsumer-not-propagating-to-onException-tp5775779p5775784.html
Sent from the Camel - Users mailing list a
Hello Saurabh,
Even I was worried about the transaction handling part if I inject
entity manager from Spring instead of using the jpa:// endpoint supported
by the Camel JPA component. Our developers felt that jpa:// was helpful only
for Simple CRUD operations but in our case we do a lot of c
19 matches
Mail list logo