[suggestion] Add camel cdi examples/tests project

Hi, I currently develop a maven project containing Camel CDI examples (+ test cases with arquillian in a next phase) about showing how to deploy in CDI environment no matter if it is JavaSE or J2EE. What is really interesting is part of the container directory (https://github.com/cmoulliard/cdi-c

Re: camel cdi extension

Hi Romain, This is really interesting what you have have developed. I don't really like how you add RouteBuilder in the create method (class CamelContextBean) and I would prefer that the user can provide this information like we do in a more Camel traditional way. By the way, I suggest that in the

Re: [DISCUSS] - Camel Maven Archetypes - Generating files with ASF license headers

On Wednesday, July 4, 2012, Christian Schneider wrote: > Very good idea. I have done some research: > > https://issues.apache.org/**jira/browse/LEGAL-124 > http://www.apache.org/legal/**src-headers.html#faq-**exceptions

camel cdi extension

Hi, following a discussion on deltaspike IRC channel i created a small CDI extension camel oriented --> https://github.com/rmannibucau/camel-cdi-extension the idea is to decorate route builders with @CamelContextConfig(contextName = "") and then be able to get injected the context directly:

Re: [CAMEL-5416] Camel Simple JMS Component

Excellent suggestion. I will add it to the list of to-do's. Thanks for the feedback. On Wed, Jul 4, 2012 at 9:30 AM, aedwards wrote: > wondering if you have considered allowing it to take a java "List", and > then > sending all the separate elements to the JMS provider as separate Messages > w

Re: [CAMEL-5416] Camel Simple JMS Component

wondering if you have considered allowing it to take a java "List", and then sending all the separate elements to the JMS provider as separate Messages within the same transaction? I wrote a small bean which does this for performance reasons(since batching the transaction creates a noticeable per

Re: Wiki Edit Access

I have and when I do it redirects me to a login page. The login fails. I get a screen that states I need to validate my login by typing in the "captcha" phrase. Each time I do it just redirects me back that same screen. I also tried to recover my pw and have never received the email. On Wed,

Re: Wiki Edit Access

On Wed, Jul 4, 2012 at 4:06 PM, Scott England-Sullivan wrote: > I can log into the Camel Jira but not Confluence. Are they two different > authentication systems? > Yes, click that edit link in the bottom of the html pages to go into confluence to edit. > On Wed, Jul 4, 2012 at 7:56 AM, Henryk

Re: Wiki Edit Access

I can log into the Camel Jira but not Confluence. Are they two different authentication systems? On Wed, Jul 4, 2012 at 7:56 AM, Henryk Konsek wrote: > > Seems ASF is down at the moment such as JIRA / SVN etc. So it may work > > fine when they get online again. > > Yep, I've been struggling wit

Re: Camel-Extra 2.10 release

> When we tag camel-extra 2.10.0, we have to update the version to 2.10.0 in > camel-extra too. For this, we need the Camel 2.10.0 artifacts (not only in > a staging repo). So Camel 2.10.0 arrived to Central [1]. Can I tag 2.10.0 version of Camel-Extra then? I can almost hear Maven release:prepare

Re: Wiki Edit Access

> Seems ASF is down at the moment such as JIRA / SVN etc. So it may work > fine when they get online again. Yep, I've been struggling with Apache Jira problems for two days. :( -- Henryk Konsek http://henryk-konsek.blogspot.com

Re: Wiki Edit Access

On Wed, Jul 4, 2012 at 2:35 PM, Scott England-Sullivan wrote: > Appears my account is horked. I have an email into the infrastructure > admins to get it fixed. > Seems ASF is down at the moment such as JIRA / SVN etc. So it may work fine when they get online again. > On Wed, Jul 4, 2012 at 12:2

Re: Wiki Edit Access

Appears my account is horked. I have an email into the infrastructure admins to get it fixed. On Wed, Jul 4, 2012 at 12:21 AM, Claus Ibsen wrote: > Hi Scott > > I granted you karma. Can you try if you can edit the wiki pages now? > > > On Wed, Jul 4, 2012 at 5:32 AM, Scott England-Sullivan > w

[DISCUSS] - Happy 5 years birthday on Camel front page

Hi I would like that the Camel team posts a "Happy birthday" on the Camel front page. http://camel.apache.org/ I took the liberty to draft some text. Feel free to help adjust and comment. There is a TODO eg where I would like that we highlight and talk about our great community and how much they

Re: [DISCUSS] - Camel Maven Archetypes - Generating files with ASF license headers

Very good idea. I have done some research: https://issues.apache.org/jira/browse/LEGAL-124 http://www.apache.org/legal/src-headers.html#faq-exceptions So it looks like we are required to have the license in all files we have in svn and also in each artifact we distribute. The only exemption ar

Re: [DISCUSS] - Camel Maven Archetypes - Generating files with ASF license headers

There's a mailing list specific for legal matters, there's no need to get the board involved with that. We should rather look for archives in legal-disc...@apache.org and in the jira https://issues.apache.org/jira/browse/LEGAL and if we can't find anything, raise a JIRA issue there. My guts feeling

Re: Camel-Extra POM update

> Looks good so far (didn't test it until now). Once I published my pet Scala project to central (via Sonatype OSS) with settings also copied from the Sonatype OSS parent POM. Worked like a charm. > How to request an account at Sonartype? You just create a Jira account [1] there. > And how to m

Re: [DISCUSS] - Camel Maven Archetypes - Generating files with ASF license headers

So my proposal is that I organize a statement from the board before our next release and we already remove the license headers. In the worst case I think we have to add a license file to the generated code and in the best case we are fine. Christian Am 04.07.2012 10:30, schrieb Christian Schne

Re: [DISCUSS] - Camel Maven Archetypes - Generating files with ASF license headers

This is already a good tendency that generated code is unproblematic. To make sure I propose we get a statement from the board then we are on the safe side. Perhaps this can then also be written down so other projects can simply follow. Christian Am 04.07.2012 10:24, schrieb Rob Davies: I th

Re: [DISCUSS] - Camel Maven Archetypes - Generating files with ASF license headers

I think this thread is helpful - its from Eclipse - http://www.eclipsezone.com/eclipse/forums/t116081.html On 4 Jul 2012, at 09:19, Christian Schneider wrote: > My current understanding is that you can not assume you are allowed to use > code if it has no license. Is there an exception for gene

Re: [DISCUSS] - Camel Maven Archetypes - Generating files with ASF license headers

My current understanding is that you can not assume you are allowed to use code if it has no license. Is there an exception for generated/template code? If yes then I am supporting this but we should make sure this works legally. Can we get some confirmation about this from some license special

Re: [DISCUSS] - Camel Maven Archetypes - Generating files with ASF license headers

Generated code should not be licensed or copyrighted. It's up to the user to decide which license to use. So +1 for removing any header from generated code. On Wed, Jul 4, 2012 at 8:33 AM, Claus Ibsen wrote: > Hi > > When end users of Camel uses the Camel Maven Archetypes to create new > projec

Re: [DISCUSS] - Camel Maven Archetypes - Generating files with ASF license headers

+1 to remove Apache License from code generated Charles Moulliard Apache Committer Blog : http://cmoulliard.blogspot.com Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard Skype: cmoulliard On Wed, Jul 4, 2012 at 8:33 AM, Claus Ibsen wrote: > Hi >

Re: [DISCUSS] - Camel Maven Archetypes - Generating files with ASF license headers

Am 04.07.2012 09:45, schrieb Claus Ibsen: On Wed, Jul 4, 2012 at 9:14 AM, Christian Schneider wrote: Basically I agree that we should not have Apache License headers as people will have to manually remove them. On the other hand it is important that we have a license for the code the archetype

Re: [DISCUSS] - Camel Maven Archetypes - Generating files with ASF license headers

On Wed, Jul 4, 2012 at 9:14 AM, Christian Schneider wrote: > Basically I agree that we should not have Apache License headers as people > will have to manually remove them. > On the other hand it is important that we have a license for the code the > archetype generates. Without > a license people

Re: [DISCUSS] - Camel Maven Archetypes - Generating files with ASF license headers

Basically I agree that we should not have Apache License headers as people will have to manually remove them. On the other hand it is important that we have a license for the code the archetype generates. Without a license people might be insecure what they may do with the code. I think the Apa

Re: [DISCUSS] - Camel Maven Archetypes - Generating files with ASF license headers

+1, end user should have the right to decide which kind of license he will use. But I'm not sure if it is right for us to remove the ASL from the source code of camel maven archetype. On Wed Jul 4 14:33:38 2012, Claus Ibsen wrote: Hi When end users of Camel uses the Camel Maven Archetypes to