Here is my use case:
I need to split a CSV file which contains orders. Parsing rules of this CSV
are very simple:
- Each order has several lines (no fix number)
- Each order begins with one line (initiator):
111;222;dynamic content
- Each order ends with two lines (terminator)
Hey guys,
at the moment, I am playing around with Amazon RDS. I also want to get a
little bit deeper into Camel internals (again). There is no camel-rds
component yet. So, if I find some time, I will create the Camel component.
However, I wonder if there is a specific reason why this component
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):
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...
I would not use BPEL anymore, but BPMN 2.0! I also would not use a
heavyweight tool such as Oracle BPEL Engine etc. Instead I would think about
using a lightweight open source BPM tool such as Activiti, jBPM or Bonita.
Take a look at my slides from CamelOne 2012:
I have create a Jira issue and added a patch already:
https://issues.apache.org/jira/browse/CAMEL-5297
If there is still any problems or missing stuff, tell me...
-
Best regards,
Kai Wauml;hner
Twitter: @KaiWaehner
Email: kont...@kai-waehner.de
Blog:
Today, I had some time to add some structure to the articles. I am not really
happy yet (because as Claus mentioned several articles are really old and
outdated - so the release date of articles is also important), I will
improve this when I find some more time. However, I think even the better
Yesterday - at the User Roundtable of CamelOne - Claus said that a scala
component (I think it was HBase?) was not added to the Camel project,
because it was written in Scala...
Therefore I wonder if it really makes sense to create components written in
Scala? Personally, I would like to see
Apache Camel is growing every month...
IMO, one single page for articles, presentations, bloggers, etc. is not
enough (http://camel.apache.org/articles.html). Besides, the site is
outdated a lot (e.g. there are so many good slides about Camel available in
the meantime).
I would suggest to either
While waiting for my flight back home from CamelOne, I have created an
archetype which generates a skeleton for a Scala component. It took longer
than I thought, because I had no experience with archetypes at all :-)
The archetype now works. The structure is the same as its Java equivalent.
The
It is really easy to create a new archetype this way. I will create an
archetype camel-archetype-component-scala soon!
--
View this message in context:
http://camel.465427.n5.nabble.com/Create-a-new-Camel-component-via-Scala-Component-Archetype-tp5708543p5709119.html
Sent from the Camel - Users
I think about writing a new Camel component (e.g. for Salesforce or Neo4j). I
also think about using Scala for the new component. However, there is only a
Java-Component-Archetype at the moment. Is this for any reason?
Should new components be in Java, too (because more people will understand
Ok, thx. I concentrated on the Splitter instead of looking at the csv, too.
My csv example is a one liner, therefore in Camel 2.6 it did not return a
List.
I was not aware of this change in Camel 2.9 - I had to change the example
code a little bit. Unfortunately, it is a little bit more code
Hello,
I am playing around with the Camel AWS component. The problems exist for SQS
and S3, same problem! Everything works fine if I use the AmazonSQSClient as
it is used in the source code of the aws component tests:
@Test
public void testFileToAmazonSQSToFileRoute() throws Exception {
Hello.
Again a question about the AWS component (S3). What is the best way to set
the CamelAwsS3Key header?
I did it this way:
from(file:files/inbox).setHeader(S3Constants.KEY, simple(Static
Key))...
The test in the source code does this:
Exchange exchange =
15 matches
Mail list logo