Hi Christian
I think it is okay for moving the activemq-camel to Camel and only
include the pieces that is the JMS component. eg so its a tiny wrapper
on top of camel-jms that is optimized for AcitveMQ which is what
people are using.
The current code in activemq-camel has some old code that are n
Hi everyone,
I've recently been working on camel-saxon and camel-xslt to enable
saxon specific stuffs in camel-xslt and this required some little
reflection hacks which could make it harder to detect potential api
breaks when updating saxon and could be problematic for java 9 if
saxon does not pro
I am using Camel Rest DSL to build my rest service but it seems that , it
does not recognize JsonProperty annotation.
I have a propery like:
class Test {
private int id;
@JsonProperty(access = Access.READ_ONLY)
private String text;
}
and the rest definition is:
http://camel.apache.
Sergey,
Thanks for the component.
I am really looking forward to the Azure Queue component.
Cheers, Thomas.
-Ursprüngliche Nachricht-
Von: Sergey Beryozkin [mailto:sberyoz...@gmail.com]
Gesendet: Donnerstag, 9. Februar 2017 18:42
An: dev@camel.apache.org
Betreff: Re: Camel Azure compon
Hi Sergey
Yeah sure its good to get this out in the hands of the users. If
something is not yet implemented or something we can always state that
in the docs.
And if there are things you think still must be done its a good idea
to log a JIRA with that.
For tests we sometimes have a maven profile
Hi
Yeah it can make sense. It also ensures that users are not in doubt if
they use saxon or not. Usually Saxon offers more advanced features
that you dont have from the JDK.
And maybe we can add something so users can install the commercial
saxon and unlock xslt 3.0 functionality or what else is
going to raise a ticket then
---
Luca Burgazzoli
On Fri, Feb 10, 2017 at 1:16 PM, Claus Ibsen wrote:
> Hi
>
> Yeah it can make sense. It also ensures that users are not in doubt if
> they use saxon or not. Usually Saxon offers more advanced features
> that you dont have from the JDK.
>
> And ma
Github user zregvart closed the pull request at:
https://github.com/apache/camel/pull/1455
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
Hi Claus
Thanks, I've opened another issue for investigating on how to enable the
Azure (integration) tests
but I've also realized I do not have a simpler component/endpoint only
test, so I'll work on it first and then I will commit
Cheers, Sergey
On 10/02/17 12:14, Claus Ibsen wrote:
Hi Ser
GitHub user godbolerr opened a pull request:
https://github.com/apache/camel/pull/1457
CAMEL-10814 Camel Kafka Integration Example
Example to test Apache Kafka Component.
Example allows user to send and receive message from the Kafka Topic as
well as showcase how to use P
10 matches
Mail list logo