[jira] [Commented] (CAMEL-6513) IncompatibleClassChangeError with weld-se 2.0.2
[ https://issues.apache.org/jira/browse/CAMEL-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700474#comment-13700474 ] Andreas Dolk commented on CAMEL-6513: - Is there a fix version or a schedule already for this upgrade? We'd like to migrate an application, that uses camel-cdi, to JavaEE7 (glassfish 4 jboss AS8) IncompatibleClassChangeError with weld-se 2.0.2 --- Key: CAMEL-6513 URL: https://issues.apache.org/jira/browse/CAMEL-6513 Project: Camel Issue Type: Task Components: camel-cdi Affects Versions: 2.11.0 Reporter: Andreas Dolk Labels: cdi After upgrading from weld 1.1.10 (CDI 1.0) to weld 2.0.2 (CDI 1.1), an Arquillian based test throws an error: Caused by: java.lang.IncompatibleClassChangeError: Class org.apache.camel.cdi.internal.CamelContextBean does not implement the requested interface javax.enterprise.inject.spi.BeanAttributes at org.jboss.weld.bean.attributes.ExternalBeanAttributesFactory.validateStereotypes(ExternalBeanAttributesFactory.java:76) at org.jboss.weld.bean.attributes.ExternalBeanAttributesFactory.validateBeanAttributes(ExternalBeanAttributesFactory.java:69) at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.processBean(AfterBeanDiscoveryImpl.java:83) at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addBean(AfterBeanDiscoveryImpl.java:77) at org.apache.camel.cdi.internal.CamelExtension.registerManagedCamelContext(CamelExtension.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:93) ... 112 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6513) IncompatibleClassChangeError with weld-se 2.0.2
[ https://issues.apache.org/jira/browse/CAMEL-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700495#comment-13700495 ] Christian Müller commented on CAMEL-6513: - Not yet. If you are able to provide a patch, it will speed up the fix... ;-) We love contributions [1]. [1] http://camel.apache.org/contributing.html IncompatibleClassChangeError with weld-se 2.0.2 --- Key: CAMEL-6513 URL: https://issues.apache.org/jira/browse/CAMEL-6513 Project: Camel Issue Type: Task Components: camel-cdi Affects Versions: 2.11.0 Reporter: Andreas Dolk Labels: cdi After upgrading from weld 1.1.10 (CDI 1.0) to weld 2.0.2 (CDI 1.1), an Arquillian based test throws an error: Caused by: java.lang.IncompatibleClassChangeError: Class org.apache.camel.cdi.internal.CamelContextBean does not implement the requested interface javax.enterprise.inject.spi.BeanAttributes at org.jboss.weld.bean.attributes.ExternalBeanAttributesFactory.validateStereotypes(ExternalBeanAttributesFactory.java:76) at org.jboss.weld.bean.attributes.ExternalBeanAttributesFactory.validateBeanAttributes(ExternalBeanAttributesFactory.java:69) at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.processBean(AfterBeanDiscoveryImpl.java:83) at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addBean(AfterBeanDiscoveryImpl.java:77) at org.apache.camel.cdi.internal.CamelExtension.registerManagedCamelContext(CamelExtension.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:93) ... 112 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6511) auto-enable and detect Dozer mappings
[ https://issues.apache.org/jira/browse/CAMEL-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated CAMEL-6511: -- Description: I wonder if we can avoid having to explicitly configure in Spring the DozerTypeConverterLoader class along with the explicit org.dozer.DozerBeanMapper; but instead get camel-core to auto-detect (with META-INF/services or similar OSGi tricks) the presence of the camel-dozer library and then just automatically create it. e.g. using a META-INF/services//TypeConverterLoader file to force the lazy creation of the DozerTypeConverterLoader object. Then also automatically scan for all META-INF/services/dozerMapping.xml files and register them all. For more info see: http://camel.apache.org/dozer-type-conversion.html Then it would feel like Dozer mapping files are kinda like Camel type converters; that they are just automatically discovered and configured on the fly - if they are defined in the convention-over-configuration way? e.g. given that camel-dozer is on the classpath, all that is required is you add a META-INF/services/dozer/mapping.xml file to the classpath and hey-presto all the type conversions defined inside it are immediately available to Camel was: I wonder if we can avoid having to explicitly configure in Spring the DozerTypeConverterLoader class along with the explicit org.dozer.DozerBeanMapper; but instead get camel-core to auto-detect (with META-INF/services or similar OSGi tricks) the presence of the camel-dozer library and then just automatically create it. e.g. using a META-INF/services//TypeConverterLoader file to force the lazy creation of the DozerTypeConverterLoader object. Then also automatically scan for all META-INF/services/dozer/mapping.xml files and register them all. For more info see: http://camel.apache.org/dozer-type-conversion.html Then it would feel like Dozer mapping files are kinda like Camel type converters; that they are just automatically discovered and configured on the fly - if they are defined in the convention-over-configuration way? e.g. given that camel-dozer is on the classpath, all that is required is you add a META-INF/services/dozer/mapping.xml file to the classpath and hey-presto all the type conversions defined inside it are immediately available to Camel auto-enable and detect Dozer mappings - Key: CAMEL-6511 URL: https://issues.apache.org/jira/browse/CAMEL-6511 Project: Camel Issue Type: New Feature Reporter: james strachan I wonder if we can avoid having to explicitly configure in Spring the DozerTypeConverterLoader class along with the explicit org.dozer.DozerBeanMapper; but instead get camel-core to auto-detect (with META-INF/services or similar OSGi tricks) the presence of the camel-dozer library and then just automatically create it. e.g. using a META-INF/services//TypeConverterLoader file to force the lazy creation of the DozerTypeConverterLoader object. Then also automatically scan for all META-INF/services/dozerMapping.xml files and register them all. For more info see: http://camel.apache.org/dozer-type-conversion.html Then it would feel like Dozer mapping files are kinda like Camel type converters; that they are just automatically discovered and configured on the fly - if they are defined in the convention-over-configuration way? e.g. given that camel-dozer is on the classpath, all that is required is you add a META-INF/services/dozer/mapping.xml file to the classpath and hey-presto all the type conversions defined inside it are immediately available to Camel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6511) auto-enable and detect Dozer mappings
[ https://issues.apache.org/jira/browse/CAMEL-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700498#comment-13700498 ] james strachan commented on CAMEL-6511: --- From a tooling perspective, it'd be nice if folks could just take any project which depends on camel-dozer and just create a file in META-INF/services/dozerMapping.xml using the Dozer eclipse plugin and then create some mappings and they automatically show up in camel as standard type conversions: http://dozer.sourceforge.net/documentation/eclipse-plugin/usage-editor.html auto-enable and detect Dozer mappings - Key: CAMEL-6511 URL: https://issues.apache.org/jira/browse/CAMEL-6511 Project: Camel Issue Type: New Feature Reporter: james strachan I wonder if we can avoid having to explicitly configure in Spring the DozerTypeConverterLoader class along with the explicit org.dozer.DozerBeanMapper; but instead get camel-core to auto-detect (with META-INF/services or similar OSGi tricks) the presence of the camel-dozer library and then just automatically create it. e.g. using a META-INF/services//TypeConverterLoader file to force the lazy creation of the DozerTypeConverterLoader object. Then also automatically scan for all META-INF/services/dozerMapping.xml files and register them all. For more info see: http://camel.apache.org/dozer-type-conversion.html Then it would feel like Dozer mapping files are kinda like Camel type converters; that they are just automatically discovered and configured on the fly - if they are defined in the convention-over-configuration way? e.g. given that camel-dozer is on the classpath, all that is required is you add a META-INF/services/dozer/mapping.xml file to the classpath and hey-presto all the type conversions defined inside it are immediately available to Camel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-6514) SFTP: NPE if no private key file is supplied
Joerg Kessler created CAMEL-6514:
Summary: SFTP: NPE if no private key file is supplied
Key: CAMEL-6514
URL: https://issues.apache.org/jira/browse/CAMEL-6514
Project: Camel
Issue Type: Bug
Components: camel-ftp
Affects Versions: 2.10.4
Reporter: Joerg Kessler
Priority: Minor
Hi,
a NPE is thrown if no private key file is supplied in the configuration for
SFTP. The error is
Caused by: java.lang.NullPointerException: while trying to get the length of an
array loaded from local variable 'foo'
at com.jcraft.jsch.Buffer.putString(Buffer.java:59)
I have analysed the code a bit and found that the problem is caused
by the class SftpOperations. The method createSession sets the userInfo for the
seesion by an inline class. Here the method promptKeyboardInteractive does not
work correctly if no private key file is supplied. In that case JSCH switches
to user/pw authorization and this method is called. But since there is no
password maintained the configation object returns NULL. The present
implementation adds it to the string array causing the error in JSCH. JSCH
either wants a NULL string array or an empty string array (I have tested both).
So the code should look e.g. as follows:
public String[] promptKeyboardInteractive(String destination,
String name, String instruction, String[] prompt, boolean[] echo) {
String password = configuration.getPassword();
if (password == null) {
return new String[0];
} else {
return new String[] { password };
}
}
With that change JSCH returns
Caused by: java.io.FileNotFoundException: ./data/ssh/id_rsa (No such file or
directory)
at java.io.FileInputStream.open(Native Method)
and that is the real cause of the error
Best Regards,
Jörg
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6139) Split the content of a Zip File
[ https://issues.apache.org/jira/browse/CAMEL-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700939#comment-13700939 ] Gardella Juan Pablo commented on CAMEL-6139: The implementation included is not working fine. I had replace the implementation that I had provided for the new one and I have this error: org.apache.camel.ExpressionEvaluationException: org.springframework.expression.spel.SpelEvaluationException: EL1011E:(pos 34): Method call: Attempted to call method size() on null context object. I will provide a test as soon as possible. Split the content of a Zip File --- Key: CAMEL-6139 URL: https://issues.apache.org/jira/browse/CAMEL-6139 Project: Camel Issue Type: New Feature Affects Versions: 2.10.0, 2.10.2, 2.10.3, 2.10.4 Environment: All Reporter: Gardella Juan Pablo Assignee: Willem Jiang Priority: Minor Attachments: camel-zipsplitter.zip Allow split the content of a Zip in a stream way. Each item is an InputStream. Related thread: http://camel.465427.n5.nabble.com/zip-file-best-practices-td5713437.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6250) Setting id on endpoint in from may not work
[ https://issues.apache.org/jira/browse/CAMEL-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller updated CAMEL-6250: Attachment: CAMEL-6250.patch Added proposed patch. I didn't want change Camel core 2.11.1 in last minute. Setting id on endpoint in from may not work - Key: CAMEL-6250 URL: https://issues.apache.org/jira/browse/CAMEL-6250 Project: Camel Issue Type: Bug Components: camel-spring Affects Versions: 2.10.0 Reporter: Claus Ibsen Priority: Minor Fix For: 2.10.7, 2.11.1, 2.12.0 Attachments: CAMEL-6250.patch See nabble http://camel.465427.n5.nabble.com/How-to-get-Id-of-an-Endpoint-tp5730470.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CAMEL-6250) Setting id on endpoint in from may not work
[ https://issues.apache.org/jira/browse/CAMEL-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700987#comment-13700987 ] Christian Müller edited comment on CAMEL-6250 at 7/5/13 4:44 PM: - Added proposed patch. I didn't want change Camel core in last minute. was (Author: muellerc): Added proposed patch. I didn't want change Camel core 2.11.1 in last minute. Setting id on endpoint in from may not work - Key: CAMEL-6250 URL: https://issues.apache.org/jira/browse/CAMEL-6250 Project: Camel Issue Type: Bug Components: camel-spring Affects Versions: 2.10.0 Reporter: Claus Ibsen Priority: Minor Fix For: 2.10.7, 2.11.1, 2.12.0 Attachments: CAMEL-6250.patch See nabble http://camel.465427.n5.nabble.com/How-to-get-Id-of-an-Endpoint-tp5730470.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6250) Setting id on endpoint in from may not work
[ https://issues.apache.org/jira/browse/CAMEL-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700989#comment-13700989 ] Christian Müller commented on CAMEL-6250: - Added an unit test [1] which shows the issue. [1] https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-spring/src/test/java/org/apache/camel/spring/issues/EndpointIdIssueTest.java;h=6f7f54cd21d5b517d9927c989cc118ecdb391653;hb=HEAD Setting id on endpoint in from may not work - Key: CAMEL-6250 URL: https://issues.apache.org/jira/browse/CAMEL-6250 Project: Camel Issue Type: Bug Components: camel-spring Affects Versions: 2.10.0 Reporter: Claus Ibsen Priority: Minor Fix For: 2.10.7, 2.11.1, 2.12.0 Attachments: CAMEL-6250.patch See nabble http://camel.465427.n5.nabble.com/How-to-get-Id-of-an-Endpoint-tp5730470.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6250) Setting id on endpoint in from may not work
[ https://issues.apache.org/jira/browse/CAMEL-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller updated CAMEL-6250: Patch Info: Patch Available Setting id on endpoint in from may not work - Key: CAMEL-6250 URL: https://issues.apache.org/jira/browse/CAMEL-6250 Project: Camel Issue Type: Bug Components: camel-spring Affects Versions: 2.10.0 Reporter: Claus Ibsen Priority: Minor Fix For: 2.10.7, 2.11.1, 2.12.0 Attachments: CAMEL-6250.patch See nabble http://camel.465427.n5.nabble.com/How-to-get-Id-of-an-Endpoint-tp5730470.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6250) Setting id on endpoint in from may not work
[ https://issues.apache.org/jira/browse/CAMEL-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller updated CAMEL-6250: Fix Version/s: (was: 2.11.1) 2.11.2 Setting id on endpoint in from may not work - Key: CAMEL-6250 URL: https://issues.apache.org/jira/browse/CAMEL-6250 Project: Camel Issue Type: Bug Components: camel-spring Affects Versions: 2.10.0 Reporter: Claus Ibsen Priority: Minor Fix For: 2.10.7, 2.11.2, 2.12.0 Attachments: CAMEL-6250.patch See nabble http://camel.465427.n5.nabble.com/How-to-get-Id-of-an-Endpoint-tp5730470.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6474) DOM2SAX doesn't provide the full support of SAX
[ https://issues.apache.org/jira/browse/CAMEL-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller updated CAMEL-6474: Fix Version/s: (was: 2.11.1) 2.11.2 DOM2SAX doesn't provide the full support of SAX --- Key: CAMEL-6474 URL: https://issues.apache.org/jira/browse/CAMEL-6474 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.11.0 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.11.2, 2.12.0 XmlConverter will convert the DomSource into SAXSource when it can find the org.apache.xalan.xsltc.trax.DOM2SAX. But the DOM2SAX doesn't provide the full support of SAX, which causes the NPE issue when we route the SAXSource into xslt transformer like saxon transformer. Here are some discussion on saxon support https://saxonica.plan.io/issues/1814. BTW, when I changed the transformer to the xalan one, I still the java.util.EmptyStackException. So my suggest we need to diable this convertor until we find other good solution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6486) Upgrade camel-bean-validator to JSR349 (Bean Validation 1.1)
[
https://issues.apache.org/jira/browse/CAMEL-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Müller updated CAMEL-6486:
Fix Version/s: (was: 2.11.1)
2.11.2
Upgrade camel-bean-validator to JSR349 (Bean Validation 1.1)
Key: CAMEL-6486
URL: https://issues.apache.org/jira/browse/CAMEL-6486
Project: Camel
Issue Type: Task
Affects Versions: 2.10.4, 2.11.0
Reporter: Raul Kripalani
Assignee: Raul Kripalani
Fix For: 2.10.7, 2.11.2, 2.12.0
SMX bundle no longer necessary as version 1.1 of the API seems to carry OSGi
exports:
{code}
karaf@root install -s mvn:javax.validation/validation-api/1.1.0.Final
Bundle ID: 254
karaf@root exports 254
ID Packages
254 javax.validation.groups; version=1.1.0.Final
254 javax.validation.metadata; version=1.1.0.Final
254 javax.validation; version=1.1.0.Final
254 javax.validation.executable; version=1.1.0.Final
254 javax.validation.constraintvalidation; version=1.1.0.Final
254 javax.validation.spi; version=1.1.0.Final
254 javax.validation.bootstrap; version=1.1.0.Final
254 javax.validation.constraints; version=1.1.0.Final
karaf@root
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6292) Camel archetype component - Use bundle packaging so component is ready to install in OSGi
[ https://issues.apache.org/jira/browse/CAMEL-6292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller updated CAMEL-6292: Fix Version/s: (was: 2.11.1) 2.11.2 Camel archetype component - Use bundle packaging so component is ready to install in OSGi - Key: CAMEL-6292 URL: https://issues.apache.org/jira/browse/CAMEL-6292 Project: Camel Issue Type: Improvement Components: tooling Affects Versions: 2.10.4, 2.11.0 Reporter: Claus Ibsen Priority: Minor Fix For: 2.10.7, 2.11.2, 2.12.0 The component archetypes should have the pom.xml changed so they generate a project that use bundle packaging with the felix bundle plugin. Then the component is ready to install in OSGi. See nabble http://camel.465427.n5.nabble.com/Creating-new-processor-components-td5730919.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6228) CXFRS: Consumer - Inject Resource instance into message
[ https://issues.apache.org/jira/browse/CAMEL-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller updated CAMEL-6228: Fix Version/s: (was: 2.11.1) 2.12.0 2.11.2 CXFRS: Consumer - Inject Resource instance into message --- Key: CAMEL-6228 URL: https://issues.apache.org/jira/browse/CAMEL-6228 Project: Camel Issue Type: Improvement Components: camel-cxf Affects Versions: 2.10.4 Reporter: Raul Kripalani Assignee: Raul Kripalani Fix For: 2.11.2, 2.12.0 CxfRsInvoker#asyncInvoke and CxfRsInvoker#syncInvoke forsake the Service Object. Instead it should be passed on to the CxfRsBinding. Will try and fix for 2.11 as it implies API changes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6228) CXFRS: Consumer - Inject Resource instance into message
[ https://issues.apache.org/jira/browse/CAMEL-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700994#comment-13700994 ] Christian Müller commented on CAMEL-6228: - If it really implies an API change, we should only fix this in Camel 2.12. now (not in Camel 2.11 because 2.11.0 is already released). CXFRS: Consumer - Inject Resource instance into message --- Key: CAMEL-6228 URL: https://issues.apache.org/jira/browse/CAMEL-6228 Project: Camel Issue Type: Improvement Components: camel-cxf Affects Versions: 2.10.4 Reporter: Raul Kripalani Assignee: Raul Kripalani Fix For: 2.11.2, 2.12.0 CxfRsInvoker#asyncInvoke and CxfRsInvoker#syncInvoke forsake the Service Object. Instead it should be passed on to the CxfRsBinding. Will try and fix for 2.11 as it implies API changes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-6266) Support for SFTP through a proxy
[ https://issues.apache.org/jira/browse/CAMEL-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller reassigned CAMEL-6266: --- Assignee: Christian Müller Support for SFTP through a proxy Key: CAMEL-6266 URL: https://issues.apache.org/jira/browse/CAMEL-6266 Project: Camel Issue Type: Improvement Components: camel-ftp Reporter: Joakim Ek Assignee: Christian Müller Priority: Minor Fix For: 2.11.1, 2.12.0 Attachments: sftp_proxy.patch FTP and FTPS have the 'ftpClient' option that allows the use of a custom org.apache.commons.net.ftp.FTPClient instance. I.e. org.apache.commons.net.ftp.FTPHTTPClient to access a FTP server through a HTTP proxy. SFTP currently lacks proxy support in Camel. The used JSch library however has support for proxies. This patch adds a SFTP only option 'proxy' which allows passing in an instance of com.jcraft.jsch.Proxy to JSch. This enables the use of SFTP through HTTP, SOCKS4 and SOCKS5 proxies. Included are two new basic unit tests using [Little Proxy|http://www.littleshoot.org/littleproxy/] to verify consuming and producing through a HTTP proxy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (CAMEL-6266) Support for SFTP through a proxy
[ https://issues.apache.org/jira/browse/CAMEL-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-6266 started by Christian Müller. Support for SFTP through a proxy Key: CAMEL-6266 URL: https://issues.apache.org/jira/browse/CAMEL-6266 Project: Camel Issue Type: Improvement Components: camel-ftp Reporter: Joakim Ek Assignee: Christian Müller Priority: Minor Fix For: 2.11.1, 2.12.0 Attachments: sftp_proxy.patch FTP and FTPS have the 'ftpClient' option that allows the use of a custom org.apache.commons.net.ftp.FTPClient instance. I.e. org.apache.commons.net.ftp.FTPHTTPClient to access a FTP server through a HTTP proxy. SFTP currently lacks proxy support in Camel. The used JSch library however has support for proxies. This patch adds a SFTP only option 'proxy' which allows passing in an instance of com.jcraft.jsch.Proxy to JSch. This enables the use of SFTP through HTTP, SOCKS4 and SOCKS5 proxies. Included are two new basic unit tests using [Little Proxy|http://www.littleshoot.org/littleproxy/] to verify consuming and producing through a HTTP proxy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6266) Support for SFTP through a proxy
[ https://issues.apache.org/jira/browse/CAMEL-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701005#comment-13701005 ] Joakim Ek commented on CAMEL-6266: -- Hi, I am on vacation until the 19th of August. For support matters please use the communicated support email addresses and someone will get back to you. Regards, Joakim Support for SFTP through a proxy Key: CAMEL-6266 URL: https://issues.apache.org/jira/browse/CAMEL-6266 Project: Camel Issue Type: Improvement Components: camel-ftp Reporter: Joakim Ek Assignee: Christian Müller Priority: Minor Fix For: 2.11.1, 2.12.0 Attachments: sftp_proxy.patch FTP and FTPS have the 'ftpClient' option that allows the use of a custom org.apache.commons.net.ftp.FTPClient instance. I.e. org.apache.commons.net.ftp.FTPHTTPClient to access a FTP server through a HTTP proxy. SFTP currently lacks proxy support in Camel. The used JSch library however has support for proxies. This patch adds a SFTP only option 'proxy' which allows passing in an instance of com.jcraft.jsch.Proxy to JSch. This enables the use of SFTP through HTTP, SOCKS4 and SOCKS5 proxies. Included are two new basic unit tests using [Little Proxy|http://www.littleshoot.org/littleproxy/] to verify consuming and producing through a HTTP proxy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6266) Support for SFTP through a proxy
[ https://issues.apache.org/jira/browse/CAMEL-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller resolved CAMEL-6266. - Resolution: Fixed Thanks for the contribution Joakim. I already updated the WIKI with the new option. It would be nice, if you could have a look at it. Support for SFTP through a proxy Key: CAMEL-6266 URL: https://issues.apache.org/jira/browse/CAMEL-6266 Project: Camel Issue Type: Improvement Components: camel-ftp Reporter: Joakim Ek Assignee: Christian Müller Priority: Minor Fix For: 2.11.1, 2.12.0 Attachments: sftp_proxy.patch FTP and FTPS have the 'ftpClient' option that allows the use of a custom org.apache.commons.net.ftp.FTPClient instance. I.e. org.apache.commons.net.ftp.FTPHTTPClient to access a FTP server through a HTTP proxy. SFTP currently lacks proxy support in Camel. The used JSch library however has support for proxies. This patch adds a SFTP only option 'proxy' which allows passing in an instance of com.jcraft.jsch.Proxy to JSch. This enables the use of SFTP through HTTP, SOCKS4 and SOCKS5 proxies. Included are two new basic unit tests using [Little Proxy|http://www.littleshoot.org/littleproxy/] to verify consuming and producing through a HTTP proxy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6507) Add aggregat ability to camel_mongodb
[
https://issues.apache.org/jira/browse/CAMEL-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre-Alban DEWITTE resolved CAMEL-6507.
-
Resolution: Fixed
Add aggregat ability to camel_mongodb
-
Key: CAMEL-6507
URL: https://issues.apache.org/jira/browse/CAMEL-6507
Project: Camel
Issue Type: New Feature
Components: camel-mongodb
Affects Versions: 2.11.0
Reporter: Pierre-Alban DEWITTE
Assignee: Willem Jiang
Labels: patch
Hi,
I just add the ability to use aggregat in camel-mongo-db route.
Now you can declare a route to aggregate :
from(...).to(mongodb:myDb?database=testcollection=testoperation=aggregatdynamicity=true);
The body should contain a valid Mongo pipeline for example { $match : {name
: my product}},{ $group: { _id: $name ,total: { $sum: $price } } }
P-Alban
PS : I just create a pull request on github
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6507) Add aggregat ability to camel_mongodb
[
https://issues.apache.org/jira/browse/CAMEL-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701090#comment-13701090
]
Raul Kripalani commented on CAMEL-6507:
---
[~padewitte] – You can edit the Wiki page here:
https://cwiki.apache.org/confluence/display/CAMEL/MongoDB.
To be granted Wiki Edit karma, please read the instructions here:
http://camel.apache.org/contributing.html.
Thanks a lot for your contribution, it's really appreciated!
Add aggregat ability to camel_mongodb
-
Key: CAMEL-6507
URL: https://issues.apache.org/jira/browse/CAMEL-6507
Project: Camel
Issue Type: New Feature
Components: camel-mongodb
Affects Versions: 2.11.0
Reporter: Pierre-Alban DEWITTE
Assignee: Willem Jiang
Labels: patch
Hi,
I just add the ability to use aggregat in camel-mongo-db route.
Now you can declare a route to aggregate :
from(...).to(mongodb:myDb?database=testcollection=testoperation=aggregatdynamicity=true);
The body should contain a valid Mongo pipeline for example { $match : {name
: my product}},{ $group: { _id: $name ,total: { $sum: $price } } }
P-Alban
PS : I just create a pull request on github
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6139) Split the content of a Zip File
[ https://issues.apache.org/jira/browse/CAMEL-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gardella Juan Pablo updated CAMEL-6139: --- Attachment: camel-zipsplitter2.zip camel-zipsplitter2.zip contains one more test: ZipProcessRouteBuilderIT.java In the test is possible reproduce the error that I mentioned. Split the content of a Zip File --- Key: CAMEL-6139 URL: https://issues.apache.org/jira/browse/CAMEL-6139 Project: Camel Issue Type: New Feature Affects Versions: 2.10.0, 2.10.2, 2.10.3, 2.10.4 Environment: All Reporter: Gardella Juan Pablo Assignee: Willem Jiang Priority: Minor Attachments: camel-zipsplitter2.zip, camel-zipsplitter.zip Allow split the content of a Zip in a stream way. Each item is an InputStream. Related thread: http://camel.465427.n5.nabble.com/zip-file-best-practices-td5713437.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6320) Provide support for ICAL data format
[ https://issues.apache.org/jira/browse/CAMEL-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701142#comment-13701142 ] Christian Müller commented on CAMEL-6320: - I added the documentation for the iCal data format. It would be good, if you could have a look at it. Provide support for ICAL data format Key: CAMEL-6320 URL: https://issues.apache.org/jira/browse/CAMEL-6320 Project: Camel Issue Type: New Feature Reporter: Łukasz Dywicki Assignee: Hadrian Zbarcea Fix For: 2.11.1, 2.12.0 ical is popular data format used for scheduling and handling calendar events. It may be easily integrated into camel thanks to ical4j library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6320) Provide support for ICAL data format
[ https://issues.apache.org/jira/browse/CAMEL-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701145#comment-13701145 ] Christian Müller commented on CAMEL-6320: - https://cwiki.apache.org/confluence/display/CAMEL/ICal Provide support for ICAL data format Key: CAMEL-6320 URL: https://issues.apache.org/jira/browse/CAMEL-6320 Project: Camel Issue Type: New Feature Reporter: Łukasz Dywicki Assignee: Hadrian Zbarcea Fix For: 2.11.1, 2.12.0 ical is popular data format used for scheduling and handling calendar events. It may be easily integrated into camel thanks to ical4j library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6320) Provide support for ICAL data format
[ https://issues.apache.org/jira/browse/CAMEL-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Müller resolved CAMEL-6320. - Resolution: Fixed Provide support for ICAL data format Key: CAMEL-6320 URL: https://issues.apache.org/jira/browse/CAMEL-6320 Project: Camel Issue Type: New Feature Reporter: Łukasz Dywicki Assignee: Hadrian Zbarcea Fix For: 2.11.1, 2.12.0 ical is popular data format used for scheduling and handling calendar events. It may be easily integrated into camel thanks to ical4j library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
