[ANNOUNCEMENT] Apache Camel 2.13.4 released

[Christian Mueller]

The Camel community announces the immediate availability of the new patch
release Camel 2.13.4. This release contains a total of 81 fixes applied in
the past 3 months by the community on the Camel master branch.

The artifacts are published and ready for you to download[1] either from
the Apache mirrors or from the Central Maven repository. For more details
please take a look at the release notes[2][3].
Many thanks to all who made this release possible.

[1]http://camel.apache.org/download.html
[2]https://cwiki.apache.org/confluence/display/CAMEL/Camel+2.13.4+Release
[3]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12328899&styleName=&projectId=12311211

On behalf of the Camel PMC,
Christian Mueller

[ANNOUNCEMENT] Apache Camel 2.14.2 released

[Christian Mueller]

[ANNOUNCEMENT] Apache Camel 2.14.2 released

The Camel community announces the immediate availability of the new patch
release Camel 2.14.2. This release contains a total of 101 fixes applied in
the past 3 months by the community on the Camel master branch.

The artifacts are published and ready for you to download[1] either from
the Apache mirrors or from the Central Maven repository. For more details
please take a look at the release notes[2][3].
Many thanks to all who made this release possible.

[1]http://camel.apache.org/download.html
[2]https://cwiki.apache.org/confluence/display/CAMEL/Camel+2.14.2+Release
[3]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329070&styleName=Html&projectId=12311211

On behalf of the Camel PMC,
Christian Mueller

[ANNOUNCEMENT] Apache Camel 2.15.0 released

[Christian Mueller]

The Camel community announces the immediate availability of the new major
release Camel 2.15.0. This release contains a total of 500+ fixes applied
in the past 6 months by the community on the Camel master branch.

The artifacts are published and ready for you to download[1] either from
the Apache mirrors or from the Central Maven repository. For more details
please take a look at the release notes[2][3].
Many thanks to all who made this release possible.

[1]http://camel.apache.org/download.html
[2]https://cwiki.apache.org/confluence/display/CAMEL/Camel+2.15.0+Release
[3]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12327940&styleName=&projectId=12311211


On behalf of the Camel PMC,
Christian Mueller

CVE-2015-0263 and CVE-2015-0264 - Apache Camel medium disclosure vulnerability

[Christian Mueller]

If you are using Apache Camel to route XML messages, please note that the
security advisories CVE-2015-0263 and CVE-2015-0264 may affect you.

Please study these critical security vulnerability carefully!

CVE-2015-0263 [1]
CVE-2015-0264 [2]

You can download the fixed Apache Camel 2.13.x and 2.14.x version from the
Apache mirrors [3] or from the Central Maven repository.

[1]
http://camel.apache.org/security-advisories.data/CVE-2015-0263.txt.asc?version=1&modificationDate=1426539178647&api=v2
[2]
http://camel.apache.org/security-advisories.data/CVE-2015-0264.txt.asc?version=1&modificationDate=1426539191142&api=v2
[3] http://camel.apache.org/download

On behalf of the Camel PMC,
Christian Mueller
-

Software Integration Specialist

Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member

Re: NPE with language:ruby and concurrentConsumers

[Christian Mueller]

Hi Christoph!

I raised the JIRA https://issues.apache.org/jira/browse/CAMEL-8201 and start
working on it.
I could successfully check, the issue is in Camel and not in JRuby. Add
yourself as watcher on the JIRA to keep you up to date...

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/NPE-with-language-ruby-and-concurrentConsumers-tp5759703p5761196.html
Sent from the Camel - Users mailing list archive at Nabble.com.

[ANNOUNCE] Apache Camel 2.13.3 Released

[Christian Mueller]

The Apache Camel project [1] is a powerful open source integration
framework based on known Enterprise Integration Patterns [2].

The Camel community announces the immediate availability of the new patch
release camel-2.13.3.

The artifacts are published and ready for you to download [3] either from
the Apache mirrors or from the Central Maven repository.
For more details please take a look at the release notes [4].

Many thanks to the Camel community for the hard work.

Christian

[1]http://camel.apache.org/
[2]http://camel.apache.org/enterprise-integration-patterns.html
[3]http://camel.apache.org/download.html
[4]http://camel.apache.org/camel-2133-release.html

[ANNOUNCE] Apache Camel 2.12.5 Released

[Christian Mueller]

The Apache Camel project [1] is a powerful open source integration
framework based on known Enterprise Integration Patterns [2].

The Camel community announces the immediate availability of the new patch
release camel-2.12.5.

The artifacts are published and ready for you to download [3] either from
the Apache mirrors or from the Central Maven repository.
For more details please take a look at the release notes [4].

Many thanks to the Camel community for the hard work.

Christian

[1] http://camel.apache.org/
[2] http://camel.apache.org/enterprise-integration-patterns.html
[3] http://camel.apache.org/download.html
[4] http://camel.apache.org/camel-2125-release.html

Re: ActiveMQ InOut JMS messaging with external system

[Christian Mueller]

Have a look at [1].

[1]
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsBinding.java;h=84b20a28fc73da7ff55ff4ad61dde64f2ed8ceb3;hb=HEAD

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/ActiveMQ-InOut-JMS-messaging-with-external-system-tp5757630p5758112.html
Sent from the Camel - Users mailing list archive at Nabble.com.

[ANNOUNCE] CVE-2014-0002 and CVE-2014-0003 - Apache Camel critical disclosure vulnerability

[Christian Mueller]

If you are using the Apache Camel XSLT component, please note that the
security advisories CVE-2014-0002 and CVE-2014-0003 may affect you.

Please study these critical security vulnerability carefully!

http://camel.apache.org/security-advisories.data/CVE-2014-0002.txt.asc
http://camel.apache.org/security-advisories.data/CVE-2014-0003.txt.asc

You can download the fixed Apache Camel 2.11.x and 2.12.x version from the
Apache mirrors or from the Central Maven repository.

[1] http://camel.apache.org/xslt
[2] http://camel.apache.org/download

On behalf of the Camel PMC,
Christian

Re: Getting rid of line separator [ BeanIO + Camel ]

[Christian Mueller]

RG,

can you please subscribe to the Camel user mailing list as we describe here
[1].
Otherwise all your mails has to be moderate manually by the Camel team so
that your post is also send to our mailing list which most of the Camel team
member are using instead of Nabble. Therefore your post is may
missed/delayed and you don't get an answer in the normal time frame we
answer questions.
Last but not least, it cost time which we cannot spend developing Camel,
answering questions or improving the documentation...

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Getting-rid-of-line-separator-BeanIO-Camel-tp5741859p5741863.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Restlet and HTTP 302

[Christian Mueller]

Abhijit,

can you please subscribe to the Camel user mailing list as we describe here
[1].
Otherwise all your mails has to be moderate manually by the Camel team so
that your post is also send to our mailing list which most of the Camel team
member are using instead of Nabble. Therefore your post is may
missed/delayed and you don't get an answer in the normal time frame we
answer questions.
Last but not least, it cost time which we cannot spend developing Camel,
answering questions or improving the documentation...

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Restlet-and-HTTP-302-tp5741853p5741862.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Being able to post and reveice email notification to subscribed posts

[Christian Mueller]

This is how we work in the ASF - with mailing lists. You can subscribe to the
lists you are interested in it and follow the discussions.

Nabble != ASF mailing list. Therefor, the ASF mailing list doesn't know
whether you are an registered user on Nabble or not.

Nabble is only one of the discussion forums which is kind like subscribed to
our mailing list. You can find your post on many more places like the mail
archive [1] and so on...

Reading questions from other users and of course the responses will also
help you to be a more experienced Camel developer in the future. If this is
you goal, you should consider subscribing to the mailing list (and may help
other users in the future - this is how open source works...).

[1]
http://mail-archives.apache.org/mod_mbox/camel-users/201310.mbox/%3C1381947855386-5741693.post%40n5.nabble.com%3E

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Being-able-to-post-and-reveice-email-notification-to-subscribed-posts-tp5741693p5741761.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Add new route runtime

[Christian Mueller]

Reji,

can you please subscribe to the discussion forum in Nabble as we describe
here [1].
Otherwise all your mails has to be moderate manually by the Camel team so
that your post is also send to our mailing list which most of the Camel team
member are using instead of Nabble. Therefore your post is may
missed/delayed and you don't get an answer in the normal time frame we
answer questions.
Last but not least, it cost time which we cannot spend developing Camel,
answering questions or improving the documentation...

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Add-new-route-runtime-tp5741694p5741758.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Being able to post and reveice email notification to subscribed posts

[Christian Mueller]

That's true. Your mail will not be forwarded to the mailing list until one of
the forum moderators moderate your mail. This may take a while and cost a
bit of time from the moderators... That's why we don't prefer this way and
ask the users to subscribe to the mailing list.

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Being-able-to-post-and-reveice-email-notification-to-subscribed-posts-tp5741693p5741757.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: CFX-Bean:headers access Issue

[Christian Mueller]

Amit,

can you please subscribe to the discussion forum in Nabble as we describe
here [1].
Otherwise all your mails has to be moderate manually by the Camel team so
that your post is also send to our mailing list which most of the Camel team
member are using instead of Nabble. Therefore your post is may
missed/delayed and you don't get an answer in the normal time frame we
answer questions.
Last but not least, it cost time which we cannot spend developing Camel,
answering questions or improving the documentation...

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/CFX-Bean-headers-access-Issue-tp5741312p5741705.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: No component found with scheme:wmq1

[Christian Mueller]

Have a look at the following article [1].
And please subscribe to the discussion forum in Nabble as we describe here
[2].

[1]
http://lowry-techie.blogspot.pt/2010/11/camel-integration-with-websphere-mq.html
[2] http://camel.apache.org/discussion-forums.html

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/No-component-found-with-scheme-wmq1-tp5741642p5741664.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Can't move excel files correctly, ActiveMQ bug?

[Christian Mueller]

Niels_S,

can you please subscribe to the discussion forum in Nabble as we describe
here [1].
Otherwise all your mails has to be moderate manually by the Camel team so
that your post is also send to our mailing list which most of the Camel team
member are using instead of Nabble. Therefore your post is may
missed/delayed and you don't get an answer in the normal time frame we
answer questions.
Last but not least, it cost time which we cannot spend developing Camel,
answering questions or improving the documentation...

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Can-t-move-excel-files-correctly-ActiveMQ-bug-tp5741661p5741663.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Is it possible to retrieve a stream for a Exchange Body?

[Christian Mueller]

Niels_s, 

can you please subscribe to the discussion forum in Nabble as we describe
here [1].
Otherwise all your mails has to be moderate manually by the Camel team so
that your post is also send to our mailing list which most of the Camel team
member are using instead of Nabble. Therefore your post is may
missed/delayed and you don't get an answer in the normal time frame we
answer questions.
Last but not least, it cost time which we cannot spend developing Camel,
answering questions or improving the documentation...

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Is-it-possible-to-retrieve-a-stream-for-a-Exchange-Body-tp5740229p5741659.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: failed to go activemq

[Christian Mueller]

Ravish4596,

can you please subscribe to the discussion forum in Nabble as we describe
here [1].
Otherwise all your mails has to be moderate manually by the Camel team so
that your post is also send to our mailing list which most of the Camel team
member are using instead of Nabble. Therefore your post is may
missed/delayed and you don't get an answer in the normal time frame we
answer questions.
Last but not least, it cost time which we cannot spend developing Camel,
answering questions or improving the documentation...

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/failed-to-go-activemq-tp5741651p5741658.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: No component found with scheme:wmq1

[Christian Mueller]

Dssankar,

can you please subscribe to the discussion forum in Nabble as we describe
here [1].
Otherwise all your mails has to be moderate manually by the Camel team so
that your post is also send to our mailing list which most of the Camel team
member are using instead of Nabble. Therefore your post is may
missed/delayed and you don't get an answer in the normal time frame we
answer questions.
Last but not least, it cost time which we cannot spend developing Camel,
answering questions or improving the documentation...

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/No-component-found-with-scheme-wmq1-tp5741642p5741657.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Working with POJO in with a cxc endpoint

[Christian Mueller]

Juliang,

can you please subscribe to the discussion forum in Nabble as we describe
here [1].
Otherwise all your mails has to be moderate manually by the Camel team so
that your post is also send to our mailing list which most of the Camel team
member are using instead of Nabble. Therefore your post is may
missed/delayed and you don't get an answer in the normal time frame we
answer questions.
Last but not least, it cost time which we cannot spend developing Camel,
answering questions or improving the documentation...

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Working-with-POJO-in-with-a-cxc-endpoint-tp5741630p5741656.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: doneFileName=${file:name} in Camel 2.12.1 doesn't get replaced correctly with camel-spring-batch

[Christian Mueller]

Nguyen,

can you please subscribe to the discussion forum in Nabble as we describe
here [1].
Otherwise all your mails has to be moderate manually by the Camel team so
that your post is also send to our mailing list which most of the Camel team
member are using instead of Nabble. Therefore your post is may
missed/delayed and you don't get an answer in the normal time frame we
answer questions.
Last but not least, it cost time which we cannot spend developing Camel,
answering questions or improving the documentation...

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/doneFileName-file-name-in-Camel-2-12-1-doesn-t-get-replaced-correctly-with-camel-spring-batch-tp5740839p5741654.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Apache Camel multithread processing

[Christian Mueller]

Astorath, can you please subscribe to the discussion forum as we describe
here [1]. Otherwise all your mails has to be moderate by the Camel team and
is may missed/delayed.

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian 



--
View this message in context: 
http://camel.465427.n5.nabble.com/Apache-Camel-multithread-processing-tp5741383p5741446.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Email Attachments - Adding to Exchange Attachments

[Christian Mueller]

Contactreji, can you please subscribe to the discussion forum as we describe
here [1]. Otherwise all your mails has to be moderate by the Camel team and
is may missed/delayed.

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian 



--
View this message in context: 
http://camel.465427.n5.nabble.com/Email-Attachments-Adding-to-Exchange-Attachments-tp5739863p5741445.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel with Multiple types of Endpoints

[Christian Mueller]

Can you please subscribe to the discussion forum as we describe here [1].
Otherwise all your mails has to be moderate by the Camel team and is may
missed/delayed.

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian 



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-with-Multiple-types-of-Endpoints-tp5741306p5741310.html
Sent from the Camel - Users mailing list archive at Nabble.com.

RE: How to consume from AMQP queue in "browsing mode" with Apache Camel?

[Christian Mueller]

Can you please subscribe to the discussion forum as we describe here [1].
Otherwise all your mails has to be moderate by the Camel team and is may
missed/delayed.

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian 



--
View this message in context: 
http://camel.465427.n5.nabble.com/How-to-consume-from-AMQP-queue-in-browsing-mode-with-Apache-Camel-tp5726756p5741242.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel and PostgreSQL

[Christian Mueller]

Can you please subscribe to the discussion forum as we describe here [1].
Otherwise all your mails has to be moderate by the Camel team and is may
missed/delayed.

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-and-PostgreSQL-tp5741232p5741241.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Getting route info problems

[Christian Mueller]

Can you please subscribe to the discussion forum as we describe here [1].
Otherwise all your mails has to be moderate by the Camel team and is may
missed/delayed.

[1] http://camel.apache.org/discussion-forums.html

Thanks in advance,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Getting-route-info-problems-tp5741123p5741150.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Revoked contribution rights.

[Christian Mueller]

I can see you edited [1] today. So, I consider this issue as resolved.

[1] https://cwiki.apache.org/confluence/display/CAMEL/Component+List+Grouped

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Revoked-contribution-rights-tp5740922p5740978.html
Sent from the Camel - Users mailing list archive at Nabble.com.

[ANNOUNCEMENT] Apache Camel 2.11.2 released

[Christian Mueller]

The Camel community announces the immediate availability of the new patch
release Camel 2.11.2. This bug fix release is issued after 2 month of
intense efforts of the Camel 2.11.x maintenance branch and resolves 120
issues in total.

The artifacts are published and ready for you to download [1] either from
the Apache mirrors or from the Central Maven repository. For more details
please take a look at the release notes [2].

Many thanks to all who made this release possible.

[1] http://camel.apache.org/download.html
[2]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324654

On behalf of the Camel PMC,
Christian

[ANNOUNCEMENT] Apache Camel 2.12.1 released

[Christian Mueller]

The Camel community announces the immediate availability of the new patch
release Camel 2.12.1. This bug fix release is issued after only 9 days of
intense efforts of the Camel 2.12.x maintenance branch and resolves 47
issues in total. We release this version in short term after 2.12.0 to
provide the latest fixes for the upcoming Apache ActiveMQ 5.9.0 release.

The artifacts are published and ready for you to download [1] either from
the Apache mirrors or from the Central Maven repository. For more details
please take a look at the release notes [2].

Many thanks to all who made this release possible.

[1] http://camel.apache.org/download.html
[2]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324857

On behalf of the Camel PMC,
Christian

[ANNOUNCEMENT] Apache Camel 2.10.7 Released

[Christian Mueller]

The Camel community announces the immediate availability of the new patch
release Camel 2.10.7. This bug fix release is issued after 2 months of
intense efforts of the Camel 2.10.x maintenance branch and resolves 63
issues in total.

The artifacts are published and ready for you to [download|
http://camel.apache.org/download.html] either from the Apache mirrors or
from the Central Maven repository. For more details please take a look at
the [release notes|
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324667
].

Many thanks to all who made this release possible.

On behalf of the Camel PMC,
Christian

Re: MailComponent/MailConsumer misses Mails

[Christian Mueller]

I just updated Camel 2.11.1-SNAPSHOT to javax.mail/mail from 1.4.5 to 1.4.7
without any problems. Could you please try Camel 2.11.0 with javax.mail/mail
1.4.7?

I don't think it's a Camel issue, but we have to investigate a bit more...

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/MailComponent-MailConsumer-misses-Mails-tp5733010p5735315.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Apache Camel 2.10.5 released

[Christian Mueller]

The Camel community announces the immediate availability of the new patch
release camel-2.10.5. This bug fix release is issued after 4 months of
intense efforts of the Camel 2.10.x maintenance branch and resolves 108
issues.

This is our first release which comes from our new Git
repository
.

The artifacts are published and ready for you to
downloadeither from the Apache
mirrors or from the Central Maven repository. For
more details please take a look at the release
notes
.

Many thanks to all who made this release possible.

Christian

WireTap doesn't process the messages in the order they arrived for each message

[Christian Mueller]

The following test fails randomly fails at message 6 up to 961 (on my
machine). I consider this as an bug:

public class WireTapTest extends CamelSpringTestSupport {

private int counter = 1;

@Test
public void test() throws InterruptedException {
getMockEndpoint("mock:result").expectedMessageCount(counter * 2);

template.setDefaultEndpointUri("direct:start");
for (int i = 0; i < counter; i++) {
template.requestBody("Camel");
}

assertMockEndpointsSatisfied();

List receivedExchanges =
getMockEndpoint("mock:result").getReceivedExchanges();
for (int i = 0; i < receivedExchanges.size(); i++) {
System.out.println("check exchange number " + i);

String body =
receivedExchanges.get(i).getIn().getBody(String.class);
if (i % 2 == 0) {
assertEquals("REQUEST", body);
} else {
assertEquals("RESPONSE", body);
}
}
}

@Override
protected AbstractApplicationContext createApplicationContext() {
return new ClassPathXmlApplicationContext("bundle-context.xml");
}
}

which is using the following route:
public class WireTapRouteBuilder extends RouteBuilder {

@Override
public void configure() throws Exception {
from("direct:start")
.wireTap("seda:wireTap").executorServiceRef("executorService")
.setHeader("TYPE", constant("RESPONSE"))
.wireTap("seda:wireTap").executorServiceRef("executorService");

from("seda:wireTap")
.choice()
.when(header("TYPE").isNull())
.setBody(constant("REQUEST"))
.to("mock:result")
.otherwise()
.setBody(constant("RESPONSE"))
.to("mock:result")
.end();
}
}

and the following configuration:
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:camel="http://camel.apache.org/schema/spring";
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd";>










We use the wiretap to send messages to an endpoint which persist some key
information about the execution in a database. It's important for us to
persist the messages into the database in the same order as they arrive in
the seda endpoint. Because of this, we configured the threadPoolProfile to
only use one thread. But some times the messages receive in the reverse
order in our database/mock endpoint.

Any suggestions what is wrong here?

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/WireTap-doesn-t-process-the-messages-in-the-order-they-arrived-for-each-message-tp5731733.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Parallel Route processing

[Christian Mueller]

I suggest something like:
from("cxf:bean:myService") // my preferred web service stack. See [1]
  .to("bean:processor") // can be a processor, bean, ... instance. See [2]
  .inOnly("seda:processAsync"); // or activemq, ... See [3], [4]

from("seda:processAsync")
  .to("...");

[1] http://camel.apache.org/cxf.html
[2] http://camel.apache.org/bean.html
[3] http://camel.apache.org/seda.html
[4] http://camel.apache.org/activemq.html

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Parallel-Route-processing-tp5730817p5730826.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Facebook component

[Christian Mueller]

Duplicate of
http://camel.465427.n5.nabble.com/Facebook-Component-td5730618.html



--
View this message in context: 
http://camel.465427.n5.nabble.com/Facebook-component-tp5730617p5730735.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Google Drive Component

[Christian Mueller]

Looking forward to have a look at the component when you could finished it.
You may consider to donate the component to Apache Camel [1] [2]?

[1] http://camel.apache.org/contributing.html
[2] http://camel.apache.org/building.html

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Google-Drive-Component-tp5730671p5730734.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: How, exactly, to get the vm component to work

[Christian Mueller]

Our unit tests are a good source [1].

[1]
https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/org/apache/camel/component/vm/

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/How-exactly-to-get-the-vm-component-to-work-tp5730678p5730733.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: If Exchange was handled(true), only first Processor in doFinally() is executed

[Christian Mueller]

What do you mean by "/When handled(true), only first processor from
DIRECT_RESPONSE_PATH_ENDPOINT is executed!/"?

What's the value of DIRECT_RESPONSE_PATH_ENDPOINT?

I created the following unit test which passed:

public class TryCatchFinallyTest extends ContextTestSupport {

public void testTryCatchCaughtExceptionFinally() throws Exception {
getMockEndpoint("mock:a").expectedMessageCount(1);
getMockEndpoint("mock:b").expectedMessageCount(1);
getMockEndpoint("mock:c").expectedMessageCount(1);
getMockEndpoint("mock:d").expectedMessageCount(1);
getMockEndpoint("mock:e").expectedMessageCount(1);
getMockEndpoint("mock:result").expectedMessageCount(1);

template.sendBody("direct:start", "Hello World");

assertMockEndpointsSatisfied();
}

@Override
protected RouteBuilder createRouteBuilder() throws Exception {
return new RouteBuilder() {
public void configure() throws Exception {
from("direct:start")
.doTry()
.to("mock:a")
.throwException(new Exception("boom"))
.doCatch(Exception.class)
.to("mock:b")
.to("mock:c")
.doFinally()
.to("mock:d")
.to("mock:e")
.end()
.to("mock:result");
}
};
}
}

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/If-Exchange-was-handled-true-only-first-Processor-in-doFinally-is-executed-tp5730705p5730732.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Accessing CamelLoopIndex in route

[Christian Mueller]

Try:
.when(simple("${header[CamelFileName]} contains ${header[CamelLoopIndex]}"))

You can find more about the simple language at [1].

[1] http://camel.apache.org/simple.html

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Accessing-CamelLoopIndex-in-route-tp5730719p5730731.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Is there a standard, DSL way to put message body in registry?

[Christian Mueller]

No, we do not have such a component at present.

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Is-there-a-standard-DSL-way-to-put-message-body-in-registry-tp5730717p5730730.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: File and FTP Components

[Christian Mueller]

Camel 2.11.0 is under vote and you can expect it beginning of next week.

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/File-and-FTP-Components-tp5730723p5730729.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: JMS Component - Customized messageConverter

[Christian Mueller]

You must be subscribed to the mailing list as we mentioned at [1]. Otherwise
the post is not forwarded to the mailing list and recognized by most of the
users/contributors/committers.

[1] http://camel.apache.org/discussion-forums.html

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/JMS-Component-Customized-messageConverter-tp5730725p5730728.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel JDBC 1.6.1

[Christian Mueller]

This is fixed some time ago...
Is it possible for you to upgrade to 2.10.0 or so?
If not, you can use the Content Enricher Pattern [2] to work around this
issue.

[1]
https://svn.apache.org/repos/asf/camel/trunk/components/camel-jdbc/src/main/java/org/apache/camel/component/jdbc/JdbcProducer.java
[2] http://camel.apache.org/content-enricher.html

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-JDBC-1-6-1-tp5716995p5717028.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Routes in camel console don't persist?

[Christian Mueller]

You should subscribe to the list. Otherwise you post is not forwarded to the
mailing list where most of the developers listening...
Checkout http://camel.apache.org/discussion-forums.html

Best,
Christian



--
View this message in context: 
http://camel.465427.n5.nabble.com/Routes-in-camel-console-don-t-persist-tp5717010p5717015.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-jaxb namespace prefix

[Christian Mueller]

See
http://docs.oracle.com/javase/6/docs/api/javax/xml/bind/annotation/XmlSchema.html
how to customize the namespace prefix.
Use the "-npa" option from the xjc compiler or maven-jaxb2-plugin to prevent
to update the package-info.java file.

--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-jaxb-namespace-prefix-tp5685354p5703483.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Welcome Bilgin Ibryam as Apache Camel committer

[Christian Mueller]

Two days ago the Camel PMC voted another one of the very active and talented 
contributors to become a committer.

Bilgin Ibryam was actively involved with Apache Camel for about 6 month 
contributing code and helping other users. Bilgin proactively assigned reported 
issues to himself and took them to resolution acting as a committer. He is 
already a committer for the Apache OFBiz project and know how Apache works. In 
recognition of his work, the PMC only had to take care of the simple task of 
making that official. Today, Bilgin got his committer account setup, concluding 
the process of becoming the newest Camel rider. Stay tuned for his first 
official commit. ;-)

On behalf of the Camel PMC, welcome aboard Bilgin and keep up the great work!

Christian

signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Improvement of the Idempotent Repository

[Christian Mueller]

Done: https://issues.apache.org/jira/browse/CAMEL-3975

--
View this message in context: 
http://camel.465427.n5.nabble.com/Improvement-of-the-Idempotent-Repository-tp4282010p4395346.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Improvement of the Idempotent Repository

[Christian Mueller]

No opinions about this?

Best,
christian

--
View this message in context: 
http://camel.465427.n5.nabble.com/Improvement-of-the-Idempotent-Repository-tp4282010p4384036.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: SAXParseException by receiving a CXF web service response

[Christian Mueller]

Hello Willem!

Sorry for not answering so long, but last week I worked together with Ade on
a production issue for one of our customers...

We see this issue (more) often in our stress tests. We use the same request,
but changing one of the request identifiers (e.g. the financial transaction
id). We are using
{noformat}
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
{noformat}

on
{noformat}
Red Hat Enterprise Linux Server release 5.4 (Tikanga)
{noformat}

Our camel cxf configuration looks like the following:
{code}
  http://server:8080/services/OrderEntry";

serviceClass="com.company.product.interfaces.module.OrderEntryWebService"
endpointName="xxx:OrderEntryWebServicePort"
serviceName="xxx:OrderEntryService"
wsdlURL="META-INF/product/module/orderEntry.wsdl"
xmlns:xxx="http://www.company.com/module/services/1_0_0";>

















  
{code}

The WSDL file, the XSD file and the generated sources are imported from a
different bundle (which only generates the sources and packge it together
with the WSDL and XSD files) because we use it in multiple bundles.

It's not possible to run these services in an actual SMX version in short
time, because this requires some code changes. We also work on an upgrade to
SMX 4.3.1-fuse-xx-yy, but it take some time...

Best,
Christian

On Mon, Apr 18, 2011 at 5:28 AM, Willem.Jiang [via Camel] <
ml-node+4309922-425547214-65...@n5.nabble.com> wrote:

> Hi Christian,
>
> I need more information before digging into the issue.
> Are there lots of requests send the camel route at the same time?
> Are there request message are same?
>
> Which version of JDK are you using, there are some known JAXP issues
> that we fixed with Fuse ESB recently.
> Can you try to run the test with latest released Fuse ESB ?
>
> Willem
>
>
> On 4/18/11 5:52 AM, Christian Mueller wrote:
>
> > Hello list!
> >
> > We are using Camel 2.2.0-fuse-02-00 and receiving some times (not all
> times)
> > the following exception by validating the response against the WSDL file:
>
> >
> > {noformat}
> > --
> >
> > 2011-04-15 16:55:22,527 | INFO  | qtp-1596710415-1 | LoggingInInterceptor
>
> > | interceptor.LoggingInInterceptor  164 | Inbound Message
> >
> > 
> >
> > ID: 1032
> >
> > Response-Code: 200
> > Encoding: UTF-8
> > Content-Type: text/xml;charset=utf-8
> > Headers: {content-type=[text/xml;charset=utf-8], Date=[Fri, 15 Apr 2011
> > 14:55:22 GMT], transfer-encoding=[chunked], Server=[Apache-Coyote/1.1]}
> >
> > Payload: > xmlns:S="http://schemas.xmlsoap.org/soap/envelope/";> > xmlns="http://www.company.com/ssp-core/services/1_0_0";
> > xmlns:ns2="
> http://www.company.com/ssp/dictionary/1_0_0";>...
> >
> > --
> > 2011-04-15 16:55:22,532 | WARN  | qtp-1596710415-1 |
> EndpointReferenceUtils
> > | .cxf.wsdl.EndpointReferenceUtils  718 | SAXException for newSchema()
> > org.xml.sax.SAXParseException: s4s-elt-invalid-content.1: The content of
> > 'schema' is invalid.  Element 'import' is invalid, misplaced, or occurs
> too
> > often.
> >  at
> >
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown
>
> > Source)
> >  at
> > com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Unknown
>
> > Source)
> >  at
> >
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown
>
> > Source)
> >  at
> >
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(Unknown
>
> > Source)
> >  at
> >
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
>
> > Source)
> >  at
> >
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseSchemas(Unknown
>
> > Source)
> >  at
> >
> com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(Unknown
>
> > Source)
> >  at
> >
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(Unknown
>
> > Source)
> >  at
> >
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(Unknown
>
> > Source)
> >  at
&g

Re: SMPP Route Configuration

[Christian Mueller]

Looks like your SMSC is not running at localhost and port 2775.

Christian

--
View this message in context: 
http://camel.465427.n5.nabble.com/SMPP-Route-Configuration-tp4335396p4336962.html
Sent from the Camel - Users mailing list archive at Nabble.com.

SAXParseException by receiving a CXF web service response

[Christian Mueller]

Hello list!

We are using Camel 2.2.0-fuse-02-00 and receiving some times (not all times)
the following exception by validating the response against the WSDL file:

{noformat}
--

2011-04-15 16:55:22,527 | INFO  | qtp-1596710415-1 | LoggingInInterceptor   
 
| interceptor.LoggingInInterceptor  164 | Inbound Message



ID: 1032

Response-Code: 200
Encoding: UTF-8
Content-Type: text/xml;charset=utf-8
Headers: {content-type=[text/xml;charset=utf-8], Date=[Fri, 15 Apr 2011
14:55:22 GMT], transfer-encoding=[chunked], Server=[Apache-Coyote/1.1]}

Payload: http://schemas.xmlsoap.org/soap/envelope/";>http://www.company.com/ssp-core/services/1_0_0";
xmlns:ns2="http://www.company.com/ssp/dictionary/1_0_0";>...

--
2011-04-15 16:55:22,532 | WARN  | qtp-1596710415-1 | EndpointReferenceUtils 
 
| .cxf.wsdl.EndpointReferenceUtils  718 | SAXException for newSchema()
org.xml.sax.SAXParseException: s4s-elt-invalid-content.1: The content of
'schema' is invalid.  Element 'import' is invalid, misplaced, or occurs too
often.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.traverseSchemas(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(Unknown
Source)
at
com.sun.org.apache.xerces.internal.jaxp.validation.XMLSchemaFactory.newSchema(Unknown
Source)
at
org.apache.cxf.wsdl.EndpointReferenceUtils.createSchema(EndpointReferenceUtils.java:712)
at
org.apache.cxf.wsdl.EndpointReferenceUtils.getSchema(EndpointReferenceUtils.java:739)
at
org.apache.cxf.interceptor.AbstractInDatabindingInterceptor.setSchemaInMessage(AbstractInDatabindingInterceptor.java:110)
at
org.apache.cxf.interceptor.AbstractInDatabindingInterceptor.getDataReader(AbstractInDatabindingInterceptor.java:95)
at
org.apache.cxf.interceptor.AbstractInDatabindingInterceptor.getDataReader(AbstractInDatabindingInterceptor.java:100)
at
org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:69)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:700)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2261)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2134)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1988)
at
org.apache.cxf.io.CacheAndWriteOutputStream.postClose(CacheAndWriteOutputStream.java:47)
at
org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:188)
at
org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
at
org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:639)
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:487)
at
org.apache.camel.component.cxf.CxfProducer.process(CxfProducer.java:146)
at
org.apache.camel.processor.SendProcessor$1.doInProducer(SendProcessor.java:97)
at
org.apache.camel.processor.SendProcessor$1.doInProducer(SendProcessor.java:95)
at
org.apache.camel.impl.ProducerCache.doInProducer(ProducerCache.java:146)
at
org.apache.camel.processor.SendProcessor.doProcess(SendProcessor.java:94)
at
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:82)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:67)
at
org.apache.camel.processor.DelegateProcessor.processNext(DelegateProcessor.java:53)
at
org.apache.camel.processor.DelegateProcessor.proceed(DelegateProcessor.java:82)
at
org.apache.camel.processor.interceptor.TraceIntercepto

Re: Problem with multiple CXF services using the same https port

[Christian Mueller]

Thank you all for your help on this example.
I think this is a very useful feature for all people which use excessive
camel-cxf in multiple different bundles (like we). Without this (and we did
it in the past), we have to choose a different port for each web service we
provided and we had to duplicate the SSL configuration for each service.
Now, it's much more easier to configure and maintain. We only have to
configure PAX WEB in org.ops4j.pax.web.cfg and everything is done.

Thank you again,
Christian

P.S.: Ade, may be a good topic for a further webinar about CXF? ;o)


--
View this message in context: 
http://camel.465427.n5.nabble.com/Problem-with-multiple-CXF-services-using-the-same-https-port-tp3379301p4296566.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: aggregator - error handling default does not propogate error

[Christian Mueller]

Claus, this is unfortunately not the same behavior we found out with the
enrich processor (which also use the AggregationStrategy).
We can reproduce the following behavior (with Camel 2.6):
- If the exception is handled, the exception is not anymore set in the
exchange (exchange.getException() as you suggested in your book doesn't
work). We have to grab the exception from the exchange property
Exchange.CAUSED_EXCEPTION.
- If the exception is not handled, the AggregationStrategy is not called.

Please see also also my post at [1] where I got no response... :-(.

Is this the expected behavior (and we have to document it) or should I raise
a JIRA for it?

Thank you in advance,
Christian

[1]
http://camel.465427.n5.nabble.com/Behavior-of-AggregationStrategy-in-conjunction-with-the-enrich-DSL-the-onException-definition-and-ann-td3695716.html


--
View this message in context: 
http://camel.465427.n5.nabble.com/aggregator-error-handling-default-does-not-propogate-error-tp4283684p4290872.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Behavior of AggregationStrategy in conjunction with the enrich DSL, the onException definition and an Exception

[Christian Mueller]

Hello list!

I have a question related to the
org.apache.camel.processor.aggregate.AggregationStrategy in conjunction with
the enrich DSL, the onException definition and a thrown exception (we are
using Camel 2.2.0-fuse-02-00).

Our simplified route looks like the following:
{code}
onException(Exception.class)
.maximumRedeliveries(0)
.handled(true)
.inOnly("seda:queue:wsResponseFile")
.end();

from("direct:start")
.split(body(String.class).tokenize("\n"))
.enrich("direct:subroute", new MySubrouteAggregationStrategy())
.inOnly("seda:queue:wsResponseFile")
.end();

from("direct:subroute").process(new Processor() {
public void process(Exchange exchange) throws Exception {
throw new Exception("forced Exception");
}
})
.end();
{code}

In this configuration, the "MySubrouteAggregationStrategy" is called.

If I set "handled(false)" in my onException definition, the
"MySubrouteAggregationStrategy" is _NOT_called.

Is this an expected behavior? I didn't found any documentation about the
expected behavior...

Camel 2.6.0 has the same behavior...

Thank you in advance,
Christian

--
View this message in context: 
http://camel.465427.n5.nabble.com/Behavior-of-AggregationStrategy-in-conjunction-with-the-enrich-DSL-the-onException-definition-and-ann-tp3695716p3695716.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Problem with multiple CXF services using the same https port

[Christian Mueller]

I could successful downgrade the
camel-example-reportincident-ws-security-osgi to Camel 2.2.0 (to deploy it
into ServiceMix 4.2.0-fuse-02-00) with only one little Code change.

I added "META-INF.cxf.osgi," to Import-Package definition in the pom.xml.

I removed the following import from camel-context.xml


I added the following two imports in camel-context.xml



I changed the address in cxf:cxfEndpoint to
address="/camel-example-reportincident/webservices/incident"

AND IT WORKS!!!

Must be something wrong in my code. I will analyze this and add an FAQ entry
and/or a new camel-example-reportincident-osgi example (at present we do not
have an example which use the Camel CXF bean binding in OSGI with a
cxfEndpoint configuration using a relative path without protocol, host or
port).

Thanks Willem and Charles for your help. I will keep you posted...
Christian


--
View this message in context: 
http://camel.465427.n5.nabble.com/Problem-with-multiple-CXF-services-using-the-same-https-port-tp3379301p3410289.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Problem with multiple CXF services using the same https port

[Christian Mueller]

Thank you Charles and Willem for your responses!

I try to collect the information I received from you:
- I do not have to change my cxfEndpoint configuration. It can/should looks
like the following:



- In my Spring configuration, the cxf resource imports should looks like the
following:
   
   
   
   

This means I have to remove the import:
   

And add the imports:
   
   

I still have to questions:
- The import of the resource "META-INF/cxf/osgi/cxf-extension-osgi.xml"
introduce a dependency to OSGI which we normaly configure in a separate
Spring configuration (bundle-context-OSGI.xml). Should we put this import
into bundle-context-OSGI.xml and in our unit tests, which didn't load this
Spring configuration, we should import another or no additional resource?
- If I want test this route in a normal unit test (no OSGI environment), do
I have to start e.g. Jetty be myself and CXF will detect this and use the
Jetty? Is there any code you can share with me?
- Something else I have to have in mind?

Thanks in advance,
Christian


--
View this message in context: 
http://camel.465427.n5.nabble.com/Problem-with-multiple-CXF-services-using-the-same-https-port-tp3379301p3409357.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Problem with multiple CXF services using the same https port

[Christian Mueller]

Me again...
In my privios mail I forgot to mention that our Camel bundles will be
deployed into ServiceMix and we will use PAX Web to configure (HTTPS) and
start a Jetty instance.
It would be nice if we can (re-) use this instance. If this is possible, we
have a centralized Web/Jetty configuration and doesn't have to configure
each Bundle (protocol, port, keystore, password, ...).

Christian


--
View this message in context: 
http://camel.465427.n5.nabble.com/Problem-with-multiple-CXF-services-using-the-same-https-port-tp3379301p3409094.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Problem with multiple CXF services using the same https port

[Christian Mueller]

Hello Willem!

I have the same problem... :-(
I will try to describe the problem and ask my question again:
In our integration project we use multiple Camel OSGI bundles which expose
multiple web servives (via Camel CXF consumer). We use the
camel-cxf:cxfEndpoint configuration (including properties and interceptors)
with an address like address="
https://0.0.0.0:8443/Services/OrderEntryService"; and the
httpj:engine-factory configuration (see my first post).

We have the problem, that we have to configure a different port for each web
service we expose to prevent the Could not start Jetty server: Address
already in use: JVM_Bind Exception (also in my first post).

Charles suggested to use an address like
address="/Services/OrderEntryService". My questions are:
- At present, I use in my route from("cxf:bean:orderEntryService"). Do I
have to use now from(cxf:/Services/OrderEntryService?...) or is it also
possible with the CXF bean binding?
- If I can still use the CXF bean binding: I didn't found any unit test or
example which test/shows this possibility. Currently I don't know how I can
test this (I think I have to start Jetty and configure it for HTTPS in my
set up method).
- If I have to use from("cxf:/Services/OrderEntryService"), how I can
configure our cxf properties (e.g. schema-validation-enabled) and
interceptors?

In short: My goal is to provide multiple web services (Apache CXF consumers)
which use the same port for the HTTPS configuration. It should be possible
to switch to HTTP without touching my Spring configuration (only my
externalized environment specific properties).

The next FAQ entry I would like to write... ;-)

Christian

On Fri, Mar 4, 2011 at 5:48 AM, Willem.Jiang [via Camel] <
ml-node+3408939-1332669798-65...@n5.nabble.com> wrote:

> Hi Christian,
>
> I cannot see any code inside the {code}{code} block.
> And I didn't get your question.
>
> Willem
>
> --
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/Problem-with-multiple-CXF-services-using-the-same-https-port-tp3379301p3408939.html
>  To unsubscribe from Problem with multiple CXF services using the same
> https port, click 
> here.
>
>


--
View this message in context: 
http://camel.465427.n5.nabble.com/Problem-with-multiple-CXF-services-using-the-same-https-port-tp3379301p3409050.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Problem with multiple CXF services using the same https port

[Christian Mueller]

And how I can test this configuration which should use https? Any suggestions
or code sample?

Thanks in advance,
Christian

--
View this message in context: 
http://camel.465427.n5.nabble.com/Problem-with-multiple-CXF-services-using-the-same-https-port-tp3379301p3408664.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Problem with multiple CXF services using the same https port

[Christian Mueller]

At present, we have a similar configuration like this one:

{code}


  

  

  

  



  


  

{code}

if we change to the solution you suggest, the configuration should looks
like this:

{code}

  


  

{code}

Right?

But I doesn't know how to configure the camel-cxf:properties and
camel-cxf:inInterceptors. Any help is welcome.

Christian

--
View this message in context: 
http://camel.465427.n5.nabble.com/Problem-with-multiple-CXF-services-using-the-same-https-port-tp3379301p3408654.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Using a camel-cxf producer and want switch between http and https without new deployments

[Christian Mueller]

Thank you Willem to figure this out.
I will make the FAQ entry tomorrow. Now it's time to catch some sleep... ;-)

Christian


-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Using-a-camel-cxf-producer-and-want-switch-between-http-and-https-without-new-deployments-tp3403048p3405901.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Using a camel-cxf producer and want switch between http and https without new deployments

[Christian Mueller]

Hello Ade!

Thank you for let us know this. Then it works for us without any
modification. Cool...

Thanks,
Christian

-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Using-a-camel-cxf-producer-and-want-switch-between-http-and-https-without-new-deployments-tp3403048p3403845.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Using a camel-cxf producer and want switch between http and https without new deployments

[Christian Mueller]

Thank you for your quick reply Willem, but I think I didn't catch it.
Extracting the http:conduit configuration doesn't make it easier to decide
at runtime whether or not the http:conduit should be applied or not.

However, we made a test using the HTTP protocoll instead of HTTPS and it
works (including the http:conduit configuration). Did you expect this
behavior or is it not reliable? Maybe CXF checks which protocol is used
before the http:conduit is applied/executed?

Christian

-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Using-a-camel-cxf-producer-and-want-switch-between-http-and-https-without-new-deployments-tp3403048p3403793.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Using a camel-cxf producer and want switch between http and https without new deployments

[Christian Mueller]

Hello List!

In our Camel routes (Camel 2.2.0-fuse-02-00 and CXF 2.2.9-fuse-01-00),
deployed into Servicemix (4.2.0-fuse-02-00), we are using camel-cxf as
producer to call external web services. For security reasons, we are using
an HTTPS connection to the web service provider, using the following
configuration (only the HTTPS configuration for CXF is shown):

{code:xml}
http://www.company.com/service/OrderEntry/1}OrderEntryServicePort.http-conduit";>
  

  



  .*_EXPORT_.*
  .*_EXPORT1024_.*
  .*_WITH_DES_.*
  .*_WITH_NULL_.*
  .*_DH_anon_.*

  

{code}

Everithing works well.

But now we got the requirement to switch between HTTPS and HTTP (we should
use HTTP in the test environment first to make sure everyting works well
before we switching to HTTPS) without redeploying our Camel routes. At
present this is not possible (in my opinion), because the Spring
configuration files are inside our Camel OSGI bundles. So, we have to
redeploy our bundles for switching between HTTP and HTTPS.

Is there an existing easy to use solution for this requirement?
Would is work, if we use a property placeholder for http:conduit name and
set this value to a not existing port or a URL we don't use (e.g.
http://localhost:/*)?
The last choice could be to evaluate the choosen protocol and if it's https
we can configure the http:conduit in Java?

Thanks in advance,
Christian

-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Using-a-camel-cxf-producer-and-want-switch-between-http-and-https-without-new-deployments-tp3403048p3403048.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Problem with multiple CXF services using the same https port

[Christian Mueller]

It would be great.
Looking forward to hear from you...

Christian

-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Problem-with-multiple-CXF-services-using-the-same-https-port-tp3379301p3379974.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Problem with multiple CXF services using the same https port

[Christian Mueller]

This is nice for the future. At present, we are using ServiceMix
4.2.0-fuse-02-00 which use Karaf 1.4.0.fuse-02-00 and I need a solution for
this environment.
Any doubts about my proposal (jetty.xml in ${SMX_ROOT} and reusing this
central jetty instance)?

Christian

-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Problem-with-multiple-CXF-services-using-the-same-https-port-tp3379301p3379902.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Problem with multiple CXF services using the same https port

[Christian Mueller]

Hello list!

In our ServiceMix 4.2.0-fuse-02-00 we deployed multiple Camel bundles which
provides web services using Apache Camel. In the first phase we used http
for all services. All services used the same port number and different
context paths.
In phase two, we tried to switch all endpoints to https with the following
(general) configuration:

{code}
https://0.0.0.0:8443:/Services/OrderEntry";
serviceClass="com.xxx.yyy.interfaces.oe.OrderEntryWebService"
endpointName="ssp:OrderEntryPort" 
serviceName="ssp:OrderEntryService"
wsdlURL="META-INF/oe/orderEntry.wsdl" 
xmlns:ssp="http://www.xxx.com/oe/services/2";>













.*.*





{code}

But now, we receive the following exception when we deploy the second
service (using the same https port):

{code}
karaf@root> Exception in thread "SpringOsgiExtenderThread-25"
org.apache.camel.RuntimeCamelException: org.apache.cxf.intercep
tor.Fault: Could not start Jetty server: Address already in use: JVM_Bind
at
org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1055)
at
org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:103)
at
org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:593)
at
org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:7
8)
at
org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
at
org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticast
er.java:76)
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274)
at
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736)
at
org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleAppl
icationContext.java:235)
at
org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecu
tionApplicationContext.java:358)
at
org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at
org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDele
gatedExecutionApplicationContext.java:320)
at
org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$Complet
eRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.cxf.interceptor.Fault: Could not start Jetty server:
Address already in use: JVM_Bind
at
org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine.addServant(JettyHTTPServerEngine.java:371)
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.activate(JettyHTTPDestination.java:167)
at
org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:48)
at
org.apache.cxf.binding.AbstractBindingFactory.addListener(AbstractBindingFactory.java:164)
at
org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:807)
at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:127)
at
org.apache.camel.component.cxf.CxfConsumer.doStart(CxfConsumer.java:122)
at
org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:53)
at
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:49)
at
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:989)
at
org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:197)
at
org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:101)
... 12 more
Caused by: java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.(ServerSocket.java:185)
at java.net.ServerSocket.(ServerSocket.java:141)
at javax.net.ssl.SSLServerSocket.(SSLServerSocket.java:84)
at
com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.(SSLServerSocketImpl.java:79)
  

Re: Using Splitter and file producer with option fileExist=Append failed

[Christian Mueller]

Hello Claus,
thanks for your help! The "thread(1)" solved my problem. Shame, that I
didn't figured it out by myself.
Without the "thread(1)" it also didn't work with Camel 2.6-SNAPSHOT. But
now, I didn't think we need the new option for the file producer.

Christian

-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Using-Splitter-and-file-producer-with-option-fileExist-Append-failed-tp3353618p3353818.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Using Splitter and file producer with option fileExist=Append failed

[Christian Mueller]

Hello list,
I'm using Camel 2.4 (inside FUSE ESB 4.3). For a POC (prove of concept) I
have to read a file with multiple address lines like this one:
{code}
1,Hahnstr,1,60525,Frankfurt
...
1,Hahnstr,1,60525,Frankfurt
{code}

Afterwards I have to call a web service (which makes the address updates on
our customer database). The web service respond with the id (the first
number in the input file) and the status (UPDATED). I have to write a result
file for each processed record which should looks like (the order of the
entries is not relevant):
{code}
1,UPDATED
...
1,UPDATED
{code}

My first solution which works fine was the following:

{code}
from("file:src/test/data?noop=true").routeId("POC-main")
  .split(body().tokenize("\n"), new
PocResultAggregationStrategy()).parallelProcessing().streaming()
.inOut("direct:addressService")
  .end()
  .inOnly(targetFileResourcePath);

from("direct:addressUpdateService").routeId("POC-addressUpdateService")
  .convertBodyTo(UpdateAddress.class)
  .inOut("cxf:bean:addressService")
  .convertBodyTo(String.class);
{code}

After thinking about this solution, it has a few cons:
1) I didn't use a persistent aggregator which could be result in loosing all
aggregated messages if someone shutdown the ESB.
2) The Aggregator looks a bit 'overingenieurd' for this requirement because
I only append new lines.

I tryied to implement a smarter solution and came up with this one:

{code}
from("file:src/test/data?noop=true").routeId("POC-main")
  .split(body().tokenize("\n")).parallelProcessing().streaming()
.inOut("direct:addressService")
.inOnly("file:target/outbox?fileExist=Append")
  .end();

from("direct:addressUpdateService").routeId("POC-addressUpdateService")
  .convertBodyTo(UpdateAddress.class)
  .inOut("cxf:bean:addressService")
  .convertBodyTo(String.class);
{code}

But unfortunately, the result file only contained 9897 lines instead of
1. :-(
I couldn't find an option in the file-component to lock the file, so that
only one thread can manipulate the file in one time.

My question is: Does the Camel file producer has an option for that? If not,
should the file producer has an option like: writeLock=fileLock (similar to
the readLock option of the file consumer)? Then maybe we also need an option
to specify how long Camel should wait for the lock until it fails...

What you are thinking?

Thanks in advance for your feedback,
Christian

-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Using-Splitter-and-file-producer-with-option-fileExist-Append-failed-tp3353618p3353618.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: csv unmarshal uses default encoding

[Christian Mueller]

I opened the JIRA https://issues.apache.org/jira/browse/CAMEL-3483 and fixed
this issue. Will also have a look on the other components.
-- 
View this message in context: 
http://camel.465427.n5.nabble.com/csv-unmarshal-uses-default-encoding-tp3325474p3326387.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: csv unmarshal uses default encoding

[Christian Mueller]

Hello Ernst,
you need to subscribe to the mailing list in order to post messages. Signing
up to Nabble isn't sufficient, your message is currently only visible to
Nabble users.
Please see http://camel.apache.org/discussion-forums.html
-- 
View this message in context: 
http://camel.465427.n5.nabble.com/csv-unmarshal-uses-default-encoding-tp3325474p3326368.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Splitting big XML files using xpath() and streaming()

[Christian Mueller]

Hello jburkhardt!
I was not aware of VDT. I will have a look on it today.
Thanks,
Christian
-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Splitting-big-XML-files-using-xpath-and-streaming-tp3300695p3302841.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Splitting big XML files using xpath() and streaming()

[Christian Mueller]

Hello Richard!
Thanks for your suggestion. I'm aware of the Smook integration, because I
developed it together with the Smooks guys. :o)
I thought if it's possible with the splitter EIP via XPath and the
streaming() mode, it is the easiest solution (also for my junior
co-workers). But it looks like it's not possible and I will make this more
clear in the wiki (because there is example code which use xpath and the
streaming mode).
I also think about whether or not it's meaningful to add this improvement to
the splitter/xpath EIP...
Cheers,
Christian
-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Splitting-big-XML-files-using-xpath-and-streaming-tp3300695p3302838.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Splitting big XML files using xpath() and streaming()

[Christian Mueller]

Hello all!

I'm using Camel 2.2.0 with Java 1.6.20, but this problem also exists in
Camel 2.5.0:

It looks like the streaming() mode did not work (for me) in conjunction with
xpath. I created a simple unit test:

{code}
public class StreamingTest extends CamelTestSupport {

@Test
public void testStreamingBigXmlfiles() throws Exception {
Thread.sleep(20); // let Camel split the big file
}

@Override
protected RouteBuilder createRouteBuilder() throws Exception {
return new RouteBuilder() {
@Override
public void configure() throws Exception {
XPathBuilder xPath = xpath("/a/b");

from("file://src/test/resources?noop=true")
.log("Starting to process big file:
${header.CamelFileName}")
.split(xPath).streaming()
.process(new Processor() {
private int counter = 0;

public void process(Exchange arg0) throws
Exception {
System.out.println("MSG: " + ++counter);
}
})
.end()
.log("Done processing big file:
${header.CamelFileName}");
}
};
}   
}
{code}

which consumes a 100MB file with the following format:

{code}



qqq
qqq
qqq
qqq
qqq
qqq
qqq
qqq
qqq
qqq


qqq
qqq
qqq
qqq
qqq
qqq
qqq
qqq
qqq
qqq


...


{code}

and each time, I get the following exception:

{code}
SCHWERWIEGEND: Caused by: [org.apache.camel.CamelExecutionException -
Exception occurred during execution on the exchange: Exchange[null]]
org.apache.camel.CamelExecutionException: Exception occurred during
execution on the exchange: Exchange[null]
at
org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1156)
at
org.apache.camel.impl.DefaultExchange.setException(DefaultExchange.java:262)
at
org.apache.camel.processor.MulticastProcessor.process(MulticastProcessor.java:196)
at org.apache.camel.processor.Splitter.process(Splitter.java:94)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:89)
at
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:99)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)
at
org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:299)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:208)
at
org.apache.camel.processor.DefaultChannel.process(DefaultChannel.java:256)
at
org.apache.camel.util.AsyncProcessorHelp

Loosing headers by using errorHandler and useOriginalMessage() in camel.jms

[Christian Mueller]

Hello list,

we are using camel-jms in conjunction with custom headers and the
useOriginalMessage() definition in our error handler for our exception
handling. We realized, that we loose all our headers in our dead letter
channel (using Camel 2.2.0.fuse-02-00). Our configuration looks like this
one:

errorHandler(
deadLetterChannel("jms:queue:dead")
.useOriginalMessage());

from("jms:queue:foo")
.processRef("allwaysThrowExceptionProcessor")
.to("jms:queue:bar");

We digg this problem down to the DefaultUnitOfWork [1], which doesn't copy
the headers if the message is a JmsMessage. The documentation says:
//cannot copy headers with a JmsMessage as the underlying javax.jms.Message
object goes nuts

Two line above, the java doc also says:
// TODO: the copy on facade strategy will help us here in the future
// TODO: optimize to only copy original message if enabled to do so in the
route
// special for JmsMessage as it can cause it to loose headers later.
// This will be resolved when we get the message facade with copy on write
implemented 

I have two questions:
1) How we can prevent or work around this (copy the original message into a
custom header and do not use useOriginalMessage(). And restore the original
message in the error flow from this custom header)?
2) When do you plan to fix this as the java doc suggests?


[1]
http://svn.apache.org/viewvc/camel/trunk/camel-core/src/main/java/org/apache/camel/impl/DefaultUnitOfWork.java?view=markup

Cheers,
Christian

-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Loosing-headers-by-using-errorHandler-and-useOriginalMessage-in-camel-jms-tp3046234p3046234.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Exchange Patters

[Christian Mueller]

Hello Ashwin, hello Bengt!

Thanks for your responses and the 2 cents :o)
Is it not confusing to provide exchange pattern in Camel which are not
supported (or differ from the spec), isn't?

However, I think Ashwin you have more experience with Camel than I. Can you
(or somebody else) recommend whether a processor/type converter/... should
write the response into the in or out message? Or should this depend on the
exchange pattern (write the response into the out message if the exchange
out capable otherwise into the in message)? Or should the processor/...
throw an exception, if it receives an exchange which is not out capable and
the processors responsibility is to change the message?
My understanding of In-Only was a fire and forgot (I don't expect a
response).

And I totally agree with Bengt, that this should be documented in the WIKI
(also how the pipeline works and the messages are copied from out to in) or
in the Camel in Action book.

Cheers,
Christian
-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Exchange-Patters-tp2836060p2837443.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: SMPP sourceAddrNpi bug.

[Christian Mueller]

Hello Pavel!

I raised a JIRA and fixed the issue with your proposed patch.
https://issues.apache.org/activemq/browse/CAMEL-3107

Feel free to test the current TRUNK whether it fixes your problem.

Thanks,
Christian
-- 
View this message in context: 
http://camel.465427.n5.nabble.com/SMPP-sourceAddrNpi-bug-tp2801906p2805307.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.

Re: Pax Exam test for Camel

[Christian Mueller]

Hello Willem!

Thank you for the quick reply and sorry for my late reaction (I was outside
my country without internet access).

In etc/startup.properties I found the following entry:
org/apache/felix/org.apache.felix.fileinstall/3.0.0/org.apache.felix.fileinstall-3.0.0.jar=11

I added the following two lines into my configure() method:

{code}
...
repositories("http://repo.fusesource.com/maven2/";,
"http://repository.ops4j.org/maven2/";),

mavenBundle().groupId("org.apache.felix").artifactId("org.apache.felix.fileinstall").version("3.0.0"),
mavenBundle().groupId("org.apache.geronimo.blueprint").artifactId("geronimo-blueprint").version("1.0.0"),

scanFeatures(getCamelKarafFeatureUrl(), "camel-core", "camel-osgi",
"camel-spring", "camel-test", "camel-jaxb", "camel-cxf"),
...
{code}

And now it works, without the error message in the log.

Thanks for helping me,
Christian
-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Pax-Exam-test-for-Camel-tp2799729p2805134.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Pax Exam test for Camel

[Christian Mueller]

Inspired from Camels OSGiIntegrationTestSupport, I plan also to test my
routes with Pax Exam, because all our routes will be deployed into
ServiceMix (FUSE ESB 4.2.0-fuse-02-00 - Camel 2.2.0-fuse-02-00).

My first Pax Exam test

{code:java}
@RunWith(JUnit4TestRunner.class)
public class OsgiPaxExamIntegrationTest extends CamelTestSupport {

@Inject
protected BundleContext bundleContext;

@EndpointInject(uri = "mock:result")
private MockEndpoint resultEndpoint;

@Test
public void testSendMessage() throws Exception {
resultEndpoint.expectedBodiesReceived("Hello World");

template.sendBody("seda:foo", "Hello World");

assertMockEndpointsSatisfied();
}

protected RouteBuilder createRouteBuilder() throws Exception {
return new RouteBuilder() {
public void configure() {
from("seda:foo").to("mock:result");
}
};
}

protected CamelContext createCamelContext() throws Exception {
setThreadContextClassLoader();

CamelContextFactory factory = new CamelContextFactory();
factory.setBundleContext(bundleContext);
return factory.createContext();
}

protected void setThreadContextClassLoader() {
// set the thread context classloader current bundle classloader
Thread.currentThread().setContextClassLoader(
this.getClass().getClassLoader());
}

public static UrlReference getCamelKarafFeatureUrl() {
return mavenBundle().groupId("org.apache.camel.karaf")

.artifactId("apache-camel").type("xml").classifier("features")
.version("2.2.0-fuse-02-00");
}

public static UrlReference getServicemixFeatureUrl() {
return mavenBundle().groupId("org.apache.servicemix")
.artifactId("apache-servicemix").type("xml")

.classifier("features").version("4.2.0-fuse-02-00");
}

@Configuration
public static Option[] configure() throws Exception {
Option[] options = options(
// install the spring dm profile
profile("spring.dm").version("1.2.0"),
org.ops4j.pax.exam.CoreOptions.systemProperty(

"org.ops4j.pax.logging.DefaultServiceLog.level").value(
"INFO"),
org.ops4j.pax.exam.CoreOptions.systemProperty(

"org.apache.camel.jmx.disable").value("true"),

repositories("http://repo.fusesource.com/maven2/";,

"http://repository.ops4j.org/maven2/";),
scanFeatures(getCamelKarafFeatureUrl(), 
"camel-core",
"camel-osgi", "camel-spring", 
"camel-test",
"camel-jaxb", "camel-cxf"),
/*
 * scanFeatures(getServicemixFeatureUrl(), 
"camel-activemq"),
 */
workingDirectory("target/paxrunner/"), felix(),

waitForFrameworkStartupFor(3));

return options;
}
}
{code}

The test succeed, but in the log I see the following error message:

{code}
ERROR: Error starting
file:bundles/org.apache.felix.karaf.deployer.spring_1.4.0.fuse-02-00.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.felix.karaf.deployer.spring [21]: package;
(&(package=org.apache.felix.fileinstall)(version>=3.0.0)(!(version>=4.0.0
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.felix.karaf.deployer.spring [21]: package;
(&(package=org.apache.felix.fileinstall)(version>=3.0.0)(!(version>=4.0.0)))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
at 
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:637)
{code}

full stack trace:

{code}
__ ___
\__   \_  ___  ___ \_   _/__  _
 | ___/\__  \ \  \/  /  |__)_\  \/  /\__  \  / \
 || / __ \_><   |\><  / __ \|  Y Y  \
 ||(  /__/\_ \ /___  /__/\_ \(  /__|_|  /
\/  

Re: SMPP data encoding.

[Christian Mueller]

Hello Pavel!

I committed a fix for this issue. Please feel free to try Camel 2.5-SNAPSHOT
whether this fix resolve your issue. It introduce a new option "dataCoding"
which should be set to "8" in your case.

Cheers,
Christian
-- 
View this message in context: 
http://camel.465427.n5.nabble.com/SMPP-data-encoding-tp2798167p2798676.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.

Re: SMPP data encoding.

[Christian Mueller]

Hello Pavel!

I raised a JIRA for it: https://issues.apache.org/activemq/browse/CAMEL-3093

Cheers,
Christian
-- 
View this message in context: 
http://camel.465427.n5.nabble.com/SMPP-data-encoding-tp2798167p2798585.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.

Re: SMPP type connection.

[Christian Mueller]

Hello Pavel!

Sorry for the late reply.

Why you have to use the "transceiver" type?

The systemType is used to categorize the type of ESME (External Short
Message Entity) that is binding to the SMSC, as described in the wiki here
[1]. You are looking for the bindType, which is set automatically by Camel
itself. If you use the SmppConsomer (from("smpp://...")), Camel will create
a session with the "receiver" bindType. If you use the SmppProducer
(to("smpp://...")), Camel will create a session with the "transmitter"
bindType. The "transceiver" bindType is currently not supported and I think
we don't need it.

Regards,
Christian

[1] is used to categorize the type of ESME (External Short Message Entity)
that is binding to the SMSC
-- 
View this message in context: 
http://camel.465427.n5.nabble.com/SMPP-type-connection-tp2796517p2798510.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.

Re: Camel, OSGI and container wide Camel route lookups

[Christian Mueller]

Hello Ron!

I had a chat with Ade and we will use the following solution in our project.
It is not so dynamic as the first one, but much more safer (we will not skip
extension processing).

{code}
// common routing template for all countries
from(fromEndpoint).id(OrderEntryRoute.class.getName() + ".main")
.to("direct:preProcess")
.to("direct:process")
.to("direct:postProcess");

from("direct:preProcess").id(OrderEntryRoute.class.getName() +
".preProcess")
.choice()

.when(header(WlsiConstants.HEADER_COUNTRY_ID).isEqualTo(new Integer(1)))

.to("activemq:queue:orderEndtryPreProcessing.be") // Belgium specific
pre process extension provided in another OSGI bundle

.when(header(WlsiConstants.HEADER_COUNTRY_ID).isEqualTo(new Integer(2)))

.to("activemq:queue:orderEndtryPreProcessing.de") // Germany specific
pre process extension provided in another OSGI bundle
.end();

from("direct:process").id(OrderEntryRoute.class.getName() + 
".process")
.bean("orderEntryService", "process"); // common 
processing for all
countries defined in this bundle

from("direct:postProcess").id(OrderEntryRoute.class.getName() +
".postProcess")
.choice()

.when(header(WlsiConstants.HEADER_COUNTRY_ID).isEqualTo(new Integer(2)))

.to("activemq:queue:orderEndtryPostProcessing.de") // Germany specific
post process extension provided in another OSGI bundle

.when(header(WlsiConstants.HEADER_COUNTRY_ID).isEqualTo(new Integer(3)))

.to("activemq:queue:orderEndtryPostProcessing.fr") // France specific
post process extension provided in another OSGI bundle
.end();
{code}

We think this will work for us, because we only have to support 3 countries.
May be in a later phase of this project and if we have requirements for a
more dynamic solution, we will come back to the nmr or the OSGI service
registry.

Thanks for taking time for my problem,
Christian
-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-OSGI-and-container-wide-Camel-route-lookups-tp2269094p2582586.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel, OSGI and container wide Camel route lookups

[Christian Mueller]

Hello Ade, Ron and Claus!

Thanks for your responses. I assume that I can send/receive a message in SMX
using Camel in this way:

first OSGI bundle:
{code}
  from("direct:start")
  .to("nmr:orderEntryPreProcessor");
{code}

second OSGI bundle:
{code}
  from("nmr:orderEntryPreProcessor")
  .to("mock:end");
{code}

But how it is possible to discover routes, deployed in another OSGI bundle
to "extend" or modify a route dynamicly? I understood the following code
will not work, if the route "nmr:orderEntryPreProcessor" is defined in
another OSGI bundle:
{code}
  Endpoint endpoint =
exchange.getContext().hasEndpoint("nmr:orderEntryPreProcessor"); 
{code}

Du you advice a solution like this:

first OSGI bundle:
{code}
  

  

  org.apache.camel.RoutesBuilder


  

  
{code}

and in the other bundle, I need a reference to the OSGI service registry and
lookup the exported route (by service property because we export multiple
routes).
I don't know whether this works and how I can inject the OSGI service
registry in a Spring managed bean. I assume, this is not the Spring
application context...

Thanks for your help,
Christian
-- 
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-OSGI-and-container-wide-Camel-route-lookups-tp2269094p2473177.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: good solution to work with jms message priority

[Christian Mueller]

Thanks for the quick responses...

Mixed processing of messages with different priorities is not a problem for
us. What we have to prevent is, that an online request is only processed
(with a huge delay) after all batch messages (several thousands) are
processed.
Writing in different queues is possible. Than, my JMS consumer route would
looks like:
{code}
from("activemq://queue:inbox.online?concurrentConsumers=5")
.to("direct:inbox");

from("activemq://queue:inbox.batch?concurrentConsumers=5")
.to("direct:inbox");

from("direct:inbox")
.processRef("myProcessor")
.to("activemq://queue:outbox");
{code}

Thanks,
Christian
-- 
View this message in context: 
http://old.nabble.com/good-solution-to-work-with-jms-message-priority-tp28778639p28779260.html
Sent from the Camel - Users mailing list archive at Nabble.com.

good solution to work with jms message priority

[Christian Mueller]

Hello list,

I have a requirement to process online (coming from an external web service)
and batch (several thousand) messages. The online messages are more prior
(the customer is waiting of the response) and should be processed before the
batch messages (I think a common requirement). Because ActiveMQ at this time
doesn't support message priority
([how-can-i-support-priority-queues|http://activemq.apache.org/how-can-i-support-priority-queues.html]),
I was looking for another solution. I read this thread
[Camel-and-jms-priority|http://old.nabble.com/Camel-and-jms-priority-ts25962858.html#a25962858]
and found it to complicated - I'm lasy... :-)

My question is, would this Camel route also do a good job for this
requirements?

{code}
from("activemq://queue:inbox?concurrentConsumers=5&selector=priority<='4'")
.to("direct:inbox");

from("activemq://queue:inbox?concurrentConsumers=5&selector=priority>'4'")
.to("direct:inbox");

from("direct:inbox")
.processRef("myProcessor")
.to("activemq://queue:outbox");
{code}

Thanks in advanced,
Christian
-- 
View this message in context: 
http://old.nabble.com/good-solution-to-work-with-jms-message-priority-tp28778639p28778639.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Proposal for a new camel-bean-validation component based on jsr 303

[Christian Mueller]

Ok, I will do this.
I opened an issue on JIRA and will track further discussions there.

https://issues.apache.org/activemq/browse/CAMEL-2565

-- 
View this message in context: 
http://old.nabble.com/Proposal-for-a-new-camel-bean-validation-component-based-on-jsr-303-tp27950969p27976253.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Proposal for a new camel-bean-validation component based on jsr 303

[Christian Mueller]

Hello Claus!

My first and easiest implementation of the bean-validator looks like (it is
inspired from the schema validation component):

public class BeanValidatorComponent extends DefaultComponent {

protected Endpoint createEndpoint(String uri, String remaining,
Map parameters) throws Exception {
BeanValidator beanValidator = new BeanValidator();

configureValidator(beanValidator, uri, remaining, parameters);

return new ProcessorEndpoint(uri, this, beanValidator);
}

protected void configureValidator(BeanValidator beanValidator, String
uri, String remaining, Map parameters) throws Exception {
ValidatorFactory factory =
Validation.buildDefaultValidatorFactory();
Validator validator = factory.getValidator();

beanValidator.setValidator(validator);
}
}

public class BeanValidator implements Processor {

private Validator validator;

public void process(Exchange exchange) throws Exception {
Object bean = exchange.getIn().getBody();

Set constraintViolations =
validator.validate(bean);
handleErrors(exchange, constraintViolations);
}

public void handleErrors(Exchange exchange, Set
constraintViolations) throws ValidationException {
if (!constraintViolations.isEmpty()) {
throw new BeanValidationException(exchange,
constraintViolations, exchange.getIn().getBody());
}
}

public Validator getValidator() {
return validator;
}

public void setValidator(Validator validator) {
this.validator = validator;
}
}

public class BeanValidationException extends ValidationException {

private Set constraintViolations;

public BeanValidationException(Exchange exchange,
Set constraintViolations, Object bean) {
super(exchange, buildMessage(constraintViolations, bean));
this.constraintViolations = constraintViolations;
}

protected static String buildMessage(Set
constraintViolations, Object bean) {
StringBuffer buffer = new StringBuffer("Validation failed for: ");
buffer.append(bean);

buffer.append(" errors: [");
for (ConstraintViolation constraintViolation : constraintViolations)
{
buffer.append("property: " +
constraintViolation.getPropertyPath() + "; value: " +
constraintViolation.getInvalidValue() + "; constraint: " +
constraintViolation.getMessage() + "; ");
}
buffer.append("]");

return buffer.toString();
}

public Set getConstraintViolations() {
return constraintViolations;
}
}

I think this shows how the Validation API works. The Validator will not
throw any exception, if the validation fails. It returns a Set with
ConstraintViolations. Some features of the Validator API are not shown, but
interesting for the users:
- Validating groups
(http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/#validator-usingvalidator-validationgroups)
- Creating custom constraints
(http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/#validator-customconstraints)
- XML configuration
(http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/#validator-xmlconfiguration)
- Configure custom ValidationProviderResolver, MessageInterpolator,
TraversableResolver or ConstraintValidatorFactory
(http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/#validator-bootstrapping)

Because the validate method of the Validator doesn't throw an exception but
returns a Set with ConstraintViolations, I'm afraid we could not use the
bean component.

I found the following two still open issues for this topic:
http://issues.apache.org/activemq/browse/CAMEL-1276
http://issues.apache.org/activemq/browse/CAMEL-1537

You and others prefers to use Predicates/Processors like this:

from("foo")
  .filter().validate(theValidationEndpointUri)
  .to("blah")

or 

from("foo")
  .validate(nonblocking)
  .to("bar")

Now, I think also this is the better solution to implements these
requirements. But I'm not so familiar with implementing
Predicates/Processors and extend the Java/XML DSL. Could you give me a hint,
where I could find a good sample in the Camel code to implement a
Predicate/Processor?

Regards,
Christian

-- 
View this message in context: 
http://old.nabble.com/Proposal-for-a-new-camel-bean-validation-component-based-on-jsr-303-tp27950969p27975303.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Proposal for a new camel-bean-validation component based on jsr 303

[Christian Mueller]

Currently, I'm working on a project where we have to read fixed length
records and csv records. Because we don't trust other developers ;-), we
want to validate the input.
What do you think about a bean validation component which is based on jsr
303 (http://jcp.org/en/jsr/detail?id=303) and which could be used like the
existing camel-validation component:

from(file://sampleIn.txt)
// transformation to a java object
.to("bean-validation://param1=value1")
.to("file://sampleOut.txt");

Pre defined validation rules are e. g.:
- @NotNull
- @AssertTrue
- @Size(min = 2, max = 14)
- @Min(2)
- @Max(2)
- @Valid
- @Pattern()
- ... and many more

JSR 303 also allows you to define custom validation rules. See here for more
details:
http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/#validator-customconstraints-simple

For more information, please have a look in the reference implementation:
http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/

The Hibernate Validator (the reference implementation) is licensed under the
Apache License Version 2:
http://anonsvn.jboss.org/repos/hibernate/validator/tags/v4_0_2_GA/license.txt

What do you think? Could this be an useful component for Camel?

Regards,
Christian
-- 
View this message in context: 
http://old.nabble.com/Proposal-for-a-new-camel-bean-validation-component-based-on-jsr-303-tp27950969p27950969.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Using HTTPS in camel-http when remote side has self-signed cert

[Christian Mueller]

Yogesh,
if you have a look on org.apache.commons.httpclient.protocol.Protocol, you
will see, that registerProtocol stores the protocol in a HashMap. Using the
same key "https" overrides the first registered protocol:

public class Protocol {
private static final Map PROTOCOLS = Collections.synchronizedMap(new
HashMap());

public static void registerProtocol(String id, Protocol protocol) {
if (id == null) {
throw new IllegalArgumentException("id is null");
}
if (protocol == null) {
throw new IllegalArgumentException("protocol is null");
}

PROTOCOLS.put(id, protocol);
}
}

Regards,
Christian
-- 
View this message in context: 
http://old.nabble.com/Using-HTTPS-in-camel-http-when-remote-side-has-self-signed-cert-tp25916878p27694404.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Spring batch integration with camel

[Christian Mueller]

Hey Charles,

I'm not sure, what is the best integration solution from Camel and Spring
Batch. That's the reason why I ask for the ideas and proposals of other
Camel riders. May be there is no need to integrate Camel and Spring Batch,
because Spring Batch could send/write the Item to a queue and let Camel
process it. 

As you can read in the first post, lazyeye has done some integration and I
would like to see how he/she integrate Spring Batch and Camel because we use
both frameworks.

Regards,
Christian
-- 
View this message in context: 
http://old.nabble.com/Spring-batch-integration-with-camel-tp25285268p27184928.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Spring batch integration with camel

[Christian Mueller]

Issue opened (https://issues.apache.org/activemq/browse/CAMEL-2367) and
waiting for replies... :working:

Christian

-- 
View this message in context: 
http://old.nabble.com/Spring-batch-integration-with-camel-tp25285268p27179703.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Spring batch integration with camel

[Christian Mueller]

Hey,

I would also like this contribution, because we use both frameworks. Any
news for that? Should we open an issue (new feature) for that?

Regards,
Christian
-- 
View this message in context: 
http://old.nabble.com/Spring-batch-integration-with-camel-tp25285268p27174835.html
Sent from the Camel - Users mailing list archive at Nabble.com.