On Thu, Mar 24, 2016 at 1:34 PM, Claus Ibsen wrote:
> On Wed, Mar 23, 2016 at 3:55 PM, lb wrote:
>> Hi,
>>
>> I've been working on a number of components in the lates months and what I
>> found
>> a little bit repetitive is to handle endpoints configura
Hi,
I've been working on a number of components in the lates months and what I found
a little bit repetitive is to handle endpoints configuration so I would like to
know if there is any interest about improving such area by adding
support as example
for:
- collections
- nested objects
- validatio
e if ("zipfile".equals(name)) {
// darn should have been lower case
return "zipFile";
} else if ("yaml-snakeyaml".equals(name)) {
return "yaml";
}
return name;
}
On Wed, Mar 2, 2016 at 5:24 PM, lb wrote:
> Hi,
&
Hi,
I'm writing a yaml dataformat which is implemented like the json
dataformat so with the possibility to choose the library to use (even
as today there is only one implementation) and I've an issue as my
component fails to install because of the following error:
Error loading dataformat model f
i docs.
>
> On Thu, Jan 7, 2016 at 10:22 AM, lb wrote:
>> Hi,
>>
>> I've sent a first PR to integrate such component
>> https://github.com/apache/camel/pull/756, please review it and let me
>> know what needs to be improved.
>> I still need to use OSGifi
ave a add component guide here
> http://camel.apache.org/add-new-component-guide.html
>
> I can see that the braintree-java library is MIT licensed so that is
> fine for ASF to accept.
>
>
>
>
>
> On Wed, Dec 16, 2015 at 4:15 PM, lb wrote:
> > Hi,
> >
> > I
Hi,
I've been working on a new Apache Camel component which provides support
for Braintree Payments gateway [1] which. Braintree lets you acees to
payment systems like PayPay (they are a PayPal company) , Apple Pay,
Android Pay through an unified gateway and sdk
The component is available on my
> On Wed, Dec 9, 2015 at 2:52 PM, lb wrote:
> > Hi,
> >
> > I've noticed that the code generated by camel-api-component-maven-plugin
> > for ApiName can potentially generate excessive garbage if fromValue is
> > invoked often, this is because:
> >
> &g
Hi,
I've noticed that the code generated by camel-api-component-maven-plugin
for ApiName can potentially generate excessive garbage if fromValue is
invoked often, this is because:
- enum::values() is not cached so it generates a new array for each call
- new for style generates an iterator each t
