[jira] [Assigned] (CAMEL-7900) hdfs2 - chunkSize not honored
[
https://issues.apache.org/jira/browse/CAMEL-7900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang reassigned CAMEL-7900:
---
Assignee: Willem Jiang
hdfs2 - chunkSize not honored
-
Key: CAMEL-7900
URL: https://issues.apache.org/jira/browse/CAMEL-7900
Project: Camel
Issue Type: Bug
Components: camel-hdfs
Affects Versions: 2.14.0
Reporter: Paolo Antinori
Assignee: Willem Jiang
Priority: Minor
{{camel-hdfs2}} component exposes {{chunkSize}} param, but that value is not
correctly used in
https://github.com/apache/camel/blob/master/components/camel-hdfs2/src/main/java/org/apache/camel/component/hdfs2/HdfsFileType.java#L79
and the constant value:
{code}
public static final int DEFAULT_BUFFERSIZE = 4096;
{code}
always overrides it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-7895) Upgrade XML Security + BouncyCastle dependencies
[ https://issues.apache.org/jira/browse/CAMEL-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-7895: --- Assignee: Willem Jiang Upgrade XML Security + BouncyCastle dependencies Key: CAMEL-7895 URL: https://issues.apache.org/jira/browse/CAMEL-7895 Project: Camel Issue Type: Improvement Components: camel-xmlsecurity Reporter: Colm O hEigeartaigh Assignee: Willem Jiang Priority: Minor Fix For: 2.15.0 Attachments: camel-7895.patch This task is to upgrade BouncyCastle + XML Security to pick up the latest releases. The former can be applied to all branches, the latter should only be applied to 2.15 + 2.14. A patch will be attached with a test fix caused by the XML Security upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7895) Upgrade XML Security + BouncyCastle dependencies
[ https://issues.apache.org/jira/browse/CAMEL-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14166551#comment-14166551 ] Willem Jiang commented on CAMEL-7895: - Hi Colm, I can only find one patch file. I'd be happy to apply the patch if you attach test fix patch :) Regards, Willem Upgrade XML Security + BouncyCastle dependencies Key: CAMEL-7895 URL: https://issues.apache.org/jira/browse/CAMEL-7895 Project: Camel Issue Type: Improvement Components: camel-xmlsecurity Reporter: Colm O hEigeartaigh Assignee: Willem Jiang Priority: Minor Fix For: 2.15.0 Attachments: camel-7895.patch This task is to upgrade BouncyCastle + XML Security to pick up the latest releases. The former can be applied to all branches, the latter should only be applied to 2.15 + 2.14. A patch will be attached with a test fix caused by the XML Security upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7901) org.apache.camel.component.mock.MockEndpoint expectedBodiesReceived fails with but was: null message
[
https://issues.apache.org/jira/browse/CAMEL-7901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14166554#comment-14166554
]
David J. M. Karlsen commented on CAMEL-7901:
Move mep.expectedBodiesReceived(test body) before sendBody and it should work.
org.apache.camel.component.mock.MockEndpoint expectedBodiesReceived fails
with but was: null message
Key: CAMEL-7901
URL: https://issues.apache.org/jira/browse/CAMEL-7901
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.13.0
Environment: scala 2.10.3
camel 2.13.0
akka 2.3.1
OSX 10.8.5
Intellij IDEA 13.0.2
Reporter: Robert Courtney
Labels: patch
A small scala + akka + camel test seems to show that the
MockEndpoint.expectedBodiesReceived(final List? bodies) method is not
working as expected.
the following scala code excerpt:
val mep =
camelContext.getEndpoint(mock:file).asInstanceOf[MockEndpoint]
camel.template.sendBody(mep, test body)
println(all exchanges:)
val exchanges = mep.getReceivedExchanges
println(exchanges)
// mep.expectedMessageCount(1) // WORKS
mep.expectedBodiesReceived(test body) // FAILS
mep.assertIsSatisfied
fails with this output:
2014-10-10 16:41:58,692 DEBUG o.a.c.component.mock.MockEndpoint -
mock://file 0 : Exchange[Message: test body] with body: test body and
headers:{breadcrumbId=ID-nbns-MacBook-Pro-local-59447-1412919718220-0-1}
all exchanges:
[Exchange[Message: test body]]
2014-10-10 16:41:58,693 INFO o.a.c.component.mock.MockEndpoint - Asserting:
Endpoint[mock://file] is satisfied
2014-10-10 16:41:58,694 DEBUG o.a.c.component.mock.MockEndpoint -
mock://file failed and received[1]: Exchange[Message: test body]
mock://file Body of message: 0. Expected: test body but was: null
java.lang.AssertionError: mock://file Body of message: 0. Expected: test
body but was: null
at
org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1333)
at
org.apache.camel.component.mock.MockEndpoint.assertEquals(MockEndpoint.java:1315)
at
org.apache.camel.component.mock.MockEndpoint$5.run(MockEndpoint.java:628)
at
org.apache.camel.component.mock.MockEndpoint.doAssertIsSatisfied(MockEndpoint.java:394)
at
org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:362)
at
org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:350)
It looks like the problem is in MockEndpoint.java (line 613), where the
actualBodyValues variable is initialised to an empty ArrayList on each
invocation of expectedBodiesReceived(...), wiping out any values which were
added to this List at line 1220 in performAssertions()
I've looked through the same code in camel-core 2.13.x and 2.14 and the same
code exists there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-7895) Upgrade XML Security + BouncyCastle dependencies
[ https://issues.apache.org/jira/browse/CAMEL-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14166562#comment-14166562 ] Colm O hEigeartaigh commented on CAMEL-7895: Hi Willem, Sorry, my comment wasn't very clear - the test fix is included in the patch I submitted. It's just a one-line fix for a regression in Santuario, that I've since fixed but not yet released. Colm. Upgrade XML Security + BouncyCastle dependencies Key: CAMEL-7895 URL: https://issues.apache.org/jira/browse/CAMEL-7895 Project: Camel Issue Type: Improvement Components: camel-xmlsecurity Reporter: Colm O hEigeartaigh Assignee: Willem Jiang Priority: Minor Fix For: 2.15.0 Attachments: camel-7895.patch This task is to upgrade BouncyCastle + XML Security to pick up the latest releases. The former can be applied to all branches, the latter should only be applied to 2.15 + 2.14. A patch will be attached with a test fix caused by the XML Security upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7901) org.apache.camel.component.mock.MockEndpoint expectedBodiesReceived fails with but was: null message
[
https://issues.apache.org/jira/browse/CAMEL-7901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14166575#comment-14166575
]
Willem Jiang commented on CAMEL-7901:
-
The MockEndpoint is just like other mock API, you need to setup the expect
states before sending the message.
But if you want to access the exchange which is received by mock endpoint after
sending the message.
org.apache.camel.component.mock.MockEndpoint expectedBodiesReceived fails
with but was: null message
Key: CAMEL-7901
URL: https://issues.apache.org/jira/browse/CAMEL-7901
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.13.0
Environment: scala 2.10.3
camel 2.13.0
akka 2.3.1
OSX 10.8.5
Intellij IDEA 13.0.2
Reporter: Robert Courtney
Labels: patch
A small scala + akka + camel test seems to show that the
MockEndpoint.expectedBodiesReceived(final List? bodies) method is not
working as expected.
the following scala code excerpt:
val mep =
camelContext.getEndpoint(mock:file).asInstanceOf[MockEndpoint]
camel.template.sendBody(mep, test body)
println(all exchanges:)
val exchanges = mep.getReceivedExchanges
println(exchanges)
// mep.expectedMessageCount(1) // WORKS
mep.expectedBodiesReceived(test body) // FAILS
mep.assertIsSatisfied
fails with this output:
2014-10-10 16:41:58,692 DEBUG o.a.c.component.mock.MockEndpoint -
mock://file 0 : Exchange[Message: test body] with body: test body and
headers:{breadcrumbId=ID-nbns-MacBook-Pro-local-59447-1412919718220-0-1}
all exchanges:
[Exchange[Message: test body]]
2014-10-10 16:41:58,693 INFO o.a.c.component.mock.MockEndpoint - Asserting:
Endpoint[mock://file] is satisfied
2014-10-10 16:41:58,694 DEBUG o.a.c.component.mock.MockEndpoint -
mock://file failed and received[1]: Exchange[Message: test body]
mock://file Body of message: 0. Expected: test body but was: null
java.lang.AssertionError: mock://file Body of message: 0. Expected: test
body but was: null
at
org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1333)
at
org.apache.camel.component.mock.MockEndpoint.assertEquals(MockEndpoint.java:1315)
at
org.apache.camel.component.mock.MockEndpoint$5.run(MockEndpoint.java:628)
at
org.apache.camel.component.mock.MockEndpoint.doAssertIsSatisfied(MockEndpoint.java:394)
at
org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:362)
at
org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:350)
It looks like the problem is in MockEndpoint.java (line 613), where the
actualBodyValues variable is initialised to an empty ArrayList on each
invocation of expectedBodiesReceived(...), wiping out any values which were
added to this List at line 1220 in performAssertions()
I've looked through the same code in camel-core 2.13.x and 2.14 and the same
code exists there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-7901) org.apache.camel.component.mock.MockEndpoint expectedBodiesReceived fails with but was: null message
[
https://issues.apache.org/jira/browse/CAMEL-7901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-7901.
-
Resolution: Not a Problem
Assignee: Willem Jiang
It works as expect.
org.apache.camel.component.mock.MockEndpoint expectedBodiesReceived fails
with but was: null message
Key: CAMEL-7901
URL: https://issues.apache.org/jira/browse/CAMEL-7901
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.13.0
Environment: scala 2.10.3
camel 2.13.0
akka 2.3.1
OSX 10.8.5
Intellij IDEA 13.0.2
Reporter: Robert Courtney
Assignee: Willem Jiang
Labels: patch
A small scala + akka + camel test seems to show that the
MockEndpoint.expectedBodiesReceived(final List? bodies) method is not
working as expected.
the following scala code excerpt:
val mep =
camelContext.getEndpoint(mock:file).asInstanceOf[MockEndpoint]
camel.template.sendBody(mep, test body)
println(all exchanges:)
val exchanges = mep.getReceivedExchanges
println(exchanges)
// mep.expectedMessageCount(1) // WORKS
mep.expectedBodiesReceived(test body) // FAILS
mep.assertIsSatisfied
fails with this output:
2014-10-10 16:41:58,692 DEBUG o.a.c.component.mock.MockEndpoint -
mock://file 0 : Exchange[Message: test body] with body: test body and
headers:{breadcrumbId=ID-nbns-MacBook-Pro-local-59447-1412919718220-0-1}
all exchanges:
[Exchange[Message: test body]]
2014-10-10 16:41:58,693 INFO o.a.c.component.mock.MockEndpoint - Asserting:
Endpoint[mock://file] is satisfied
2014-10-10 16:41:58,694 DEBUG o.a.c.component.mock.MockEndpoint -
mock://file failed and received[1]: Exchange[Message: test body]
mock://file Body of message: 0. Expected: test body but was: null
java.lang.AssertionError: mock://file Body of message: 0. Expected: test
body but was: null
at
org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1333)
at
org.apache.camel.component.mock.MockEndpoint.assertEquals(MockEndpoint.java:1315)
at
org.apache.camel.component.mock.MockEndpoint$5.run(MockEndpoint.java:628)
at
org.apache.camel.component.mock.MockEndpoint.doAssertIsSatisfied(MockEndpoint.java:394)
at
org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:362)
at
org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:350)
It looks like the problem is in MockEndpoint.java (line 613), where the
actualBodyValues variable is initialised to an empty ArrayList on each
invocation of expectedBodiesReceived(...), wiping out any values which were
added to this List at line 1220 in performAssertions()
I've looked through the same code in camel-core 2.13.x and 2.14 and the same
code exists there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-7900) hdfs2 - chunkSize not honored
[
https://issues.apache.org/jira/browse/CAMEL-7900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14166584#comment-14166584
]
Willem Jiang commented on CAMEL-7900:
-
I just checked the code camel-hdfs, it has the same issue.
hdfs2 - chunkSize not honored
-
Key: CAMEL-7900
URL: https://issues.apache.org/jira/browse/CAMEL-7900
Project: Camel
Issue Type: Bug
Components: camel-hdfs
Affects Versions: 2.14.0
Reporter: Paolo Antinori
Assignee: Willem Jiang
Priority: Minor
{{camel-hdfs2}} component exposes {{chunkSize}} param, but that value is not
correctly used in
https://github.com/apache/camel/blob/master/components/camel-hdfs2/src/main/java/org/apache/camel/component/hdfs2/HdfsFileType.java#L79
and the constant value:
{code}
public static final int DEFAULT_BUFFERSIZE = 4096;
{code}
always overrides it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-7890) XmlConverter.toSAXSourceFromStream does not set setNamespaceAware
[
https://issues.apache.org/jira/browse/CAMEL-7890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang reassigned CAMEL-7890:
---
Assignee: Willem Jiang
XmlConverter.toSAXSourceFromStream does not set setNamespaceAware
-
Key: CAMEL-7890
URL: https://issues.apache.org/jira/browse/CAMEL-7890
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.14.0
Reporter: Mateusz Nowakowski
Assignee: Willem Jiang
XmlConverter.toSAXSourceFromStream does not set
{code}
sfactory.setNamespaceAware(true);
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-7889) Add Support for CamelRetrieveGeneratedKeys with useHeadersAsParameters
[ https://issues.apache.org/jira/browse/CAMEL-7889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-7889: --- Assignee: Willem Jiang Add Support for CamelRetrieveGeneratedKeys with useHeadersAsParameters -- Key: CAMEL-7889 URL: https://issues.apache.org/jira/browse/CAMEL-7889 Project: Camel Issue Type: New Feature Components: camel-jdbc Affects Versions: 2.13.2 Reporter: Nathan Wray Assignee: Willem Jiang Priority: Minor Attachments: JdbcProducer-patch.txt Adds support for retrieving generated keys when also using prepared statements (useHeadersAsParameters). This combination was not previously supported. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-7891) SetMessageEmmiter addition not work with latest Saxon
[ https://issues.apache.org/jira/browse/CAMEL-7891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-7891: --- Assignee: Willem Jiang SetMessageEmmiter addition not work with latest Saxon - Key: CAMEL-7891 URL: https://issues.apache.org/jira/browse/CAMEL-7891 Project: Camel Issue Type: Improvement Components: camel-xslt Affects Versions: 2.14.0 Reporter: Mateusz Nowakowski Assignee: Willem Jiang Saxon 9.6 introduces a couple of non-backward compatible changes: - template.newTransformer() does not return net.sf.saxon.Controller anymore so setting setMessageEmmiter won't work on the latest Saxon. - DOMResult provided to transform method cannot have null node field (current DomResultHandler won't work) that's backward compatibility change will be fixed : https://saxonica.plan.io/issues/2164 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-7888) HL7Decoder leaks memory
[ https://issues.apache.org/jira/browse/CAMEL-7888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-7888: --- Assignee: Willem Jiang HL7Decoder leaks memory --- Key: CAMEL-7888 URL: https://issues.apache.org/jira/browse/CAMEL-7888 Project: Camel Issue Type: Bug Components: camel-hl7 Affects Versions: 2.12.0, 2.13.0, 2.14.0 Reporter: christian ohr Assignee: Willem Jiang Fix For: 2.14.1, 2.15.0 Attachments: CAMEL-7888.patch Under constant load (i.e. Mina session never idles out), the HL7Decoder leaks memory. In fact, all received messages are appended to Mina's IOBuffer, which leads to OOME after some time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7902) Add tests for camel-github component
Kevin Earls created CAMEL-7902: -- Summary: Add tests for camel-github component Key: CAMEL-7902 URL: https://issues.apache.org/jira/browse/CAMEL-7902 Project: Camel Issue Type: Improvement Reporter: Kevin Earls Priority: Minor The new camel-github component (See CAMEL-) needs integration tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-7902) Add tests for camel-github component
[ https://issues.apache.org/jira/browse/CAMEL-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-7902: --- Assignee: Willem Jiang Add tests for camel-github component Key: CAMEL-7902 URL: https://issues.apache.org/jira/browse/CAMEL-7902 Project: Camel Issue Type: Improvement Reporter: Kevin Earls Assignee: Willem Jiang Priority: Minor Fix For: 2.15.0 The new camel-github component (See CAMEL-) needs integration tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-7902) Add tests for camel-github component
[ https://issues.apache.org/jira/browse/CAMEL-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7902. - Resolution: Fixed Fix Version/s: 2.15.0 Merged the pull request into camel master branch. Add tests for camel-github component Key: CAMEL-7902 URL: https://issues.apache.org/jira/browse/CAMEL-7902 Project: Camel Issue Type: Improvement Reporter: Kevin Earls Assignee: Willem Jiang Priority: Minor Fix For: 2.15.0 The new camel-github component (See CAMEL-) needs integration tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7777) GitHub component
[ https://issues.apache.org/jira/browse/CAMEL-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14166972#comment-14166972 ] Willem Jiang commented on CAMEL-: - Applied the PR 289 into camel master branch. It's time to write document about this new component. GitHub component Key: CAMEL- URL: https://issues.apache.org/jira/browse/CAMEL- Project: Camel Issue Type: New Feature Reporter: Brett E. Meyer Assignee: Willem Jiang Fix For: 2.15.0 For Overlord (http://projectoverlord.io), we need to consume events from GitHub, as well as produce actions. We're moving towards using Camel as a backbone for various capabilities, and as such are writing the endpoint functionality as new Camel components. I'd love to see this incorporated as another mainline Camel component. Work in progress: https://github.com/brmeyer/camel-github Consumer ideas: github://pullRequest (new pull requests) github://pullRequestComment (new pull request comments) github://commit/[branch] (new commits) github://tag (new tags) Producer ideas: github://pullRequestComment/[pr #] Obviously, that's only a small portion of the capabilities. The GitHub API is extensive and opens a large variety of possibilities. It uses the org.eclipse.egit.github.core SDK (https://github.com/eclipse/egit-github/tree/master/org.eclipse.egit.github.core), which is a part of Mylyn and licensed under the EPL. So, there shouldn't be any reason why this would need to be restricted to Camel Extras. Similar to what I did for camel-twitter, the Exchange payloads would be the SDK-provided objects themselves (PullRequest, CommitComment, RepositoryTag, RepositoryCommit, etc.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7902) Add tests for camel-github component
[ https://issues.apache.org/jira/browse/CAMEL-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14166973#comment-14166973 ] Willem Jiang commented on CAMEL-7902: - Hi Kevin, I just noticed there are some updated on the camel-github, do you mind to add another unit test for it? Add tests for camel-github component Key: CAMEL-7902 URL: https://issues.apache.org/jira/browse/CAMEL-7902 Project: Camel Issue Type: Improvement Reporter: Kevin Earls Assignee: Willem Jiang Priority: Minor Fix For: 2.15.0 The new camel-github component (See CAMEL-) needs integration tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7902) Add tests for camel-github component
[ https://issues.apache.org/jira/browse/CAMEL-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14166977#comment-14166977 ] Kevin Earls commented on CAMEL-7902: Sure, I can look at it next week. Add tests for camel-github component Key: CAMEL-7902 URL: https://issues.apache.org/jira/browse/CAMEL-7902 Project: Camel Issue Type: Improvement Reporter: Kevin Earls Assignee: Willem Jiang Priority: Minor Fix For: 2.15.0 The new camel-github component (See CAMEL-) needs integration tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7891) SetMessageEmmiter addition not work with latest Saxon
[
https://issues.apache.org/jira/browse/CAMEL-7891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14167022#comment-14167022
]
Willem Jiang commented on CAMEL-7891:
-
I got below compile error when update saxon to 9.6.0-1.
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile)
on project camel-saxon: Compilation failure: Compilation failure:
[ERROR]
/Users/jiangning/work/camel/git/camel/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java:[607,27]
error: method setParameter in class DynamicQueryContext cannot be applied to
given types;
[ERROR] required: StructuredQName,Sequence
[ERROR] found: String,Object
[ERROR] reason: actual argument String cannot be converted to StructuredQName
by method invocation conversion
[ERROR]
/Users/jiangning/work/camel/git/camel/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java:[610,27]
error: method setParameter in class DynamicQueryContext cannot be applied to
given types;
[ERROR] required: StructuredQName,Sequence
[ERROR] found: String,Exchange
[ERROR] reason: actual argument String cannot be converted to StructuredQName
by method invocation conversion
[ERROR]
/Users/jiangning/work/camel/git/camel/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java:[612,31]
error: method setParameter in class DynamicQueryContext cannot be applied to
given types;
[ERROR] required: StructuredQName,Sequence
[ERROR] found: String,Object
[ERROR] reason: actual argument String cannot be converted to StructuredQName
by method invocation conversion
[ERROR]
/Users/jiangning/work/camel/git/camel/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java:[624,31]
error: method setParameter in class DynamicQueryContext cannot be applied to
given types;
[ERROR] required: StructuredQName,Sequence
[ERROR] found: String,Object
[ERROR] reason: actual argument String cannot be converted to StructuredQName
by method invocation conversion
[ERROR]
/Users/jiangning/work/camel/git/camel/components/camel-saxon/src/main/java/org/apache/camel/component/xquery/XQueryBuilder.java:[641,29]
error: cannot find symbol
{code}
SetMessageEmmiter addition not work with latest Saxon
-
Key: CAMEL-7891
URL: https://issues.apache.org/jira/browse/CAMEL-7891
Project: Camel
Issue Type: Improvement
Components: camel-xslt
Affects Versions: 2.14.0
Reporter: Mateusz Nowakowski
Assignee: Willem Jiang
Saxon 9.6 introduces a couple of non-backward compatible changes:
- template.newTransformer() does not return net.sf.saxon.Controller anymore
so setting setMessageEmmiter won't work on the latest Saxon.
- DOMResult provided to transform method cannot have null node field
(current DomResultHandler won't work) that's backward compatibility change
will be fixed : https://saxonica.plan.io/issues/2164
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
