[
https://issues.apache.org/jira/browse/CAMEL-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-3681.
Resolution: Fixed
trunk: 1071901.
> Add byte[] to DOMSource type converter
> -
Add byte[] to DOMSource type converter
--
Key: CAMEL-3681
URL: https://issues.apache.org/jira/browse/CAMEL-3681
Project: Camel
Issue Type: Improvement
Components: camel-core
Affects Versions:
[
https://issues.apache.org/jira/browse/CAMEL-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-3676.
Resolution: Fixed
> Remove $version$ from the source files
> --
Hi
On Fri, Feb 18, 2011 at 1:45 AM, Hiram Chirino wrote:
> I just did a similar thing for ActiveMQ, If there were actually a
> couple of variations need to hand the other svn keyword tags. Gotta
> dig for them in my bash history. If you don't get to it before I do,
> I'll apply them to the sour
I just did a similar thing for ActiveMQ, If there were actually a
couple of variations need to hand the other svn keyword tags. Gotta
dig for them in my bash history. If you don't get to it before I do,
I'll apply them to the source tree.
Regards,
Hiram
FuseSource
Web: http://fusesource.com/
[
https://issues.apache.org/jira/browse/CAMEL-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-3676 started by Claus Ibsen.
> Remove $version$ from the source files
> --
>
> Key: CAMEL-3676
>
[
https://issues.apache.org/jira/browse/CAMEL-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995905#comment-12995905
]
Claus Ibsen commented on CAMEL-3676:
Hmm seems like that last command was a bit to gre
[
https://issues.apache.org/jira/browse/CAMEL-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-3676:
--
Assignee: Claus Ibsen
> Remove $version$ from the source files
> --
[
https://issues.apache.org/jira/browse/CAMEL-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995890#comment-12995890
]
Claus Ibsen commented on CAMEL-3676:
This is the command I used
{code}
find . -name '*
camel-rmi - Add support for using Spring RMI exporter
-
Key: CAMEL-3680
URL: https://issues.apache.org/jira/browse/CAMEL-3680
Project: Camel
Issue Type: Improvement
Affects Versions: 2.
People is welcome to experiment with the Java DSL to see if you can
find a nicer solution.
I added 2 tests in the CBR which is the goal to have working. Just
rename endChoice to end.
The commit is here:
http://svn.apache.org/viewvc?rev=1071613&view=rev
On Thu, Feb 17, 2011 at 2:52 PM, Claus Ib
[
https://issues.apache.org/jira/browse/CAMEL-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995808#comment-12995808
]
Claus Ibsen commented on CAMEL-3678:
trunk: 1071613.
I added {{endChoice()}} to the D
Hmmm DSL in pure Java is pants.
I have made several attempts, and it may compile but then fail at runtime.
The endChoice is out best option so far. So I am gonna commit that so
people can use the CBR with whatever EIPs inside as they want to do.
Without this they would have to create new routes a
There is enough consensus :). Just go for it.
Hadrian
On Feb 16, 2011, at 7:19 PM, Willem Jiang wrote:
> +1 to remove it, we can see the file version by checking the file svn
> property.
>
> On 2/16/11 10:11 PM, Claus Ibsen wrote:
>> Hi
>>
>> Many of the Java files in Camel source code have
[
https://issues.apache.org/jira/browse/CAMEL-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995799#comment-12995799
]
Willem Jiang commented on CAMEL-3679:
-
This issue is caused by [an issue|http://jira.c
Workaround the maven javadoc link issue.
Key: CAMEL-3679
URL: https://issues.apache.org/jira/browse/CAMEL-3679
Project: Camel
Issue Type: Improvement
Reporter: Willem Jiang
Pri
Hi Ashwin,
Thanks for your input. The way you described it, without port number, is
also how it's explained on the JavaSpaces component website. I should have
mentioned that in my first posting, but I tried that already and it didn't
work, that's when I figured adding the port number might help -
[
https://issues.apache.org/jira/browse/CAMEL-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Jelinski closed CAMEL-3677.
--
Resolution: Fixed
Workaround no longer needed.
> When splitting inside another split, the cust
[
https://issues.apache.org/jira/browse/CAMEL-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995790#comment-12995790
]
Oliver Jelinski commented on CAMEL-3677:
Yes, sorry, I didn't use 2.6 yet, because
[
https://issues.apache.org/jira/browse/CAMEL-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Jelinski updated CAMEL-3677:
---
Fix Version/s: 2.6.0
> When splitting inside another split, the custom aggregationStrategy is
Hi
Thanks for the suggestions. I have created a ticket
https://issues.apache.org/jira/browse/CAMEL-3678
I managed to get a bit further. I will attach a patch with as far as I will get.
You can actually have the code compile, but when you run the Java DSL
fails with a type cast exception when sta
Java DSL - Allow load balancer to be used inside CBR
Key: CAMEL-3678
URL: https://issues.apache.org/jira/browse/CAMEL-3678
Project: Camel
Issue Type: Improvement
Components: came
[
https://issues.apache.org/jira/browse/CAMEL-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995780#comment-12995780
]
Claus Ibsen commented on CAMEL-3677:
Can you try with Camel 2.6.0 - We have fixed issu
When splitting inside another split, the custom aggregationStrategy is not used.
Key: CAMEL-3677
URL: https://issues.apache.org/jira/browse/CAMEL-3677
Project: Camel
Hi Claus,
you do not need to override the to actually, it's my mistake. Your example
compiles without overriding the "to" method (s) and whatever methods.
because
extends ProcessorDefinition
gives processor definition the right type.
Regards,
Mitko
From:
Claus Ibsen
To:
dev
Hi
It is a good idea but do we really dont want to override every methods
from ProcessorDefinition in all the sub classes, to work around the
limitations with DSLs in Java? And the implications of keeping the
code synchronized.
On Thu, Feb 17, 2011 at 11:54 AM, wrote:
> Hello Camel Developer
Hello Camel Developers what about this:
public class LoadBalanceDefinition>
extends ProcessorDefinition {
...
public LoadBalanceDefinition roundRobin() {
...
@SuppressWarnings("unchecked")
public Type to(String uri) {
return (Type) this;
}
...
}
Thus yo
[
https://issues.apache.org/jira/browse/CAMEL-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved CAMEL-3638.
Resolution: Fixed
> Upgrade maven-bundle-plugin to version 1.3.4
>
On 17 February 2011 08:48, Claus Ibsen wrote:
> Hi
>
> DSL in plain Java is somewhat limited how far you can go with Java and
> Generics.
>
> A common issue over the times has been the Content Based Router where
> users would use other "complex patterns" inside the when/otherwise
> blocks.
> By c
Hi
DSL in plain Java is somewhat limited how far you can go with Java and Generics.
A common issue over the times has been the Content Based Router where
users would use other "complex patterns" inside the when/otherwise
blocks.
By complex patterns I mean patterns which have additional DSL for
co
30 matches
Mail list logo
