The Apache Jenkins build system has built Camel.trunk.notest (build #2714)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2714/
to view the results.
Hi,
Which camel version are you using? MIME-Multipart is only available starting
Camel 2.17.0.
I am not 100% sure, but your response looks somewhat like SOAP with attachments
or MTOM. If you are using some kind of Camel-CXF endpoint for receiving it, the
endpoint might parse it for you.
Best
On Thu, Mar 24, 2016 at 1:12 PM, Gnanaguru S wrote:
>
> Guys,
>
> These are some of the feature, I wish to see in upcoming camel versions. It
> would be useful to have.
>
> 1. Timeout option in a internal synchronous endpoint - we very much use
> camel for orchestration layer. In a use case where
On Thu, Apr 7, 2016 at 2:51 PM, tristanh wrote:
> Claus Ibsen-2 wrote
>> Can you provide an example of the two uris with and withour arn. What
>> are the rules for an arn, is it just a text or does it use colons in
>> the text ?
>
> Yes the arn contains colons.
>
> With just the queue name current
tristanh wrote
> With just the queue name currently it's
>
> sqs:queue-name?amazonSQSClient=#sqsClient&attributeNames=#sqsAttributeNames&queueOwnerAWSAccountId=123456789®ion=eu-west-1
>
> equivalent using an arn would be:
>
> sqs:arn:aws:sqs:eu-west-1:123456789:queue-name?amazonSQSClient=#sqsCli
Claus Ibsen-2 wrote
> Can you provide an example of the two uris with and withour arn. What
> are the rules for an arn, is it just a text or does it use colons in
> the text ?
Yes the arn contains colons.
With just the queue name currently it's
sqs:queue-name?amazonSQSClient=#sqsClient&attribute
Hi,
Is there anybody available in this list who knows why the attachment handling
in Camel is as it is?
I have had a look into this topic with the Camel-Mail and Camel-CXF components
and would like to discuss my thoughts about that.
In General the attachment handling is designed to support use
GitHub user erwelch opened a pull request:
https://github.com/apache/camel/pull/935
CAMEL-9462 HTTP 1.1 Host header be dealt wrongly in proxy & load balancer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/erwelch/camel CAMEL-946
+1 (binding)
Regards
JB
On 04/03/2016 09:27 PM, Gregor Zurowski wrote:
Hi Everyone:
This is a vote to release Apache Camel 2.16.3, a new patch release
that includes 75+ fixes and improvements.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334721&projectId=12
Can you provide an example of the two uris with and withour arn. What
are the rules for an arn, is it just a text or does it use colons in
the text ?
The concern is how parsing the uri becomes more complicated in terms
of mapping that correct to the options.
On Thu, Apr 7, 2016 at 1:34 PM, Tris
Hi,
To simplify our application configuration I would like camel's aws-sqs
component to accept an arn as well as the queue name is does currently.
Since the region and account number are also in the arn this would
also help avoid needing the listqueues permissions as the queue url
could be co
Github user spegelref closed the pull request at:
https://github.com/apache/camel/pull/934
---
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
GitHub user spegelref opened a pull request:
https://github.com/apache/camel/pull/934
Support for PATCH method in Rest DSL
Added new verb to the Rest model, the PatchVerbDefinition and made made
the jaxb parser aware of this new file.
Added instructions in RestDefinition and
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/932
---
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 enabl
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/931
---
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 enabl
Hi Raúl
A simple workaround to remove this ambiguity is to use odd micro
versions for snapshots only and even micro versions for releases. We
use this strategy in the Apache Sling project successfully since
several years.
I.e.
1.0.1-SNAPSHOT
1.0.2 <-- release
1.0.3-SNAPSHOT
1.0.4 <-- release
Reg
16 matches
Mail list logo
