Re: Camel-box download file version

[Vladimir Cherepnalkovski]

I found the issue, and a solution.


First there is a mistake in camel - box documentation.


Endpoint "downloadPreviousFileVersions" should be  
"downloadPreviousFileVersion".


If we use full endpoint name downloadPreviousFileVersion, the route will work.


Also, there is a problem in camel - box endpoint mapping.

I saw that shorthand alias name is mapped to "downloadPreviousFileVersions" 
which not exists.

Re: Camel-box download file version

[Andrea Cosentino]

You're welcome to work on a PR.

The documentation for this component is here

https://github.com/apache/camel/blob/master/components/camel-box/camel-box-component/src/main/docs/box-component.adoc

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Wednesday, November 28, 2018, 11:19:12 AM GMT+1, Vladimir Cherepnalkovski 
 wrote: 





I found the issue, and a solution.


First there is a mistake in camel - box documentation.


Endpoint "downloadPreviousFileVersions" should be  
"downloadPreviousFileVersion".


If we use full endpoint name downloadPreviousFileVersion, the route will work.


Also, there is a problem in camel - box endpoint mapping.

I saw that shorthand alias name is mapped to "downloadPreviousFileVersions" 
which not exists.

Re: Camel-box download file version

[Vladimir Cherepnalkovski]

Done.



I hope that someone will change the mapping on backend, so the shorthand alias 
will be available for use.


From: Andrea Cosentino 
Sent: Wednesday, November 28, 2018 11:22 AM
To: users@camel.apache.org
Subject: Re: Camel-box download file version

You're welcome to work on a PR.

The documentation for this component is here

https://github.com/apache/camel/blob/master/components/camel-box/camel-box-component/src/main/docs/box-component.adoc
[https://avatars3.githubusercontent.com/u/47359?s=400&v=4]

camel/box-component.adoc at master · apache/camel · 
GitHub
github.com
Box.com requires the use of OAuth2.0 for all client application authentication. 
In order to use camel-box with your account, you’ll need to create a new 
application within Box.com at https://developer.box.com.The Box application’s 
client id and secret will allow access to Box APIs which require a current user.




--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Wednesday, November 28, 2018, 11:19:12 AM GMT+1, Vladimir Cherepnalkovski 
 wrote:





I found the issue, and a solution.


First there is a mistake in camel - box documentation.


Endpoint "downloadPreviousFileVersions" should be  
"downloadPreviousFileVersion".


If we use full endpoint name downloadPreviousFileVersion, the route will work.


Also, there is a problem in camel - box endpoint mapping.

I saw that shorthand alias name is mapped to "downloadPreviousFileVersions" 
which not exists.

Re: Camel-box download file version

[Andrea Cosentino]

That class is generated. You just need to change the methodPattern here:

https://github.com/apache/camel/blob/master/components/camel-box/camel-box-component/pom.xml#L278

If you are fancy opening a PR about that after testing the fix, you're welcome 
to do it

--
Andrea Cosentino 
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Wednesday, November 28, 2018, 11:35:48 AM GMT+1, Vladimir Cherepnalkovski 
 wrote: 







Done. 

 

I hope that someone will change the mapping on backend, so the shorthand alias 
will be available for use.

 





From: Andrea Cosentino 
Sent: Wednesday, November 28, 2018 11:22 AM
To: users@camel.apache.org
Subject: Re: Camel-box download file version 


 





You're welcome to work on a PR.The documentation for this component is 
herehttps://github.com/apache/camel/blob/master/components/camel-box/camel-box-component/src/main/docs/box-component.adoc
 


  





camel/box-component.adoc at master · apache/camel · GitHub

  

github.com

  

Box.com requires the use of OAuth2.0 for all client application authentication. 
In order to use camel-box with your account, you’ll need to create a new 
application within Box.com at https://developer.box.com.The Box application’s 
client id and secret will allow access to Box APIs which require a current user.


   





--Andrea Cosentino --Apache Camel PMC 
ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: 
ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerdOn Wednesday, November 28, 
2018, 11:19:12 AM GMT+1, Vladimir Cherepnalkovski  
wrote: I found the issue, and a solution.First there is a mistake in camel - 
box documentation.Endpoint "downloadPreviousFileVersions" should be  
"downloadPreviousFileVersion".If we use full endpoint name 
downloadPreviousFileVersion, the route will work.Also, there is a problem in 
camel - box endpoint mapping.I saw that shorthand alias name is mapped to 
"downloadPreviousFileVersions" which not exists.

RE: Camel-box download file version

[Vladimir Cherepnalkovski]

I will test this, and reply.



Sent from Mail for Windows 10




From: Andrea Cosentino 
Sent: Wednesday, November 28, 2018 11:44:00 AM
To: users@camel.apache.org; Vladimir Cherepnalkovski
Subject: Re: Camel-box download file version

That class is generated. You just need to change the methodPattern here:

https://github.com/apache/camel/blob/master/components/camel-box/camel-box-component/pom.xml#L278

If you are fancy opening a PR about that after testing the fix, you're welcome 
to do it

--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Wednesday, November 28, 2018, 11:35:48 AM GMT+1, Vladimir Cherepnalkovski 
 wrote:







Done.



I hope that someone will change the mapping on backend, so the shorthand alias 
will be available for use.







From: Andrea Cosentino 
Sent: Wednesday, November 28, 2018 11:22 AM
To: users@camel.apache.org
Subject: Re: Camel-box download file version








You're welcome to work on a PR.The documentation for this component is 
herehttps://github.com/apache/camel/blob/master/components/camel-box/camel-box-component/src/main/docs/box-component.adoc








camel/box-component.adoc at master · apache/camel · GitHub



github.com



Box.com requires the use of OAuth2.0 for all client application authentication. 
In order to use camel-box with your account, you’ll need to create a new 
application within Box.com at https://developer.box.com.The Box application’s 
client id and secret will allow access to Box APIs which require a current user.








--Andrea Cosentino --Apache Camel PMC 
ChairApache Karaf CommitterApache Servicemix PMC MemberEmail: 
ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerdOn Wednesday, November 28, 
2018, 11:19:12 AM GMT+1, Vladimir Cherepnalkovski  
wrote: I found the issue, and a solution.First there is a mistake in camel - 
box documentation.Endpoint "downloadPreviousFileVersions" should be  
"downloadPreviousFileVersion".If we use full endpoint name 
downloadPreviousFileVersion, the route will work.Also, there is a problem in 
camel - box endpoint mapping.I saw that shorthand alias name is mapped to 
"downloadPreviousFileVersions" which not exists.

readLockLoggingLevel File Component

[bjoern . ohm]

Hi,

one little thing...
I have noticed that in the javadocs, documentations,... for the the 
property readLockLoggingLevel in the File Component, respectively in the 
class FileChangedExclusiveReadLockStrategy the default is described as 
'WARN'. But in the implementation it is 'DEBUG'. It could be helpful to 
adjust this...
 
Best regards
Björn

 
Diese E-Mail könnte vertrauliche und / oder rechtlich geschützte Informationen 
enthalten. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail 
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und 
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
Weitergabe dieser Mail sind nicht gestattet.

This e-mail may contain confidential and / or privileged information. If you 
are not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorised 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden. 

Re: readLockLoggingLevel File Component

[Zoran Regvart]

Hi Björn,
sounds like a great contribution, we love those :)

zoran
On Wed, Nov 28, 2018 at 1:19 PM  wrote:
>
> Hi,
>
> one little thing...
> I have noticed that in the javadocs, documentations,... for the the
> property readLockLoggingLevel in the File Component, respectively in the
> class FileChangedExclusiveReadLockStrategy the default is described as
> 'WARN'. But in the implementation it is 'DEBUG'. It could be helpful to
> adjust this...
>
> Best regards
> Björn
>
>
> Diese E-Mail könnte vertrauliche und / oder rechtlich geschützte 
> Informationen enthalten. Wenn Sie nicht der richtige Adressat sind oder diese 
> E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender 
> und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
> Weitergabe dieser Mail sind nicht gestattet.
>
> This e-mail may contain confidential and / or privileged information. If you 
> are not the intended recipient (or have received this e-mail in error) please 
> notify the sender immediately and destroy this e-mail. Any unauthorised 
> copying, disclosure or distribution of the material in this e-mail is 
> strictly forbidden.



-- 
Zoran Regvart

Feedback on Deprecating the Camel Maven Archetypes

[Claus Ibsen]

Hi

The Camel team is considering deprecating the Camel Maven Archetypes
for 2.x and to remove them in 3.0. We want to remove stuff that are
not much / not in use etc.

I logged a JIRA ticket about this
https://issues.apache.org/jira/browse/CAMEL-12965

We would like feedback from the Camel community users about your point of view.

-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: readLockLoggingLevel File Component

[Claus Ibsen]

Hi

Yeah you are welcome to provide a fix via a github PR
https://github.com/apache/camel/blob/master/CONTRIBUTING.md

If you are a bit lazy you can even just do the PR by editing the
source file from the github web ui directly
On Wed, Nov 28, 2018 at 2:34 PM Zoran Regvart  wrote:
>
> Hi Björn,
> sounds like a great contribution, we love those :)
>
> zoran
> On Wed, Nov 28, 2018 at 1:19 PM  wrote:
> >
> > Hi,
> >
> > one little thing...
> > I have noticed that in the javadocs, documentations,... for the the
> > property readLockLoggingLevel in the File Component, respectively in the
> > class FileChangedExclusiveReadLockStrategy the default is described as
> > 'WARN'. But in the implementation it is 'DEBUG'. It could be helpful to
> > adjust this...
> >
> > Best regards
> > Björn
> >
> >
> > Diese E-Mail könnte vertrauliche und / oder rechtlich geschützte 
> > Informationen enthalten. Wenn Sie nicht der richtige Adressat sind oder 
> > diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den 
> > Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die 
> > unbefugte Weitergabe dieser Mail sind nicht gestattet.
> >
> > This e-mail may contain confidential and / or privileged information. If 
> > you are not the intended recipient (or have received this e-mail in error) 
> > please notify the sender immediately and destroy this e-mail. Any 
> > unauthorised copying, disclosure or distribution of the material in this 
> > e-mail is strictly forbidden.
>
>
>
> --
> Zoran Regvart



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Feedback on Deprecating the Camel Maven Archetypes

[Ron Cecchini]

I don't know if you wanted comments here or on the ticket, but I'll just 
quickly say:

I have made extensive use of the 'camel-archetype-spring-boot' and love it (and 
Camel) to pieces.

> On November 28, 2018 at 12:21 PM Claus Ibsen  wrote:

> The Camel team is considering deprecating the Camel Maven Archetypes
> for 2.x and to remove them in 3.0. We want to remove stuff that are
> not much / not in use etc.
> 
> I logged a JIRA ticket about this
> https://issues.apache.org/jira/browse/CAMEL-12965
> 
> We would like feedback from the Camel community users about your point of 
> view.

Re: Feedback on Deprecating the Camel Maven Archetypes

[Arturo Moreno Arriaga]

I agree. I've found the archetypes very useful to quickly put together Camel 
based applications.

I've done this for POCs and actual production apps.

Arturo,

> On Nov 28, 2018, at 12:47 PM, Ron Cecchini  wrote:
> 
> I don't know if you wanted comments here or on the ticket, but I'll just 
> quickly say:
> 
> I have made extensive use of the 'camel-archetype-spring-boot' and love it 
> (and Camel) to pieces.
> 
>> On November 28, 2018 at 12:21 PM Claus Ibsen  wrote:
> 
>> The Camel team is considering deprecating the Camel Maven Archetypes
>> for 2.x and to remove them in 3.0. We want to remove stuff that are
>> not much / not in use etc.
>> 
>> I logged a JIRA ticket about this
>> https://issues.apache.org/jira/browse/CAMEL-12965
>> 
>> We would like feedback from the Camel community users about your point of 
>> view.

R: Feedback on Deprecating the Camel Maven Archetypes

[Andrea Cosentino]

Yes. Community, we'd like to hear your opinion!

Inviato da Yahoo Mail su Android 
 
  Il mer, 28 nov, 2018 alle 17:21, Claus Ibsen ha 
scritto:   Hi

The Camel team is considering deprecating the Camel Maven Archetypes
for 2.x and to remove them in 3.0. We want to remove stuff that are
not much / not in use etc.

I logged a JIRA ticket about this
https://issues.apache.org/jira/browse/CAMEL-12965

We would like feedback from the Camel community users about your point of view.

-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
  

how could I get multiple different ProducerTemplate instances with Auto-Configured Producer Templates

[Wang Yan]

If I use the auto configured ProducerTemplate, how could I get multiple
different ProducerTemplate instances?

for example I need use producer template send different exchanges to
different endpoints
in this case, Do i need different producer template instances? if yes how ?
Any suggestions ?
Auto-Configured Consumer and Producer Templates

Camel auto-configuration provides pre-configured *ConsumerTemplate* and
*ProducerTemplate* instances. You can simply inject them into your
Spring-managed beans:

@Component
public class InvoiceProcessor {

  @Autowired
  private ProducerTemplate producerTemplate;

  @Autowired
  private ConsumerTemplate consumerTemplate;
  public void processNextInvoice() {
Invoice invoice = consumerTemplate.receiveBody("jms:invoices",
Invoice.class);
...
producerTemplate.sendBody("netty-http:http://invoicing.com/received/";
+ invoice.id());
  }
}

how could I get multiple different ProducerTemplate instances with Auto-Configured Producer Templates

[Wang Yan]

If I use the auto configured ProducerTemplate, how could I get multiple
different ProducerTemplate instances?

for example I need use producer template send different exchanges to
different endpoints
in this case, Do i need different producer template instances? if yes how ?
Auto-Configured Consumer and Producer Templates

Camel auto-configuration provides pre-configured *ConsumerTemplate* and
*ProducerTemplate* instances. You can simply inject them into your
Spring-managed beans:

@Component
public class InvoiceProcessor {

  @Autowired
  private ProducerTemplate producerTemplate;

  @Autowired
  private ConsumerTemplate consumerTemplate;
  public void processNextInvoice() {
Invoice invoice = consumerTemplate.receiveBody("jms:invoices",
Invoice.class);
...
producerTemplate.sendBody("netty-http:http://invoicing.com/received/";
+ invoice.id());
  }
}

Re: Feedback on Deprecating the Camel Maven Archetypes

[Riaan Annandale]

Hi All

I've always used these to spin up a new camel skeleton.

What would the alternative be if they get removed in Camel 3.0?

Thanks

On 2018/11/28 7:21 PM, Claus Ibsen wrote:

Hi

The Camel team is considering deprecating the Camel Maven Archetypes
for 2.x and to remove them in 3.0. We want to remove stuff that are
not much / not in use etc.

I logged a JIRA ticket about this
https://issues.apache.org/jira/browse/CAMEL-12965

We would like feedback from the Camel community users about your point of view.

Rest dynamic load bilancer

[FabryProg]

hello everybody

i have a rest service using rest DSL.

I would write / use a load bilancer based to system load to increase
consumer's thread.

The max number of threads are
Math.max(1, floor10(cpu * 8))

There are a dynamic load bilancer into  apache camel?