[jira] [Updated] (CAMEL-7924) java.lang.ClassNotFoundException: org.codehaus.groovy.runtime.callsite.CallSiteArray
[
https://issues.apache.org/jira/browse/CAMEL-7924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Müller updated CAMEL-7924:
Fix Version/s: (was: 2.12.5)
java.lang.ClassNotFoundException:
org.codehaus.groovy.runtime.callsite.CallSiteArray
Key: CAMEL-7924
URL: https://issues.apache.org/jira/browse/CAMEL-7924
Project: Camel
Issue Type: Bug
Components: camel-groovy
Affects Versions: 2.12.3, 2.13.2, 2.14.0
Reporter: Charles Moulliard
Assignee: Charles Moulliard
Fix For: 2.13.3, 2.14.1, 2.15.0
When a camelRoute using the camel-groovy component is deployed on Karaf, we
get this class not found exception. Apparently, the class is not imported and
the package is not declared in the MANIFEST file of the component.
{code}
Caused by: java.lang.NoClassDefFoundError:
org/codehaus/groovy/runtime/callsite/CallSiteArray
at
script1413531356181697720774.$createCallSiteArray(script1413531356181697720774.groovy)
at
script1413531356181697720774.$getCallSiteArray(script1413531356181697720774.groovy)
at
script1413531356181697720774.__$swapInit(script1413531356181697720774.groovy)
at
script1413531356181697720774.clinit(script1413531356181697720774.groovy)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)[:1.7.0_51]
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
at
java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
at
org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
at
org.apache.camel.language.groovy.GroovyExpression.evaluate(GroovyExpression.java:50)
at
org.apache.camel.builder.ProcessorBuilder$4.process(ProcessorBuilder.java:103)
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
... 89 more
Caused by: java.lang.ClassNotFoundException:
org.codehaus.groovy.runtime.callsite.CallSiteArray
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)[:1.7.0_51]
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)[:1.7.0_51]
at java.security.AccessController.doPrivileged(Native Method)[:1.7.0_51]
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)[:1.7.0_51]
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)[:1.7.0_51]
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:648)
at
groovy.lang.GroovyClassLoader$InnerLoader.loadClass(GroovyClassLoader.java:401)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:758)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:746)
... 102 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-7924) java.lang.ClassNotFoundException: org.codehaus.groovy.runtime.callsite.CallSiteArray
[
https://issues.apache.org/jira/browse/CAMEL-7924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Moulliard resolved CAMEL-7924.
--
Resolution: Fixed
java.lang.ClassNotFoundException:
org.codehaus.groovy.runtime.callsite.CallSiteArray
Key: CAMEL-7924
URL: https://issues.apache.org/jira/browse/CAMEL-7924
Project: Camel
Issue Type: Bug
Components: camel-groovy
Affects Versions: 2.12.3, 2.13.2, 2.14.0
Reporter: Charles Moulliard
Assignee: Charles Moulliard
Fix For: 2.13.3, 2.14.1, 2.15.0
When a camelRoute using the camel-groovy component is deployed on Karaf, we
get this class not found exception. Apparently, the class is not imported and
the package is not declared in the MANIFEST file of the component.
{code}
Caused by: java.lang.NoClassDefFoundError:
org/codehaus/groovy/runtime/callsite/CallSiteArray
at
script1413531356181697720774.$createCallSiteArray(script1413531356181697720774.groovy)
at
script1413531356181697720774.$getCallSiteArray(script1413531356181697720774.groovy)
at
script1413531356181697720774.__$swapInit(script1413531356181697720774.groovy)
at
script1413531356181697720774.clinit(script1413531356181697720774.groovy)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)[:1.7.0_51]
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)[:1.7.0_51]
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.7.0_51]
at
java.lang.reflect.Constructor.newInstance(Constructor.java:526)[:1.7.0_51]
at java.lang.Class.newInstance(Class.java:374)[:1.7.0_51]
at
org.apache.camel.language.groovy.GroovyExpression.instantiateScript(GroovyExpression.java:71)
at
org.apache.camel.language.groovy.GroovyExpression.evaluate(GroovyExpression.java:50)
at
org.apache.camel.builder.ProcessorBuilder$4.process(ProcessorBuilder.java:103)
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
... 89 more
Caused by: java.lang.ClassNotFoundException:
org.codehaus.groovy.runtime.callsite.CallSiteArray
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)[:1.7.0_51]
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)[:1.7.0_51]
at java.security.AccessController.doPrivileged(Native Method)[:1.7.0_51]
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)[:1.7.0_51]
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)[:1.7.0_51]
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:648)
at
groovy.lang.GroovyClassLoader$InnerLoader.loadClass(GroovyClassLoader.java:401)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:758)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:746)
... 102 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-7872) Post processing action for input mail box
[ https://issues.apache.org/jira/browse/CAMEL-7872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7872. - Resolution: Fixed Fix Version/s: 2.15.0 Applied this new feature to camel master branch with thanks to Christian. Post processing action for input mail box - Key: CAMEL-7872 URL: https://issues.apache.org/jira/browse/CAMEL-7872 Project: Camel Issue Type: New Feature Components: camel-mail Affects Versions: 2.14.0 Reporter: Christian Amann Assignee: Willem Jiang Priority: Minor Labels: patch Fix For: 2.15.0 Please see the pull request at https://github.com/apache/camel/pull/278 Patch plus unit test are available -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7931) JCR need to support multi-valued property
Willem Jiang created CAMEL-7931: --- Summary: JCR need to support multi-valued property Key: CAMEL-7931 URL: https://issues.apache.org/jira/browse/CAMEL-7931 Project: Camel Issue Type: Bug Components: camel-jcr Affects Versions: 2.14.0, 2.13.2 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.13.3, 2.14.1 Regarding to the issue at Camel User Forum as [[camel-jcr] The trouble about the JCR multi-valued property when using JCR_GET_BY_ID](http://camel.465427.n5.nabble.com/camel-jcr-The-trouble-about-the-JCR-multi-valued-property-when-using-JCR-GET-BY-ID-td5757029.html). Here is the fix from https://github.com/apache/camel/pull/287.patch from charlee. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7872) Post processing action for input mail box
[ https://issues.apache.org/jira/browse/CAMEL-7872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176663#comment-14176663 ] Christian Amann commented on CAMEL-7872: Thanks :-) Post processing action for input mail box - Key: CAMEL-7872 URL: https://issues.apache.org/jira/browse/CAMEL-7872 Project: Camel Issue Type: New Feature Components: camel-mail Affects Versions: 2.14.0 Reporter: Christian Amann Assignee: Willem Jiang Priority: Minor Labels: patch Fix For: 2.15.0 Please see the pull request at https://github.com/apache/camel/pull/278 Patch plus unit test are available -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7873) Add capability to sort incoming mail messages
[ https://issues.apache.org/jira/browse/CAMEL-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176664#comment-14176664 ] Christian Amann commented on CAMEL-7873: Thanks :-) Add capability to sort incoming mail messages - Key: CAMEL-7873 URL: https://issues.apache.org/jira/browse/CAMEL-7873 Project: Camel Issue Type: New Feature Components: camel-mail Affects Versions: 2.14.0 Reporter: Christian Amann Assignee: Willem Jiang Priority: Minor Labels: patch Please see the pull request at https://github.com/apache/camel/pull/277 Patch plus unit test are available -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7872) Post processing action for input mail box
[ https://issues.apache.org/jira/browse/CAMEL-7872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1417#comment-1417 ] ASF GitHub Bot commented on CAMEL-7872: --- Github user camann9 closed the pull request at: https://github.com/apache/camel/pull/278 Post processing action for input mail box - Key: CAMEL-7872 URL: https://issues.apache.org/jira/browse/CAMEL-7872 Project: Camel Issue Type: New Feature Components: camel-mail Affects Versions: 2.14.0 Reporter: Christian Amann Assignee: Willem Jiang Priority: Minor Labels: patch Fix For: 2.15.0 Please see the pull request at https://github.com/apache/camel/pull/278 Patch plus unit test are available -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7873) Add capability to sort incoming mail messages
[ https://issues.apache.org/jira/browse/CAMEL-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176665#comment-14176665 ] ASF GitHub Bot commented on CAMEL-7873: --- Github user camann9 closed the pull request at: https://github.com/apache/camel/pull/277 Add capability to sort incoming mail messages - Key: CAMEL-7873 URL: https://issues.apache.org/jira/browse/CAMEL-7873 Project: Camel Issue Type: New Feature Components: camel-mail Affects Versions: 2.14.0 Reporter: Christian Amann Assignee: Willem Jiang Priority: Minor Labels: patch Please see the pull request at https://github.com/apache/camel/pull/277 Patch plus unit test are available -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-7873) Add capability to sort incoming mail messages
[ https://issues.apache.org/jira/browse/CAMEL-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7873. - Resolution: Fixed Fix Version/s: 2.15.0 Add capability to sort incoming mail messages - Key: CAMEL-7873 URL: https://issues.apache.org/jira/browse/CAMEL-7873 Project: Camel Issue Type: New Feature Components: camel-mail Affects Versions: 2.14.0 Reporter: Christian Amann Assignee: Willem Jiang Priority: Minor Labels: patch Fix For: 2.15.0 Please see the pull request at https://github.com/apache/camel/pull/277 Patch plus unit test are available -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7932) Adding initial properties to PropertiesComponent
Willem Jiang created CAMEL-7932: --- Summary: Adding initial properties to PropertiesComponent Key: CAMEL-7932 URL: https://issues.apache.org/jira/browse/CAMEL-7932 Project: Camel Issue Type: Improvement Components: el-core, camel-core Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.15.0 Added setInitialProperties(Properties initialProperties) and getInitialProperties() public methods to PropertiesComponent. These methods allow us to add properties to PropertiesComponent when we can't/won't use external properties (locations). In SCR bundle, for example, properties are passed to our program as a Map and the only way to get them into PropertiesComponent was setOverrideProperties method. Override properties are however not used if they are the only properties, so we were forced to use a dummy properties file in the bundle. In addition to the new methods, this pull request changes the override properties handling so that they are always used if they exist (which is the logical thing to do). Here is pull request for it. https://github.com/apache/camel/pull/295.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7931) JCR need to support multi-valued property
[ https://issues.apache.org/jira/browse/CAMEL-7931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-7931: Fix Version/s: (was: 2.13.3) JCR need to support multi-valued property - Key: CAMEL-7931 URL: https://issues.apache.org/jira/browse/CAMEL-7931 Project: Camel Issue Type: Bug Components: camel-jcr Affects Versions: 2.13.2, 2.14.0 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.14.1, 2.15.0 Regarding to the issue at Camel User Forum as [[camel-jcr] The trouble about the JCR multi-valued property when using JCR_GET_BY_ID](http://camel.465427.n5.nabble.com/camel-jcr-The-trouble-about-the-JCR-multi-valued-property-when-using-JCR-GET-BY-ID-td5757029.html). Here is the fix from https://github.com/apache/camel/pull/287.patch from charlee. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7931) JCR need to support multi-valued property
[ https://issues.apache.org/jira/browse/CAMEL-7931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-7931: Fix Version/s: 2.15.0 JCR need to support multi-valued property - Key: CAMEL-7931 URL: https://issues.apache.org/jira/browse/CAMEL-7931 Project: Camel Issue Type: Bug Components: camel-jcr Affects Versions: 2.13.2, 2.14.0 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.14.1, 2.15.0 Regarding to the issue at Camel User Forum as [[camel-jcr] The trouble about the JCR multi-valued property when using JCR_GET_BY_ID](http://camel.465427.n5.nabble.com/camel-jcr-The-trouble-about-the-JCR-multi-valued-property-when-using-JCR-GET-BY-ID-td5757029.html). Here is the fix from https://github.com/apache/camel/pull/287.patch from charlee. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-7931) JCR need to support multi-valued property
[ https://issues.apache.org/jira/browse/CAMEL-7931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7931. - Resolution: Fixed Merged the patch into camel master, camel-2.14.x branches with thanks to Charlee. JCR need to support multi-valued property - Key: CAMEL-7931 URL: https://issues.apache.org/jira/browse/CAMEL-7931 Project: Camel Issue Type: Bug Components: camel-jcr Affects Versions: 2.13.2, 2.14.0 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.14.1, 2.15.0 Regarding to the issue at Camel User Forum as [[camel-jcr] The trouble about the JCR multi-valued property when using JCR_GET_BY_ID](http://camel.465427.n5.nabble.com/camel-jcr-The-trouble-about-the-JCR-multi-valued-property-when-using-JCR-GET-BY-ID-td5757029.html). Here is the fix from https://github.com/apache/camel/pull/287.patch from charlee. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-7932) Adding initial properties to PropertiesComponent
[ https://issues.apache.org/jira/browse/CAMEL-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7932. - Resolution: Fixed Adding initial properties to PropertiesComponent - Key: CAMEL-7932 URL: https://issues.apache.org/jira/browse/CAMEL-7932 Project: Camel Issue Type: Improvement Components: camel-core, el-core Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.13.3, 2.14.1, 2.15.0 Added setInitialProperties(Properties initialProperties) and getInitialProperties() public methods to PropertiesComponent. These methods allow us to add properties to PropertiesComponent when we can't/won't use external properties (locations). In SCR bundle, for example, properties are passed to our program as a Map and the only way to get them into PropertiesComponent was setOverrideProperties method. Override properties are however not used if they are the only properties, so we were forced to use a dummy properties file in the bundle. In addition to the new methods, this pull request changes the override properties handling so that they are always used if they exist (which is the logical thing to do). Here is pull request for it. https://github.com/apache/camel/pull/295.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7932) Adding initial properties to PropertiesComponent
[ https://issues.apache.org/jira/browse/CAMEL-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-7932: Fix Version/s: 2.14.1 2.13.3 Adding initial properties to PropertiesComponent - Key: CAMEL-7932 URL: https://issues.apache.org/jira/browse/CAMEL-7932 Project: Camel Issue Type: Improvement Components: camel-core, el-core Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.13.3, 2.14.1, 2.15.0 Added setInitialProperties(Properties initialProperties) and getInitialProperties() public methods to PropertiesComponent. These methods allow us to add properties to PropertiesComponent when we can't/won't use external properties (locations). In SCR bundle, for example, properties are passed to our program as a Map and the only way to get them into PropertiesComponent was setOverrideProperties method. Override properties are however not used if they are the only properties, so we were forced to use a dummy properties file in the bundle. In addition to the new methods, this pull request changes the override properties handling so that they are always used if they exist (which is the logical thing to do). Here is pull request for it. https://github.com/apache/camel/pull/295.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7932) Adding initial properties to PropertiesComponent
[ https://issues.apache.org/jira/browse/CAMEL-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176714#comment-14176714 ] Willem Jiang commented on CAMEL-7932: - Merged the patch into camel master, camel-2.14.x and camel-2.13.x branches. Adding initial properties to PropertiesComponent - Key: CAMEL-7932 URL: https://issues.apache.org/jira/browse/CAMEL-7932 Project: Camel Issue Type: Improvement Components: camel-core, el-core Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.13.3, 2.14.1, 2.15.0 Added setInitialProperties(Properties initialProperties) and getInitialProperties() public methods to PropertiesComponent. These methods allow us to add properties to PropertiesComponent when we can't/won't use external properties (locations). In SCR bundle, for example, properties are passed to our program as a Map and the only way to get them into PropertiesComponent was setOverrideProperties method. Override properties are however not used if they are the only properties, so we were forced to use a dummy properties file in the bundle. In addition to the new methods, this pull request changes the override properties handling so that they are always used if they exist (which is the logical thing to do). Here is pull request for it. https://github.com/apache/camel/pull/295.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-4494) Allow replyTo message header to be different from actual reply queue
[ https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176895#comment-14176895 ] Susan Javurek commented on CAMEL-4494: -- Hi Jens, We'd like to pick up your fix. Would you reattach the files so we can legally incorporate it into the product? Thank you, Susan Allow replyTo message header to be different from actual reply queue Key: CAMEL-4494 URL: https://issues.apache.org/jira/browse/CAMEL-4494 Project: Camel Issue Type: New Feature Components: camel-jms Affects Versions: 2.8.1 Reporter: Jens Granseuer Attachments: camel-jms-replyto.diff, camel-jms-replyto2.diff We have an application that acts as a JMS client in the following setup: * a local queue manager (L) with queues for request (L.REQUEST) and reply (L.REPLY) messages * a remote queue manager (R) with queues for request (R.REQUEST) and reply (R.REPLY) messages The remote queue manager is unknown to the client application, and messages sent to L.REQUEST are automatically forwarded to R.REQUEST. Similarly, there is a server application listening on R.REQUEST, posting responses in R.REPLY. The local queue manager is unknown to the server application. Messages sent to R.REPLY are automatically forwarded to L.REPLY. The client needs to put message in L.REQUEST and receive the reply in L.REPLY. However, in the message header it must set R.REPLY as the reply queue because L.REPLY is not known to the server application. The Camel JMS component currently doesn't seem to support this scenario. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-4494) Allow replyTo message header to be different from actual reply queue
[ https://issues.apache.org/jira/browse/CAMEL-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176901#comment-14176901 ] Jens Granseuer commented on CAMEL-4494: --- I'd love to do so but I don't see where I can set that infamous X even when making a new attachment. Any pointers? Allow replyTo message header to be different from actual reply queue Key: CAMEL-4494 URL: https://issues.apache.org/jira/browse/CAMEL-4494 Project: Camel Issue Type: New Feature Components: camel-jms Affects Versions: 2.8.1 Reporter: Jens Granseuer Attachments: camel-jms-replyto.diff, camel-jms-replyto2.diff We have an application that acts as a JMS client in the following setup: * a local queue manager (L) with queues for request (L.REQUEST) and reply (L.REPLY) messages * a remote queue manager (R) with queues for request (R.REQUEST) and reply (R.REPLY) messages The remote queue manager is unknown to the client application, and messages sent to L.REQUEST are automatically forwarded to R.REQUEST. Similarly, there is a server application listening on R.REQUEST, posting responses in R.REPLY. The local queue manager is unknown to the server application. Messages sent to R.REPLY are automatically forwarded to L.REPLY. The client needs to put message in L.REQUEST and receive the reply in L.REPLY. However, in the message header it must set R.REPLY as the reply queue because L.REPLY is not known to the server application. The Camel JMS component currently doesn't seem to support this scenario. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CAMEL-7930) org.apache.camel.itest.ftp.SpringFtpEndpointTest is failing
[
https://issues.apache.org/jira/browse/CAMEL-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Müller reopened CAMEL-7930:
-
Willem (and all others), could you please rerun the test with Java 6 in camel
2.13.x branch (we do not support Java 7 in Camel 2.13.x):
{noformat}
Christians-MBP:camel-itest cmueller$ git status
On branch camel-2.13.x
Your branch is up-to-date with 'origin/camel-2.13.x'.
nothing to commit, working directory clean
{noformat}
My Maven settings:
{noformat}
Christians-MBP:camel-itest cmueller$ mvn -v
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
14:51:28+0100)
Maven home: /Applications/apache-maven-3.0.5
Java version: 1.6.0_65, vendor: Apple Inc.
Java home: /Library/Java/JavaVirtualMachines/1.6.0_65-b14-462.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x, version: 10.10, arch: x86_64, family: mac
{noformat}
Run the command in camel/tests/camel-itests:
{noformat}
Christians-MBP:camel-itest cmueller$ mvn clean test -Dtest=SpringFtpEndpointTest
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Camel :: Integration Tests :: Non OSGi 2.13.3-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ camel-itest ---
[INFO] Deleting /Users/cmueller/workspaceCamel/camel/tests/camel-itest/target
[INFO]
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (versions) @ camel-itest ---
[INFO]
[INFO] --- cxf-codegen-plugin:2.7.12:wsdl2java (generate-test-sources) @
camel-itest ---
[INFO] Running code generation in fork mode...
[INFO] Building jar:
/var/folders/jl/mtm191_155qg810p8m0662trgn/T/cxf-tmp-365454/cxf-codegen1815344060534911509.jar
[INFO]
[INFO] --- maven-remote-resources-plugin:1.4:process (default) @ camel-itest ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
camel-itest ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ camel-itest
---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
camel-itest ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 101 resources
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @
camel-itest ---
[INFO] Compiling 173 source files to
/Users/cmueller/workspaceCamel/camel/tests/camel-itest/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.16:test (default-test) @ camel-itest ---
[WARNING] The parameter forkMode is deprecated since version 2.14. Use
forkCount and reuseForks instead.
[INFO] Surefire report directory:
/Users/cmueller/workspaceCamel/camel/tests/camel-itest/target/surefire-reports
---
T E S T S
---
---
T E S T S
---
Running org.apache.camel.itest.ftp.SpringFtpEndpointTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.498 sec
FAILURE! - in org.apache.camel.itest.ftp.SpringFtpEndpointTest
testFtpEndpointAsSpringBean(org.apache.camel.itest.ftp.SpringFtpEndpointTest)
Time elapsed: 1.308 sec ERROR!
java.lang.IllegalStateException: Failed to load ApplicationContext
at
org.springframework.test.context.CacheAwareContextLoaderDelegate.loadContext(CacheAwareContextLoaderDelegate.java:99)
at
org.springframework.test.context.TestContext.getApplicationContext(TestContext.java:122)
at
org.springframework.test.context.support.DependencyInjectionTestExecutionListener.injectDependencies(DependencyInjectionTestExecutionListener.java:109)
at
org.springframework.test.context.support.DependencyInjectionTestExecutionListener.prepareTestInstance(DependencyInjectionTestExecutionListener.java:75)
at
org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:307)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:211)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:288)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:284)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231)
at
[jira] [Updated] (CAMEL-7930) org.apache.camel.itest.ftp.SpringFtpEndpointTest is failing
[
https://issues.apache.org/jira/browse/CAMEL-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Müller updated CAMEL-7930:
Environment: Java 6
org.apache.camel.itest.ftp.SpringFtpEndpointTest is failing
---
Key: CAMEL-7930
URL: https://issues.apache.org/jira/browse/CAMEL-7930
Project: Camel
Issue Type: Improvement
Components: tests
Affects Versions: 2.12.3, 2.12.4, 2.12.5, 2.13.2, 2.14.0
Environment: Java 6
Reporter: Christian Müller
Assignee: Willem Jiang
it's failing with the following stack trace:
{noformat}
java.lang.IllegalStateException: Failed to load ApplicationContext
at
org.springframework.test.context.CacheAwareContextLoaderDelegate.loadContext(CacheAwareContextLoaderDelegate.java:99)
at
org.springframework.test.context.TestContext.getApplicationContext(TestContext.java:122)
at
org.springframework.test.context.support.DependencyInjectionTestExecutionListener.injectDependencies(DependencyInjectionTestExecutionListener.java:109)
at
org.springframework.test.context.support.DependencyInjectionTestExecutionListener.prepareTestInstance(DependencyInjectionTestExecutionListener.java:75)
at
org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:321)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:211)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:288)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:284)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:88)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at
org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at
org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
Caused by: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'myFTPEndpoint' defined in class path resource
[org/apache/camel/itest/ftp/SpringFtpEndpointTest-context.xml]: Error setting
property values; nested exception is
org.springframework.beans.NotWritablePropertyException: Invalid property
'configuration' of bean class
[org.apache.camel.component.file.remote.FtpEndpoint]: Bean property
'configuration' is not writable or has an invalid setter method. Does the
parameter type of the setter match the return type of the getter?
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1455)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1160)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
at
[jira] [Created] (CAMEL-7933) Camel-apns should create https connections using SSLContextParameters
Chess Hazlett created CAMEL-7933: Summary: Camel-apns should create https connections using SSLContextParameters Key: CAMEL-7933 URL: https://issues.apache.org/jira/browse/CAMEL-7933 Project: Camel Issue Type: Bug Components: camel-apns Reporter: Chess Hazlett Currently camel-apns uses SSLContext directly to create connections; it should use SSLContextParameters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7934) Camel-olingo2 should create https connections using SSLContextParameters
Chess Hazlett created CAMEL-7934: Summary: Camel-olingo2 should create https connections using SSLContextParameters Key: CAMEL-7934 URL: https://issues.apache.org/jira/browse/CAMEL-7934 Project: Camel Issue Type: Bug Reporter: Chess Hazlett Currently camel-olingo2 uses SSLContext directly to create connections; it should use SSLContextParameters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7930) org.apache.camel.itest.ftp.SpringFtpEndpointTest is failing
[
https://issues.apache.org/jira/browse/CAMEL-7930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177897#comment-14177897
]
Willem Jiang commented on CAMEL-7930:
-
Hi Christian,
I can reproduce the error now by using JDK6, it looks like the there are two
setConfiguration method that confuse Spring about it.
The test can be fixed by removing one of them, actually these methods are doing
the same thing.
{code}
diff --git
a/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpEndpoint.java
b/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpEndpoint.java
index dfb6def..0652022 100644
---
a/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpEndpoint.java
+++
b/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/FtpEndpoint.java
@@ -146,10 +146,6 @@ public class FtpEndpointT extends FTPFile extends
RemoteFileEndpointFTPFile
@Override
public void setConfiguration(GenericFileConfiguration configuration) {
-setConfiguration((FtpConfiguration)configuration);
-}
-
-public void setConfiguration(FtpConfiguration configuration) {
if (configuration == null) {
throw new IllegalArgumentException(FtpConfiguration expected);
}
{code}
Regards,
Willem
org.apache.camel.itest.ftp.SpringFtpEndpointTest is failing
---
Key: CAMEL-7930
URL: https://issues.apache.org/jira/browse/CAMEL-7930
Project: Camel
Issue Type: Improvement
Components: tests
Affects Versions: 2.12.3, 2.12.4, 2.12.5, 2.13.2, 2.14.0
Environment: Java 6
Reporter: Christian Müller
Assignee: Willem Jiang
it's failing with the following stack trace:
{noformat}
java.lang.IllegalStateException: Failed to load ApplicationContext
at
org.springframework.test.context.CacheAwareContextLoaderDelegate.loadContext(CacheAwareContextLoaderDelegate.java:99)
at
org.springframework.test.context.TestContext.getApplicationContext(TestContext.java:122)
at
org.springframework.test.context.support.DependencyInjectionTestExecutionListener.injectDependencies(DependencyInjectionTestExecutionListener.java:109)
at
org.springframework.test.context.support.DependencyInjectionTestExecutionListener.prepareTestInstance(DependencyInjectionTestExecutionListener.java:75)
at
org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:321)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:211)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:288)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:284)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:88)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at
org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at
org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
Caused by: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'myFTPEndpoint' defined in class path resource
