i was scrubbing this page when i saw two endpoint options that both appear
to limit the capacity of the SEDA queue - size, and queueSize [1].
if i'm reading the trunk [2] correctly, i believe *size* is the queue
capacity, whereas queueSize is the actual capacity utilization and is not
actually a (
the wording on this section is unclear to me - does "Also if set to true"
(et seq.) apply to throwExcpetionOnFailure or to bridgeEndpoint?
| {{bridgeEndpoint}} | {{false}} | If true, HttpProducer will ignore the
> Exchange.HTTP_URI header, and use the endpoint's URI for request. You may
> also set
3 sounds good to me too - could benefit other projects besides just Karaf
and Camel :]
~ Reuben
On Fri, Apr 6, 2012 at 13:04, Christian Schneider
wrote:
> We can do three things:
>
> 1. copy the table printer over to camel till 3.0 is out and generally in
> use
> 2. backport table printer to 2.2
in light of feedback from Karaf committers [1], would it be okay to copy
Christian Schneider's table printer [2] into the Camel Karaf commands
project (org.apache.camel.karaf.commands.internal) as a private utility
class, at least until it's available in a Karaf release?
i strongly agree with Clau
not sure if JIRA comments are still replicated to the dev list.
when you have time for a minor issue, kindly review this patch.
~ Reuben
-- Forwarded message --
From: *Reuben Garrett (Updated) (JIRA)*
Date: Wednesday, April 4, 2012
Subject: [jira] [Updated] (CAMEL-4931) Improve
wow,
I'd like to move this discussion to the user list since you have usage
concerns.
my only suggestion is to use log [1] or tracer [2] to help diagnose that
routing details (e.g. headers) match their expected values. the commiters
will be able to give further insight.
[1]: http://camel.apache
apologies - looking at the source code, the component already appears to
support producing [1]. maybe i should better acquaint myself with it and
expand the wiki.
[1] :
http://svn.apache.org/viewvc/camel/trunk/components/camel-eventadmin/src/main/java/org/apache/camel/component/eventadmin/EventAd
just discovered the EventAdmin component - i love OSGi, so i see a lot of
potential here!
is anyone else interested in expanding the component to support LDAP
subscription filters, as well as producing (i.e. publishing OSGi events)?
are there any pitfalls to beware of?
tender scion though i am, i
Impressive! I especially like that the HTML passes validation.
Documentation is sometimes the "unsung hero" of a project, so I appreciate
all your attention to it.
Best regards,
Reuben
r case, it's *not* the email account you used to send this
> message :).
>
> Hadrian
>
>
>
> On 03/01/2012 05:24 PM, Reuben Garrett wrote:
>
>> Bruno,
>>
>> I see your name in the "Unlisted" CLAs @
>> http://people.apache.org/**com
Bruno,
I see your name in the "Unlisted" CLAs @
http://people.apache.org/committer-index.html#unlistedclas
If I remember correctly, you can make your own Confluence and JIRA
accounts, and then ask the committers for karma.
https://issues.apache.org/jira/secure/Signup!default.jspa
https://issues.
bare tokens are interpreted as directories - however
you should be able to use an
Expression<http://camel.apache.org/expression.html>to fine-tune a
rename strategy as described in the File component's user
guide:
http://camel.apache.org/file2.html#File2-FinegrainedcontroloverMoveandPreMoveop
not sure if this is the correct forum to target the issue - but I am
committed to Apache, and in particular I want to build up and promote Camel
as an EIP leader. Is there a way I can resolve this error?
Regards,
Reuben Garrett
Good morning!
Thanks for the advice. I have registered on confluence with the username
rubytuesdaydono.
May I please have editing karma so I can contribute to Camel's
documentation?
Thanks,
Reuben Garrett
On Wed, Mar 10, 2010 at 06:32, Claus Ibsen wrote:
> Hi Reuben
>
> Welco
Salutations!
I am excited to see that my CLA has been received, and I would like to request
an account to commit contributions to Camel. In particular, I would like to
help improve the documentation, at least by proof-reading it for any editorial
issues.
Apache Camel introduced me to the
15 matches
Mail list logo
