[jira] [Commented] (CAMEL-7422) camel-rabbit - Consumer tuning: thread count, prefetch
[ https://issues.apache.org/jira/browse/CAMEL-7422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017416#comment-14017416 ] Willem Jiang commented on CAMEL-7422: - Applied the patch into master branch with thanks to Ramon. camel-rabbit - Consumer tuning: thread count, prefetch -- Key: CAMEL-7422 URL: https://issues.apache.org/jira/browse/CAMEL-7422 Project: Camel Issue Type: Improvement Components: camel-rabbitmq Affects Versions: 2.13.0 Reporter: Gérald Quintana Priority: Minor Add RabbitMQ consumer options: - consumerCount : number of concurrent threads/channels used to consume messages - prefetchSize : amount of content (in octets) the broker will deliver - prefetchCount : number of messages the broker will deliver http://www.rabbitmq.com/javadoc/com/rabbitmq/client/Channel.html#basicQos%28int,%20int,%20boolean%29 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7422) camel-rabbit - Consumer tuning: thread count, prefetch
[ https://issues.apache.org/jira/browse/CAMEL-7422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017424#comment-14017424 ] Willem Jiang commented on CAMEL-7422: - I just updated the wiki page of camel-rabbitmq to add these new options. camel-rabbit - Consumer tuning: thread count, prefetch -- Key: CAMEL-7422 URL: https://issues.apache.org/jira/browse/CAMEL-7422 Project: Camel Issue Type: Improvement Components: camel-rabbitmq Affects Versions: 2.13.0 Reporter: Gérald Quintana Priority: Minor Add RabbitMQ consumer options: - consumerCount : number of concurrent threads/channels used to consume messages - prefetchSize : amount of content (in octets) the broker will deliver - prefetchCount : number of messages the broker will deliver http://www.rabbitmq.com/javadoc/com/rabbitmq/client/Channel.html#basicQos%28int,%20int,%20boolean%29 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-6869) camel-rabbitmq - Support reconnection when broker goes down
[ https://issues.apache.org/jira/browse/CAMEL-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017475#comment-14017475 ] Gérald Quintana commented on CAMEL-6869: Is there any problem with my PR? I am open to criticism. camel-rabbitmq - Support reconnection when broker goes down --- Key: CAMEL-6869 URL: https://issues.apache.org/jira/browse/CAMEL-6869 Project: Camel Issue Type: New Feature Components: camel-rabbitmq Affects Versions: 2.12.0 Reporter: Marcus Nilsson Assignee: Rich Newcomb Currently, the if you stop the RabbitMQ broker, no reconnects happen. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7477) camel-jclouds - operation is wrong in docs
Claus Ibsen created CAMEL-7477: -- Summary: camel-jclouds - operation is wrong in docs Key: CAMEL-7477 URL: https://issues.apache.org/jira/browse/CAMEL-7477 Project: Camel Issue Type: Task Components: camel-jclouds, documentation Reporter: Claus Ibsen Priority: Minor Fix For: 2.14.0 See http://camel.465427.n5.nabble.com/camel-jclouds-parameter-operation-ignored-tp5750789p5750791.html Though the value of the operation would be better if it was just get or put etc. But the key should be CamelJcloudsOperation still. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7455) supporting body in sql component
[
https://issues.apache.org/jira/browse/CAMEL-7455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017676#comment-14017676
]
ASF GitHub Bot commented on CAMEL-7455:
---
GitHub user adessaigne opened a pull request:
https://github.com/apache/camel/pull/169
CAMEL-7455 supporting body in sql component
This pull request supports the `:#${property.foo}` notation and evaluates
it as a Simple expression
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/adessaigne/camel CAMEL-7455
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/169.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 #169
commit 8c7ef91006477ed1a9256b8de795a85a25c8d984
Author: Antoine DESSAIGNE antoine.dessai...@gmail.com
Date: 2014-06-04T13:01:58Z
CAMEL-7455 supporting body in sql component
supporting body in sql component
Key: CAMEL-7455
URL: https://issues.apache.org/jira/browse/CAMEL-7455
Project: Camel
Issue Type: New Feature
Components: camel-sql
Affects Versions: 2.13.0
Reporter: Poyan Gerami
Priority: Minor
Adding support for sending the body as one sql parameter:
Answer from Claus in mailing list:
Yeah for a single parameter, or just to refer to the body as is, or to
allow using simple expressions, we could maybe look at adding support
for that to the sql component,
so eg :#body just refers to the body itself
Or allow doing :#${body} and have a simple expression available, that
gives you a bit more power.
Though support for :#body is likely the easiest at first.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (CAMEL-7434) Provide a way to force the completion of a aggregate exchange from an external event
[ https://issues.apache.org/jira/browse/CAMEL-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben O'Day reassigned CAMEL-7434: Assignee: Ben O'Day Provide a way to force the completion of a aggregate exchange from an external event Key: CAMEL-7434 URL: https://issues.apache.org/jira/browse/CAMEL-7434 Project: Camel Issue Type: New Feature Components: camel-core, eip Affects Versions: 2.13.0 Reporter: Susan Javurek Assignee: Ben O'Day Fix For: Future There is a way to do this by creating a trigger exchange that is handled in a special way by the aggregation strategy and a completion predicate. But this solution is quite intrusive and painful to write. It would actually be much easier if the AggregateProcessor would implement and expose the following methods: public void forceCompletionOfGroup(String key) public Expression getCorrelationExpression() This way, it becomes possible to control externally an aggregator without having to implement some intrusive logic. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CAMEL-7434) Provide a way to force the completion of a aggregate exchange from an external event
[ https://issues.apache.org/jira/browse/CAMEL-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017378#comment-14017378 ] Ben O'Day edited comment on CAMEL-7434 at 6/4/14 3:31 PM: -- [~sjavurek] - if we added forceCompletionOfGroup(key) on the AggregateProcessor class, how would you invoke it externally? I suppose we could add support for a new marker header (AGGREGATION_COMPLETE_FOR_GROUP) and expect a groupKey as the body of the message to force the completion...though this would still require an explicit message be sent (vs. an API call)...is that what you are looking for? was (Author: boday): [~sjavurek] - if we added forceCompletionOfGroup(key) on the AggregateProcessor class, how would you invoke it externally? Provide a way to force the completion of a aggregate exchange from an external event Key: CAMEL-7434 URL: https://issues.apache.org/jira/browse/CAMEL-7434 Project: Camel Issue Type: New Feature Components: camel-core, eip Affects Versions: 2.13.0 Reporter: Susan Javurek Assignee: Ben O'Day Fix For: Future There is a way to do this by creating a trigger exchange that is handled in a special way by the aggregation strategy and a completion predicate. But this solution is quite intrusive and painful to write. It would actually be much easier if the AggregateProcessor would implement and expose the following methods: public void forceCompletionOfGroup(String key) public Expression getCorrelationExpression() This way, it becomes possible to control externally an aggregator without having to implement some intrusive logic. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-6568) camel-linkedin component
[ https://issues.apache.org/jira/browse/CAMEL-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017789#comment-14017789 ] Jonathan Anstey commented on CAMEL-6568: [~sachin.handiekar] did you still have an interest in creating this component? LinkedIn is very popular so it would be nice to have this one in Camel. Cheers, Jon camel-linkedin component Key: CAMEL-6568 URL: https://issues.apache.org/jira/browse/CAMEL-6568 Project: Camel Issue Type: New Feature Reporter: Claus Ibsen Fix For: Future People have been asking for a camel-linkedin component. It would be nice to have some component that can lookup a linkedin profile and get some details of that profile. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7476) cxfrs throwExceptionOnFailure option not working
[ https://issues.apache.org/jira/browse/CAMEL-7476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017818#comment-14017818 ] Sergey Beryozkin commented on CAMEL-7476: - Regarding 2), IMHO we should keep the existing default (true) as is to prevent the existing code out there from breaking, possibly default to 'false' later on... cxfrs throwExceptionOnFailure option not working Key: CAMEL-7476 URL: https://issues.apache.org/jira/browse/CAMEL-7476 Project: Camel Issue Type: Bug Components: camel-cxf Affects Versions: 2.13.0, 2.13.1 Reporter: TechBird Assignee: Willem Jiang Priority: Minor (1) The cxfrs option throwExceptionOnFailure=true does not suppress exceptions from being thrown when an invoked REST service returns a http status 207. i.e. the following does not work: ... .to(cxfrs:bean:rsClient?throwExceptionOnFailure=false) (2) The cxfrs throwExceptionOnFailure option should default to false; to make it easier to process status codes in the route. When invoking REST services, the logic is currently complicated by the fact that common status' need to be processed in exception handlers. i,e (404 not found, 412 precondition failed). It would be more useful to filter on statuses with a main route. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Issue Comment Deleted] (CAMEL-7428) Simple Language - Operators are not evaluated for setting body or headers
[
https://issues.apache.org/jira/browse/CAMEL-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Keller updated CAMEL-7428:
Comment: was deleted
(was: I was not able to install 2.13.1. I downloaded
http://repository.apache.org/content/repositories/orgapachecamel-1008/org/apache/camel/apache-camel/2.13.1/apache-camel-2.13.1-src.zip,
executed {{mvn install}} and got following error:
{noformat}
Running org.apache.camel.view.XmlGraphTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.092 sec - in
org.apache.camel.view.XmlGraphTest
Results :
Failed tests:
FileProducerRenameUsingCopyTestTestSupport.runBare:58-testMove:41-ContextTestSupport.assertMockEndpointsSatisfied:343
mock://result Content of file: target/file/done/hello.txt. Expected: Hello
Camel but was:
Tests run: 4902, Failures: 1, Errors: 0, Skipped: 3
{noformat}
I use MacOS with java version 1.7.0_40.
I tried to subscribe to dev-subscr...@camel.apache.org but without success
(yet), so I post the error here.)
Simple Language - Operators are not evaluated for setting body or headers
-
Key: CAMEL-7428
URL: https://issues.apache.org/jira/browse/CAMEL-7428
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.12.3, 2.13.0
Reporter: Peter Keller
Assignee: Claus Ibsen
Fix For: 2.12.4, 2.13.1, 2.14.0
Operators are not evaluated if using {{simple}} for setting bodies or headers:
{code}
from(direct:simple)
.setHeader(myHeader).simple(true == true, Boolean.class)
.log(header = [${header.myHeader}])
.setBody(simple(true == true, Boolean.class))
.log(body = [${body}]);
{code}
Output is as follows:
{code}
INFO header = [false]
INFO body = [false]
{code}
The outcome should be {{true}} in both cases.
Also, see
http://stackoverflow.com/questions/23523409/camel-how-to-set-boolean-header-parameter-using-simple-comparison/23560989#23560989
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CAMEL-7478) Simple Language - Length of array properties is not correctly evaluated
Peter Keller created CAMEL-7478:
---
Summary: Simple Language - Length of array properties is not
correctly evaluated
Key: CAMEL-7478
URL: https://issues.apache.org/jira/browse/CAMEL-7478
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.13.1
Reporter: Peter Keller
If the exchange body is an array, then {{body.length}} returns correctly the
length of the array. However, if the array is a property of an object, then not
the correct value is returned:
{code:title=MyClass.java}
public class MyClass {
public Object[] getMyArray() {
return new Object[]{Hallo, World, !};
}
}
{code}
Accessing the property {{myArray}} with Simple:
{code}
setHeader headerName=mySimpleHeader
simplebody.myArray.length/simple
/setHeader
log message=mySimpleHeader = ${header.mySimpleHeader} /
{code}
Java:
{code}
final ProducerTemplate template = main.getCamelTemplate();
template.sendBody(direct:start, new MyClass());
{code}
Log:
{noformat}
[main] route1 INFO mySimpleHeader = 1
{noformat}
The return value should be {{3}} instead of {{1}}.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CAMEL-6568) camel-linkedin component
[ https://issues.apache.org/jira/browse/CAMEL-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017934#comment-14017934 ] Sachin Handiekar commented on CAMEL-6568: - I've started working on it. Also there is a github repo I've created for the camel-linkedin (https://github.com/sachin-handiekar/camel-linkedin) It's not fully ready yet, but I'm planning to get it finished with some basic features by next week. [~janstey] camel-linkedin component Key: CAMEL-6568 URL: https://issues.apache.org/jira/browse/CAMEL-6568 Project: Camel Issue Type: New Feature Reporter: Claus Ibsen Fix For: Future People have been asking for a camel-linkedin component. It would be nice to have some component that can lookup a linkedin profile and get some details of that profile. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-6568) camel-linkedin component
[ https://issues.apache.org/jira/browse/CAMEL-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017941#comment-14017941 ] Jonathan Anstey commented on CAMEL-6568: Cool stuff. Looking forward to trying it out :-) camel-linkedin component Key: CAMEL-6568 URL: https://issues.apache.org/jira/browse/CAMEL-6568 Project: Camel Issue Type: New Feature Reporter: Claus Ibsen Fix For: Future People have been asking for a camel-linkedin component. It would be nice to have some component that can lookup a linkedin profile and get some details of that profile. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7479) Test fails in non-English environments
Peter Keller created CAMEL-7479:
---
Summary: Test fails in non-English environments
Key: CAMEL-7479
URL: https://issues.apache.org/jira/browse/CAMEL-7479
Project: Camel
Issue Type: Bug
Components: camel-jaxb, camel-test
Environment: MacOS, Java 1.7.0_40, German language
Reporter: Peter Keller
Some Java exception messages are language specific and JUnit tests evaluating
theses messages fail in a non-English environment.
Such assertions are done in {{JaxbDataFormatSchemaValidationSpringTest}} and
{{JaxbDataFormatSchemaValidationTest}}:
* The assertion Invalid content was found fails for the German message
Ungültiger Content wurde beginnend mit Element age gefunden
({{#testMarshallWithValidationException}})
* The assertion The content of element 'person' is not complete fails for the
German message Content des Elements person ist nicht vollständig
(#testUnmarshallWithValidationException()}}.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CAMEL-7479) Test fails in non-English environments
[
https://issues.apache.org/jira/browse/CAMEL-7479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Keller updated CAMEL-7479:
Description:
Some Java exception messages are language specific and JUnit tests evaluating
theses messages fail in a non-English environment.
Such assertions are done in {{JaxbDataFormatSchemaValidationSpringTest}} and
{{JaxbDataFormatSchemaValidationTest}}:
* The assertion Invalid content was found fails for the German message
Ungültiger Content wurde beginnend mit Element age gefunden
({{#testMarshallWithValidationException}})
* The assertion The content of element 'person' is not complete fails for the
German message Content des Elements person ist nicht vollständig
({{#testUnmarshallWithValidationException()}}.
was:
Some Java exception messages are language specific and JUnit tests evaluating
theses messages fail in a non-English environment.
Such assertions are done in {{JaxbDataFormatSchemaValidationSpringTest}} and
{{JaxbDataFormatSchemaValidationTest}}:
* The assertion Invalid content was found fails for the German message
Ungültiger Content wurde beginnend mit Element age gefunden
({{#testMarshallWithValidationException}})
* The assertion The content of element 'person' is not complete fails for the
German message Content des Elements person ist nicht vollständig
(#testUnmarshallWithValidationException()}}.
Test fails in non-English environments
--
Key: CAMEL-7479
URL: https://issues.apache.org/jira/browse/CAMEL-7479
Project: Camel
Issue Type: Bug
Components: camel-jaxb, camel-test
Environment: MacOS, Java 1.7.0_40, German language
Reporter: Peter Keller
Some Java exception messages are language specific and JUnit tests evaluating
theses messages fail in a non-English environment.
Such assertions are done in {{JaxbDataFormatSchemaValidationSpringTest}} and
{{JaxbDataFormatSchemaValidationTest}}:
* The assertion Invalid content was found fails for the German message
Ungültiger Content wurde beginnend mit Element age gefunden
({{#testMarshallWithValidationException}})
* The assertion The content of element 'person' is not complete fails for
the German message Content des Elements person ist nicht vollständig
({{#testUnmarshallWithValidationException()}}.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CAMEL-7479) Test fails in non-English environments
[
https://issues.apache.org/jira/browse/CAMEL-7479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregor Zurowski updated CAMEL-7479:
---
Assignee: Gregor Zurowski
Test fails in non-English environments
--
Key: CAMEL-7479
URL: https://issues.apache.org/jira/browse/CAMEL-7479
Project: Camel
Issue Type: Bug
Components: camel-jaxb, camel-test
Environment: MacOS, Java 1.7.0_40, German language
Reporter: Peter Keller
Assignee: Gregor Zurowski
Some Java exception messages are language specific and JUnit tests evaluating
theses messages fail in a non-English environment.
Such assertions are done in {{JaxbDataFormatSchemaValidationSpringTest}} and
{{JaxbDataFormatSchemaValidationTest}}:
* The assertion Invalid content was found fails for the German message
Ungültiger Content wurde beginnend mit Element age gefunden
({{#testMarshallWithValidationException()}})
* The assertion The content of element 'person' is not complete fails for
the German message Content des Elements person ist nicht vollständig
({{#testUnmarshallWithValidationException()}}).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CAMEL-7479) Test fails in non-English environments
[
https://issues.apache.org/jira/browse/CAMEL-7479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018471#comment-14018471
]
ASF GitHub Bot commented on CAMEL-7479:
---
GitHub user gzurowski opened a pull request:
https://github.com/apache/camel/pull/170
CAMEL-7479: Make unit tests run with any JVM system locale
Use SAX validation error code instead of the localized error message in
assert statements, so that the tests run with any JVM system locale.
Signed-off-by: Gregor Zurowski gre...@zurowski.org
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gzurowski/camel CAMEL-7479
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/170.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 #170
commit a16c105141bbd434c248f55f37ed3143c6bd127c
Author: Gregor Zurowski gre...@zurowski.org
Date: 2014-06-05T04:20:45Z
CAMEL-7479: Make unit tests run with any JVM system locale
Use SAX validation error code instead of the localized error message in
assert statements, so that the tests run with any JVM system locale.
Signed-off-by: Gregor Zurowski gre...@zurowski.org
Test fails in non-English environments
--
Key: CAMEL-7479
URL: https://issues.apache.org/jira/browse/CAMEL-7479
Project: Camel
Issue Type: Bug
Components: camel-jaxb, camel-test
Environment: MacOS, Java 1.7.0_40, German language
Reporter: Peter Keller
Assignee: Gregor Zurowski
Some Java exception messages are language specific and JUnit tests evaluating
theses messages fail in a non-English environment.
Such assertions are done in {{JaxbDataFormatSchemaValidationSpringTest}} and
{{JaxbDataFormatSchemaValidationTest}}:
* The assertion Invalid content was found fails for the German message
Ungültiger Content wurde beginnend mit Element age gefunden
({{#testMarshallWithValidationException()}})
* The assertion The content of element 'person' is not complete fails for
the German message Content des Elements person ist nicht vollständig
({{#testUnmarshallWithValidationException()}}).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CAMEL-7479) Test fails in non-English environments
[
https://issues.apache.org/jira/browse/CAMEL-7479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018473#comment-14018473
]
Gregor Zurowski commented on CAMEL-7479:
Fix successfully tested by running unit tests with languages en, de, sv, zh and
using the following Maven configuration:
{code:title=pom.xml}
plugin
artifactIdmaven-surefire-plugin/artifactId
configuration
forkModepertest/forkMode
argLine-Duser.language=de/argLine !-- replace language code here --
/configuration
/plugin
{code}
Test fails in non-English environments
--
Key: CAMEL-7479
URL: https://issues.apache.org/jira/browse/CAMEL-7479
Project: Camel
Issue Type: Bug
Components: camel-jaxb, camel-test
Environment: MacOS, Java 1.7.0_40, German language
Reporter: Peter Keller
Assignee: Gregor Zurowski
Some Java exception messages are language specific and JUnit tests evaluating
theses messages fail in a non-English environment.
Such assertions are done in {{JaxbDataFormatSchemaValidationSpringTest}} and
{{JaxbDataFormatSchemaValidationTest}}:
* The assertion Invalid content was found fails for the German message
Ungültiger Content wurde beginnend mit Element age gefunden
({{#testMarshallWithValidationException()}})
* The assertion The content of element 'person' is not complete fails for
the German message Content des Elements person ist nicht vollständig
({{#testUnmarshallWithValidationException()}}).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (CAMEL-7479) Test fails in non-English environments
[
https://issues.apache.org/jira/browse/CAMEL-7479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018473#comment-14018473
]
Gregor Zurowski edited comment on CAMEL-7479 at 6/5/14 4:53 AM:
Fix successfully tested by running unit tests with languages en, de, sv, zh and
using the following Maven configuration:
{code:title=camel-jaxb/pom.xml}
plugin
artifactIdmaven-surefire-plugin/artifactId
configuration
forkModepertest/forkMode
argLine-Duser.language=de/argLine !-- replace language code here --
/configuration
/plugin
{code}
was (Author: gzurowski):
Fix successfully tested by running unit tests with languages en, de, sv, zh and
using the following Maven configuration:
{code:title=pom.xml}
plugin
artifactIdmaven-surefire-plugin/artifactId
configuration
forkModepertest/forkMode
argLine-Duser.language=de/argLine !-- replace language code here --
/configuration
/plugin
{code}
Test fails in non-English environments
--
Key: CAMEL-7479
URL: https://issues.apache.org/jira/browse/CAMEL-7479
Project: Camel
Issue Type: Bug
Components: camel-jaxb, camel-test
Environment: MacOS, Java 1.7.0_40, German language
Reporter: Peter Keller
Assignee: Gregor Zurowski
Some Java exception messages are language specific and JUnit tests evaluating
theses messages fail in a non-English environment.
Such assertions are done in {{JaxbDataFormatSchemaValidationSpringTest}} and
{{JaxbDataFormatSchemaValidationTest}}:
* The assertion Invalid content was found fails for the German message
Ungültiger Content wurde beginnend mit Element age gefunden
({{#testMarshallWithValidationException()}})
* The assertion The content of element 'person' is not complete fails for
the German message Content des Elements person ist nicht vollständig
({{#testUnmarshallWithValidationException()}}).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
