On Fri, May 25, 2012 at 7:52 PM, Nestor Urquiza
nestor.urqu...@gmail.com wrote:
Thanks Clous. Your answers brought me back to earth.
I think I missed the point about what the ftp components and any other Camel
component is about (Producer/Consumer). I was trying to activate a route
from a
On Tue, May 22, 2012 at 7:57 PM, szh.s...@gmail.com wrote:
Hi gurus,
Recently I've published camel component that uses OSGi services to
communicate between endpoints in different bundles.
Here is the link: https://github.com/szhem/camel-osgi
I've already raised JIRA issue -
Thank you Henryk,
Your solution has worked for me.
Note: I had to get the original exchange from inside one of the returned
(multicast) exchanges to get the original headers and make sure they were
preserved.
This was done inside a Processor implementation.
Once again, thank you
Regards,
Just for fun (and learning by doing), I have written a Salesforce component
for Apache Camel. It is not feature-complete, just some methods of the
Salesforce API are supported.
There are two alternatives for communicating with Salesforce:
1) Use Java API (this is what it did for my component):
On Wed, May 30, 2012 at 10:40 AM, megachucky megachu...@googlemail.com wrote:
Just for fun (and learning by doing), I have written a Salesforce component
for Apache Camel. It is not feature-complete, just some methods of the
Salesforce API are supported.
Ah cool. This would be a nice
On Wed, May 30, 2012 at 11:05 AM, Claus Ibsen claus.ib...@gmail.com wrote:
On Wed, May 30, 2012 at 10:40 AM, megachucky megachu...@googlemail.com
wrote:
Just for fun (and learning by doing), I have written a Salesforce component
for Apache Camel. It is not feature-complete, just some methods
Hi all,
I would like to test my CronScheduledRoutePolicy in my JUnit test using
org.apache.camel.test.junit4.CamelSpringTestSupport.
When I try to run my test, I get the following exception :
java.lang.NoSuchMethodError: org.quartz.Scheduler.isStarted()Z
at
I do not understand:
I shall use another existing Camel component to create a new component, e.g.
camel-restlet or camel-ahc?
Why and how? I do not have routes inside the component source code for using
these endpoints? Besides, a new component would depend on this existing
component, too...
Camel 2.6.0 use Quartz 1.8.4. Try this version.
You do not have to define this dependency by the way...
https://svn.apache.org/repos/asf/camel/tags/camel-2.6.0/parent/pom.xml
Best,
Christian
Sent from a mobile device
Am 30.05.2012 12:27 schrieb DEPREZ Arnaud AWL-IT arnaud.dep...@atos.net:
Hi
I still have the same issue with this dependency :
dependency
groupIdorg.quartz-scheduler/groupId
artifactIdquartz/artifactId
version1.8.4/version
/dependency
Arnaud Deprez
-Original Message-
From: Christian Müller [mailto:christian.muel...@gmail.com]
Sent: mercredi
Jens wrote
Claus Ibsen-2 wrote
Hi
Have you tried enabling stream caching?
http://camel.apache.org/stream-caching.html
Yes, and I also tried converting the message to a String right away but
neither change helped.
This is with Camel 2.8.3, by the way.
It seems this problem
I still have the same issue with this dependency :
dependency
groupIdorg.quartz-scheduler/groupId
artifactIdquartz/artifactId
version1.8.4/version
/dependency
Try...
mvn dependency:tree
...in the top Maven module of your project and search for the
'quartz'. Probably
Currently there is no need to perform any transforms on the request. Just a
straight pass through camel.
Sorry for my ignorance, but what would the route look like if I were to take
your suggestion of using the http endpoint to send the request?
Thank you for your response.
--
View this
Cannot find class
[org.apache.camel.processor.aggregate.AggregationStrategy]
...
osgi:reference id=aggregatorStrategyService
interface=org.apache.camel.processor.aggregate.AggregationStrategy
bean-name=aggregatorStrategy/
The most probably source of your problems is that you're got a
Hi,
I have next question:
Is it possible to pass some Camel Message Headers to File Endpoint?
Example:
1. I have jms topic and I set some custom headers in the message
2. I route from that jms topic to file endpoint
3. i consume the message from the file endpoint and I want to consume my
custom
Ok, after toying around with it I realized that I messed up the uri for the
cxfrs endpoint. I have it working now. I would still be interested in seeing
the route that send the request via the http endpoint, just to educate
myself more.
Thank you for all the help. The final route ends up looking
The file protocol doesn't support headers. You have to marshal/serialize
your message in a way which preserve your headers in the message payload.
Best,
Christian
Sent from a mobile device
Am 30.05.2012 15:22 schrieb RadoslavStoyanov
radoslav.stoya...@softwareag.com:
Hi,
I have next
Hi Radoslav,
Is it possible to pass some Camel Message Headers to File Endpoint?
Only body of a message is saved to the file. If you want save some
metadata from headers you need to append them to the body of a
message.
You could also consider using the multicast.
from(jms:queue).
Thanks, I solve the problem.
It was a conflict with another dependency :
dependency
groupIdorg.apache.openejb/groupId
artifactIdopenejb-core-osgi/artifactId
version3.1.4/version
/dependency
KR,
Arnaud Deprez
-Original Message-
From: Henryk Konsek
Hi Claus,
I just created https://issues.apache.org/jira/browse/CAMEL-5320
Thanks again for your suggestions. I think for now I found how to rely on
the clustering capabilities of my current tomcat sticky session deployments
for load balancing. If the process is initiated from a regular http
Hi Romain,
Any recommendations on how to proceed to point to release instead of
snapshot so the plugin works from my Jenkins server?
At the moment it is pointing to bunch of snapshots which clearly will not be
downloaded as we only use releases. One way could be installing it locally
in the
Hi,
I have multiple messages on the Active MQ and I have multiple destinations.
At the destination I need to read messages from the queue and decide if that
message corresponds to that destination or not.
What are the ways to implement it?
Can I use the header value to uniquely identify? Are
Hi Nestor,
currently the easier is to fork to remove snapshots.
- Romain
2012/5/30 Nestor Urquiza nestor.urqu...@gmail.com
Hi Romain,
Any recommendations on how to proceed to point to release instead of
snapshot so the plugin works from my Jenkins server?
At the moment it is pointing to
Hi Claus,
The component can be used right now without any additions, but I'd
like to include some integration tests which will check that:
1. Any camel processor (even not included into the camel route) can be
published into the OSGi service registry to process exchanges.
2. Multiple
For example, I have a queue named testqueue1 on server1.
I have messages msg1,msg2,msg3,msg4,msg5 on testqueue1.
I have multiple camel instances running on different servers, say server2,
server3,server4 which will be listening to testqueue1.
I want server2 instance to pick only msg1 and msg2,
You can use message selectors if you can distinguish your messages based on
JMS headers [1].
Otherwise you can use a topic instead of a queue and persistent consumers.
Than each JMS client will receive each message and you can use a filter [2]
to filter out messages you are not interested in.
[1]
Done (https://github.com/nestoru/diagram-generator-parent). Thanks!
--
View this message in context:
http://camel.465427.n5.nabble.com/diagram-generator-tp4375588p5713754.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Deploy your Camel routes as OSGI bundles as Claus already recommend - JBI
is dead.
Use the maven-bundle-plugin [1] to generate the needed OSGI meta data.
[1] http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
Best,
Christian
On Tue, May 22, 2012 at 10:09 AM, Claus Ibsen
Ramesh,
I was able to recreate the issue. I opened up a ticket with Camel and
attached a patch and the test case. It can be found here:
https://issues.apache.org/jira/browse/CAMEL-5321.
For the short-term you should be able to deploy the XSD files with an
absolute path on the imported XSD.
If you are using JBI, you may hit the classloader issue[1].
With OSGi, you will not hit that kind of issue any more :)
[1]http://camel.apache.org/classloader-issue-of-servicemix-camel-component.html
On 5/22/12 4:09 PM, Claus Ibsen wrote:
JBI is dead / deprecated. Don't use that.
For SMX you
30 matches
Mail list logo