[
https://issues.apache.org/jira/browse/CAMEL-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Keller resolved CAMEL-4476.
-
Resolution: Not A Problem
This looks like it was caused by using xxx expressions for the
complet
[
https://issues.apache.org/jira/browse/CAMEL-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112353#comment-13112353
]
Claus Ibsen commented on CAMEL-4475:
ProcessorDefinition should implement NamedNode, a
[
https://issues.apache.org/jira/browse/CAMEL-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112352#comment-13112352
]
Claus Ibsen commented on CAMEL-4475:
Another problem is that you remove existing code,
[
https://issues.apache.org/jira/browse/CAMEL-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112351#comment-13112351
]
Claus Ibsen commented on CAMEL-4475:
Do not change the model classes, they should stil
I think in general we should only port bug fixes. Normally I would not
backport improvements as they have a higher chance of breaking code.
This said I think the backports for 2.8.2 are ok as 2.9.0 will
definately introduce some incompatibilities because of the many
refactorings I did. So the
On Wed, Sep 21, 2011 at 4:23 PM, Daniel Kulp wrote:
> On Wednesday, September 21, 2011 2:53:49 PM Rob Davies wrote:
>> For my part it is the principle - at some point this will go wrong - doing
>> what Chistian suggested makes a lot of sense. And, users in production want
>> stability, fixes are g
On Thu, Sep 22, 2011 at 4:17 AM, Johan Edstrom wrote:
> I'll step in here…
>
> Much of what Dan has done is in the corporate world very very much wanted.
> Dan offered his time to keep on back porting fixing and non api breaking
> features.
>
Dan is not the only person doing this. We are already
On Thu, Sep 22, 2011 at 4:08 AM, Christian Müller
wrote:
> May I miss something, but at the moment it's not really clear for me WHAT
> should be backported.
Me too.
> Do we backport EVERYTHING which doesn't break existing code (not only bugs)?
> Also new features and enhancements with the risk o
[
https://issues.apache.org/jira/browse/CAMEL-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112328#comment-13112328
]
Taariq Levack commented on CAMEL-4474:
--
Great.
The reason is stated in the comments
I'll step in here…
Much of what Dan has done is in the corporate world very very much wanted.
Dan offered his time to keep on back porting fixing and non api breaking
features.
That means we'll see (and we can debate that) "done in 2.9, available in 2.8.5)
I think Dan already said he should hav
May I miss something, but at the moment it's not really clear for me WHAT
should be backported.
Do we backport EVERYTHING which doesn't break existing code (not only bugs)?
Also new features and enhancements with the risk of introducing new bugs?
Only to make it clear for me and may others...
And
[
https://issues.apache.org/jira/browse/CAMEL-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112283#comment-13112283
]
Hadrian Zbarcea commented on CAMEL-4034:
@Ioannis, committed patch and minor fixes
Camel splitter/aggregator 2x slower in 2.8.1 vs 2.7.3
-
Key: CAMEL-4476
URL: https://issues.apache.org/jira/browse/CAMEL-4476
Project: Camel
Issue Type: Bug
Components: camel-core
[
https://issues.apache.org/jira/browse/CAMEL-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben O'Day resolved CAMEL-4097.
--
Resolution: Fixed
change committed and docs updated (Aggregator2, 2.9 Release Notes)...
> Add option o
okei, i think i am subscribed now.
Our maven is using this version:
2.7.1
We do not need a bug fix, as we found out that we need multiple codec. We
are just reporting a bug.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-netty-encode-bug-tp4825369p4827395.htm
[
https://issues.apache.org/jira/browse/CAMEL-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109759#comment-13109759
]
David J. M. Karlsen commented on CAMEL-4474:
Hah! You are dead-right - but why
[
https://issues.apache.org/jira/browse/CAMEL-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated CAMEL-4475:
---
Attachment: camel-4475-1.patch
> Make API self contained
> ---
>
[
https://issues.apache.org/jira/browse/CAMEL-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated CAMEL-4475:
---
Attachment: camel-4475-after.png
camel-4475-before.png
> Make API sel
Make API self contained
---
Key: CAMEL-4475
URL: https://issues.apache.org/jira/browse/CAMEL-4475
Project: Camel
Issue Type: Improvement
Components: camel-core
Affects Versions: 2.8.0
Reporter: C
[
https://issues.apache.org/jira/browse/CAMEL-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Zhemzhitsky updated CAMEL-4473:
--
Attachment: camel-cxf-binding-failure-test.zip
Valid camel-cxf-binding-failure-test.zip
[
https://issues.apache.org/jira/browse/CAMEL-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Zhemzhitsky updated CAMEL-4473:
--
Comment: was deleted
(was: Hi, please change the extension of the attachment to 7z.)
>
[
https://issues.apache.org/jira/browse/CAMEL-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Zhemzhitsky updated CAMEL-4473:
--
Attachment: (was: camel-cxf-binding-failure-test.zip)
> Unable to use cxf:binding c
[
https://issues.apache.org/jira/browse/CAMEL-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider closed CAMEL-4431.
--
> Zookeeper tests do not work on windows
> --
>
>
[
https://issues.apache.org/jira/browse/CAMEL-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved CAMEL-4431.
Resolution: Fixed
> Zookeeper tests do not work on windows
> --
Awesome! - thanks Dan
On 21 Sep 2011, at 15:23, Daniel Kulp wrote:
> On Wednesday, September 21, 2011 2:53:49 PM Rob Davies wrote:
>> For my part it is the principle - at some point this will go wrong - doing
>> what Chistian suggested makes a lot of sense. And, users in production want
>> stabili
[
https://issues.apache.org/jira/browse/CAMEL-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109670#comment-13109670
]
Sergey Zhemzhitsky commented on CAMEL-4473:
---
Hi, please change the extension of
[
https://issues.apache.org/jira/browse/CAMEL-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben O'Day updated CAMEL-4397:
-
Description:
add support for Hazelcast distributed locking/unlocking APIs in a route...see
http://www.ha
[
https://issues.apache.org/jira/browse/CAMEL-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109638#comment-13109638
]
Ben O'Day commented on CAMEL-4397:
--
hey Sergey, what you described is CAMEL-4454...using
[
https://issues.apache.org/jira/browse/CAMEL-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109617#comment-13109617
]
David J. M. Karlsen commented on CAMEL-4474:
I will have to test tomorrow at w
[
https://issues.apache.org/jira/browse/CAMEL-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109600#comment-13109600
]
Taariq Levack commented on CAMEL-4474:
--
You're using a dot in the directory name whic
[
https://issues.apache.org/jira/browse/CAMEL-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109597#comment-13109597
]
Claus Ibsen commented on CAMEL-4397:
Sergey sounds good. And possible make it possible
[
https://issues.apache.org/jira/browse/CAMEL-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4472.
Resolution: Fixed
Fix Version/s: 2.9.0
2.8.2
Assignee: Claus Ibse
[
https://issues.apache.org/jira/browse/CAMEL-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109590#comment-13109590
]
Claus Ibsen commented on CAMEL-4472:
The copyHeaders is only used by the producers as
[
https://issues.apache.org/jira/browse/CAMEL-4366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4366.
Resolution: Fixed
> Expose Exchange Load statistics in Route and Context MBeans
> -
[
https://issues.apache.org/jira/browse/CAMEL-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David J. M. Karlsen updated CAMEL-4474:
---
Attachment: test-context.xml
app-config-context.xml
Ca
[
https://issues.apache.org/jira/browse/CAMEL-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109534#comment-13109534
]
Taariq Levack edited comment on CAMEL-4474 at 9/21/11 2:40 PM:
-
[
https://issues.apache.org/jira/browse/CAMEL-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109534#comment-13109534
]
Taariq Levack commented on CAMEL-4474:
--
David can you please post a test for this?
Th
On Wednesday, September 21, 2011 2:53:49 PM Rob Davies wrote:
> For my part it is the principle - at some point this will go wrong - doing
> what Chistian suggested makes a lot of sense. And, users in production want
> stability, fixes are good, new features leads naturally to concern about
> stabi
[
https://issues.apache.org/jira/browse/CAMEL-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang reassigned CAMEL-4473:
---
Assignee: Willem Jiang
> Unable to use cxf:binding configuration for the endpoint
> -
For my part it is the principle - at some point this will go wrong - doing what
Chistian suggested makes a lot of sense. And, users in production want
stability, fixes are good, new features leads naturally to concern about
stability. It should be good practice to give a heads up at least, befor
This is an emotional non-discussion. The question in the title is what
is the reason for the *many* backports. An explanation was also given:
if they are *many* bugs (or improvements), they should be fixed, and in
dkulp's opinion not only on the trunk but also on the maintained
branches. There
[
https://issues.apache.org/jira/browse/CAMEL-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109460#comment-13109460
]
Sergey Zhemzhitsky edited comment on CAMEL-4397 at 9/21/11 1:29 PM:
[
https://issues.apache.org/jira/browse/CAMEL-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109460#comment-13109460
]
Sergey Zhemzhitsky commented on CAMEL-4397:
---
Hi guys,
What do you think about o
file: consumer does not create directory
Key: CAMEL-4474
URL: https://issues.apache.org/jira/browse/CAMEL-4474
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.8
[
https://issues.apache.org/jira/browse/CAMEL-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Zhemzhitsky updated CAMEL-4473:
--
Attachment: camel-cxf-binding-failure-test.zip
Unit test has been attached
> Unable to
Unable to use cxf:binding configuration for the endpoint
Key: CAMEL-4473
URL: https://issues.apache.org/jira/browse/CAMEL-4473
Project: Camel
Issue Type: Bug
Components: came
[
https://issues.apache.org/jira/browse/CAMEL-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomislav Mrkus updated CAMEL-4472:
--
Attachment: CAMEL-4472.patch
> HazelcastComponentHelper. copyHeaders() creates an Out message
>
HazelcastComponentHelper. copyHeaders() creates an Out message
--
Key: CAMEL-4472
URL: https://issues.apache.org/jira/browse/CAMEL-4472
Project: Camel
Issue Type: Bug
Comp
Hi,
I have an question about the printercomponent.
This component does currently not support things like MediaTray, are there any
plans
to add support for this printer attribute?
Best regards,
Evert
Hi
Its best to use the @user mailing list.
Anyway what version of Camel are you using?
On Wed, Sep 21, 2011 at 9:01 AM, stenver wrote:
> we tried to set up a custom encoder with netty tcp.
>
> Here was our encoder class, for testing:
>
> @Component("EndOfLineEncoder")
> public class EndOfLineE
we tried to set up a custom encoder with netty tcp.
Here was our encoder class, for testing:
@Component("EndOfLineEncoder")
public class EndOfLineEncoder extends OneToOneEncoder{
@Override
protected Object encode(ChannelHandlerContext channelHandlerContext,
Channel channe
51 matches
Mail list logo
