[GitHub] camel pull request #1235: Introduce XmppDirectProducer
Github user allancth closed the pull request at: https://github.com/apache/camel/pull/1235 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1239: Cleanup - remove a redundant test resource file
Github user tadayosi closed the pull request at: https://github.com/apache/camel/pull/1239 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Camel 2.19 - Java 8 DSL
Hi I would like to see if we could experiment with continue improving the Java DSL for Java 8 to see if we can make it more Java 8'ish for Content Enricher and Aggregator EIP. They require using the AggregationStrategy interface when you need to merge the 2 exchanges. And it has a POJO binding that allows you to build custom POJO classes without implementing this interface but following a convention. See more at: http://camel.apache.org/aggregator2 in the bottom. And there may be other areas we could ponder about. But the AggregationStrategy has always been one I would like to see can be done simpler when you have simpler use-cases, and hence the POJOs or the FlexibleAggregationStragegyBuilder we have in camel-core somewhere. This is just a quick email to get this though out. -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
[GitHub] camel pull request #1240: CAMEL-10427 - CXFRS client gets "Response timeout"...
Github user asfgit closed the pull request at: https://github.com/apache/camel/pull/1240 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1241: CAMEL-10431: camel-elslq Fix lookup for named para...
GitHub user osmman opened a pull request: https://github.com/apache/camel/pull/1241 CAMEL-10431: camel-elslq Fix lookup for named parameter from headers You can merge this pull request into a Git repository by running: $ git pull https://github.com/osmman/camel camel-elsql Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1241.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1241 commit 1028021b3821a67ef7dfa2d7949f2c9a397dc87d Author: Tomas Turek Date: 2016-11-01T15:26:05Z CAMEL-10431: camel-elslq Fix lookup for named parameter from headers --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
zipfile question - thank you
Camel users, ( thank you ) My project is to receive a zip compressed and encrypted file attachment from a customer, naturally, decompress and decrypt the attachment via email transfer. I am only focusing on the zip portion now because over email I can't get it to work. Seems that the compression size changes when sent over email. It seems my logic works, if I take the zip file and simply drop it in the route from my Jboss environment it works. I can zip, unzip, the file from command line and the camel route. However, if I send the file as an attachment over email, the file size changes, and of course it does not work and throws the error... org.apache.camel.RuntimeCamelException: java.util.zip.ZipException: invalid code lengths set which suggests the zip file attachment has been altered during its transfer over email. The original file size is 9044 Bytes, after email xfr becomes, 15580 Bytes. If I try opening it from the OS with unzip, gunzip, it shows: [root@alphprdfuse2i latest]# unzip ge-ip/core/tobeprocessed/archive/cfindustries.zip.ge Archive: ge-ip/core/tobeprocessed/archive/cfindustries.zip.ge caution: zipfile comment truncated error [ge-ip/core/tobeprocessed/archive/cfindustries.zip.ge]: missing 3282862893 bytes in zipfile (attempting to process anyway) error [ge-ip/core/tobeprocessed/archive/cfindustries.zip.ge]: attempt to seek before beginning of zipfile (please check that you have transferred or created the zipfile in the appropriate BINARY mode and that you have compiled UnZip properly) I've tried changing the file extension to JPEG, PNG, ge, etc... with no success. Does anyone know what I can do to get around this??? Thank you !! Gary Mills
[GitHub] camel pull request #1241: CAMEL-10431: camel-elslq Fix lookup for named para...
Github user osmman closed the pull request at: https://github.com/apache/camel/pull/1241 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Camel 2.19 - Java 8 DSL
Hi Claus, do you have any simple use case to be used as reference to prototype new Java 8 DSL extensions ? --- Luca Burgazzoli On Tue, Nov 1, 2016 at 12:09 PM, Claus Ibsen wrote: > Hi > > I would like to see if we could experiment with continue improving the > Java DSL for Java 8 to see if we can make it more Java 8'ish for > Content Enricher and Aggregator EIP. They require using the > AggregationStrategy interface when you need to merge the 2 exchanges. > And it has a POJO binding that allows you to build custom POJO classes > without implementing this interface but following a convention. See > more at: http://camel.apache.org/aggregator2 in the bottom. > > And there may be other areas we could ponder about. But the > AggregationStrategy has always been one I would like to see can be > done simpler when you have simpler use-cases, and hence the POJOs or > the FlexibleAggregationStragegyBuilder we have in camel-core > somewhere. > > This is just a quick email to get this though out. > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
RE: zipfile question - thank you
DefaultErrorHandler | 198 - org.apache.camel.camel-core -
2.15.1.redhat-620133 | Failed delivery for (MessageId:
ID-alphprdfuse2i-43262-1478008924653-2-36907 on ExchangeId:
ID-alphprdfuse2i-43262-1478008924653-2-36908). Exhausted after delivery
attempt: 1 caught: org.apache.camel.InvalidPayloadException: No body available
of type: java.lang.String but has value:
org.apache.camel.dataformat.zipfile.ZipInputStreamWrapper@bcbe474 of type:
org.apache.camel.dataformat.zipfile.ZipInputStreamWrapper on: Message: [Body is
instance of java.io.InputStream]. Caused by: Error during type conversion from
type: java.lang.String to the required type: java.lang.String with value [Body
is instance of java.io.InputStream] due java.util.zip.ZipException: invalid
code lengths set. Exchange[Message: [Body is instance of java.io.InputStream]].
Caused by: [org.apache.camel.TypeConversionException - Error during type
conversion from type: java.lang.String to the required type: java.lang.String
with value [Body is instance of java.io.InputStream] due
java.util.zip.ZipException: invalid code lengths set]
I am very confused. If I take that zip file and simply drop it in the
fileEntranceEndpoint everything works fine. If I send it through email it
doesn't work. The only thing I've noticed is that the zip file appears to be
corrupted after extracting the attachment and the above is what error is thrown.
Thank you
From: Mills, Gary (GE Digital)
Sent: Tuesday, November 01, 2016 11:52 AM
To: Mills, Gary (GE Digital)
Subject: RE: zipfile question - thank you
Update:
When I send an email to the endpoint email address, with an zip file
attachment, and I open the zip file attachment directly from email endpoint
mailbox, the zip file attachment opens ok. It appears to be related to the
extraction of the attachment in Camel ?
?
From: Mills, Gary (GE Digital)
Sent: Tuesday, November 01, 2016 10:34 AM
To: 'users-i...@camel.apache.org'
mailto:users-i...@camel.apache.org>>
Subject: RE: zipfile question - thank you
Here is the code used to unmarshall the zip file
public void configure() throws Exception {
ZipFileDataFormat zipFile = new ZipFileDataFormat();
zipFile.setUsingIterator(true);
from(fileEntranceEndpoint).id("cfi.zipfile.endpointListenerRoute").log("Message
received zip file: ${file:name}")
.unmarshal(zipFile).split(body(Iterator.class)).streaming().convertBodyTo(String.class)
.log("file names from ZipFile: ${file:name}").to("file://" +
outDirectory);
}
From: Mills, Gary (GE Digital)
Sent: Tuesday, November 01, 2016 10:58 AM
To: 'dev@camel.apache.org' mailto:dev@camel.apache.org>>
Subject: zipfile question - thank you
Camel users, ( thank you )
My project is to receive a zip compressed and encrypted file attachment from a
customer, naturally, decompress and decrypt the attachment via email transfer.
I am only focusing on the zip portion now because over email I can't get it to
work. Seems that the compression size changes when sent over email.
It seems my logic works, if I take the zip file and simply drop it in the route
from my Jboss environment it works. I can zip, unzip, the file from command
line and the camel route. However, if I send the file as an attachment over
email, the file size changes, and of course it does not work and throws the
error...
org.apache.camel.RuntimeCamelException: java.util.zip.ZipException: invalid
code lengths set
which suggests the zip file attachment has been altered during its transfer
over email. The original file size is 9044 Bytes, after email xfr becomes,
15580 Bytes. If I try opening it from the OS with unzip, gunzip, it shows:
[root@alphprdfuse2i latest]# unzip
ge-ip/core/tobeprocessed/archive/cfindustries.zip.ge
Archive: ge-ip/core/tobeprocessed/archive/cfindustries.zip.ge
caution: zipfile comment truncated
error [ge-ip/core/tobeprocessed/archive/cfindustries.zip.ge]: missing
3282862893 bytes in zipfile
(attempting to process anyway)
error [ge-ip/core/tobeprocessed/archive/cfindustries.zip.ge]: attempt to seek
before beginning of zipfile
(please check that you have transferred or created the zipfile in the
appropriate BINARY mode and that you have compiled UnZip properly)
I've tried changing the file extension to JPEG, PNG, ge, etc... with no success.
Does anyone know what I can do to get around this???
Thank you !!
Gary Mills
[GitHub] camel pull request #1236: CAMEL-10350: Add Bonita Component
Github user lio-p closed the pull request at: https://github.com/apache/camel/pull/1236 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Camel 2.19 - Java 8 DSL
Hi
Not yet, but maybe some of those POJO examples in the aggregator EIP.
For example to supply a function as a lambda that is used for
aggregation. For example how would it look like if it was just a basic
function for String concat?
For example this example
public void configure() throws Exception {
from("direct:start")
.aggregate(constant(true),
AggregationStrategies.bean(MyBodyAppender.class, "append"))
.completionSize(3)
.to("mock:result");
}
Also wonder if the lambda can cope with either working with exchange
vs message body only. A bit like what you can do today for message
transformation you did.
On Tue, Nov 1, 2016 at 1:00 PM, Luca Burgazzoli wrote:
> Hi Claus,
>
> do you have any simple use case to be used as reference to prototype
> new Java 8 DSL extensions ?
>
> ---
> Luca Burgazzoli
>
>
> On Tue, Nov 1, 2016 at 12:09 PM, Claus Ibsen wrote:
>> Hi
>>
>> I would like to see if we could experiment with continue improving the
>> Java DSL for Java 8 to see if we can make it more Java 8'ish for
>> Content Enricher and Aggregator EIP. They require using the
>> AggregationStrategy interface when you need to merge the 2 exchanges.
>> And it has a POJO binding that allows you to build custom POJO classes
>> without implementing this interface but following a convention. See
>> more at: http://camel.apache.org/aggregator2 in the bottom.
>>
>> And there may be other areas we could ponder about. But the
>> AggregationStrategy has always been one I would like to see can be
>> done simpler when you have simpler use-cases, and hence the POJOs or
>> the FlexibleAggregationStragegyBuilder we have in camel-core
>> somewhere.
>>
>> This is just a quick email to get this though out.
>>
>>
>>
>> --
>> Claus Ibsen
>> -
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
[GitHub] camel pull request #1242: CAMEL-10344: RouteIdFactory - assigning route ids ...
GitHub user tkopczynski opened a pull request: https://github.com/apache/camel/pull/1242 CAMEL-10344: RouteIdFactory - assigning route ids based on uris This PR adds RouteIdFactory which can be used as a NodeIdFactory implementation in CamelContext as a different strategy for assigning route ids. Currently, it works with direct and similar routes. Unfortunately, I'm not sure on how to integrate this with assigning ids in rest routes. It feels like this should be somewhere in `RestDefinition.addRouteDefinition` but route id is assigned so early that RouteDefinition doesn't have enough information for creating the id from the path. @davsclaus do you have any ideas/suggestions on this? You can merge this pull request into a Git repository by running: $ git pull https://github.com/tkopczynski/camel camel-10344 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1242.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1242 commit f0bc524b7546b398a4a4f804c63a7e0807d1b58a Author: Tomasz Kopczynski Date: 2016-11-01T18:49:06Z CAMEL-10344: RouteIdFactory - assigning route ids based on uris --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Camel 2.19 - Java 8 DSL
Something like:
public void configure() throws Exception {
from("direct:start")
.aggregate()
.always()
.body(String.class, (existing, next) -> next + existing)
.completionSize(3)
.to("mock:result");
}
---
Luca Burgazzoli
On Tue, Nov 1, 2016 at 7:44 PM, Claus Ibsen wrote:
> Hi
>
> Not yet, but maybe some of those POJO examples in the aggregator EIP.
> For example to supply a function as a lambda that is used for
> aggregation. For example how would it look like if it was just a basic
> function for String concat?
>
> For example this example
>
> public void configure() throws Exception {
> from("direct:start")
> .aggregate(constant(true),
> AggregationStrategies.bean(MyBodyAppender.class, "append"))
> .completionSize(3)
> .to("mock:result");
> }
>
>
> Also wonder if the lambda can cope with either working with exchange
> vs message body only. A bit like what you can do today for message
> transformation you did.
>
>
> On Tue, Nov 1, 2016 at 1:00 PM, Luca Burgazzoli wrote:
>> Hi Claus,
>>
>> do you have any simple use case to be used as reference to prototype
>> new Java 8 DSL extensions ?
>>
>> ---
>> Luca Burgazzoli
>>
>>
>> On Tue, Nov 1, 2016 at 12:09 PM, Claus Ibsen wrote:
>>> Hi
>>>
>>> I would like to see if we could experiment with continue improving the
>>> Java DSL for Java 8 to see if we can make it more Java 8'ish for
>>> Content Enricher and Aggregator EIP. They require using the
>>> AggregationStrategy interface when you need to merge the 2 exchanges.
>>> And it has a POJO binding that allows you to build custom POJO classes
>>> without implementing this interface but following a convention. See
>>> more at: http://camel.apache.org/aggregator2 in the bottom.
>>>
>>> And there may be other areas we could ponder about. But the
>>> AggregationStrategy has always been one I would like to see can be
>>> done simpler when you have simpler use-cases, and hence the POJOs or
>>> the FlexibleAggregationStragegyBuilder we have in camel-core
>>> somewhere.
>>>
>>> This is just a quick email to get this though out.
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2: https://www.manning.com/ibsen2
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
[GitHub] camel pull request #1243: CAMEL-10423 - Introduce XmppDirectProducer
GitHub user allancth opened a pull request: https://github.com/apache/camel/pull/1243 CAMEL-10423 - Introduce XmppDirectProducer The order of which producer is used depends on what parameters are specified to the endpoint, with the following precendence: room (GroupChat), pubsub (PubSub), doc (Direct). When these parameters are not specified, by default, a PrivateChat producer will be used. You can merge this pull request into a Git repository by running: $ git pull https://github.com/allancth/camel CAMEL-10423 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1243.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1243 commit b65c9feffe569c392b0b25866e7e35fb4a715f11 Author: Allan C Date: 2016-11-02T02:31:21Z CAMEL-10423 - Introduce XmppDirectProducer --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1244: fix CAMEL-10433 in Camel 2.16.x
GitHub user xldai opened a pull request: https://github.com/apache/camel/pull/1244 fix CAMEL-10433 in Camel 2.16.x You can merge this pull request into a Git repository by running: $ git pull https://github.com/xldai/camel patch-4 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1244.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1244 commit 3e096a5dde6a2a6c352b8ae7c9787addf739c3ac Author: Xilai Dai Date: 2016-11-02T03:17:17Z fix CAMEL-10433 in Camel 2.16.x --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1245: fix CAMEL-10433 in Camel 2.17.x
GitHub user xldai opened a pull request: https://github.com/apache/camel/pull/1245 fix CAMEL-10433 in Camel 2.17.x You can merge this pull request into a Git repository by running: $ git pull https://github.com/xldai/camel patch-3 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1245.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1245 commit 20775ecf3b5c211ab309009e78ee7f529ae38645 Author: Xilai Dai Date: 2016-11-02T03:13:10Z fix CAMEL-10433 in Camel 2.17.x --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Camel.trunk.notest - Build # 2923 - Still Failing
The Apache Jenkins build system has built Camel.trunk.notest (build #2923) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.trunk.notest/2923/ to view the results.
