On Thu, Nov 10, 2011 at 11:08 PM, marcelk wrote:
> Hi,
>
> I noticed that when using generateHeaderColumns the header generated doesnt
> have the right seperator as in the content:
>
> @CsvRecord(separator = "\\t", generateHeaderColumns=true, crlf="WINDOWS")
>
> This produces:
> orderNr\tfirstName
Hi,
I noticed that when using generateHeaderColumns the header generated doesnt
have the right seperator as in the content:
@CsvRecord(separator = "\\t", generateHeaderColumns=true, crlf="WINDOWS")
This produces:
orderNr\tfirstName
10 Marcel
I would expect the \t to be handled as tab.
So
[
https://issues.apache.org/jira/browse/CAMEL-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148312#comment-13148312
]
Björn Bength commented on CAMEL-4666:
-
Yes, i sent a separate email to the dev-list wi
Upgrade CXF version to 2.4.4
Key: CAMEL-4667
URL: https://issues.apache.org/jira/browse/CAMEL-4667
Project: Camel
Issue Type: Task
Components: camel-cxf
Reporter: Willem Jiang
As
This is for the latest 2.8.2 version.
--
View this message in context:
http://camel.465427.n5.nabble.com/Bindy-csv-and-generateHeaderColumns-doesnt-work-with-tabs-tp4982555p4982563.html
Sent from the Camel Development mailing list archive at Nabble.com.
[
https://issues.apache.org/jira/browse/CAMEL-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148191#comment-13148191
]
Christian Müller commented on CAMEL-4666:
-
Björn, I have a look on it right now.
[
https://issues.apache.org/jira/browse/CAMEL-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Müller reassigned CAMEL-4666:
---
Assignee: Christian Müller
> support catalog entity resolver in validator-compone
[
https://issues.apache.org/jira/browse/CAMEL-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148085#comment-13148085
]
Björn Bength edited comment on CAMEL-4666 at 11/10/11 11:01 PM:
[
https://issues.apache.org/jira/browse/CAMEL-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Björn Bength updated CAMEL-4666:
Attachment: validator-catalog.patch
applies to camel-core.
decided to upload my little patch to hav
Should we make an improvement to specify a catalog file on the
validator uri? (simple but "limited" to just this catalog resolver)
Or should the validator processor and component offer a setter to
inject whatever entity resolver and make this catalog resolver a
separately configured bean. (more com
[
https://issues.apache.org/jira/browse/CAMEL-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148035#comment-13148035
]
Björn Bength commented on CAMEL-4666:
-
Since I didn't find a way to configure a catalo
[
https://issues.apache.org/jira/browse/CAMEL-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ole Kristian Hofstad updated CAMEL-4660:
Patch Info: Patch Available
Labels: Aggregation (was: aggregator)
> Ha
support catalog entity resolver in validator-component
--
Key: CAMEL-4666
URL: https://issues.apache.org/jira/browse/CAMEL-4666
Project: Camel
Issue Type: Improvement
Components:
Agreed. Thanks Christian.
On Thu, Nov 10, 2011 at 1:01 PM, Christian Müller (Commented) (JIRA) <
j...@apache.org> wrote:
>
>[
> https://issues.apache.org/jira/browse/CAMEL-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148006#comment-13148006]
>
[
https://issues.apache.org/jira/browse/CAMEL-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148006#comment-13148006
]
Christian Müller commented on CAMEL-4528:
-
Hey Rich!
Thank you for the patch. We
[
https://issues.apache.org/jira/browse/CAMEL-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Valeri reassigned CAMEL-4665:
---
Assignee: David Valeri
> Add support for Camel JSSE Configuration Util to Mail component
Add support for Camel JSSE Configuration Util to Mail component
---
Key: CAMEL-4665
URL: https://issues.apache.org/jira/browse/CAMEL-4665
Project: Camel
Issue Type: Improvement
Add support for Camel JSSE Configuration Util to IRC component
--
Key: CAMEL-4664
URL: https://issues.apache.org/jira/browse/CAMEL-4664
Project: Camel
Issue Type: Improvement
Add support for Camel JSSE Configuration Util to Comet component
Key: CAMEL-4663
URL: https://issues.apache.org/jira/browse/CAMEL-4663
Project: Camel
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/CAMEL-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Müller closed CAMEL-4654.
---
Resolution: Fixed
> Upgrade the org.apache.servicemix.bundles to the lates hotfix version
Figured I should respond to this important email... though maybe we have
lazy consensus on the topic? ;)
I think in general this makes a lot of sense and really, we are following
most of this right now anyways. And of course, these are not hard and fast
rules and we can always DISCUSS later for sp
[
https://issues.apache.org/jira/browse/CAMEL-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147911#comment-13147911
]
Tarjei Huse commented on CAMEL-4650:
Babak, thank you for working on this issue.
As
[
https://issues.apache.org/jira/browse/CAMEL-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tarjei Huse closed CAMEL-4650.
--
Resolution: Not A Problem
Closed as API misuse.
> NPE when using SEDA route and attac
Hi guys,
I've just created a feature request to add batch SQL update support to
the SQL component. It includes a patch with a prototype implementation:
https://issues.apache.org/jira/browse/CAMEL-4662
I'd be interested to hear any opinions, suggestions, etc.
Take care,
Daniel
[
https://issues.apache.org/jira/browse/CAMEL-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Newcomb updated CAMEL-4528:
Patch Info: Patch Available
> XSLT component - Add JMX to the endpoint, and expose operations t
[
https://issues.apache.org/jira/browse/CAMEL-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Newcomb reassigned CAMEL-4528:
---
Assignee: (was: Rich Newcomb)
> XSLT component - Add JMX to the endpoint, and expose
[
https://issues.apache.org/jira/browse/CAMEL-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Newcomb updated CAMEL-4528:
Attachment: camel-4528.patch
Patch with unit tests attached.
I also added a note to the XSLT wiki
[
https://issues.apache.org/jira/browse/CAMEL-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147832#comment-13147832
]
Babak Vahdat commented on CAMEL-4650:
-
I could reproduce your issue on the trunk throu
add batching support to sql component
-
Key: CAMEL-4662
URL: https://issues.apache.org/jira/browse/CAMEL-4662
Project: Camel
Issue Type: New Feature
Components: camel-sql
Affects Versions: 2.
[
https://issues.apache.org/jira/browse/CAMEL-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Gredler updated CAMEL-4662:
--
Attachment: camel-4662.patch
patch to trunk
> add batching support to sql comp
DefaultUnitOfWork doesn't copy headers to originalInMessage for JmsMessages
---
Key: CAMEL-4661
URL: https://issues.apache.org/jira/browse/CAMEL-4661
Project: Camel
Issu
[
https://issues.apache.org/jira/browse/CAMEL-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ole Kristian Hofstad updated CAMEL-4660:
Attachment: initialCompletionIntervalTest.patch
Added patch with test to reproduce
[
https://issues.apache.org/jira/browse/CAMEL-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-4528 started by Rich Newcomb.
> XSLT component - Add JMX to the endpoint, and expose operations to clear the
> cache, so resources is forced to be reloaded
[
https://issues.apache.org/jira/browse/CAMEL-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Newcomb reassigned CAMEL-4528:
---
Assignee: Rich Newcomb
> XSLT component - Add JMX to the endpoint, and expose operations
[
https://issues.apache.org/jira/browse/CAMEL-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ole Kristian Hofstad updated CAMEL-4660:
Summary: Hardcoded initial delay for completionInterval in
AggregateProcessor (was
[
https://issues.apache.org/jira/browse/CAMEL-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ole Kristian Hofstad updated CAMEL-4660:
Description:
When setting the completionInterval on an aggregator, the first comple
[
https://issues.apache.org/jira/browse/CAMEL-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ole Kristian Hofstad updated CAMEL-4660:
Attachment: initialCompletionInterval.patch
Patch which sets the initial delay to t
Hardcoded initial delay for completionInterval in AggregatorService
---
Key: CAMEL-4660
URL: https://issues.apache.org/jira/browse/CAMEL-4660
Project: Camel
Issue Type: Bug
Open the range when importing org.apache.fe lix.gogo.commands package
-
Key: CAMEL-4659
URL: https://issues.apache.org/jira/browse/CAMEL-4659
Project: Camel
Issue Type: Bug
Yeah, currently you'd need a karaf 2.2.4
I think we should open the range to older versions of karaf so that it can
still be deployed onto older karaf versions.
On Thu, Nov 10, 2011 at 05:49, Aleksey Sushko (Created) (JIRA) <
j...@apache.org> wrote:
> Camel 2.9.0 SNAPSHOT not start on OSGI apach
[
https://issues.apache.org/jira/browse/CAMEL-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Sushko updated CAMEL-4658:
--
Description:
Compiling my project is done using maven pluggins
maven-dependency-plugin and feat
Camel 2.9.0 SNAPSHOT not start on OSGI apache karaf
---
Key: CAMEL-4658
URL: https://issues.apache.org/jira/browse/CAMEL-4658
Project: Camel
Issue Type: Bug
Reporter: Aleksey Sushko
[
https://issues.apache.org/jira/browse/CAMEL-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147558#comment-13147558
]
Babak Vahdat edited comment on CAMEL-4650 at 11/10/11 11:57 AM:
camel-jms - Request/Reply - Leak in ActiveMQSessionPool causing it to eat up
memory, when using fixed replyTo queue names
-
Key: CAMEL-4657
URL
[
https://issues.apache.org/jira/browse/CAMEL-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4656.
Resolution: Fixed
> camel-jms - Request/Reply - Cache consumer for exclusive replyTo type, or i
camel-jms - Request/Reply - Cache consumer for exclusive replyTo type, or if
replyToDestinationSelectorName is used for shared replyTo type
---
[
https://issues.apache.org/jira/browse/CAMEL-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147558#comment-13147558
]
Babak Vahdat commented on CAMEL-4650:
-
Yeah try stopping the main route first before s
[
https://issues.apache.org/jira/browse/CAMEL-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147551#comment-13147551
]
Tarjei Huse commented on CAMEL-4650:
Hi Babak,
1. Yes both routes are in the same con
48 matches
Mail list logo