[jira] [Commented] (CAMEL-9991) lots of broken links on camel.apache.org
[ https://issues.apache.org/jira/browse/CAMEL-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394427#comment-15394427 ] onder sezgin commented on CAMEL-9991: - I can help fixing the links > lots of broken links on camel.apache.org > > > Key: CAMEL-9991 > URL: https://issues.apache.org/jira/browse/CAMEL-9991 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Bennet Schulz >Priority: Trivial > > Hi guys, > I recently found some broken links and used a link checker after that. In > total there are 86 broken links. > here is a listing (sorry for the format): > http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.asc > > http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.md5 > > http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.sha1 > > http://camel.apache.org/confluence/display/~gzurowski > http://camel.apache.org/confluence/display/~muellerc > http://servicemix.apache.org/uris.htmlServiceMix URI Guide > http://servicemix.apache.org/maven-jbi-plugin.htmlServiceMix Maven JBI > Plugins > http://servicemix.apache.org/3-beginner-using-apache-camel-inside-servicemix.html > Using Camel with ServiceMix > http://servicemix.apache.org/order-file-processing.html Cookbook on > using Camel with ServiceMix > http://mina.apache.org/iofilter.html Mina IoFilters > http://mina.apache.org/tutorial-on-protocolcodecfilter.html Mina > documentation > http://mina.apache.org/report/1.1/apidocs/org/apache/mina/transport/vmpipe/package-summary.html >MINA VM-Pipe API documentation > http://servicemix.apache.org/servicemix-camel.htmlServiceMix Camel module > http://people.apache.org/repo/m2-ibiblio-rsync-repository/ > http://people.apache.org/repo/m2-ibiblio-rsync-repository/ > http://activemq.apache.org/maven/5.5.0/activemq-camel/apidocs/org/apache/activemq/camel/component/ActiveMQComponent.html > activeMQComponent() method > http://camel.apache.org/$base/privacy-policy.html Privacy Policy > http://apache.org/hello_world_soap_http > http://apache.org/hello_world_soap_http > http://example.com/servicehttp://example.com/service > http://www.eu.apachecon.com ApacheCon Europe 2008 > https://svn.apache.org/repos/asf/cxf/trunk/api/src/main/java/org/apache/cxf/endpoint/Client.java > cxf client API > http://apache.org/cxf/Apache CXF > http://newhosthttp://newhost > http://hadoop.apache.org/hdfs/HDFS > http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/ > Hibernate Validator > http://metrics.codahale.com/ Metrics > http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html bayeux protocol > http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/eventbus/package-summary.html > Google Guava EventBus > http://servicemix.apache.org/SMX4NMR/index.html ServiceMix 4.x > https://rhiot.gitbooks.io/rhiotdocumentation/content/backend/camel_components/camel_openimaj_component.html >OpenIMAJ > http://svn.apache.org/repos/asf/camel/trunk/components/camel-test-cdi/src/test/java/org/apache/camel/test/cdi/FilterTest.java > example > http://gliesian.com/camel/ApacheCamelComponents.pdf Free PDF > https://rhiot.gitbooks.io/rhiotdocumentation/content/gateway/camel_components/camel_kura_cloud_component.html > kura-cloud > http://gauthcloud.appspot.com/http://gauthcloud.appspot.com/ > http://camelcloud.appspot.com/http://camelcloud.appspot.com/ > http://http//www.enterpriseintegrationpatterns.com/ComposedMessagingExample.html > EIP composed messaging sample > http://scalate.fusesource.org/Scalate > http://www.smooks.org/mediawiki/index.php?title=V1.5:Smooks_v1.5_User_Guide > Camel integration out of the box > http://scalate.fusesource.org/camel.html Scalate > http://www.db4o.com/ db4o > http://fabric8.io/gitbook/camelEndpointAmq.html AMQ > http://servicemix.apache.org/camel-example.html example > https://open-esb.dev.java.net/Open ESB > http://www.subrecord.org/ SubRecord > http://www.opensplice.com/section-item.asp?id=964 PrismTech > http://doc.akkasource.org/actors actors > http://doc.akkasource.org/camel akka-camel > http://touk.pl/toukeu/rw/pages/index.en.doTouK > http://forge.jboss.org/ JBoss Forge > http://forge.jboss.org/addon/io.fabric8.forge:camel Camel addon > http://www.linkedin.com/in/gregorzurowski/Gregor Zurowski > http://www.systechnologies.com/ SYS Technologies > http://www.drkw.com/ Dresdner Kleinwort Wasserstein > http://www.trevorpounds.com Trevor Pounds > http://irclogs.dankulp.com/logs/irclogger_logs/apache-camel >
[jira] [Commented] (CAMEL-10185) camel-ftp - fastExistsCheck issue
[ https://issues.apache.org/jira/browse/CAMEL-10185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407378#comment-15407378 ] onder sezgin commented on CAMEL-10185: -- please see my comment as well. https://github.com/apache/camel/commit/91c086b7af22b6cfaf2f66b2c872b752dc10a19c > camel-ftp - fastExistsCheck issue > - > > Key: CAMEL-10185 > URL: https://issues.apache.org/jira/browse/CAMEL-10185 > Project: Camel > Issue Type: Bug > Components: camel-ftp >Affects Versions: 2.17.2 >Reporter: Claus Ibsen > Fix For: 2.16.4, 2.17.3, 2.18.0 > > > See SO > https://github.com/apache/camel/commit/91c086b7af22b6cfaf2f66b2c872b752dc10a19c#commitcomment-18363186 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10185) camel-ftp - fastExistsCheck issue
[ https://issues.apache.org/jira/browse/CAMEL-10185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407923#comment-15407923 ] onder sezgin commented on CAMEL-10185: -- issue is not valid, https://github.com/apache/camel/commit/91c086b7af22b6cfaf2f66b2c872b752dc10a19c > camel-ftp - fastExistsCheck issue > - > > Key: CAMEL-10185 > URL: https://issues.apache.org/jira/browse/CAMEL-10185 > Project: Camel > Issue Type: Bug > Components: camel-ftp >Affects Versions: 2.17.2 >Reporter: Claus Ibsen > Fix For: 2.16.4, 2.17.3, 2.18.0 > > > See SO > https://github.com/apache/camel/commit/91c086b7af22b6cfaf2f66b2c872b752dc10a19c#commitcomment-18363186 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10228) camel-sql - Preserver attachments
[ https://issues.apache.org/jira/browse/CAMEL-10228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420297#comment-15420297 ] onder sezgin commented on CAMEL-10228: -- I know attachment concept but i am not sure if i understand why attachment needed in sqlproducer. what might be the use case for it? > camel-sql - Preserver attachments > - > > Key: CAMEL-10228 > URL: https://issues.apache.org/jira/browse/CAMEL-10228 > Project: Camel > Issue Type: Improvement > Components: camel-sql >Reporter: Claus Ibsen > Fix For: 2.18.0 > > > See nabble > http://camel.465427.n5.nabble.com/camel-sql-insert-ouput-tp5786200.html > In the SqlProducer where we preserve headers, we should also preserve the > attachments as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8418) Add documentation to camel-atmos component
[ https://issues.apache.org/jira/browse/CAMEL-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420317#comment-15420317 ] onder sezgin commented on CAMEL-8418: - if you can guide me, I can help about the documentation (keep in mind; i am not familiar of this component, be sure i can figure out :) ) > Add documentation to camel-atmos component > -- > > Key: CAMEL-8418 > URL: https://issues.apache.org/jira/browse/CAMEL-8418 > Project: Camel > Issue Type: Task > Components: camel-atmos, documentation >Affects Versions: 2.15.0 >Reporter: Claus Ibsen > Fix For: Future > > > We need to add documentation to the wiki -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10171) Camel CXF expired continuations cause memory leak
[
https://issues.apache.org/jira/browse/CAMEL-10171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416897#comment-15416897
]
onder sezgin commented on CAMEL-10171:
--
let me explain what i did.
I found out that i need to detect continuation expiry in CxfConsumer.
I logged a ticket and it is partially fixed.
(https://issues.apache.org/jira/browse/CXF-7002)
Because it is not provided via Contunation interface.
However, let's assume we have method access in Continuation interface (as i did
in my local source)
and in CxfConsumer.asyncInvoke method i can add
if(continuation.isExpired()) {
//...
// handle camel exchange
//
}
I know contunation is expired but i dont have the exchange.
> Camel CXF expired continuations cause memory leak
> -
>
> Key: CAMEL-10171
> URL: https://issues.apache.org/jira/browse/CAMEL-10171
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
>Affects Versions: 2.17.1
>Reporter: Damian Malczyk
>
> Looks like exchanges expired by CXF continuation timeout are being
> accumulated in InflightRepository. Tested with Camel 2.17.1 and
> cxf-rt-transports-http-jetty:
> Dependencies:
> {code}
>
> org.apache.camel
> camel-core
> 2.17.1
>
>
> org.apache.camel
> camel-cxf
> 2.17.1
>
>
> org.apache.cxf
> cxf-rt-transports-http-jetty
> 3.1.5
>
> {code}
> Reproducer:
> {code}import org.apache.camel.CamelContext;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.cxf.CxfEndpoint;
> import org.apache.camel.component.cxf.DataFormat;
> import org.apache.camel.impl.DefaultCamelContext;
> import org.springframework.util.StreamUtils;
> import org.w3c.dom.Document;
> import javax.xml.parsers.DocumentBuilder;
> import javax.xml.parsers.DocumentBuilderFactory;
> import javax.xml.soap.MessageFactory;
> import javax.xml.soap.SOAPMessage;
> import java.io.ByteArrayInputStream;
> import java.io.ByteArrayOutputStream;
> import java.net.HttpURLConnection;
> import java.net.URL;
> import java.util.Timer;
> import java.util.TimerTask;
> import java.util.concurrent.Executor;
> import java.util.concurrent.Executors;
> public class Sample {
> private final static String URI = "http://127.0.0.1:8080/;;
> private final static long CONTINUATION_TIMEOUT = 100L;
> private final static long DELAYER_VALUE = 200L;
> private final static int SENDER_THREADS =
> Runtime.getRuntime().availableProcessors();
> private final static int MESSAGES_PER_SENDER = 1;
> private static void setupCamel() throws Exception {
> final CamelContext camelContext = new DefaultCamelContext();
> final CxfEndpoint endpoint = (CxfEndpoint)camelContext.getEndpoint(
> "cxf://" + URI );
> endpoint.setContinuationTimeout( CONTINUATION_TIMEOUT );
> endpoint.setDataFormat( DataFormat.PAYLOAD );
> camelContext.addRoutes( new RouteBuilder() {
> public void configure() throws Exception {
> from( endpoint )
> .threads()
> .setBody( constant( "" ) )
> .delay( DELAYER_VALUE )
> .end();
> }
> });
> final TimerTask repoSizeReporter = new TimerTask() {
> public void run() {
> System.out.println( "Inflight repository size: " +
> camelContext.getInflightRepository().size() );
> System.gc();
> System.out.println( "Memory usage: " +
> (Runtime.getRuntime().totalMemory() -
> Runtime.getRuntime().freeMemory())/(1024*1024) + "MB" );
> }
> };
> final Timer repoSizeReporterTimer = new Timer();
> repoSizeReporterTimer.schedule( repoSizeReporter, 1000, 1000 );
> camelContext.start();
> }
> private static byte[] createSoapMessage() throws Exception {
> final StringBuilder payloadBuilder = new StringBuilder( "" );
> for( int i = 0; i < 5000; i++ ) {
> payloadBuilder.append( "" );
> }
> final String payload = payloadBuilder.append( ""
> ).toString();
> final DocumentBuilder documentBuilder =
> DocumentBuilderFactory.newInstance().newDocumentBuilder();
> final Document payloadDocument = documentBuilder.parse( new
> ByteArrayInputStream( payload.getBytes() ) );
> final ByteArrayOutputStream soapOutStream = new
> ByteArrayOutputStream();
> final SOAPMessage message =
> MessageFactory.newInstance().createMessage();
> message.getSOAPBody().addDocument( payloadDocument );
> message.writeTo( soapOutStream );
> return soapOutStream.toByteArray();
> }
> private static Runnable
[jira] [Commented] (CAMEL-10171) Camel CXF expired continuations cause memory leak
[
https://issues.apache.org/jira/browse/CAMEL-10171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415144#comment-15415144
]
onder sezgin commented on CAMEL-10171:
--
I can get the expiry callback, however i can't get the exhange. Any suggestion?
> Camel CXF expired continuations cause memory leak
> -
>
> Key: CAMEL-10171
> URL: https://issues.apache.org/jira/browse/CAMEL-10171
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
>Affects Versions: 2.17.1
>Reporter: Damian Malczyk
>
> Looks like exchanges expired by CXF continuation timeout are being
> accumulated in InflightRepository. Tested with Camel 2.17.1 and
> cxf-rt-transports-http-jetty:
> Dependencies:
> {code}
>
> org.apache.camel
> camel-core
> 2.17.1
>
>
> org.apache.camel
> camel-cxf
> 2.17.1
>
>
> org.apache.cxf
> cxf-rt-transports-http-jetty
> 3.1.5
>
> {code}
> Reproducer:
> {code}import org.apache.camel.CamelContext;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.cxf.CxfEndpoint;
> import org.apache.camel.component.cxf.DataFormat;
> import org.apache.camel.impl.DefaultCamelContext;
> import org.springframework.util.StreamUtils;
> import org.w3c.dom.Document;
> import javax.xml.parsers.DocumentBuilder;
> import javax.xml.parsers.DocumentBuilderFactory;
> import javax.xml.soap.MessageFactory;
> import javax.xml.soap.SOAPMessage;
> import java.io.ByteArrayInputStream;
> import java.io.ByteArrayOutputStream;
> import java.net.HttpURLConnection;
> import java.net.URL;
> import java.util.Timer;
> import java.util.TimerTask;
> import java.util.concurrent.Executor;
> import java.util.concurrent.Executors;
> public class Sample {
> private final static String URI = "http://127.0.0.1:8080/;;
> private final static long CONTINUATION_TIMEOUT = 100L;
> private final static long DELAYER_VALUE = 200L;
> private final static int SENDER_THREADS =
> Runtime.getRuntime().availableProcessors();
> private final static int MESSAGES_PER_SENDER = 1;
> private static void setupCamel() throws Exception {
> final CamelContext camelContext = new DefaultCamelContext();
> final CxfEndpoint endpoint = (CxfEndpoint)camelContext.getEndpoint(
> "cxf://" + URI );
> endpoint.setContinuationTimeout( CONTINUATION_TIMEOUT );
> endpoint.setDataFormat( DataFormat.PAYLOAD );
> camelContext.addRoutes( new RouteBuilder() {
> public void configure() throws Exception {
> from( endpoint )
> .threads()
> .setBody( constant( "" ) )
> .delay( DELAYER_VALUE )
> .end();
> }
> });
> final TimerTask repoSizeReporter = new TimerTask() {
> public void run() {
> System.out.println( "Inflight repository size: " +
> camelContext.getInflightRepository().size() );
> System.gc();
> System.out.println( "Memory usage: " +
> (Runtime.getRuntime().totalMemory() -
> Runtime.getRuntime().freeMemory())/(1024*1024) + "MB" );
> }
> };
> final Timer repoSizeReporterTimer = new Timer();
> repoSizeReporterTimer.schedule( repoSizeReporter, 1000, 1000 );
> camelContext.start();
> }
> private static byte[] createSoapMessage() throws Exception {
> final StringBuilder payloadBuilder = new StringBuilder( "" );
> for( int i = 0; i < 5000; i++ ) {
> payloadBuilder.append( "" );
> }
> final String payload = payloadBuilder.append( ""
> ).toString();
> final DocumentBuilder documentBuilder =
> DocumentBuilderFactory.newInstance().newDocumentBuilder();
> final Document payloadDocument = documentBuilder.parse( new
> ByteArrayInputStream( payload.getBytes() ) );
> final ByteArrayOutputStream soapOutStream = new
> ByteArrayOutputStream();
> final SOAPMessage message =
> MessageFactory.newInstance().createMessage();
> message.getSOAPBody().addDocument( payloadDocument );
> message.writeTo( soapOutStream );
> return soapOutStream.toByteArray();
> }
> private static Runnable soapSender() {
> return () -> {
> try {
> final byte[] soapMessage = createSoapMessage();
> for( int i = 0; i < MESSAGES_PER_SENDER; i++ ) {
> final HttpURLConnection connection =
> (HttpURLConnection)new URL( URI ).openConnection();
> connection.setDoOutput( true );
> connection.setRequestProperty( "Content-Type", "text/xml"
> );
>
[jira] [Commented] (CAMEL-10171) Camel CXF expired continuations cause memory leak
[
https://issues.apache.org/jira/browse/CAMEL-10171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411781#comment-15411781
]
onder sezgin commented on CAMEL-10171:
--
I went through the problem. As i can see, cxf-rt-transports-http-jetty-3.1.7
has no such method to propagate the continuation time out back to camel-cxf.
First, Servlet3Continuation and and JettyContinuationWrapper should have the
required method implementation to query if timeout is expired and camel-cxf
should have such implementation as the following;
else if (continuation.isExpired()) {
// mark the exchange with server timeout error
// trigger the exhange as done so that it is not counted as
inflight.
.
}
I will try and see if i can provide PR.
> Camel CXF expired continuations cause memory leak
> -
>
> Key: CAMEL-10171
> URL: https://issues.apache.org/jira/browse/CAMEL-10171
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
>Affects Versions: 2.17.1
>Reporter: Damian Malczyk
> Fix For: 2.17.3, 2.18.0
>
>
> Looks like exchanges expired by CXF continuation timeout are being
> accumulated in InflightRepository. Tested with Camel 2.17.1 and
> cxf-rt-transports-http-jetty:
> Dependencies:
> {code}
>
> org.apache.camel
> camel-core
> 2.17.1
>
>
> org.apache.camel
> camel-cxf
> 2.17.1
>
>
> org.apache.cxf
> cxf-rt-transports-http-jetty
> 3.1.5
>
> {code}
> Reproducer:
> {code}import org.apache.camel.CamelContext;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.cxf.CxfEndpoint;
> import org.apache.camel.component.cxf.DataFormat;
> import org.apache.camel.impl.DefaultCamelContext;
> import org.springframework.util.StreamUtils;
> import org.w3c.dom.Document;
> import javax.xml.parsers.DocumentBuilder;
> import javax.xml.parsers.DocumentBuilderFactory;
> import javax.xml.soap.MessageFactory;
> import javax.xml.soap.SOAPMessage;
> import java.io.ByteArrayInputStream;
> import java.io.ByteArrayOutputStream;
> import java.net.HttpURLConnection;
> import java.net.URL;
> import java.util.Timer;
> import java.util.TimerTask;
> import java.util.concurrent.Executor;
> import java.util.concurrent.Executors;
> public class Sample {
> private final static String URI = "http://127.0.0.1:8080/;;
> private final static long CONTINUATION_TIMEOUT = 100L;
> private final static long DELAYER_VALUE = 200L;
> private final static int SENDER_THREADS =
> Runtime.getRuntime().availableProcessors();
> private final static int MESSAGES_PER_SENDER = 1;
> private static void setupCamel() throws Exception {
> final CamelContext camelContext = new DefaultCamelContext();
> final CxfEndpoint endpoint = (CxfEndpoint)camelContext.getEndpoint(
> "cxf://" + URI );
> endpoint.setContinuationTimeout( CONTINUATION_TIMEOUT );
> endpoint.setDataFormat( DataFormat.PAYLOAD );
> camelContext.addRoutes( new RouteBuilder() {
> public void configure() throws Exception {
> from( endpoint )
> .threads()
> .setBody( constant( "" ) )
> .delay( DELAYER_VALUE )
> .end();
> }
> });
> final TimerTask repoSizeReporter = new TimerTask() {
> public void run() {
> System.out.println( "Inflight repository size: " +
> camelContext.getInflightRepository().size() );
> System.gc();
> System.out.println( "Memory usage: " +
> (Runtime.getRuntime().totalMemory() -
> Runtime.getRuntime().freeMemory())/(1024*1024) + "MB" );
> }
> };
> final Timer repoSizeReporterTimer = new Timer();
> repoSizeReporterTimer.schedule( repoSizeReporter, 1000, 1000 );
> camelContext.start();
> }
> private static byte[] createSoapMessage() throws Exception {
> final StringBuilder payloadBuilder = new StringBuilder( "" );
> for( int i = 0; i < 5000; i++ ) {
> payloadBuilder.append( "" );
> }
> final String payload = payloadBuilder.append( ""
> ).toString();
> final DocumentBuilder documentBuilder =
> DocumentBuilderFactory.newInstance().newDocumentBuilder();
> final Document payloadDocument = documentBuilder.parse( new
> ByteArrayInputStream( payload.getBytes() ) );
> final ByteArrayOutputStream soapOutStream = new
> ByteArrayOutputStream();
> final SOAPMessage message =
> MessageFactory.newInstance().createMessage();
>
[jira] [Commented] (CAMEL-10781) Add available from to misc list of components
[ https://issues.apache.org/jira/browse/CAMEL-10781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857903#comment-15857903 ] onder sezgin commented on CAMEL-10781: -- any help still needed? > Add available from to misc list of components > - > > Key: CAMEL-10781 > URL: https://issues.apache.org/jira/browse/CAMEL-10781 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Claus Ibsen >Priority: Minor > Fix For: 2.19.0 > > > In this table > https://github.com/apache/camel/tree/master/components#other-components > We should add the `Available From` column with the version when it was added. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (CAMEL-5980) camel-mail - Better handle null values when extracting attachments
[ https://issues.apache.org/jira/browse/CAMEL-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-5980 started by onder sezgin. --- > camel-mail - Better handle null values when extracting attachments > -- > > Key: CAMEL-5980 > URL: https://issues.apache.org/jira/browse/CAMEL-5980 > Project: Camel > Issue Type: Improvement > Components: camel-mail >Affects Versions: 2.9.0, 2.10.0 >Reporter: Claus Ibsen >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > Attachments: CAMEL-5980FirstPass.patch, debug_log.txt, > EmailExceptionTest.java, EmailTest.java, Exception Mail.eml > > > See nabble > http://camel.465427.n5.nabble.com/MailComponent-s-claim-to-handle-special-mail-multipart-formats-and-attachments-tp5724859.html > We should see if we can fix the Camel code to handle those null data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-5980) camel-mail - Better handle null values when extracting attachments
[
https://issues.apache.org/jira/browse/CAMEL-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837313#comment-15837313
]
onder sezgin commented on CAMEL-5980:
-
Hi, I am trying to reproduce the issue,
when i ran the junit case on windows, i see error as below;
java.lang.AssertionError: expected null, but
was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotNull(Assert.java:755)
at org.junit.Assert.assertNull(Assert.java:737)
at org.junit.Assert.assertNull(Assert.java:747)
at
org.apache.camel.component.mail.EmailExceptionTest.testEmailFileNew(EmailExceptionTest.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
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:678)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
then i changed the consuming endpoint as below;
{code}
template.send("log:logging?level=WARN=true", exchange);
{code}
then there is no error.
however, when i ran junit test case on mac(unix), i got the error as Axel
mentioned.
I am not sure if this is really a problem.
> camel-mail - Better handle null values when extracting attachments
> --
>
> Key: CAMEL-5980
> URL: https://issues.apache.org/jira/browse/CAMEL-5980
> Project: Camel
> Issue Type: Improvement
> Components: camel-mail
>Affects Versions: 2.9.0, 2.10.0
>Reporter: Claus Ibsen
>Assignee: onder sezgin
>Priority: Minor
> Fix For: Future
>
> Attachments: CAMEL-5980FirstPass.patch, debug_log.txt,
> EmailExceptionTest.java, EmailTest.java, Exception Mail.eml
>
>
> See nabble
> http://camel.465427.n5.nabble.com/MailComponent-s-claim-to-handle-special-mail-multipart-formats-and-attachments-tp5724859.html
> We should see if we can fix the Camel code to handle those null data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-8162) camel-spring-ws removes WSHandlerResult.
[ https://issues.apache.org/jira/browse/CAMEL-8162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-8162: --- Assignee: onder sezgin > camel-spring-ws removes WSHandlerResult. > > > Key: CAMEL-8162 > URL: https://issues.apache.org/jira/browse/CAMEL-8162 > Project: Camel > Issue Type: Improvement > Components: camel-spring-ws >Affects Versions: 2.14.0 >Reporter: Jimmy Selgen Nielsen >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > > When using camel-spring-ws with WS-Security and Wss4jSecurityInterceptor, > camel-spring-ws removes the list of WSHandlerResult when it creates the > exchange from the messageContext. > I'm trying to extract an X.509 certificate from the Soap header. > Wss4jSecurityInterceptor removes the Security header when it successfully > validates a message, and stores the information within the MessageContext in > a List. > I currently get around this by overriding Wss4jSecurityInterceptor so that it > no longer deletes the Security header, but the information is essentially > lost when Camel takes over, and it should be corrected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-5980) camel-mail - Better handle null values when extracting attachments
[ https://issues.apache.org/jira/browse/CAMEL-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838433#comment-15838433 ] onder sezgin edited comment on CAMEL-5980 at 1/26/17 5:16 AM: -- tried on mac os once again (being suspicious about the platform) and verify what i saw on windows and mac(yesterday) was correct. It was incorrect. Today i have tried both macos and windows. they all seem ok. i don't think this is reproducible unless somebody else also can try and see the same error as Axel did. Unless nobody can reproduce, i propose the issue got resolved. and please reopen if you can reproduce again. thanks. was (Author: onders): tried on mac os once again (being suspicious about the platform) and verify what i saw on windows and mac(yesterday) was correct. It was in correct. Today i have tried both macos and windows. they all seem ok. i don't think this is reproducible unless somebody else also can try and see the same error as Axel did. Unless nobody can reproduce, i propose the issue got resolved. and please reopen if you can reproduce again. thanks. > camel-mail - Better handle null values when extracting attachments > -- > > Key: CAMEL-5980 > URL: https://issues.apache.org/jira/browse/CAMEL-5980 > Project: Camel > Issue Type: Improvement > Components: camel-mail >Affects Versions: 2.9.0, 2.10.0 >Reporter: Claus Ibsen >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > Attachments: CAMEL-5980FirstPass.patch, debug_log.txt, > EmailExceptionTest.java, EmailTest.java, Exception Mail.eml > > > See nabble > http://camel.465427.n5.nabble.com/MailComponent-s-claim-to-handle-special-mail-multipart-formats-and-attachments-tp5724859.html > We should see if we can fix the Camel code to handle those null data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-5980) camel-mail - Better handle null values when extracting attachments
[ https://issues.apache.org/jira/browse/CAMEL-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838434#comment-15838434 ] onder sezgin commented on CAMEL-5980: - tried on mac os once again (being suspicious about the platform) and verify what i saw on windows and mac(yesterday) was correct. It was in correct. Today i have tried both macos and windows. they all seem ok. i don't think this is reproducible unless somebody else also can try and see the same error as Axel did. Unless nobody can reproduce, i propose the issue got resolved. and please reopen if you can reproduce again. thanks. > camel-mail - Better handle null values when extracting attachments > -- > > Key: CAMEL-5980 > URL: https://issues.apache.org/jira/browse/CAMEL-5980 > Project: Camel > Issue Type: Improvement > Components: camel-mail >Affects Versions: 2.9.0, 2.10.0 >Reporter: Claus Ibsen >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > Attachments: CAMEL-5980FirstPass.patch, debug_log.txt, > EmailExceptionTest.java, EmailTest.java, Exception Mail.eml > > > See nabble > http://camel.465427.n5.nabble.com/MailComponent-s-claim-to-handle-special-mail-multipart-formats-and-attachments-tp5724859.html > We should see if we can fix the Camel code to handle those null data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (CAMEL-5980) camel-mail - Better handle null values when extracting attachments
[ https://issues.apache.org/jira/browse/CAMEL-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin updated CAMEL-5980: Comment: was deleted (was: tried on mac os once again (being suspicious about the platform) and verify what i saw on windows and mac(yesterday) was correct. It was in correct. Today i have tried both macos and windows. they all seem ok. i don't think this is reproducible unless somebody else also can try and see the same error as Axel did. Unless nobody can reproduce, i propose the issue got resolved. and please reopen if you can reproduce again. thanks.) > camel-mail - Better handle null values when extracting attachments > -- > > Key: CAMEL-5980 > URL: https://issues.apache.org/jira/browse/CAMEL-5980 > Project: Camel > Issue Type: Improvement > Components: camel-mail >Affects Versions: 2.9.0, 2.10.0 >Reporter: Claus Ibsen >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > Attachments: CAMEL-5980FirstPass.patch, debug_log.txt, > EmailExceptionTest.java, EmailTest.java, Exception Mail.eml > > > See nabble > http://camel.465427.n5.nabble.com/MailComponent-s-claim-to-handle-special-mail-multipart-formats-and-attachments-tp5724859.html > We should see if we can fix the Camel code to handle those null data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-5980) camel-mail - Better handle null values when extracting attachments
[ https://issues.apache.org/jira/browse/CAMEL-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838433#comment-15838433 ] onder sezgin commented on CAMEL-5980: - tried on mac os once again (being suspicious about the platform) and verify what i saw on windows and mac(yesterday) was correct. It was in correct. Today i have tried both macos and windows. they all seem ok. i don't think this is reproducible unless somebody else also can try and see the same error as Axel did. Unless nobody can reproduce, i propose the issue got resolved. and please reopen if you can reproduce again. thanks. > camel-mail - Better handle null values when extracting attachments > -- > > Key: CAMEL-5980 > URL: https://issues.apache.org/jira/browse/CAMEL-5980 > Project: Camel > Issue Type: Improvement > Components: camel-mail >Affects Versions: 2.9.0, 2.10.0 >Reporter: Claus Ibsen >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > Attachments: CAMEL-5980FirstPass.patch, debug_log.txt, > EmailExceptionTest.java, EmailTest.java, Exception Mail.eml > > > See nabble > http://camel.465427.n5.nabble.com/MailComponent-s-claim-to-handle-special-mail-multipart-formats-and-attachments-tp5724859.html > We should see if we can fix the Camel code to handle those null data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-5980) camel-mail - Better handle null values when extracting attachments
[ https://issues.apache.org/jira/browse/CAMEL-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin resolved CAMEL-5980. - Resolution: Invalid > camel-mail - Better handle null values when extracting attachments > -- > > Key: CAMEL-5980 > URL: https://issues.apache.org/jira/browse/CAMEL-5980 > Project: Camel > Issue Type: Improvement > Components: camel-mail >Affects Versions: 2.9.0, 2.10.0 >Reporter: Claus Ibsen >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > Attachments: CAMEL-5980FirstPass.patch, debug_log.txt, > EmailExceptionTest.java, EmailTest.java, Exception Mail.eml > > > See nabble > http://camel.465427.n5.nabble.com/MailComponent-s-claim-to-handle-special-mail-multipart-formats-and-attachments-tp5724859.html > We should see if we can fix the Camel code to handle those null data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8162) camel-spring-ws removes WSHandlerResult.
[ https://issues.apache.org/jira/browse/CAMEL-8162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15875795#comment-15875795 ] onder sezgin commented on CAMEL-8162: - set to resolved as UT provided. should be considered as invalid ticket. > camel-spring-ws removes WSHandlerResult. > > > Key: CAMEL-8162 > URL: https://issues.apache.org/jira/browse/CAMEL-8162 > Project: Camel > Issue Type: Improvement > Components: camel-spring-ws >Affects Versions: 2.14.0 >Reporter: Jimmy Selgen Nielsen >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > > When using camel-spring-ws with WS-Security and Wss4jSecurityInterceptor, > camel-spring-ws removes the list of WSHandlerResult when it creates the > exchange from the messageContext. > I'm trying to extract an X.509 certificate from the Soap header. > Wss4jSecurityInterceptor removes the Security header when it successfully > validates a message, and stores the information within the MessageContext in > a List. > I currently get around this by overriding Wss4jSecurityInterceptor so that it > no longer deletes the Security header, but the information is essentially > lost when Camel takes over, and it should be corrected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (CAMEL-8162) camel-spring-ws removes WSHandlerResult.
[ https://issues.apache.org/jira/browse/CAMEL-8162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin resolved CAMEL-8162. - Resolution: Resolved > camel-spring-ws removes WSHandlerResult. > > > Key: CAMEL-8162 > URL: https://issues.apache.org/jira/browse/CAMEL-8162 > Project: Camel > Issue Type: Improvement > Components: camel-spring-ws >Affects Versions: 2.14.0 >Reporter: Jimmy Selgen Nielsen >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > > When using camel-spring-ws with WS-Security and Wss4jSecurityInterceptor, > camel-spring-ws removes the list of WSHandlerResult when it creates the > exchange from the messageContext. > I'm trying to extract an X.509 certificate from the Soap header. > Wss4jSecurityInterceptor removes the Security header when it successfully > validates a message, and stores the information within the MessageContext in > a List. > I currently get around this by overriding Wss4jSecurityInterceptor so that it > no longer deletes the Security header, but the information is essentially > lost when Camel takes over, and it should be corrected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-9552) Cannot consume and produce to beanstalk component in the same route
[
https://issues.apache.org/jira/browse/CAMEL-9552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin reassigned CAMEL-9552:
---
Assignee: onder sezgin
> Cannot consume and produce to beanstalk component in the same route
> ---
>
> Key: CAMEL-9552
> URL: https://issues.apache.org/jira/browse/CAMEL-9552
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.15.0, 2.16.0
>Reporter: J Smith
>Assignee: onder sezgin
>
> It appears that when creating a route that consumes from one beanstalk tube
> and produces to another, the exchange headers from the consumer somehow get
> mixed in with the producer and cause errors.
> Example route:
> .from("beanstalk://localhost?tube=A")
> .setBody("hello")
> .to("beanstalk://localhost?tube=B")
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (CAMEL-10888) camel-spring-ws - Has problem with returning proper response due invalid IN vs OUT code
[ https://issues.apache.org/jira/browse/CAMEL-10888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-10888: Assignee: onder sezgin > camel-spring-ws - Has problem with returning proper response due invalid IN > vs OUT code > --- > > Key: CAMEL-10888 > URL: https://issues.apache.org/jira/browse/CAMEL-10888 > Project: Camel > Issue Type: Bug > Components: camel-spring-ws >Reporter: Claus Ibsen >Assignee: onder sezgin > Fix For: 2.18.3, 2.19.0 > > > See SO > http://stackoverflow.com/questions/42385355/apache-camel-spring-webservices-springwebserviceconsumer-does-not-read-answer-fr -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (CAMEL-10888) camel-spring-ws - Has problem with returning proper response due invalid IN vs OUT code
[ https://issues.apache.org/jira/browse/CAMEL-10888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-10888 started by onder sezgin. > camel-spring-ws - Has problem with returning proper response due invalid IN > vs OUT code > --- > > Key: CAMEL-10888 > URL: https://issues.apache.org/jira/browse/CAMEL-10888 > Project: Camel > Issue Type: Bug > Components: camel-spring-ws >Reporter: Claus Ibsen >Assignee: onder sezgin > Fix For: 2.18.3, 2.19.0 > > > See SO > http://stackoverflow.com/questions/42385355/apache-camel-spring-webservices-springwebserviceconsumer-does-not-read-answer-fr -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (CAMEL-10859) camel-jasypt - Update docs about JAR dependency to run
[ https://issues.apache.org/jira/browse/CAMEL-10859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-10859 started by onder sezgin. > camel-jasypt - Update docs about JAR dependency to run > -- > > Key: CAMEL-10859 > URL: https://issues.apache.org/jira/browse/CAMEL-10859 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Claus Ibsen >Assignee: onder sezgin >Priority: Minor > Fix For: 2.19.0 > > > See nabble > http://camel.465427.n5.nabble.com/Error-encrypting-value-using-camel-jasypt-2-18-1-jar-td5794000.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-2331) WebDAV component
[ https://issues.apache.org/jira/browse/CAMEL-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876522#comment-15876522 ] onder sezgin commented on CAMEL-2331: - webdav seems to be very inactive. and somehow the component expected to be release did not come out. i propose closing the ticket > WebDAV component > > > Key: CAMEL-2331 > URL: https://issues.apache.org/jira/browse/CAMEL-2331 > Project: Camel > Issue Type: New Feature >Reporter: S. Ali Tokmen > Fix For: Future > > > In the past, there had been plans for the camel-ftp to support WebDAV. This > is not the case now. > It would be great for Camel to have a WebDAV component, that could be as easy > to use as a File or FTP component, as a consumer or a producer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-2331) WebDAV component
[ https://issues.apache.org/jira/browse/CAMEL-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876547#comment-15876547 ] onder sezgin commented on CAMEL-2331: - at least i can see the inactivity on http://www.webdav.org/ as last edited ''Last modified: Apr 21 2010" and there seems to an experimental project on https://github.com/Giwi/camel-dav which is inactive as well and if anyone interested may try to make the component mature and do PR again maybe in future. at least for now, i believe we can close the ticket > WebDAV component > > > Key: CAMEL-2331 > URL: https://issues.apache.org/jira/browse/CAMEL-2331 > Project: Camel > Issue Type: New Feature >Reporter: S. Ali Tokmen > Fix For: Future > > > In the past, there had been plans for the camel-ftp to support WebDAV. This > is not the case now. > It would be great for Camel to have a WebDAV component, that could be as easy > to use as a File or FTP component, as a consumer or a producer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-10859) camel-jasypt - Update docs about JAR dependency to run
[ https://issues.apache.org/jira/browse/CAMEL-10859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-10859: Assignee: onder sezgin > camel-jasypt - Update docs about JAR dependency to run > -- > > Key: CAMEL-10859 > URL: https://issues.apache.org/jira/browse/CAMEL-10859 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Claus Ibsen >Assignee: onder sezgin >Priority: Minor > Fix For: 2.19.0 > > > See nabble > http://camel.465427.n5.nabble.com/Error-encrypting-value-using-camel-jasypt-2-18-1-jar-td5794000.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-8162) camel-spring-ws removes WSHandlerResult.
[ https://issues.apache.org/jira/browse/CAMEL-8162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin updated CAMEL-8162: Estimated Complexity: Moderate (was: Novice) > camel-spring-ws removes WSHandlerResult. > > > Key: CAMEL-8162 > URL: https://issues.apache.org/jira/browse/CAMEL-8162 > Project: Camel > Issue Type: Improvement > Components: camel-spring-ws >Affects Versions: 2.14.0 >Reporter: Jimmy Selgen Nielsen >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > > When using camel-spring-ws with WS-Security and Wss4jSecurityInterceptor, > camel-spring-ws removes the list of WSHandlerResult when it creates the > exchange from the messageContext. > I'm trying to extract an X.509 certificate from the Soap header. > Wss4jSecurityInterceptor removes the Security header when it successfully > validates a message, and stores the information within the MessageContext in > a List. > I currently get around this by overriding Wss4jSecurityInterceptor so that it > no longer deletes the Security header, but the information is essentially > lost when Camel takes over, and it should be corrected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (CAMEL-8162) camel-spring-ws removes WSHandlerResult.
[ https://issues.apache.org/jira/browse/CAMEL-8162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-8162 started by onder sezgin. --- > camel-spring-ws removes WSHandlerResult. > > > Key: CAMEL-8162 > URL: https://issues.apache.org/jira/browse/CAMEL-8162 > Project: Camel > Issue Type: Improvement > Components: camel-spring-ws >Affects Versions: 2.14.0 >Reporter: Jimmy Selgen Nielsen >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > > When using camel-spring-ws with WS-Security and Wss4jSecurityInterceptor, > camel-spring-ws removes the list of WSHandlerResult when it creates the > exchange from the messageContext. > I'm trying to extract an X.509 certificate from the Soap header. > Wss4jSecurityInterceptor removes the Security header when it successfully > validates a message, and stores the information within the MessageContext in > a List. > I currently get around this by overriding Wss4jSecurityInterceptor so that it > no longer deletes the Security header, but the information is essentially > lost when Camel takes over, and it should be corrected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-8162) camel-spring-ws removes WSHandlerResult.
[ https://issues.apache.org/jira/browse/CAMEL-8162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867889#comment-15867889 ] onder sezgin commented on CAMEL-8162: - this is not camel-spring-ws component issue. This is how you should implement using wss4j via webServiceTemplate(org.springframework.ws.client.core.WebServiceTemplate) normally wss4j removes security headers when returning to client unless removeSecurityHeader is specified as false in the interceptor. this should not be issue. i am going to set this issue as invalid after providing some unit tests. > camel-spring-ws removes WSHandlerResult. > > > Key: CAMEL-8162 > URL: https://issues.apache.org/jira/browse/CAMEL-8162 > Project: Camel > Issue Type: Improvement > Components: camel-spring-ws >Affects Versions: 2.14.0 >Reporter: Jimmy Selgen Nielsen >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > > When using camel-spring-ws with WS-Security and Wss4jSecurityInterceptor, > camel-spring-ws removes the list of WSHandlerResult when it creates the > exchange from the messageContext. > I'm trying to extract an X.509 certificate from the Soap header. > Wss4jSecurityInterceptor removes the Security header when it successfully > validates a message, and stores the information within the MessageContext in > a List. > I currently get around this by overriding Wss4jSecurityInterceptor so that it > no longer deletes the Security header, but the information is essentially > lost when Camel takes over, and it should be corrected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-9210) Make credentials optional in AWS component. Use instance profile if not supplied.
[ https://issues.apache.org/jira/browse/CAMEL-9210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-9210: --- Assignee: onder sezgin > Make credentials optional in AWS component. Use instance profile if not > supplied. > - > > Key: CAMEL-9210 > URL: https://issues.apache.org/jira/browse/CAMEL-9210 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Affects Versions: 2.16.0 >Reporter: Ben Parry >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > Original Estimate: 4h > Remaining Estimate: 4h > > AWS supports instance profiles so users don't need to manage credentials on > individual instances. > Please update the AWS connector so that the access key and secret are > optional, and if not given try to use those provided by an instance profile > attached to the instance if one exists. Most AWS SDKs support this, so it > should just be a matter of updating the AWS SDK and making those two > parameters optional. > As a bonus, it'd be great for development if it also looked in environment > variables for the token and secret as well. That way users of the AWS > connector could choose not to pass the token & secret, but if they exported > them into their environment they would be picked up. This would allow local > development on a non-EC2 instance (i.e. an instance without an instance > profile attached). > So, the order of resolution would be: > 1. If key & token are provided to the AWS connector, use them (current > behaviour). > 2. If not, try to pull out AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY from > environment variables, and use those. If not present, expect the AWS SDK to > look into an instance profile associated with the instance for credentials. > See https://github.com/aws/aws-cli for an example implementation with > python/boto. The suggestion above mirrors the approach they take. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8418) Add documentation to camel-atmos component
[ https://issues.apache.org/jira/browse/CAMEL-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427748#comment-15427748 ] onder sezgin commented on CAMEL-8418: - for this issue, it is expected to update atmos-component.adoc, not the wiki documentation. Am i right? > Add documentation to camel-atmos component > -- > > Key: CAMEL-8418 > URL: https://issues.apache.org/jira/browse/CAMEL-8418 > Project: Camel > Issue Type: Task > Components: camel-atmos, documentation >Affects Versions: 2.15.0 >Reporter: Claus Ibsen > Fix For: Future > > > We need to add documentation to the wiki -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8418) Add documentation to camel-atmos component
[ https://issues.apache.org/jira/browse/CAMEL-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429599#comment-15429599 ] onder sezgin commented on CAMEL-8418: - I am working on it. How can i get myself as assignee? Thanks > Add documentation to camel-atmos component > -- > > Key: CAMEL-8418 > URL: https://issues.apache.org/jira/browse/CAMEL-8418 > Project: Camel > Issue Type: Task > Components: camel-atmos, documentation >Affects Versions: 2.15.0 >Reporter: Claus Ibsen > Fix For: Future > > > We need to add documentation to the wiki -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10185) camel-ftp - fastExistsCheck issue
[ https://issues.apache.org/jira/browse/CAMEL-10185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407281#comment-15407281 ] onder sezgin commented on CAMEL-10185: -- not sure if the issue is on. FtpChangedReadLockFastExistCheckTest passes. > camel-ftp - fastExistsCheck issue > - > > Key: CAMEL-10185 > URL: https://issues.apache.org/jira/browse/CAMEL-10185 > Project: Camel > Issue Type: Bug > Components: camel-ftp >Affects Versions: 2.17.2 >Reporter: Claus Ibsen > Fix For: 2.16.4, 2.17.3, 2.18.0 > > > See SO > https://github.com/apache/camel/commit/91c086b7af22b6cfaf2f66b2c872b752dc10a19c#commitcomment-18363186 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-9991) lots of broken links on camel.apache.org
[ https://issues.apache.org/jira/browse/CAMEL-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15501490#comment-15501490 ] onder sezgin commented on CAMEL-9991: - One more thing, As with the original config, i ran and got the output as below. If that means adocs are OK, maybe this issue may be closed. otherwise, as i previously mentioned if there is a guide how i can run link checker for new wiki version (i mean adoc s), i can run the link checker and try to fix the links in adoc s if neccessary. regards > lots of broken links on camel.apache.org > > > Key: CAMEL-9991 > URL: https://issues.apache.org/jira/browse/CAMEL-9991 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Bennet Schulz >Priority: Trivial > > Hi guys, > I recently found some broken links and used a link checker after that. In > total there are 86 broken links. > here is a listing (sorry for the format): > http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.asc > > http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.md5 > > http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.sha1 > > http://camel.apache.org/confluence/display/~gzurowski > http://camel.apache.org/confluence/display/~muellerc > http://servicemix.apache.org/uris.htmlServiceMix URI Guide > http://servicemix.apache.org/maven-jbi-plugin.htmlServiceMix Maven JBI > Plugins > http://servicemix.apache.org/3-beginner-using-apache-camel-inside-servicemix.html > Using Camel with ServiceMix > http://servicemix.apache.org/order-file-processing.html Cookbook on > using Camel with ServiceMix > http://mina.apache.org/iofilter.html Mina IoFilters > http://mina.apache.org/tutorial-on-protocolcodecfilter.html Mina > documentation > http://mina.apache.org/report/1.1/apidocs/org/apache/mina/transport/vmpipe/package-summary.html >MINA VM-Pipe API documentation > http://servicemix.apache.org/servicemix-camel.htmlServiceMix Camel module > http://people.apache.org/repo/m2-ibiblio-rsync-repository/ > http://people.apache.org/repo/m2-ibiblio-rsync-repository/ > http://activemq.apache.org/maven/5.5.0/activemq-camel/apidocs/org/apache/activemq/camel/component/ActiveMQComponent.html > activeMQComponent() method > http://camel.apache.org/$base/privacy-policy.html Privacy Policy > http://apache.org/hello_world_soap_http > http://apache.org/hello_world_soap_http > http://example.com/servicehttp://example.com/service > http://www.eu.apachecon.com ApacheCon Europe 2008 > https://svn.apache.org/repos/asf/cxf/trunk/api/src/main/java/org/apache/cxf/endpoint/Client.java > cxf client API > http://apache.org/cxf/Apache CXF > http://newhosthttp://newhost > http://hadoop.apache.org/hdfs/HDFS > http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/ > Hibernate Validator > http://metrics.codahale.com/ Metrics > http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html bayeux protocol > http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/eventbus/package-summary.html > Google Guava EventBus > http://servicemix.apache.org/SMX4NMR/index.html ServiceMix 4.x > https://rhiot.gitbooks.io/rhiotdocumentation/content/backend/camel_components/camel_openimaj_component.html >OpenIMAJ > http://svn.apache.org/repos/asf/camel/trunk/components/camel-test-cdi/src/test/java/org/apache/camel/test/cdi/FilterTest.java > example > http://gliesian.com/camel/ApacheCamelComponents.pdf Free PDF > https://rhiot.gitbooks.io/rhiotdocumentation/content/gateway/camel_components/camel_kura_cloud_component.html > kura-cloud > http://gauthcloud.appspot.com/http://gauthcloud.appspot.com/ > http://camelcloud.appspot.com/http://camelcloud.appspot.com/ > http://http//www.enterpriseintegrationpatterns.com/ComposedMessagingExample.html > EIP composed messaging sample > http://scalate.fusesource.org/Scalate > http://www.smooks.org/mediawiki/index.php?title=V1.5:Smooks_v1.5_User_Guide > Camel integration out of the box > http://scalate.fusesource.org/camel.html Scalate > http://www.db4o.com/ db4o > http://fabric8.io/gitbook/camelEndpointAmq.html AMQ > http://servicemix.apache.org/camel-example.html example > https://open-esb.dev.java.net/Open ESB > http://www.subrecord.org/ SubRecord > http://www.opensplice.com/section-item.asp?id=964 PrismTech > http://doc.akkasource.org/actors actors > http://doc.akkasource.org/camel akka-camel > http://touk.pl/toukeu/rw/pages/index.en.doTouK > http://forge.jboss.org/ JBoss Forge > http://forge.jboss.org/addon/io.fabric8.forge:camel Camel addon >
[jira] [Comment Edited] (CAMEL-9991) lots of broken links on camel.apache.org
[
https://issues.apache.org/jira/browse/CAMEL-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15501490#comment-15501490
]
onder sezgin edited comment on CAMEL-9991 at 9/18/16 7:11 PM:
--
One more thing,
As with the original config, i ran and got the output as below. If that means
adocs are OK, maybe this issue may be closed.
{code}
$ grunt --gruntfile=Gruntfile.js
Running "http-server:dev" (http-server) task
Server running on http://0.0.0.0:8282/
Hit CTRL-C to stop the server
Running "linkChecker:dev" (linkChecker) task
>> Checking for broken links at: localhost:8282
>> No broken links found at: localhost:8282
Done, without errors.
{code}
otherwise, as i previously mentioned if there is a guide how i can run link
checker for new wiki version (i mean adoc s), i can run the link checker and
try to fix the links in adoc s if neccessary.
regards
was (Author: onders):
One more thing,
As with the original config, i ran and got the output as below. If that means
adocs are OK, maybe this issue may be closed.
otherwise, as i previously mentioned if there is a guide how i can run link
checker for new wiki version (i mean adoc s), i can run the link checker and
try to fix the links in adoc s if neccessary.
regards
> lots of broken links on camel.apache.org
>
>
> Key: CAMEL-9991
> URL: https://issues.apache.org/jira/browse/CAMEL-9991
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Bennet Schulz
>Priority: Trivial
>
> Hi guys,
> I recently found some broken links and used a link checker after that. In
> total there are 86 broken links.
> here is a listing (sorry for the format):
> http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.asc
>
> http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.md5
>
> http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.sha1
>
> http://camel.apache.org/confluence/display/~gzurowski
> http://camel.apache.org/confluence/display/~muellerc
> http://servicemix.apache.org/uris.htmlServiceMix URI Guide
> http://servicemix.apache.org/maven-jbi-plugin.htmlServiceMix Maven JBI
> Plugins
> http://servicemix.apache.org/3-beginner-using-apache-camel-inside-servicemix.html
> Using Camel with ServiceMix
> http://servicemix.apache.org/order-file-processing.html Cookbook on
> using Camel with ServiceMix
> http://mina.apache.org/iofilter.html Mina IoFilters
> http://mina.apache.org/tutorial-on-protocolcodecfilter.html Mina
> documentation
> http://mina.apache.org/report/1.1/apidocs/org/apache/mina/transport/vmpipe/package-summary.html
>MINA VM-Pipe API documentation
> http://servicemix.apache.org/servicemix-camel.htmlServiceMix Camel module
> http://people.apache.org/repo/m2-ibiblio-rsync-repository/
> http://people.apache.org/repo/m2-ibiblio-rsync-repository/
> http://activemq.apache.org/maven/5.5.0/activemq-camel/apidocs/org/apache/activemq/camel/component/ActiveMQComponent.html
> activeMQComponent() method
> http://camel.apache.org/$base/privacy-policy.html Privacy Policy
> http://apache.org/hello_world_soap_http
> http://apache.org/hello_world_soap_http
> http://example.com/servicehttp://example.com/service
> http://www.eu.apachecon.com ApacheCon Europe 2008
> https://svn.apache.org/repos/asf/cxf/trunk/api/src/main/java/org/apache/cxf/endpoint/Client.java
> cxf client API
> http://apache.org/cxf/Apache CXF
> http://newhosthttp://newhost
> http://hadoop.apache.org/hdfs/HDFS
> http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/
> Hibernate Validator
> http://metrics.codahale.com/ Metrics
> http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html bayeux protocol
> http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/eventbus/package-summary.html
> Google Guava EventBus
> http://servicemix.apache.org/SMX4NMR/index.html ServiceMix 4.x
> https://rhiot.gitbooks.io/rhiotdocumentation/content/backend/camel_components/camel_openimaj_component.html
>OpenIMAJ
> http://svn.apache.org/repos/asf/camel/trunk/components/camel-test-cdi/src/test/java/org/apache/camel/test/cdi/FilterTest.java
> example
> http://gliesian.com/camel/ApacheCamelComponents.pdf Free PDF
> https://rhiot.gitbooks.io/rhiotdocumentation/content/gateway/camel_components/camel_kura_cloud_component.html
> kura-cloud
> http://gauthcloud.appspot.com/http://gauthcloud.appspot.com/
> http://camelcloud.appspot.com/http://camelcloud.appspot.com/
> http://http//www.enterpriseintegrationpatterns.com/ComposedMessagingExample.html
> EIP composed messaging sample
> http://scalate.fusesource.org/Scalate
[jira] [Commented] (CAMEL-9991) lots of broken links on camel.apache.org
[
https://issues.apache.org/jira/browse/CAMEL-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15501478#comment-15501478
]
onder sezgin commented on CAMEL-9991:
-
Hi Claus,
I've tried to run link checker agaisnt camel.apache.org port=80. There are lots
of 404s and other warning/error messages on the console i receive as below.
So i guess you suggest us to run link checker on localhost against
camel-website project. How could we run link checker for camel-website?
If there is a guide, i can give it a go? if not(i'll try anyway :) ), let me
see if i can get around.
Cheers
{code}
$ grunt --gruntfile=Gruntfile.js
Running "http-server:dev" (http-server) task
Server running on http://0.0.0.0:8282/
Hit CTRL-C to stop the server
Running "linkChecker:dev" (linkChecker) task
>> Checking for broken links at: camel.apache.org:80
>> Resource not found linked from http://camel.apache.org/ to
>> http://camel.apache.org/confluence/display/~muellerc%20
>> Status code: 404
>> Resource not found linked from http://camel.apache.org/ to
>> http://camel.apache.org/confluence/display/~davsclaus%20
>> Status code: 404
>> Resource not found linked from http://camel.apache.org/ to
>> http://camel.apache.org/confluence/display/~gzurowski%20
{code}
> lots of broken links on camel.apache.org
>
>
> Key: CAMEL-9991
> URL: https://issues.apache.org/jira/browse/CAMEL-9991
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Bennet Schulz
>Priority: Trivial
>
> Hi guys,
> I recently found some broken links and used a link checker after that. In
> total there are 86 broken links.
> here is a listing (sorry for the format):
> http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.asc
>
> http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.md5
>
> http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.sha1
>
> http://camel.apache.org/confluence/display/~gzurowski
> http://camel.apache.org/confluence/display/~muellerc
> http://servicemix.apache.org/uris.htmlServiceMix URI Guide
> http://servicemix.apache.org/maven-jbi-plugin.htmlServiceMix Maven JBI
> Plugins
> http://servicemix.apache.org/3-beginner-using-apache-camel-inside-servicemix.html
> Using Camel with ServiceMix
> http://servicemix.apache.org/order-file-processing.html Cookbook on
> using Camel with ServiceMix
> http://mina.apache.org/iofilter.html Mina IoFilters
> http://mina.apache.org/tutorial-on-protocolcodecfilter.html Mina
> documentation
> http://mina.apache.org/report/1.1/apidocs/org/apache/mina/transport/vmpipe/package-summary.html
>MINA VM-Pipe API documentation
> http://servicemix.apache.org/servicemix-camel.htmlServiceMix Camel module
> http://people.apache.org/repo/m2-ibiblio-rsync-repository/
> http://people.apache.org/repo/m2-ibiblio-rsync-repository/
> http://activemq.apache.org/maven/5.5.0/activemq-camel/apidocs/org/apache/activemq/camel/component/ActiveMQComponent.html
> activeMQComponent() method
> http://camel.apache.org/$base/privacy-policy.html Privacy Policy
> http://apache.org/hello_world_soap_http
> http://apache.org/hello_world_soap_http
> http://example.com/servicehttp://example.com/service
> http://www.eu.apachecon.com ApacheCon Europe 2008
> https://svn.apache.org/repos/asf/cxf/trunk/api/src/main/java/org/apache/cxf/endpoint/Client.java
> cxf client API
> http://apache.org/cxf/Apache CXF
> http://newhosthttp://newhost
> http://hadoop.apache.org/hdfs/HDFS
> http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/
> Hibernate Validator
> http://metrics.codahale.com/ Metrics
> http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html bayeux protocol
> http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/eventbus/package-summary.html
> Google Guava EventBus
> http://servicemix.apache.org/SMX4NMR/index.html ServiceMix 4.x
> https://rhiot.gitbooks.io/rhiotdocumentation/content/backend/camel_components/camel_openimaj_component.html
>OpenIMAJ
> http://svn.apache.org/repos/asf/camel/trunk/components/camel-test-cdi/src/test/java/org/apache/camel/test/cdi/FilterTest.java
> example
> http://gliesian.com/camel/ApacheCamelComponents.pdf Free PDF
> https://rhiot.gitbooks.io/rhiotdocumentation/content/gateway/camel_components/camel_kura_cloud_component.html
> kura-cloud
> http://gauthcloud.appspot.com/http://gauthcloud.appspot.com/
> http://camelcloud.appspot.com/http://camelcloud.appspot.com/
> http://http//www.enterpriseintegrationpatterns.com/ComposedMessagingExample.html
> EIP composed messaging sample
> http://scalate.fusesource.org/Scalate
>
[jira] [Commented] (CAMEL-8947) LevelDBAggregatorRepository redelivers incorrectly
[
https://issues.apache.org/jira/browse/CAMEL-8947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15644107#comment-15644107
]
onder sezgin commented on CAMEL-8947:
-
Any relation to the issue as below:
http://camel.465427.n5.nabble.com/Aggregator-LevelDB-or-HawtDB-for-persistency-incorrect-behavior-td5765524.html#a5789810
> LevelDBAggregatorRepository redelivers incorrectly
> --
>
> Key: CAMEL-8947
> URL: https://issues.apache.org/jira/browse/CAMEL-8947
> Project: Camel
> Issue Type: Bug
> Components: camel-leveldb
>Affects Versions: 2.14.1
>Reporter: Ben O'Day
>Assignee: Ben O'Day
> Attachments: LevelDBAggregatorUseLatestTest.patch
>
>
> I'm using an the aggregator with the LevelDBAggregationRepository and seeing
> an incorrect redelivery of a message when using the
> UseLatestAggregationStrategy...
> this very basic route (see attached)...
> from("direct:start")
> .aggregate(constant(true), new
> UseLatestAggregationStrategy())
> .completionSize(2)
>
> .aggregationRepository(repo)
> .to("mock:mock");
> shows the following behavior...
> WARN LevelDBAggregationRepository - Unable to confirm exchangeId
> [ID-localhost-63819-1436483565832-0-6 from repository repo1: Not Found]
> DEBUG LevelDBAggregationRepository - Scanned and found 1 exchange(s) to
> recover (note some of them may already be in progress).
> DEBUG LevelDBAggregationRepository - Recovering exchangeId
> [ID-localhost-63819-1436483565832-0-3] -> Exchange[Message: test1]
> resulting in a duplicate message being processed through the aggregator
> route...
> if the default in-memory repo is used, the test behaves as expected...no
> unnecessary redelivery, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8947) LevelDBAggregatorRepository redelivers incorrectly
[
https://issues.apache.org/jira/browse/CAMEL-8947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15644104#comment-15644104
]
onder sezgin commented on CAMEL-8947:
-
Any update?
> LevelDBAggregatorRepository redelivers incorrectly
> --
>
> Key: CAMEL-8947
> URL: https://issues.apache.org/jira/browse/CAMEL-8947
> Project: Camel
> Issue Type: Bug
> Components: camel-leveldb
>Affects Versions: 2.14.1
>Reporter: Ben O'Day
>Assignee: Ben O'Day
> Attachments: LevelDBAggregatorUseLatestTest.patch
>
>
> I'm using an the aggregator with the LevelDBAggregationRepository and seeing
> an incorrect redelivery of a message when using the
> UseLatestAggregationStrategy...
> this very basic route (see attached)...
> from("direct:start")
> .aggregate(constant(true), new
> UseLatestAggregationStrategy())
> .completionSize(2)
>
> .aggregationRepository(repo)
> .to("mock:mock");
> shows the following behavior...
> WARN LevelDBAggregationRepository - Unable to confirm exchangeId
> [ID-localhost-63819-1436483565832-0-6 from repository repo1: Not Found]
> DEBUG LevelDBAggregationRepository - Scanned and found 1 exchange(s) to
> recover (note some of them may already be in progress).
> DEBUG LevelDBAggregationRepository - Recovering exchangeId
> [ID-localhost-63819-1436483565832-0-3] -> Exchange[Message: test1]
> resulting in a duplicate message being processed through the aggregator
> route...
> if the default in-memory repo is used, the test behaves as expected...no
> unnecessary redelivery, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-9991) lots of broken links on camel.apache.org
[ https://issues.apache.org/jira/browse/CAMEL-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15615251#comment-15615251 ] onder sezgin commented on CAMEL-9991: - i propose to close the issue as adocs seems to be ok. and as adocs will be the new base we dont need to worry about the current broken links in the website. regards > lots of broken links on camel.apache.org > > > Key: CAMEL-9991 > URL: https://issues.apache.org/jira/browse/CAMEL-9991 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Bennet Schulz >Priority: Trivial > > Hi guys, > I recently found some broken links and used a link checker after that. In > total there are 86 broken links. > here is a listing (sorry for the format): > http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.asc > > http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.md5 > > http://www.apache.org/dist/camel/apache-camel/2.11.3/apache-camel-2.11.3.zip.sha1 > > http://camel.apache.org/confluence/display/~gzurowski > http://camel.apache.org/confluence/display/~muellerc > http://servicemix.apache.org/uris.htmlServiceMix URI Guide > http://servicemix.apache.org/maven-jbi-plugin.htmlServiceMix Maven JBI > Plugins > http://servicemix.apache.org/3-beginner-using-apache-camel-inside-servicemix.html > Using Camel with ServiceMix > http://servicemix.apache.org/order-file-processing.html Cookbook on > using Camel with ServiceMix > http://mina.apache.org/iofilter.html Mina IoFilters > http://mina.apache.org/tutorial-on-protocolcodecfilter.html Mina > documentation > http://mina.apache.org/report/1.1/apidocs/org/apache/mina/transport/vmpipe/package-summary.html >MINA VM-Pipe API documentation > http://servicemix.apache.org/servicemix-camel.htmlServiceMix Camel module > http://people.apache.org/repo/m2-ibiblio-rsync-repository/ > http://people.apache.org/repo/m2-ibiblio-rsync-repository/ > http://activemq.apache.org/maven/5.5.0/activemq-camel/apidocs/org/apache/activemq/camel/component/ActiveMQComponent.html > activeMQComponent() method > http://camel.apache.org/$base/privacy-policy.html Privacy Policy > http://apache.org/hello_world_soap_http > http://apache.org/hello_world_soap_http > http://example.com/servicehttp://example.com/service > http://www.eu.apachecon.com ApacheCon Europe 2008 > https://svn.apache.org/repos/asf/cxf/trunk/api/src/main/java/org/apache/cxf/endpoint/Client.java > cxf client API > http://apache.org/cxf/Apache CXF > http://newhosthttp://newhost > http://hadoop.apache.org/hdfs/HDFS > http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single/ > Hibernate Validator > http://metrics.codahale.com/ Metrics > http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html bayeux protocol > http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/eventbus/package-summary.html > Google Guava EventBus > http://servicemix.apache.org/SMX4NMR/index.html ServiceMix 4.x > https://rhiot.gitbooks.io/rhiotdocumentation/content/backend/camel_components/camel_openimaj_component.html >OpenIMAJ > http://svn.apache.org/repos/asf/camel/trunk/components/camel-test-cdi/src/test/java/org/apache/camel/test/cdi/FilterTest.java > example > http://gliesian.com/camel/ApacheCamelComponents.pdf Free PDF > https://rhiot.gitbooks.io/rhiotdocumentation/content/gateway/camel_components/camel_kura_cloud_component.html > kura-cloud > http://gauthcloud.appspot.com/http://gauthcloud.appspot.com/ > http://camelcloud.appspot.com/http://camelcloud.appspot.com/ > http://http//www.enterpriseintegrationpatterns.com/ComposedMessagingExample.html > EIP composed messaging sample > http://scalate.fusesource.org/Scalate > http://www.smooks.org/mediawiki/index.php?title=V1.5:Smooks_v1.5_User_Guide > Camel integration out of the box > http://scalate.fusesource.org/camel.html Scalate > http://www.db4o.com/ db4o > http://fabric8.io/gitbook/camelEndpointAmq.html AMQ > http://servicemix.apache.org/camel-example.html example > https://open-esb.dev.java.net/Open ESB > http://www.subrecord.org/ SubRecord > http://www.opensplice.com/section-item.asp?id=964 PrismTech > http://doc.akkasource.org/actors actors > http://doc.akkasource.org/camel akka-camel > http://touk.pl/toukeu/rw/pages/index.en.doTouK > http://forge.jboss.org/ JBoss Forge > http://forge.jboss.org/addon/io.fabric8.forge:camel Camel addon > http://www.linkedin.com/in/gregorzurowski/Gregor Zurowski > http://www.systechnologies.com/ SYS Technologies > http://www.drkw.com/ Dresdner Kleinwort Wasserstein >
[jira] [Assigned] (CAMEL-10528) Contributing file for Apache Camel
[ https://issues.apache.org/jira/browse/CAMEL-10528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-10528: Assignee: onder sezgin > Contributing file for Apache Camel > -- > > Key: CAMEL-10528 > URL: https://issues.apache.org/jira/browse/CAMEL-10528 > Project: Camel > Issue Type: Task > Components: documentation >Reporter: Claus Ibsen >Assignee: onder sezgin > Fix For: 2.19.0 > > > See > http://camel.465427.n5.nabble.com/Contributing-file-in-Apache-Camel-td5790520.html > Contributions and help is much welcome -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-10459) camel-elsql - option batch is not implemented in producer
[
https://issues.apache.org/jira/browse/CAMEL-10459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin reassigned CAMEL-10459:
Assignee: onder sezgin
> camel-elsql - option batch is not implemented in producer
> -
>
> Key: CAMEL-10459
> URL: https://issues.apache.org/jira/browse/CAMEL-10459
> Project: Camel
> Issue Type: Improvement
> Components: camel-elsql
>Affects Versions: 2.18.0
>Reporter: Tomas Turek
>Assignee: onder sezgin
>Priority: Minor
> Fix For: Future
>
>
> Option {{batch}} which should enable support for SQL batch update statements
> is not working.
> Route:
> {code}
>
>
>
>
>
> {code}
> ElSql:
> {code}
> @NAME(insert)
> INSERT INTO projects (id, project, license)
> VALUES (:id, :project, :license)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (CAMEL-10086) Remove Pattern.compile usages
[
https://issues.apache.org/jira/browse/CAMEL-10086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin updated CAMEL-10086:
-
Comment: was deleted
(was: $ grep -iR 'Pattern.compile' * | grep -v 'private static final'
camel-core/src/main/java/org/apache/camel/builder/ExpressionBuilder.java:
final Pattern pattern = Pattern.compile(regexTokenizer);
camel-core/src/main/java/org/apache/camel/builder/ExpressionBuilder.java:
final Pattern pattern = Pattern.compile(regex);
camel-core/src/main/java/org/apache/camel/builder/ExpressionBuilder.java:
final Pattern pattern = Pattern.compile(regex);
camel-core/src/main/java/org/apache/camel/builder/PredicateBuilder.java:
return regex(expression, Pattern.compile(regex));
camel-core/src/main/java/org/apache/camel/component/file/GenericFileEndpoint.java:
this.includePattern = Pattern.compile(include,
Pattern.CASE_INSENSITIVE);
camel-core/src/main/java/org/apache/camel/component/file/GenericFileEndpoint.java:
this.excludePattern = Pattern.compile(exclude,
Pattern.CASE_INSENSITIVE);
camel-core/src/main/java/org/apache/camel/impl/DefaultHeaderFilterStrategy.java:
outFilterPattern = Pattern.compile(value);
camel-core/src/main/java/org/apache/camel/impl/DefaultHeaderFilterStrategy.java:
inFilterPattern = Pattern.compile(value);
camel-core/src/main/java/org/apache/camel/support/TokenXMLExpressionIterator.java:
Pattern.compile(MessageFormat.format(SCAN_BLOCK_TOKEN_REGEX_TEMPLATE,
camel-core/src/main/java/org/apache/camel/support/TokenXMLExpressionIterator.java:
Pattern.compile(MessageFormat.format(SCAN_PARENT_TOKEN_REGEX_TEMPLATE,
camel-core/src/main/java/org/apache/camel/support/TokenXMLPairExpressionIterator.java:
this.startTokenPattern = Pattern.compile(tokenSb.toString());
camel-core/src/main/java/org/apache/camel/support/TokenXMLPairExpressionIterator.java:
this.inheritNamespaceTokenPattern =
Pattern.compile(tokenSb.toString(), Pattern.MULTILINE | Pattern.DOTALL);
camel-core/src/main/java/org/apache/camel/support/XMLTokenExpressionIterator.java:
lcpattern = Pattern.compile(sb.toString());
camel-core/src/main/java/org/apache/camel/util/component/ApiMethodHelper.java:
aliasPatterns.put(Pattern.compile(alias.getKey()), alias.getValue());
camel-core/src/main/java/org/apache/camel/util/component/ApiMethodParser.java:
public static final Pattern ARGS_PATTERN =
Pattern.compile("\\s*([^<\\s]+)\\s*(<[^>]+>)?\\s+([^\\s,]+)\\s*,?");
camel-core/src/main/java/org/apache/camel/util/component/ArgumentSubstitutionParser.java:
nameReplacement.typePattern =
Pattern.compile(substitution.argType);
camel-core/src/main/java/org/apache/camel/util/component/ArgumentSubstitutionParser.java:
argMap.put(Pattern.compile(arg.getKey()), arg.getValue());
camel-core/src/main/java/org/apache/camel/util/component/ArgumentSubstitutionParser.java:
methodMap.put(Pattern.compile(method.getKey()), argMap);
camel-core/src/main/java/org/apache/camel/util/jsse/FilterParameters.java:
patterns.add(Pattern.compile(this.parsePropertyValue(expression)));
camel-core/src/test/java/org/apache/camel/util/jsse/SSLContextParametersTest.java:
Arrays.asList(new
Pattern[]{Pattern.compile("TLS.*")}),
camel-core/src/test/java/org/apache/camel/util/jsse/SSLContextParametersTest.java:
Arrays.asList(new Pattern[]{Pattern.compile(".*")}),
camel-core/src/test/java/org/apache/camel/util/jsse/SSLContextParametersTest.java:
Arrays.asList(new
Pattern[]{Pattern.compile("SSL.*")}));
components/camel-aws/src/test/java/org/apache/camel/component/aws/ddbstream/DdbStreamConsumerTest.java:
private final Pattern shardIteratorPattern =
Pattern.compile("shard_iterator_d_0*(\\d+)");
components/camel-mail/src/main/java/org/apache/camel/dataformat/mime/multipart/MimeMultipartDataFormat.java:
this.includeHeaders = Pattern.compile(includeHeaders,
Pattern.CASE_INSENSITIVE);
components/camel-olingo2/camel-olingo2-api/src/main/java/org/apache/camel/component/olingo2/api/impl/AbstractFutureCallback.java:
public static final Pattern ODATA_MIME_TYPE =
Pattern.compile("application/((atom)|(json)|(xml)).*");
components/camel-salesforce/camel-salesforce-component/src/test/java/org/apache/camel/component/salesforce/api/dto/composite/SObjectBatchTest.java:
final String json =
Pattern.compile("\\s+(?=([^\"]*\"[^\"]*\")*[^\"]*$)", Pattern.DOTALL)
components/camel-salesforce/camel-salesforce-maven-plugin/src/main/java/org/apache/camel/maven/CamelSalesforceMojo.java:
incPattern = Pattern.compile(includePattern.trim());
components/camel-salesforce/camel-salesforce-maven-plugin/src/main/java/org/apache/camel/maven/CamelSalesforceMojo.java:
[jira] [Commented] (CAMEL-10086) Remove Pattern.compile usages
[
https://issues.apache.org/jira/browse/CAMEL-10086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812935#comment-15812935
]
onder sezgin commented on CAMEL-10086:
--
$ grep -iR 'Pattern.compile' * | grep -v 'private static final'
camel-core/src/main/java/org/apache/camel/builder/ExpressionBuilder.java:
final Pattern pattern = Pattern.compile(regexTokenizer);
camel-core/src/main/java/org/apache/camel/builder/ExpressionBuilder.java:
final Pattern pattern = Pattern.compile(regex);
camel-core/src/main/java/org/apache/camel/builder/ExpressionBuilder.java:
final Pattern pattern = Pattern.compile(regex);
camel-core/src/main/java/org/apache/camel/builder/PredicateBuilder.java:
return regex(expression, Pattern.compile(regex));
camel-core/src/main/java/org/apache/camel/component/file/GenericFileEndpoint.java:
this.includePattern = Pattern.compile(include,
Pattern.CASE_INSENSITIVE);
camel-core/src/main/java/org/apache/camel/component/file/GenericFileEndpoint.java:
this.excludePattern = Pattern.compile(exclude,
Pattern.CASE_INSENSITIVE);
camel-core/src/main/java/org/apache/camel/impl/DefaultHeaderFilterStrategy.java:
outFilterPattern = Pattern.compile(value);
camel-core/src/main/java/org/apache/camel/impl/DefaultHeaderFilterStrategy.java:
inFilterPattern = Pattern.compile(value);
camel-core/src/main/java/org/apache/camel/support/TokenXMLExpressionIterator.java:
Pattern.compile(MessageFormat.format(SCAN_BLOCK_TOKEN_REGEX_TEMPLATE,
camel-core/src/main/java/org/apache/camel/support/TokenXMLExpressionIterator.java:
Pattern.compile(MessageFormat.format(SCAN_PARENT_TOKEN_REGEX_TEMPLATE,
camel-core/src/main/java/org/apache/camel/support/TokenXMLPairExpressionIterator.java:
this.startTokenPattern = Pattern.compile(tokenSb.toString());
camel-core/src/main/java/org/apache/camel/support/TokenXMLPairExpressionIterator.java:
this.inheritNamespaceTokenPattern =
Pattern.compile(tokenSb.toString(), Pattern.MULTILINE | Pattern.DOTALL);
camel-core/src/main/java/org/apache/camel/support/XMLTokenExpressionIterator.java:
lcpattern = Pattern.compile(sb.toString());
camel-core/src/main/java/org/apache/camel/util/component/ApiMethodHelper.java:
aliasPatterns.put(Pattern.compile(alias.getKey()), alias.getValue());
camel-core/src/main/java/org/apache/camel/util/component/ApiMethodParser.java:
public static final Pattern ARGS_PATTERN =
Pattern.compile("\\s*([^<\\s]+)\\s*(<[^>]+>)?\\s+([^\\s,]+)\\s*,?");
camel-core/src/main/java/org/apache/camel/util/component/ArgumentSubstitutionParser.java:
nameReplacement.typePattern =
Pattern.compile(substitution.argType);
camel-core/src/main/java/org/apache/camel/util/component/ArgumentSubstitutionParser.java:
argMap.put(Pattern.compile(arg.getKey()), arg.getValue());
camel-core/src/main/java/org/apache/camel/util/component/ArgumentSubstitutionParser.java:
methodMap.put(Pattern.compile(method.getKey()), argMap);
camel-core/src/main/java/org/apache/camel/util/jsse/FilterParameters.java:
patterns.add(Pattern.compile(this.parsePropertyValue(expression)));
camel-core/src/test/java/org/apache/camel/util/jsse/SSLContextParametersTest.java:
Arrays.asList(new
Pattern[]{Pattern.compile("TLS.*")}),
camel-core/src/test/java/org/apache/camel/util/jsse/SSLContextParametersTest.java:
Arrays.asList(new Pattern[]{Pattern.compile(".*")}),
camel-core/src/test/java/org/apache/camel/util/jsse/SSLContextParametersTest.java:
Arrays.asList(new
Pattern[]{Pattern.compile("SSL.*")}));
components/camel-aws/src/test/java/org/apache/camel/component/aws/ddbstream/DdbStreamConsumerTest.java:
private final Pattern shardIteratorPattern =
Pattern.compile("shard_iterator_d_0*(\\d+)");
components/camel-mail/src/main/java/org/apache/camel/dataformat/mime/multipart/MimeMultipartDataFormat.java:
this.includeHeaders = Pattern.compile(includeHeaders,
Pattern.CASE_INSENSITIVE);
components/camel-olingo2/camel-olingo2-api/src/main/java/org/apache/camel/component/olingo2/api/impl/AbstractFutureCallback.java:
public static final Pattern ODATA_MIME_TYPE =
Pattern.compile("application/((atom)|(json)|(xml)).*");
components/camel-salesforce/camel-salesforce-component/src/test/java/org/apache/camel/component/salesforce/api/dto/composite/SObjectBatchTest.java:
final String json =
Pattern.compile("\\s+(?=([^\"]*\"[^\"]*\")*[^\"]*$)", Pattern.DOTALL)
components/camel-salesforce/camel-salesforce-maven-plugin/src/main/java/org/apache/camel/maven/CamelSalesforceMojo.java:
incPattern = Pattern.compile(includePattern.trim());
[jira] [Commented] (CAMEL-10086) Remove Pattern.compile usages
[
https://issues.apache.org/jira/browse/CAMEL-10086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812945#comment-15812945
]
onder sezgin commented on CAMEL-10086:
--
$ grep -iR 'Pattern.compile' * | grep -v 'static final'
camel-core/src/main/java/org/apache/camel/builder/ExpressionBuilder.java:
final Pattern pattern = Pattern.compile(regexTokenizer);
camel-core/src/main/java/org/apache/camel/builder/ExpressionBuilder.java:
final Pattern pattern = Pattern.compile(regex);
camel-core/src/main/java/org/apache/camel/builder/ExpressionBuilder.java:
final Pattern pattern = Pattern.compile(regex);
camel-core/src/main/java/org/apache/camel/builder/PredicateBuilder.java:
return regex(expression, Pattern.compile(regex));
camel-core/src/main/java/org/apache/camel/component/file/GenericFileEndpoint.java:
this.includePattern = Pattern.compile(include,
Pattern.CASE_INSENSITIVE);
camel-core/src/main/java/org/apache/camel/component/file/GenericFileEndpoint.java:
this.excludePattern = Pattern.compile(exclude,
Pattern.CASE_INSENSITIVE);
camel-core/src/main/java/org/apache/camel/impl/DefaultHeaderFilterStrategy.java:
outFilterPattern = Pattern.compile(value);
camel-core/src/main/java/org/apache/camel/impl/DefaultHeaderFilterStrategy.java:
inFilterPattern = Pattern.compile(value);
camel-core/src/main/java/org/apache/camel/support/TokenXMLExpressionIterator.java:
Pattern.compile(MessageFormat.format(SCAN_BLOCK_TOKEN_REGEX_TEMPLATE,
camel-core/src/main/java/org/apache/camel/support/TokenXMLExpressionIterator.java:
Pattern.compile(MessageFormat.format(SCAN_PARENT_TOKEN_REGEX_TEMPLATE,
camel-core/src/main/java/org/apache/camel/support/TokenXMLPairExpressionIterator.java:
this.startTokenPattern = Pattern.compile(tokenSb.toString());
camel-core/src/main/java/org/apache/camel/support/TokenXMLPairExpressionIterator.java:
this.inheritNamespaceTokenPattern =
Pattern.compile(tokenSb.toString(), Pattern.MULTILINE | Pattern.DOTALL);
camel-core/src/main/java/org/apache/camel/support/XMLTokenExpressionIterator.java:
lcpattern = Pattern.compile(sb.toString());
camel-core/src/main/java/org/apache/camel/util/component/ApiMethodHelper.java:
aliasPatterns.put(Pattern.compile(alias.getKey()), alias.getValue());
camel-core/src/main/java/org/apache/camel/util/component/ArgumentSubstitutionParser.java:
nameReplacement.typePattern =
Pattern.compile(substitution.argType);
camel-core/src/main/java/org/apache/camel/util/component/ArgumentSubstitutionParser.java:
argMap.put(Pattern.compile(arg.getKey()), arg.getValue());
camel-core/src/main/java/org/apache/camel/util/component/ArgumentSubstitutionParser.java:
methodMap.put(Pattern.compile(method.getKey()), argMap);
camel-core/src/main/java/org/apache/camel/util/jsse/FilterParameters.java:
patterns.add(Pattern.compile(this.parsePropertyValue(expression)));
camel-core/src/test/java/org/apache/camel/util/jsse/SSLContextParametersTest.java:
Arrays.asList(new
Pattern[]{Pattern.compile("TLS.*")}),
camel-core/src/test/java/org/apache/camel/util/jsse/SSLContextParametersTest.java:
Arrays.asList(new Pattern[]{Pattern.compile(".*")}),
camel-core/src/test/java/org/apache/camel/util/jsse/SSLContextParametersTest.java:
Arrays.asList(new
Pattern[]{Pattern.compile("SSL.*")}));
components/camel-aws/src/test/java/org/apache/camel/component/aws/ddbstream/DdbStreamConsumerTest.java:
private final Pattern shardIteratorPattern =
Pattern.compile("shard_iterator_d_0*(\\d+)");
components/camel-mail/src/main/java/org/apache/camel/dataformat/mime/multipart/MimeMultipartDataFormat.java:
this.includeHeaders = Pattern.compile(includeHeaders,
Pattern.CASE_INSENSITIVE);
components/camel-salesforce/camel-salesforce-component/src/test/java/org/apache/camel/component/salesforce/api/dto/composite/SObjectBatchTest.java:
final String json =
Pattern.compile("\\s+(?=([^\"]*\"[^\"]*\")*[^\"]*$)", Pattern.DOTALL)
components/camel-salesforce/camel-salesforce-maven-plugin/src/main/java/org/apache/camel/maven/CamelSalesforceMojo.java:
incPattern = Pattern.compile(includePattern.trim());
components/camel-salesforce/camel-salesforce-maven-plugin/src/main/java/org/apache/camel/maven/CamelSalesforceMojo.java:
excPattern = Pattern.compile(excludePattern.trim());
components/camel-snakeyaml/src/main/java/org/apache/camel/component/snakeyaml/TypeFilters.java:
this.predicates =
Collections.singletonList(Pattern.compile(pattern).asPredicate());
components/camel-sql/src/main/java/org/apache/camel/component/sql/DefaultSqlPrepareStatementStrategy.java:
Matcher paramMatcher =
[jira] [Resolved] (CAMEL-11016) Add an option in the TarFileDataFormat to let the iterator support the empty directory
[ https://issues.apache.org/jira/browse/CAMEL-11016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin resolved CAMEL-11016. -- Resolution: Fixed > Add an option in the TarFileDataFormat to let the iterator support the empty > directory > -- > > Key: CAMEL-11016 > URL: https://issues.apache.org/jira/browse/CAMEL-11016 > Project: Camel > Issue Type: Sub-task > Components: camel-tarfile >Affects Versions: 2.18.2 >Reporter: onder sezgin >Assignee: onder sezgin >Priority: Minor > Fix For: 2.19.0 > > > same option in tarfile component would be proper -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-10949) Websocket clients get message from all resources on one port
[
https://issues.apache.org/jira/browse/CAMEL-10949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin reassigned CAMEL-10949:
Assignee: onder sezgin
> Websocket clients get message from all resources on one port
> -
>
> Key: CAMEL-10949
> URL: https://issues.apache.org/jira/browse/CAMEL-10949
> Project: Camel
> Issue Type: Bug
> Components: camel-websocket
>Reporter: Ravi Godbole
>Assignee: onder sezgin
>Priority: Minor
>
> Routebuider configuration in which only resource URI is different while port
> is same.
> 1. newsTopic
> 2. stockQuoteTopic
> Ideally other clients connecting to newsTopic should get messages published
> on this topic only but they are also getting messages published on
> stockQuoteTopic.
> On further investigation I found out that memory store used to by sendAll
> is shared by all resource uri for a given port in the server.
> from("activemq:topic:newsTopic").to("websocket://
> 0.0.0.0:9090/newsTopic?sendToAll=true");
> from("activemq:topic:stockQuoteTopic").to("websocket://
> 0.0.0.0:9090/stockQuoteTopic?sendToAll=true");
> Sample Ouput received from client
> 2017-03-06 15:35:15.789:INFO::main: Logging initialized @313ms
> Connected to server
> Message received from server:MSFT[ published on stockQuoteTopic.
> Expected ..]
> Message received from server:CNBC News [ published on newsTopic. should
> not have received ]
> Message received from server:BBC News[ published on newsTopic. should
> not have received ]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (CAMEL-11052) Soap11DataFormatAdapter throwing exception when using JAXB/JAX-WS generated code
[
https://issues.apache.org/jira/browse/CAMEL-11052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin reassigned CAMEL-11052:
Assignee: onder sezgin
> Soap11DataFormatAdapter throwing exception when using JAXB/JAX-WS generated
> code
>
>
> Key: CAMEL-11052
> URL: https://issues.apache.org/jira/browse/CAMEL-11052
> Project: Camel
> Issue Type: Bug
> Components: camel-soap
>Affects Versions: 2.18.3
>Reporter: Kieran Simpson
>Assignee: onder sezgin
>Priority: Minor
> Labels: soap11
>
> When using WsImport, the structure of the generated Exception class for SOAP
> Faults have only a two arg constructor generated ie:
> {code:java}public MyException(String message, faultInfo) {}{code}
> However in {{Soap11DataFormatAdapter::createExceptionFromFault}} the code is
> trying to get a reference to the single argument constructor, before it tries
> to find/use the two argument constructor, which would cause a
> {{NoSuchMethodException}} to be thrown as no such constructor exits on the
> class.
> The solution is to move the {{messageConstructor}} variable inside the catch
> block. So we try to get/use the two arg constructor and if that fails then
> we try to get/use the single argument constructor, which is the real logic of
> that try/catch block anyway.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (CAMEL-11044) CLONE - EndpointHelper.resolveReferenceListParameter should not return immutable lists
[ https://issues.apache.org/jira/browse/CAMEL-11044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-11044: Assignee: onder sezgin > CLONE - EndpointHelper.resolveReferenceListParameter should not return > immutable lists > -- > > Key: CAMEL-11044 > URL: https://issues.apache.org/jira/browse/CAMEL-11044 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 2.17.3 >Reporter: Chandra Bose Renganathan >Assignee: onder sezgin >Priority: Minor > Fix For: 2.19.0 > > > EndpointHelper.resolveReferenceListParameter still sometimes return immutable > lists. > Following is an example URL: > jetty:http://0.0.0.0:8080/entitlements/v1?matchOnUriPrefix=true=true=myFilter > Since it already has filter, when the component adds crossOriginFilter, it > fails with UnsupportedOperationException. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11019) Please insert setter and getter for MESSAGE_HISTORY_HEADER and MESSAGE_HISTORY_OUTPUT
[ https://issues.apache.org/jira/browse/CAMEL-11019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947874#comment-15947874 ] onder sezgin commented on CAMEL-11019: -- any comment? > Please insert setter and getter for MESSAGE_HISTORY_HEADER and > MESSAGE_HISTORY_OUTPUT > - > > Key: CAMEL-11019 > URL: https://issues.apache.org/jira/browse/CAMEL-11019 > Project: Camel > Issue Type: Wish > Components: camel-core >Affects Versions: 2.17.5 >Reporter: Björn Paulsen >Priority: Minor > Fix For: Future > > > We use IDs for Processors and some others. Our IDs are longer than 18 chars > so we cannot read the MessageHistory clearly. But MessageHelper is final and > both properties too. Please give us a chance to customize the MessageHistory. > Thank you -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-10497) Improve documentation detailing websocket implementation details
[ https://issues.apache.org/jira/browse/CAMEL-10497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-10497: Assignee: onder sezgin > Improve documentation detailing websocket implementation details > > > Key: CAMEL-10497 > URL: https://issues.apache.org/jira/browse/CAMEL-10497 > Project: Camel > Issue Type: Improvement > Components: camel-websocket, documentation >Affects Versions: 2.18.0 >Reporter: Stuart Ingram >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > > Improve behavior documentation of this component, specifically around port > workflows. > While the initial port can be declaratively exposed for clients to connect > the component opens up two random(?) ports per client connected rather than > communicate through the single exposed port declared. > This was not apparent from the documentation and makes this component > somewhat inappropriate for containerization which would be useful to consider > when evaluating the 3 websocket implementations currently available for Camel. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-11019) Please insert setter and getter for MESSAGE_HISTORY_HEADER and MESSAGE_HISTORY_OUTPUT
[ https://issues.apache.org/jira/browse/CAMEL-11019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-11019: Assignee: onder sezgin > Please insert setter and getter for MESSAGE_HISTORY_HEADER and > MESSAGE_HISTORY_OUTPUT > - > > Key: CAMEL-11019 > URL: https://issues.apache.org/jira/browse/CAMEL-11019 > Project: Camel > Issue Type: Wish > Components: camel-core >Affects Versions: 2.17.5 >Reporter: Björn Paulsen >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > > We use IDs for Processors and some others. Our IDs are longer than 18 chars > so we cannot read the MessageHistory clearly. But MessageHelper is final and > both properties too. Please give us a chance to customize the MessageHistory. > Thank you -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (CAMEL-11016) Add an option in the TarFileDataFormat to let the iterator support the empty directory
[ https://issues.apache.org/jira/browse/CAMEL-11016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-11016 started by onder sezgin. > Add an option in the TarFileDataFormat to let the iterator support the empty > directory > -- > > Key: CAMEL-11016 > URL: https://issues.apache.org/jira/browse/CAMEL-11016 > Project: Camel > Issue Type: Sub-task > Components: camel-tarfile >Affects Versions: 2.18.2 >Reporter: onder sezgin >Assignee: onder sezgin >Priority: Minor > Fix For: 2.19.0 > > > same option in tarfile component would be proper -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-11017) if empty directory exists in source directory, file consumer does not pass directory structure to destination
[ https://issues.apache.org/jira/browse/CAMEL-11017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-11017: Assignee: onder sezgin > if empty directory exists in source directory, file consumer does not pass > directory structure to destination > - > > Key: CAMEL-11017 > URL: https://issues.apache.org/jira/browse/CAMEL-11017 > Project: Camel > Issue Type: New Feature > Components: camel-core >Affects Versions: 2.18.3 >Reporter: onder sezgin >Assignee: onder sezgin >Priority: Minor > Attachments: FileConsumerEmptyDirectoryTest.java > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-11017) if empty directory exists in source directory, file consumer does not pass directory structure to destination
[ https://issues.apache.org/jira/browse/CAMEL-11017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin updated CAMEL-11017: - Attachment: FileConsumerEmptyDirectoryTest.java ~/github/camel/camel-core/src/test/resources/org/apache/camel/component/file/data$ ls -ltrR .: total 12 -rw-rw-r-- 1 onders onders2 Oca 26 14:00 hi.txt drwxrwxr-x 2 onders onders 4096 Mar 15 15:41 another drwxrwxr-x 2 onders onders 4096 Mar 15 15:42 emptydir ./another: total 4 -rw-rw-r-- 1 onders onders 5 Oca 26 14:00 hello.txt ./emptydir: total 0 > if empty directory exists in source directory, file consumer does not pass > directory structure to destination > - > > Key: CAMEL-11017 > URL: https://issues.apache.org/jira/browse/CAMEL-11017 > Project: Camel > Issue Type: New Feature > Components: camel-core >Affects Versions: 2.18.3 >Reporter: onder sezgin >Priority: Minor > Attachments: FileConsumerEmptyDirectoryTest.java > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-11017) if empty directory exists in source directory, file consumer does not pass directory structure to destination
[ https://issues.apache.org/jira/browse/CAMEL-11017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin updated CAMEL-11017: - Attachment: (was: FileConsumerEmptyDirectoryTest.java) > if empty directory exists in source directory, file consumer does not pass > directory structure to destination > - > > Key: CAMEL-11017 > URL: https://issues.apache.org/jira/browse/CAMEL-11017 > Project: Camel > Issue Type: New Feature > Components: camel-core >Affects Versions: 2.18.3 >Reporter: onder sezgin >Assignee: onder sezgin >Priority: Minor > Attachments: FileConsumerEmptyDirectoryTest.java > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (CAMEL-11017) if empty directory exists in source directory, file consumer does not pass directory structure to destination
[ https://issues.apache.org/jira/browse/CAMEL-11017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin updated CAMEL-11017: - Attachment: FileConsumerEmptyDirectoryTest.java > if empty directory exists in source directory, file consumer does not pass > directory structure to destination > - > > Key: CAMEL-11017 > URL: https://issues.apache.org/jira/browse/CAMEL-11017 > Project: Camel > Issue Type: New Feature > Components: camel-core >Affects Versions: 2.18.3 >Reporter: onder sezgin >Assignee: onder sezgin >Priority: Minor > Attachments: FileConsumerEmptyDirectoryTest.java > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-11017) if empty directory exists in source directory, file consumer does not pass directory structure to destination
onder sezgin created CAMEL-11017: Summary: if empty directory exists in source directory, file consumer does not pass directory structure to destination Key: CAMEL-11017 URL: https://issues.apache.org/jira/browse/CAMEL-11017 Project: Camel Issue Type: New Feature Components: camel-core Affects Versions: 2.18.3 Reporter: onder sezgin Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (CAMEL-11017) if empty directory exists in source directory, file consumer does not pass directory structure to destination
[ https://issues.apache.org/jira/browse/CAMEL-11017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-11017 started by onder sezgin. > if empty directory exists in source directory, file consumer does not pass > directory structure to destination > - > > Key: CAMEL-11017 > URL: https://issues.apache.org/jira/browse/CAMEL-11017 > Project: Camel > Issue Type: New Feature > Components: camel-core >Affects Versions: 2.18.3 >Reporter: onder sezgin >Assignee: onder sezgin >Priority: Minor > Attachments: FileConsumerEmptyDirectoryTest.java > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10903) Getting Error due to higher version of JSCH
[ https://issues.apache.org/jira/browse/CAMEL-10903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924810#comment-15924810 ] onder sezgin commented on CAMEL-10903: -- i had a similar problem. this issue is not relevant to camel. probably, your problem is due to your client-side algorithm is not supported by your server side ssh connection provider libraries. i had to resolve my isse using bouncycastle on client side. it supports some kex algorithms. as claus already suggested, please look for support either with jsch or please debug your ssh or secure connection provider's libraries > Getting Error due to higher version of JSCH > --- > > Key: CAMEL-10903 > URL: https://issues.apache.org/jira/browse/CAMEL-10903 > Project: Camel > Issue Type: Task > Components: camel-ftp >Affects Versions: 2.16.2 >Reporter: Sourabh Jain >Priority: Minor > > Hi, We are getting error when we are using higher version(0.1.53) of JSCH > jar. but it work fine with JSCH version (0.1.49) while using camel-ftp route > while making SFTP connection. Here we are using the proxy for getting > connected to SFTP. Please let me know if you need more detail. > Please find the below error : > This is the set of credentials was provided by HSBC but we were getting the > following error: > org.apache.camel.component.file.GenericFileOperationFailedException: Cannot > connect to sftp://x...@ftp.:22 >at > org.apache.camel.component.file.remote.SftpOperations.connect(SftpOperations.java:146) >at > org.apache.camel.component.file.remote.RemoteFileConsumer.connectIfNecessary(RemoteFileConsumer.java:203) >at > org.apache.camel.component.file.remote.SftpConsumer.doStart(SftpConsumer.java:52) >at > org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) >at > org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:3269) >at > org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:3563) >at > org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:3499) >at > org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3429) >at > org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3197) >at > org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3053) >at > org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:175) >at > org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:2848) >at > org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:2844) >at > org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:2867) >at > org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:2844) >at > org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) >at > org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:2813) >at > org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:270) >at > org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:136) >at > org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:340) >at > org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:163) >at > org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:136) >at > org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:380) >at > org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334) >at > org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:851) >at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:540) >at > org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:139) >at > org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:93) >at com.bfm.etf.dixie.BDServer.loadApplicationContext(BDServer.java:98) >at com.bfm.etf.dixie.BDServer.main(BDServer.java:60) > Caused by: com.jcraft.jsch.JSchException: Session.connect: > java.security.InvalidAlgorithmParameterException: Prime size must be multiple > of 64, and can
[jira] [Resolved] (CAMEL-10791) Add an option in the ZipFileDataFormat to let the iterator support the empty directory
[ https://issues.apache.org/jira/browse/CAMEL-10791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin resolved CAMEL-10791. -- Resolution: Fixed Fix Version/s: 2.18.4 > Add an option in the ZipFileDataFormat to let the iterator support the empty > directory > --- > > Key: CAMEL-10791 > URL: https://issues.apache.org/jira/browse/CAMEL-10791 > Project: Camel > Issue Type: Improvement > Components: camel-zipfile >Affects Versions: 2.18.2 >Reporter: Uladzimir Zhuraulevich >Assignee: onder sezgin >Priority: Minor > Fix For: 2.18.4 > > > Would be great to have an option to ask camel-zipfile to catch empty folders > too. > http://camel.465427.n5.nabble.com/camel-zipfile-td5793495.html > Thanks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10497) Improve documentation detailing websocket implementation details
[ https://issues.apache.org/jira/browse/CAMEL-10497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954800#comment-15954800 ] onder sezgin commented on CAMEL-10497: -- [~singram777] I am not sure i understand what you require in camel-websocket documents.As far as i can see, if port specified, the component uses it, otherwise default port 9292 is in use. > Improve documentation detailing websocket implementation details > > > Key: CAMEL-10497 > URL: https://issues.apache.org/jira/browse/CAMEL-10497 > Project: Camel > Issue Type: Improvement > Components: camel-websocket, documentation >Affects Versions: 2.18.0 >Reporter: Stuart Ingram >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > > Improve behavior documentation of this component, specifically around port > workflows. > While the initial port can be declaratively exposed for clients to connect > the component opens up two random(?) ports per client connected rather than > communicate through the single exposed port declared. > This was not apparent from the documentation and makes this component > somewhat inappropriate for containerization which would be useful to consider > when evaluating the 3 websocket implementations currently available for Camel. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-11060) dn shouldn't be strictly required for Spring LDAP component
[ https://issues.apache.org/jira/browse/CAMEL-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955226#comment-15955226 ] onder sezgin commented on CAMEL-11060: -- well, i think better approach would be able to check if baseDN was set on LdapTemplate and if none, grab the DN from the enpoint options. I am not an expert on ldap and spring-ldap API. However, i could not see a way to check if LdapTemplate was created with baseDN. spring-ldap has limitations i guess and so the component comes with it. How about an option on the endpoint, so that camel would give you the control over if you set the base dn or not? maybe we can work on such PR? what do you think? > dn shouldn't be strictly required for Spring LDAP component > --- > > Key: CAMEL-11060 > URL: https://issues.apache.org/jira/browse/CAMEL-11060 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.18.3 >Reporter: Ken Geis >Priority: Minor > > I set a base DN in my LdapContextSource underlying the LdapTemplate. It's > redundant to need to set it in my route, but if I don't, the > SpringLdapProducer complains "DN must not be empty, but you provided an empty > DN". > In other code, I do this and regularly pass an empty string as the base to > LdapTemplate.search(base, ...). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-11120) Camel ZipFile does cannot move file after succesful processing
[
https://issues.apache.org/jira/browse/CAMEL-11120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin reassigned CAMEL-11120:
Assignee: onder sezgin
> Camel ZipFile does cannot move file after succesful processing
> --
>
> Key: CAMEL-11120
> URL: https://issues.apache.org/jira/browse/CAMEL-11120
> Project: Camel
> Issue Type: Bug
> Components: camel-zipfile
>Affects Versions: 2.18.3
> Environment: Windows 7 x64
>Reporter: Thomas Leber
>Assignee: onder sezgin
>
> When creating a route as follows:
> {code:xml}
>
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:camel="http://camel.apache.org/schema/spring;
> xmlns:context="http://www.springframework.org/schema/context;
> xmlns:util="http://www.springframework.org/schema/util;
> xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-4.2.xsd
> http://www.springframework.org/schema/context
> http://www.springframework.org/schema/context/spring-context-4.2.xsd
> http://camel.apache.org/schema/spring
> http://camel.apache.org/schema/spring/camel-spring.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util-2.5.xsd;>
>class="org.apache.camel.dataformat.zipfile.ZipFileDataFormat">
>
>
> http://camel.apache.org/schema/spring;
> streamCache="true">
>
>
>
>
> ${body}
>
>
>
>
>
>
>
> {code}
> the renaming of the file fails with
> {code}
> Renaming file from 'C:\camelTest\in\20161201T0030Z_1D_BE00_EQ.zip' to
> 'C:\camelTest\in\.camel\20161201T0030Z_1D_BE00_EQ.zip' failed: Cannot delete
> file 'C:\camelTest\in\20161201T0030Z_1D_BE00_EQ.zip' after copy succeeded
> {code}
> The file stays in input folder and gets processed over and over again.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (CAMEL-11065) Cannot parse CSV record starting with separator character
[
https://issues.apache.org/jira/browse/CAMEL-11065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin reassigned CAMEL-11065:
Assignee: onder sezgin
> Cannot parse CSV record starting with separator character
> -
>
> Key: CAMEL-11065
> URL: https://issues.apache.org/jira/browse/CAMEL-11065
> Project: Camel
> Issue Type: Bug
> Components: camel-bindy
>Affects Versions: 2.18.3
>Reporter: Tomáš Livora
>Assignee: onder sezgin
>
> Camel Bindy is not able to parse a CSV file where one value starts with a
> separator character. Example of such a record:
> {code}
> 'text1',',text2',3
> {code}
> And the Java class used:
> {code:title=Bar.java|borderStyle=solid}
> @CsvRecord(separator = ",", quote = "'")
> public class Record {
> @DataField(pos = 1)
> private String text1;
> @DataField(pos = 2)
> private String text2;
> @DataField(pos = 3, pattern = ".##")
> private BigDecimal number;
> }
> {code}
> You will get an exception like this:
> {code}
> java.lang.IllegalArgumentException: Parsing error detected for field defined
> at the position: 3, line: 1
> at
> org.apache.camel.dataformat.bindy.BindyCsvFactory.bind(BindyCsvFactory.java:213)
> at
> org.apache.camel.dataformat.bindy.csv.BindyCsvDataFormat.unmarshal(BindyCsvDataFormat.java:173)
> at
> org.apache.camel.processor.UnmarshalProcessor.process(UnmarshalProcessor.java:69)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> at
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> at
> org.apache.camel.processor.MulticastProcessor.doProcessSequential(MulticastProcessor.java:681)
> at
> org.apache.camel.processor.MulticastProcessor.doProcessSequential(MulticastProcessor.java:609)
> at
> org.apache.camel.processor.MulticastProcessor.process(MulticastProcessor.java:238)
> at org.apache.camel.processor.Splitter.process(Splitter.java:108)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> at
> org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:460)
> at
> org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:227)
> at
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:191)
> at
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:175)
> at
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:102)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
[jira] [Assigned] (CAMEL-11065) Cannot parse CSV record starting with separator character
[
https://issues.apache.org/jira/browse/CAMEL-11065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin reassigned CAMEL-11065:
Assignee: (was: onder sezgin)
> Cannot parse CSV record starting with separator character
> -
>
> Key: CAMEL-11065
> URL: https://issues.apache.org/jira/browse/CAMEL-11065
> Project: Camel
> Issue Type: Bug
> Components: camel-bindy
>Affects Versions: 2.18.3
>Reporter: Tomáš Livora
>
> Camel Bindy is not able to parse a CSV file where one value starts with a
> separator character. Example of such a record:
> {code}
> 'text1',',text2',3
> {code}
> And the Java class used:
> {code:title=Bar.java|borderStyle=solid}
> @CsvRecord(separator = ",", quote = "'")
> public class Record {
> @DataField(pos = 1)
> private String text1;
> @DataField(pos = 2)
> private String text2;
> @DataField(pos = 3, pattern = ".##")
> private BigDecimal number;
> }
> {code}
> You will get an exception like this:
> {code}
> java.lang.IllegalArgumentException: Parsing error detected for field defined
> at the position: 3, line: 1
> at
> org.apache.camel.dataformat.bindy.BindyCsvFactory.bind(BindyCsvFactory.java:213)
> at
> org.apache.camel.dataformat.bindy.csv.BindyCsvDataFormat.unmarshal(BindyCsvDataFormat.java:173)
> at
> org.apache.camel.processor.UnmarshalProcessor.process(UnmarshalProcessor.java:69)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> at
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> at
> org.apache.camel.processor.MulticastProcessor.doProcessSequential(MulticastProcessor.java:681)
> at
> org.apache.camel.processor.MulticastProcessor.doProcessSequential(MulticastProcessor.java:609)
> at
> org.apache.camel.processor.MulticastProcessor.process(MulticastProcessor.java:238)
> at org.apache.camel.processor.Splitter.process(Splitter.java:108)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
> at
> org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:460)
> at
> org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:227)
> at
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:191)
> at
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:175)
> at
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:102)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
[jira] [Commented] (CAMEL-11120) Camel ZipFile does cannot move file after succesful processing
[
https://issues.apache.org/jira/browse/CAMEL-11120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15960518#comment-15960518
]
onder sezgin commented on CAMEL-11120:
--
Tested both windows and unix box. It is working.
please see my UT
https://github.com/onders86/camel/commit/077e5df4f6904e13d76444821737bcc0dafe23c0
> Camel ZipFile does cannot move file after succesful processing
> --
>
> Key: CAMEL-11120
> URL: https://issues.apache.org/jira/browse/CAMEL-11120
> Project: Camel
> Issue Type: Bug
> Components: camel-zipfile
>Affects Versions: 2.18.3
> Environment: Windows 7 x64
>Reporter: Thomas Leber
>Assignee: onder sezgin
>
> When creating a route as follows:
> {code:xml}
>
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:camel="http://camel.apache.org/schema/spring;
> xmlns:context="http://www.springframework.org/schema/context;
> xmlns:util="http://www.springframework.org/schema/util;
> xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-4.2.xsd
> http://www.springframework.org/schema/context
> http://www.springframework.org/schema/context/spring-context-4.2.xsd
> http://camel.apache.org/schema/spring
> http://camel.apache.org/schema/spring/camel-spring.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util-2.5.xsd;>
>class="org.apache.camel.dataformat.zipfile.ZipFileDataFormat">
>
>
> http://camel.apache.org/schema/spring;
> streamCache="true">
>
>
>
>
> ${body}
>
>
>
>
>
>
>
> {code}
> the renaming of the file fails with
> {code}
> Renaming file from 'C:\camelTest\in\20161201T0030Z_1D_BE00_EQ.zip' to
> 'C:\camelTest\in\.camel\20161201T0030Z_1D_BE00_EQ.zip' failed: Cannot delete
> file 'C:\camelTest\in\20161201T0030Z_1D_BE00_EQ.zip' after copy succeeded
> {code}
> The file stays in input folder and gets processed over and over again.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (CAMEL-11120) Camel ZipFile does cannot move file after succesful processing
[
https://issues.apache.org/jira/browse/CAMEL-11120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin resolved CAMEL-11120.
--
Resolution: Not A Problem
> Camel ZipFile does cannot move file after succesful processing
> --
>
> Key: CAMEL-11120
> URL: https://issues.apache.org/jira/browse/CAMEL-11120
> Project: Camel
> Issue Type: Bug
> Components: camel-zipfile
>Affects Versions: 2.18.3
> Environment: Windows 7 x64
>Reporter: Thomas Leber
>Assignee: onder sezgin
>
> When creating a route as follows:
> {code:xml}
>
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:camel="http://camel.apache.org/schema/spring;
> xmlns:context="http://www.springframework.org/schema/context;
> xmlns:util="http://www.springframework.org/schema/util;
> xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-4.2.xsd
> http://www.springframework.org/schema/context
> http://www.springframework.org/schema/context/spring-context-4.2.xsd
> http://camel.apache.org/schema/spring
> http://camel.apache.org/schema/spring/camel-spring.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util-2.5.xsd;>
>class="org.apache.camel.dataformat.zipfile.ZipFileDataFormat">
>
>
> http://camel.apache.org/schema/spring;
> streamCache="true">
>
>
>
>
> ${body}
>
>
>
>
>
>
>
> {code}
> the renaming of the file fails with
> {code}
> Renaming file from 'C:\camelTest\in\20161201T0030Z_1D_BE00_EQ.zip' to
> 'C:\camelTest\in\.camel\20161201T0030Z_1D_BE00_EQ.zip' failed: Cannot delete
> file 'C:\camelTest\in\20161201T0030Z_1D_BE00_EQ.zip' after copy succeeded
> {code}
> The file stays in input folder and gets processed over and over again.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CAMEL-11120) Camel ZipFile does cannot move file after succesful processing
[
https://issues.apache.org/jira/browse/CAMEL-11120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15960519#comment-15960519
]
onder sezgin commented on CAMEL-11120:
--
I guess something is wrong with your filesystem. your file may be
write-protected.
> Camel ZipFile does cannot move file after succesful processing
> --
>
> Key: CAMEL-11120
> URL: https://issues.apache.org/jira/browse/CAMEL-11120
> Project: Camel
> Issue Type: Bug
> Components: camel-zipfile
>Affects Versions: 2.18.3
> Environment: Windows 7 x64
>Reporter: Thomas Leber
>Assignee: onder sezgin
>
> When creating a route as follows:
> {code:xml}
>
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:camel="http://camel.apache.org/schema/spring;
> xmlns:context="http://www.springframework.org/schema/context;
> xmlns:util="http://www.springframework.org/schema/util;
> xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-4.2.xsd
> http://www.springframework.org/schema/context
> http://www.springframework.org/schema/context/spring-context-4.2.xsd
> http://camel.apache.org/schema/spring
> http://camel.apache.org/schema/spring/camel-spring.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util-2.5.xsd;>
>class="org.apache.camel.dataformat.zipfile.ZipFileDataFormat">
>
>
> http://camel.apache.org/schema/spring;
> streamCache="true">
>
>
>
>
> ${body}
>
>
>
>
>
>
>
> {code}
> the renaming of the file fails with
> {code}
> Renaming file from 'C:\camelTest\in\20161201T0030Z_1D_BE00_EQ.zip' to
> 'C:\camelTest\in\.camel\20161201T0030Z_1D_BE00_EQ.zip' failed: Cannot delete
> file 'C:\camelTest\in\20161201T0030Z_1D_BE00_EQ.zip' after copy succeeded
> {code}
> The file stays in input folder and gets processed over and over again.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-11120) Camel ZipFile does cannot move file after succesful processing
[
https://issues.apache.org/jira/browse/CAMEL-11120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15960518#comment-15960518
]
onder sezgin edited comment on CAMEL-11120 at 4/7/17 11:20 AM:
---
Tested both windows and unix box. It is working.
please see my UT
https://github.com/onders86/camel/commit/a67b49c9653c4f49f7acf4c0a88a54408e870a6b
was (Author: onders):
Tested both windows and unix box. It is working.
please see my UT
https://github.com/onders86/camel/commit/077e5df4f6904e13d76444821737bcc0dafe23c0
> Camel ZipFile does cannot move file after succesful processing
> --
>
> Key: CAMEL-11120
> URL: https://issues.apache.org/jira/browse/CAMEL-11120
> Project: Camel
> Issue Type: Bug
> Components: camel-zipfile
>Affects Versions: 2.18.3
> Environment: Windows 7 x64
>Reporter: Thomas Leber
>Assignee: onder sezgin
>Priority: Minor
>
> When creating a route as follows:
> {code:xml}
>
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:camel="http://camel.apache.org/schema/spring;
> xmlns:context="http://www.springframework.org/schema/context;
> xmlns:util="http://www.springframework.org/schema/util;
> xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-4.2.xsd
> http://www.springframework.org/schema/context
> http://www.springframework.org/schema/context/spring-context-4.2.xsd
> http://camel.apache.org/schema/spring
> http://camel.apache.org/schema/spring/camel-spring.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util-2.5.xsd;>
>class="org.apache.camel.dataformat.zipfile.ZipFileDataFormat">
>
>
> http://camel.apache.org/schema/spring;
> streamCache="true">
>
>
>
>
> ${body}
>
>
>
>
>
>
>
> {code}
> the renaming of the file fails with
> {code}
> Renaming file from 'C:\camelTest\in\20161201T0030Z_1D_BE00_EQ.zip' to
> 'C:\camelTest\in\.camel\20161201T0030Z_1D_BE00_EQ.zip' failed: Cannot delete
> file 'C:\camelTest\in\20161201T0030Z_1D_BE00_EQ.zip' after copy succeeded
> {code}
> The file stays in input folder and gets processed over and over again.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CAMEL-11120) Camel ZipFile does cannot move file after succesful processing
[
https://issues.apache.org/jira/browse/CAMEL-11120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin updated CAMEL-11120:
-
Priority: Minor (was: Major)
> Camel ZipFile does cannot move file after succesful processing
> --
>
> Key: CAMEL-11120
> URL: https://issues.apache.org/jira/browse/CAMEL-11120
> Project: Camel
> Issue Type: Bug
> Components: camel-zipfile
>Affects Versions: 2.18.3
> Environment: Windows 7 x64
>Reporter: Thomas Leber
>Assignee: onder sezgin
>Priority: Minor
>
> When creating a route as follows:
> {code:xml}
>
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:camel="http://camel.apache.org/schema/spring;
> xmlns:context="http://www.springframework.org/schema/context;
> xmlns:util="http://www.springframework.org/schema/util;
> xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-4.2.xsd
> http://www.springframework.org/schema/context
> http://www.springframework.org/schema/context/spring-context-4.2.xsd
> http://camel.apache.org/schema/spring
> http://camel.apache.org/schema/spring/camel-spring.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util-2.5.xsd;>
>class="org.apache.camel.dataformat.zipfile.ZipFileDataFormat">
>
>
> http://camel.apache.org/schema/spring;
> streamCache="true">
>
>
>
>
> ${body}
>
>
>
>
>
>
>
> {code}
> the renaming of the file fails with
> {code}
> Renaming file from 'C:\camelTest\in\20161201T0030Z_1D_BE00_EQ.zip' to
> 'C:\camelTest\in\.camel\20161201T0030Z_1D_BE00_EQ.zip' failed: Cannot delete
> file 'C:\camelTest\in\20161201T0030Z_1D_BE00_EQ.zip' after copy succeeded
> {code}
> The file stays in input folder and gets processed over and over again.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CAMEL-11017) if empty directory exists in source directory, file consumer does not pass directory structure to destination
[ https://issues.apache.org/jira/browse/CAMEL-11017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin updated CAMEL-11017: - Patch Info: Patch Available > if empty directory exists in source directory, file consumer does not pass > directory structure to destination > - > > Key: CAMEL-11017 > URL: https://issues.apache.org/jira/browse/CAMEL-11017 > Project: Camel > Issue Type: New Feature > Components: camel-core >Affects Versions: 2.18.3 >Reporter: onder sezgin >Assignee: onder sezgin >Priority: Minor > Attachments: FileConsumerEmptyDirectoryTest.java > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-9477) Camel test examples are not working
[ https://issues.apache.org/jira/browse/CAMEL-9477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-9477: --- Assignee: (was: onder sezgin) > Camel test examples are not working > --- > > Key: CAMEL-9477 > URL: https://issues.apache.org/jira/browse/CAMEL-9477 > Project: Camel > Issue Type: Task > Components: documentation >Affects Versions: 2.16.1 >Reporter: Serge Smertin >Priority: Minor > Fix For: Future > > > While preparing internal demo of Camel i've tried to go over examples on test > page and most of them are not actually working - > http://camel.apache.org/spring-testing.html. I've seen [~davsclaus] writing > about > http://www.davsclaus.com/2015/12/my-thoughts-on-buying-professional.html, so > i find this issue as important. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-11152) camel-ssh - Allow to use message headers for username/password
[ https://issues.apache.org/jira/browse/CAMEL-11152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-11152: Assignee: onder sezgin > camel-ssh - Allow to use message headers for username/password > -- > > Key: CAMEL-11152 > URL: https://issues.apache.org/jira/browse/CAMEL-11152 > Project: Camel > Issue Type: Improvement > Components: camel-ssh >Reporter: Claus Ibsen >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > > See nabble > http://camel.465427.n5.nabble.com/Camel-SSH-dynamic-values-tp5797435p5797545.html > In the > org.apache.camel.component.ssh.SshHelper#sendExecCommand > We should allow the exchange to provide a username/password to be used, so > you can more dynamic reuse the same ssh endpoint but for different logins. > Using toD has a drawback of creating a new endpoint per username. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10843) Add readme.adoc files for other components
[ https://issues.apache.org/jira/browse/CAMEL-10843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966466#comment-15966466 ] onder sezgin commented on CAMEL-10843: -- [~lb] Hi, I'd written very very initial things about ribbon before i was very busy with work and thinking of discussions around deprecating components before 2.19 release, i'd not found a chance to add anything and even trying to do something about the other components. I've just sent a PR for that one, considering better than nothing. As it is very initial, feel free to dump my PR. please just let me know, i don't mind closing it. Apart from my situation, i agree your suggestion around skipping some of them. [~igarashitm] if you want, you can carry on and if you want to share, we can split them up and share and maybe finish quicker(even though i am not sure if i can give them go in the following two weeks.) Thanks > Add readme.adoc files for other components > -- > > Key: CAMEL-10843 > URL: https://issues.apache.org/jira/browse/CAMEL-10843 > Project: Camel > Issue Type: Improvement > Components: documentation >Reporter: Claus Ibsen > Fix For: 2.19.0 > > > We need a little bit of documentation for these > [INFO] > [WARNING] Missing .adoc other documentation : 11 > [WARNING] hystrix > [WARNING] ribbon > [WARNING] scala > [WARNING] scr > [WARNING] shiro > [WARNING] spring-dm > [WARNING] spring-javaconfig > [WARNING] test-cdi > [WARNING] test-karaf > [WARNING] test-spring > [WARNING] testng -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-7519) camel-bindy - CSV unbinding does not escape embedded quote character
[ https://issues.apache.org/jira/browse/CAMEL-7519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-7519: --- Assignee: onder sezgin > camel-bindy - CSV unbinding does not escape embedded quote character > > > Key: CAMEL-7519 > URL: https://issues.apache.org/jira/browse/CAMEL-7519 > Project: Camel > Issue Type: Improvement > Components: camel-bindy >Reporter: James Birchfield >Assignee: onder sezgin > Fix For: Future > > > If you have String field that contains the same character (String) as the > quote character, and quoting is set to true, the embedded character should be > escaped. > val s:String = "\"foo\"" > Bindy will unmarshal to the CSV stream ""foo"","...","...","...",... > it should be "\"foo\"","...","...","...",... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-7862) Allow empty csv files in the Camel Bindy unmarshalling process
[ https://issues.apache.org/jira/browse/CAMEL-7862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-7862: --- Assignee: onder sezgin > Allow empty csv files in the Camel Bindy unmarshalling process > -- > > Key: CAMEL-7862 > URL: https://issues.apache.org/jira/browse/CAMEL-7862 > Project: Camel > Issue Type: Improvement > Components: camel-bindy >Reporter: Tom So >Assignee: onder sezgin >Priority: Minor > > Currently the unmarshal process of Camel Bindy will throw an > IllegalArgumentException if the provided data stream is empty. Therefore the > client has to catch that Exception or bypass the unmarshal process to handle > empty files. > It would be an improvement if Bindy will always return an empty collection if > the data stream is empty and there is nothing to unmarshal. Or if there is an > annotation available to decide how empty stream should be treated (i.e., > throw an exception or return an empty collection). The annotation could be > part of the @CsvRecord annotation: @CsvRecord(allowEmptyFiles = true). > Please see this discussion on the camel users mailing list for further > information: > http://camel.465427.n5.nabble.com/Why-does-Bindy-prohibit-empty-files-td5756976.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-7862) Allow empty csv files in the Camel Bindy unmarshalling process
[ https://issues.apache.org/jira/browse/CAMEL-7862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903019#comment-15903019 ] onder sezgin commented on CAMEL-7862: - i'll try to have a look. > Allow empty csv files in the Camel Bindy unmarshalling process > -- > > Key: CAMEL-7862 > URL: https://issues.apache.org/jira/browse/CAMEL-7862 > Project: Camel > Issue Type: Improvement > Components: camel-bindy >Reporter: Tom So >Assignee: onder sezgin >Priority: Minor > > Currently the unmarshal process of Camel Bindy will throw an > IllegalArgumentException if the provided data stream is empty. Therefore the > client has to catch that Exception or bypass the unmarshal process to handle > empty files. > It would be an improvement if Bindy will always return an empty collection if > the data stream is empty and there is nothing to unmarshal. Or if there is an > annotation available to decide how empty stream should be treated (i.e., > throw an exception or return an empty collection). The annotation could be > part of the @CsvRecord annotation: @CsvRecord(allowEmptyFiles = true). > Please see this discussion on the camel users mailing list for further > information: > http://camel.465427.n5.nabble.com/Why-does-Bindy-prohibit-empty-files-td5756976.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-10791) Add an option in the ZipFileDataFormat to let the iterator support the empty directory
[ https://issues.apache.org/jira/browse/CAMEL-10791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-10791: Assignee: onder sezgin > Add an option in the ZipFileDataFormat to let the iterator support the empty > directory > --- > > Key: CAMEL-10791 > URL: https://issues.apache.org/jira/browse/CAMEL-10791 > Project: Camel > Issue Type: Improvement > Components: camel-zipfile >Affects Versions: 2.18.2 >Reporter: Uladzimir Zhuraulevich >Assignee: onder sezgin >Priority: Minor > > Would be great to have an option to ask camel-zipfile to catch empty folders > too. > http://camel.465427.n5.nabble.com/camel-zipfile-td5793495.html > Thanks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10791) Add an option in the ZipFileDataFormat to let the iterator support the empty directory
[ https://issues.apache.org/jira/browse/CAMEL-10791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903020#comment-15903020 ] onder sezgin commented on CAMEL-10791: -- i'll try to have a look. > Add an option in the ZipFileDataFormat to let the iterator support the empty > directory > --- > > Key: CAMEL-10791 > URL: https://issues.apache.org/jira/browse/CAMEL-10791 > Project: Camel > Issue Type: Improvement > Components: camel-zipfile >Affects Versions: 2.18.2 >Reporter: Uladzimir Zhuraulevich >Priority: Minor > > Would be great to have an option to ask camel-zipfile to catch empty folders > too. > http://camel.465427.n5.nabble.com/camel-zipfile-td5793495.html > Thanks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (CAMEL-10791) Add an option in the ZipFileDataFormat to let the iterator support the empty directory
[ https://issues.apache.org/jira/browse/CAMEL-10791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-10791 started by onder sezgin. > Add an option in the ZipFileDataFormat to let the iterator support the empty > directory > --- > > Key: CAMEL-10791 > URL: https://issues.apache.org/jira/browse/CAMEL-10791 > Project: Camel > Issue Type: Improvement > Components: camel-zipfile >Affects Versions: 2.18.2 >Reporter: Uladzimir Zhuraulevich >Assignee: onder sezgin >Priority: Minor > > Would be great to have an option to ask camel-zipfile to catch empty folders > too. > http://camel.465427.n5.nabble.com/camel-zipfile-td5793495.html > Thanks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-9552) Cannot consume and produce to beanstalk component in the same route
[
https://issues.apache.org/jira/browse/CAMEL-9552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898936#comment-15898936
]
onder sezgin commented on CAMEL-9552:
-
Instead of setting camel exhange's headers in both beanstalkproducer and
beanstalkconsumer as
{code}
exchange.getIn().setHeader(Headers.JOB_ID, job.getJobId())
{code}
which is
Headers.JOB_ID -> "beanstalk.jobId"; (which is actually Headers.PREFIX+"jobId")
maybe we can change the lines where we set camel exchange's headers
like
{code}
exchange.getIn().setHeader(Headers.PREFIX+"producer."+"jobId", job.getJobId())
{code}
however, This suggestion requires a lot of code change.
Thinking of a simpler code change to avoid such a huge change which may break
existing codes of this component's users.
> Cannot consume and produce to beanstalk component in the same route
> ---
>
> Key: CAMEL-9552
> URL: https://issues.apache.org/jira/browse/CAMEL-9552
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.15.0, 2.16.0
>Reporter: J Smith
>Assignee: onder sezgin
>
> It appears that when creating a route that consumes from one beanstalk tube
> and produces to another, the exchange headers from the consumer somehow get
> mixed in with the producer and cause errors.
> Example route:
> .from("beanstalk://localhost?tube=A")
> .setBody("hello")
> .to("beanstalk://localhost?tube=B")
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Work started] (CAMEL-9552) Cannot consume and produce to beanstalk component in the same route
[
https://issues.apache.org/jira/browse/CAMEL-9552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-9552 started by onder sezgin.
---
> Cannot consume and produce to beanstalk component in the same route
> ---
>
> Key: CAMEL-9552
> URL: https://issues.apache.org/jira/browse/CAMEL-9552
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.15.0, 2.16.0
>Reporter: J Smith
>Assignee: onder sezgin
>
> It appears that when creating a route that consumes from one beanstalk tube
> and produces to another, the exchange headers from the consumer somehow get
> mixed in with the producer and cause errors.
> Example route:
> .from("beanstalk://localhost?tube=A")
> .setBody("hello")
> .to("beanstalk://localhost?tube=B")
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Issue Comment Deleted] (CAMEL-9552) Cannot consume and produce to beanstalk component in the same route
[
https://issues.apache.org/jira/browse/CAMEL-9552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin updated CAMEL-9552:
Comment: was deleted
(was: Instead of setting camel exhange's headers in both beanstalkproducer and
beanstalkconsumer as
{code}
exchange.getIn().setHeader(Headers.JOB_ID, job.getJobId())
{code}
which is
Headers.JOB_ID -> "beanstalk.jobId"; (which is actually Headers.PREFIX+"jobId")
maybe we can change the lines where we set camel exchange's headers
like
{code}
exchange.getIn().setHeader(Headers.PREFIX+"producer."+"jobId", job.getJobId())
{code}
however, This suggestion requires a lot of code change.
Thinking of a simpler code change to avoid such a huge change which may break
existing codes of this component's users.
)
> Cannot consume and produce to beanstalk component in the same route
> ---
>
> Key: CAMEL-9552
> URL: https://issues.apache.org/jira/browse/CAMEL-9552
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.15.0, 2.16.0
>Reporter: J Smith
>Assignee: onder sezgin
>
> It appears that when creating a route that consumes from one beanstalk tube
> and produces to another, the exchange headers from the consumer somehow get
> mixed in with the producer and cause errors.
> Example route:
> .from("beanstalk://localhost?tube=A")
> .setBody("hello")
> .to("beanstalk://localhost?tube=B")
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CAMEL-8351) Spring-ws consumer ignores breadcrumbId http header
[
https://issues.apache.org/jira/browse/CAMEL-8351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888705#comment-15888705
]
onder sezgin commented on CAMEL-8351:
-
I'll try to have a look.
> Spring-ws consumer ignores breadcrumbId http header
> ---
>
> Key: CAMEL-8351
> URL: https://issues.apache.org/jira/browse/CAMEL-8351
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-ws
>Affects Versions: 2.14.1
>Reporter: Ralf Steppacher
>Assignee: onder sezgin
>
> The spring-ws consumer does not pick up a {{breadcrumbId}} HTTP header. I
> tried to find a hook where I could jump in and make the breadcrumbId from the
> HTTP headers available, but could not find any.
> The spring-ws endpoint ({{SpringWebserviceConsumer}}) does not care about
> HTTP headers, only about SOAP headers and properties of the
> {{org.springframework.ws.context.MessageContext}}. SOAP headers get converted
> into exchange headers while message context properties get converted into
> exchange properties. Properties could be added by using a
> {{org.springframework.ws.server.EndpointInterceptor}}.
> A breadcrumbId property is not picked up by Camel though. The
> {{org.apache.camel.impl.DefaultUnitOfWork}} creates a new breadcrumbId
> because it only checks the headers of the in-message, not the exchange
> properties for an already existing breadcrumb ID.
> A SOAPHeader "breadcrumbId" is copied over to the in-message headers and
> picked up by the DefaultUnitOfWork, but it is not automagically converted
> from {{org.springframework.ws.soap.saaj.SaajSoapHeaderElement}} to its text
> content.
> Ideally the web service consumer would pick up the breadcrumId (and others)
> from the HTTP headers and restore them as in-message headers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (CAMEL-8351) Spring-ws consumer ignores breadcrumbId http header
[
https://issues.apache.org/jira/browse/CAMEL-8351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin reassigned CAMEL-8351:
---
Assignee: onder sezgin
> Spring-ws consumer ignores breadcrumbId http header
> ---
>
> Key: CAMEL-8351
> URL: https://issues.apache.org/jira/browse/CAMEL-8351
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-ws
>Affects Versions: 2.14.1
>Reporter: Ralf Steppacher
>Assignee: onder sezgin
>
> The spring-ws consumer does not pick up a {{breadcrumbId}} HTTP header. I
> tried to find a hook where I could jump in and make the breadcrumbId from the
> HTTP headers available, but could not find any.
> The spring-ws endpoint ({{SpringWebserviceConsumer}}) does not care about
> HTTP headers, only about SOAP headers and properties of the
> {{org.springframework.ws.context.MessageContext}}. SOAP headers get converted
> into exchange headers while message context properties get converted into
> exchange properties. Properties could be added by using a
> {{org.springframework.ws.server.EndpointInterceptor}}.
> A breadcrumbId property is not picked up by Camel though. The
> {{org.apache.camel.impl.DefaultUnitOfWork}} creates a new breadcrumbId
> because it only checks the headers of the in-message, not the exchange
> properties for an already existing breadcrumb ID.
> A SOAPHeader "breadcrumbId" is copied over to the in-message headers and
> picked up by the DefaultUnitOfWork, but it is not automagically converted
> from {{org.springframework.ws.soap.saaj.SaajSoapHeaderElement}} to its text
> content.
> Ideally the web service consumer would pick up the breadcrumId (and others)
> from the HTTP headers and restore them as in-message headers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CAMEL-9477) Camel test examples are not working
[ https://issues.apache.org/jira/browse/CAMEL-9477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958789#comment-15958789 ] onder sezgin commented on CAMEL-9477: - The PR above only contains the changes what's complained in the issue. I agree there is much work needed on documentation to keep it sync with code and website. as the website will already be renewed, i believe keeping and fixing adocs is hopefully sufficient. and instead of doing a huge work in a single ticket, i think we need to divide and conquer the completion of documents. as a small note, maybe we need to think of a way to extract and document even the examples from the code. maybe some adocs should be created for examples as well. just a thought > Camel test examples are not working > --- > > Key: CAMEL-9477 > URL: https://issues.apache.org/jira/browse/CAMEL-9477 > Project: Camel > Issue Type: Task > Components: documentation >Affects Versions: 2.16.1 >Reporter: Serge Smertin >Priority: Minor > Fix For: Future > > > While preparing internal demo of Camel i've tried to go over examples on test > page and most of them are not actually working - > http://camel.apache.org/spring-testing.html. I've seen [~davsclaus] writing > about > http://www.davsclaus.com/2015/12/my-thoughts-on-buying-professional.html, so > i find this issue as important. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-9477) Camel test examples are not working
[ https://issues.apache.org/jira/browse/CAMEL-9477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-9477: --- Assignee: onder sezgin > Camel test examples are not working > --- > > Key: CAMEL-9477 > URL: https://issues.apache.org/jira/browse/CAMEL-9477 > Project: Camel > Issue Type: Task > Components: documentation >Affects Versions: 2.16.1 >Reporter: Serge Smertin >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > > While preparing internal demo of Camel i've tried to go over examples on test > page and most of them are not actually working - > http://camel.apache.org/spring-testing.html. I've seen [~davsclaus] writing > about > http://www.davsclaus.com/2015/12/my-thoughts-on-buying-professional.html, so > i find this issue as important. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10497) Improve documentation detailing websocket implementation details
[ https://issues.apache.org/jira/browse/CAMEL-10497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972268#comment-15972268 ] onder sezgin commented on CAMEL-10497: -- [~singram777]i got what you mean. however, i can not verify that i can see what you meant in the code. if you could provide test env or steps that i can reproduce, i can provide better documentation (i just don't want to add a simple statement to adoc and close the issue.) or why don't you create github PR if you are already able to test and see the issue and maybe you can do a blog post about your experience? > Improve documentation detailing websocket implementation details > > > Key: CAMEL-10497 > URL: https://issues.apache.org/jira/browse/CAMEL-10497 > Project: Camel > Issue Type: Improvement > Components: camel-websocket, documentation >Affects Versions: 2.18.0 >Reporter: Stuart Ingram >Assignee: onder sezgin >Priority: Minor > Fix For: Future > > > Improve behavior documentation of this component, specifically around port > workflows. > While the initial port can be declaratively exposed for clients to connect > the component opens up two random(?) ports per client connected rather than > communicate through the single exposed port declared. > This was not apparent from the documentation and makes this component > somewhat inappropriate for containerization which would be useful to consider > when evaluating the 3 websocket implementations currently available for Camel. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (CAMEL-10497) Improve documentation detailing websocket implementation details
[ https://issues.apache.org/jira/browse/CAMEL-10497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin reassigned CAMEL-10497: Assignee: (was: onder sezgin) > Improve documentation detailing websocket implementation details > > > Key: CAMEL-10497 > URL: https://issues.apache.org/jira/browse/CAMEL-10497 > Project: Camel > Issue Type: Improvement > Components: camel-websocket, documentation >Affects Versions: 2.18.0 >Reporter: Stuart Ingram >Priority: Minor > Fix For: Future > > > Improve behavior documentation of this component, specifically around port > workflows. > While the initial port can be declaratively exposed for clients to connect > the component opens up two random(?) ports per client connected rather than > communicate through the single exposed port declared. > This was not apparent from the documentation and makes this component > somewhat inappropriate for containerization which would be useful to consider > when evaluating the 3 websocket implementations currently available for Camel. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-11533) Simple language - comparison againist negative value fails with unknown token
onder sezgin created CAMEL-11533:
Summary: Simple language - comparison againist negative value
fails with unknown token
Key: CAMEL-11533
URL: https://issues.apache.org/jira/browse/CAMEL-11533
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: onder sezgin
Assignee: onder sezgin
Priority: Minor
Fix For: 2.20.0
{code}
from("seda:test")
.choice()
.when()
.simple("${in.body.someval} == -1}").to("mock:mock1")
.otherwise()
.to("mock:mock2")
.endChoice();
{code}
ends with
org.apache.camel.language.simple.types.SimpleIllegalSyntaxException: Binary
operator == does not support token -
this can be improved to note - sign
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (CAMEL-6049) ZipDataFormat and the zip( ) DSL actually use the deflate compression, not zip
[ https://issues.apache.org/jira/browse/CAMEL-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin resolved CAMEL-6049. - Resolution: Not A Problem Assignee: onder sezgin Fix Version/s: (was: 3.0.0) I think this enhancement is already done. Marking. > ZipDataFormat and the zip( ) DSL actually use the deflate compression, not zip > -- > > Key: CAMEL-6049 > URL: https://issues.apache.org/jira/browse/CAMEL-6049 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 2.10.3 >Reporter: Daniel Gredler >Assignee: onder sezgin > > The existing ZipDataFormat and .zip( ) DSL are misnamed, and actually use > deflate compression, causing confusion among users [1, 2]. > Release 3.0 would be a good chance to (a) rename these classes and methods to > reflect reality, and to (b) add a different set of zip classes and DSL > elements that actually perform zip (de)compression. > [1] http://markmail.org/thread/b6b6wibxpsqwwysy > [2] > http://hillert.blogspot.com/2009/10/camellos-iii-zipping-files-with-apache.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CAMEL-11516) FtpConsumerFileSplitTest fails on windows due to platform line.seperator
[ https://issues.apache.org/jira/browse/CAMEL-11516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin resolved CAMEL-11516. -- Resolution: Fixed Fix Version/s: (was: 2.19.2) > FtpConsumerFileSplitTest fails on windows due to platform line.seperator > > > Key: CAMEL-11516 > URL: https://issues.apache.org/jira/browse/CAMEL-11516 > Project: Camel > Issue Type: Test > Components: camel-ftp >Affects Versions: 2.19.1 > Environment: On Windows >Reporter: onder sezgin >Assignee: onder sezgin >Priority: Trivial > Labels: Novice > Fix For: 2.20.0 > > > [ERROR] Failures: > [ERROR] > org.apache.camel.component.file.remote.FtpConsumerFileSplitTest.testFtpR > oute(org.apache.camel.component.file.remote.FtpConsumerFileSplitTest) > [ERROR] Run 1: FtpConsumerFileSplitTest.testFtpRoute:42 mock://result Body > of > >essage: 0. Expected: but was: [ERROR] Run 2: FtpConsumerFileSplitTest.testFtpRoute:42 mock://result Body > of > >essage: 0. Expected: but was: [ERROR] Run 3: FtpConsumerFileSplitTest.testFtpRoute:42 mock://result Body > of > >essage: 0. Expected: but was:
[jira] [Updated] (CAMEL-11509) Cannot set content type with parameters without specifying charset
[
https://issues.apache.org/jira/browse/CAMEL-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin updated CAMEL-11509:
-
Patch Info: Patch Available
External issue URL: https://issues.apache.org/jira/browse/HTTPCORE-476
External issue ID: https://issues.apache.org/jira/browse/HTTPCORE-476
Estimated Complexity: Moderate (was: Unknown)
> Cannot set content type with parameters without specifying charset
> --
>
> Key: CAMEL-11509
> URL: https://issues.apache.org/jira/browse/CAMEL-11509
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 2.19.0, 2.19.1
>Reporter: Steffen F.
>Assignee: onder sezgin
> Fix For: 2.19.2, 2.20.0
>
>
> When setting a content type that does not contain a charset parameter, for
> example this:
> {noformat}
> .setHeader("Content-Type", constant("application/json;odata=verbose"))
> {noformat}
> the route will fail with the following exception:
> {noformat}
> java.lang.IllegalArgumentException: MIME type may not contain reserved
> characters
> at org.apache.http.util.Args.check(Args.java:36)
> at org.apache.http.entity.ContentType.create(ContentType.java:206)
> at org.apache.http.entity.ContentType.create(ContentType.java:218)
> at
> org.apache.camel.component.http4.HttpProducer.createRequestEntity(HttpProducer.java:511)
> {noformat}
> although this is clearly a valid content type according to the RFC:
> https://tools.ietf.org/html/rfc2045#section-5.1
> This only affects version 2.19+, because in version 4.4.6 of the
> httpcomponents-core library, they changed the behavior of {{create}} to check
> the mime type for semicolons, which it previously didn't. If we, however,
> also use a charset parameter, you will call the {{parse}} method instead:
> {noformat}
> if (contentTypeString != null) {
> if (contentTypeString.indexOf("charset") > 0) {
> contentType = ContentType.parse(contentTypeString);
> } else {
> contentType = ContentType.create(contentTypeString);
> }
> }
> {noformat}
> There can be all kind of different parameters, though. Instead of checking
> for charset, it should rather check for the existence of a semicolon.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CAMEL-11516) FtpConsumerFileSplitTest fails on windows due to platform line.seperator
[ https://issues.apache.org/jira/browse/CAMEL-11516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin updated CAMEL-11516: - Fix Version/s: 2.19.2 > FtpConsumerFileSplitTest fails on windows due to platform line.seperator > > > Key: CAMEL-11516 > URL: https://issues.apache.org/jira/browse/CAMEL-11516 > Project: Camel > Issue Type: Test > Components: camel-ftp >Affects Versions: 2.19.1 > Environment: On Windows >Reporter: onder sezgin >Assignee: onder sezgin >Priority: Trivial > Labels: Novice > Fix For: 2.19.2, 2.20.0 > > > [ERROR] Failures: > [ERROR] > org.apache.camel.component.file.remote.FtpConsumerFileSplitTest.testFtpR > oute(org.apache.camel.component.file.remote.FtpConsumerFileSplitTest) > [ERROR] Run 1: FtpConsumerFileSplitTest.testFtpRoute:42 mock://result Body > of > >essage: 0. Expected: but was: [ERROR] Run 2: FtpConsumerFileSplitTest.testFtpRoute:42 mock://result Body > of > >essage: 0. Expected: but was: [ERROR] Run 3: FtpConsumerFileSplitTest.testFtpRoute:42 mock://result Body > of > >essage: 0. Expected: but was:
[jira] [Commented] (CAMEL-11482) SSLContextParameters settings are not properly copied to SslContextFactory
[
https://issues.apache.org/jira/browse/CAMEL-11482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074335#comment-16074335
]
onder sezgin commented on CAMEL-11482:
--
2.16.X is EOL. 2.17.X is EOL.
I guess Java 6 and 7 support is not needed.
for the setting to copy, IMHO i would suppose the nicer way would be to have
full default copying all configurations to SSLContextFactory and also have
configurable base strategy(which may be pluggable via SPI) and where you can
choose which settings to copy and put to SSLContextFactory.
> SSLContextParameters settings are not properly copied to SslContextFactory
> --
>
> Key: CAMEL-11482
> URL: https://issues.apache.org/jira/browse/CAMEL-11482
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 2.19.0, 2.19.1
> Environment: Max OS X, Java 8 Update 131
> Ubuntu 14.04 LTS, Java 8 Update 111
> Camel 2.19.0
> Jetty9 9.4.5v20170502 and 9.3.14.v20161028
>Reporter: Roman Vottner
> Fix For: 2.19.2, 2.20.0
>
>
> Jetty 9.3+ excludes unsecure ciphers which end on either MD5, SHA or SHA1 by
> default now. This will however remove all ciphers that are used by either
> TLSv1 or TLSv1.1 and thus no ciphers remain in order to agree on a cipher for
> TLSv1 or TLSv1.1 connection attempts. (Further reading:
> https://github.com/eclipse/jetty.project/issues/860)
> The Jetty 9 SSL configuration documentation
> (https://www.eclipse.org/jetty/documentation/9.3.x/configuring-ssl.html)
> states that this exclusion cipher suites can be customized by providing an
> own exclusion list. On specifying SSLContextParameters like below however
> will not correctly propagate this exclution cipher suites to the
> SslContextFactory of Jetty and thus use the default setting which prevents
> TLSv1 and TLSv1.1 connections.
> {code:title=SSLContextParameters Spring Config|borderStyle=solid}
> @Bean(name = "sslContextParameters")
> public SSLContextParameters sslContextParameters() {
> String keyStore = env.getProperty("ssl.keyStore.resource");
> URL keyStoreUrl = this.getClass().getResource(keyStore);
> // http://camel.apache.org/jetty.html
> KeyStoreParameters ksp = new KeyStoreParameters();
> ksp.setResource(keyStoreUrl.getPath());
> ksp.setPassword(env.getProperty("ssl.keyStore.password"));
> KeyManagersParameters kmp = new KeyManagersParameters();
> kmp.setKeyStore(ksp);
> kmp.setKeyPassword(env.getProperty("ssl.key.password"));
> SSLContextParameters scp = new SSLContextParameters();
> scp.setKeyManagers(kmp);
> // Jetty 9.3+ support only TLSv1.2 by default hence clients not
> supporting this protocol will fail
> List supportedSslProtocols = Arrays.asList("TLSv1", "TLSv1.1",
> "TLSv1.2");
> SecureSocketProtocolsParameters protocolsParameters = new
> SecureSocketProtocolsParameters();
> protocolsParameters.setSecureSocketProtocol(supportedSslProtocols);
> scp.setSecureSocketProtocols(protocolsParameters);
> // TLS 1.0 / 1.1 have been disabled by jetty 9.3
> // this is a first attempt to re-enable them
> // see
> // -
> https://www.eclipse.org/jetty/documentation/9.3.x/configuring-ssl.html
> // - https://github.com/eclipse/jetty.project/issues/860
> // - http://camel.apache.org/camel-configuration-utilities.html
> FilterParameters cipherParameters = new FilterParameters();
> cipherParameters.getInclude().add(".*");
> cipherParameters.getExclude().add("^.*_(MD5|SHA1)$");
> scp.setCipherSuitesFilter(cipherParameters);
> return scp;
> }
> {code}
> A workaround is to use a custom JettyHttpComponent9 implementation that sets
> the excludedCipherSuites manually like depicted below:
> {code:title=Workaround|borderStyle=solid}
> /**
>* A custom jetty http component which explicitly sets the
> excludedCipherSuites during creation of
>* the jetty connector.
>*
>* Why? It seems camel does not push included/excluded cipherSuites from
> {@link
>* SSLContextParameters} to the {@link SslContextFactory} nor does push
> explicitly listed cipher
>* suites (i.e. like TLS_RSA_WITH_AES_256_CBC_SHA) to the Jetty
> SSL context factory.
>*/
> public static class HackedJettyHttpComponent extends JettyHttpComponent9 {
> @Override
> protected AbstractConnector createConnectorJettyInternal(Server server,
>
> JettyHttpEndpoint endpoint,
>
> SslContextFactory sslcf) {
> sslcf.setExcludeCipherSuites("^.*_(MD5|SHA1)$");
> return super.createConnectorJettyInternal(server, endpoint, sslcf);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
[jira] [Updated] (CAMEL-11516) FtpConsumerFileSplitTest fails on windows due to platform line.seperator
[ https://issues.apache.org/jira/browse/CAMEL-11516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] onder sezgin updated CAMEL-11516: - Labels: Novice (was: ) > FtpConsumerFileSplitTest fails on windows due to platform line.seperator > > > Key: CAMEL-11516 > URL: https://issues.apache.org/jira/browse/CAMEL-11516 > Project: Camel > Issue Type: Test > Components: camel-ftp >Affects Versions: 2.19.1 > Environment: On Windows >Reporter: onder sezgin >Assignee: onder sezgin >Priority: Trivial > Labels: Novice > Fix For: 2.19.2, 2.20.0 > > > [ERROR] Failures: > [ERROR] > org.apache.camel.component.file.remote.FtpConsumerFileSplitTest.testFtpR > oute(org.apache.camel.component.file.remote.FtpConsumerFileSplitTest) > [ERROR] Run 1: FtpConsumerFileSplitTest.testFtpRoute:42 mock://result Body > of > >essage: 0. Expected: but was: [ERROR] Run 2: FtpConsumerFileSplitTest.testFtpRoute:42 mock://result Body > of > >essage: 0. Expected: but was: [ERROR] Run 3: FtpConsumerFileSplitTest.testFtpRoute:42 mock://result Body > of > >essage: 0. Expected: but was:
[jira] [Assigned] (CAMEL-11509) Cannot set content type with parameters without specifying charset
[
https://issues.apache.org/jira/browse/CAMEL-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
onder sezgin reassigned CAMEL-11509:
Assignee: onder sezgin
> Cannot set content type with parameters without specifying charset
> --
>
> Key: CAMEL-11509
> URL: https://issues.apache.org/jira/browse/CAMEL-11509
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 2.19.0, 2.19.1
>Reporter: Steffen F.
>Assignee: onder sezgin
> Fix For: 2.19.2, 2.20.0
>
>
> When setting a content type that does not contain a charset parameter, for
> example this:
> {noformat}
> .setHeader("Content-Type", constant("application/json;odata=verbose"))
> {noformat}
> the route will fail with the following exception:
> {noformat}
> java.lang.IllegalArgumentException: MIME type may not contain reserved
> characters
> at org.apache.http.util.Args.check(Args.java:36)
> at org.apache.http.entity.ContentType.create(ContentType.java:206)
> at org.apache.http.entity.ContentType.create(ContentType.java:218)
> at
> org.apache.camel.component.http4.HttpProducer.createRequestEntity(HttpProducer.java:511)
> {noformat}
> although this is clearly a valid content type according to the RFC:
> https://tools.ietf.org/html/rfc2045#section-5.1
> This only affects version 2.19+, because in version 4.4.6 of the
> httpcomponents-core library, they changed the behavior of {{create}} to check
> the mime type for semicolons, which it previously didn't. If we, however,
> also use a charset parameter, you will call the {{parse}} method instead:
> {noformat}
> if (contentTypeString != null) {
> if (contentTypeString.indexOf("charset") > 0) {
> contentType = ContentType.parse(contentTypeString);
> } else {
> contentType = ContentType.create(contentTypeString);
> }
> }
> {noformat}
> There can be all kind of different parameters, though. Instead of checking
> for charset, it should rather check for the existence of a semicolon.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11509) Cannot set content type with parameters without specifying charset
[
https://issues.apache.org/jira/browse/CAMEL-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074730#comment-16074730
]
onder sezgin commented on CAMEL-11509:
--
even if you pass like this,
{noformat}
.setHeader("Content-Type", constant("application/json;odata=verbose"))
{noformat}
the endpoint sees the content-type like "application/json; odata=verbose".
please notice the space after ;
> Cannot set content type with parameters without specifying charset
> --
>
> Key: CAMEL-11509
> URL: https://issues.apache.org/jira/browse/CAMEL-11509
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 2.19.0, 2.19.1
>Reporter: Steffen F.
>Assignee: onder sezgin
> Fix For: 2.19.2, 2.20.0
>
>
> When setting a content type that does not contain a charset parameter, for
> example this:
> {noformat}
> .setHeader("Content-Type", constant("application/json;odata=verbose"))
> {noformat}
> the route will fail with the following exception:
> {noformat}
> java.lang.IllegalArgumentException: MIME type may not contain reserved
> characters
> at org.apache.http.util.Args.check(Args.java:36)
> at org.apache.http.entity.ContentType.create(ContentType.java:206)
> at org.apache.http.entity.ContentType.create(ContentType.java:218)
> at
> org.apache.camel.component.http4.HttpProducer.createRequestEntity(HttpProducer.java:511)
> {noformat}
> although this is clearly a valid content type according to the RFC:
> https://tools.ietf.org/html/rfc2045#section-5.1
> This only affects version 2.19+, because in version 4.4.6 of the
> httpcomponents-core library, they changed the behavior of {{create}} to check
> the mime type for semicolons, which it previously didn't. If we, however,
> also use a charset parameter, you will call the {{parse}} method instead:
> {noformat}
> if (contentTypeString != null) {
> if (contentTypeString.indexOf("charset") > 0) {
> contentType = ContentType.parse(contentTypeString);
> } else {
> contentType = ContentType.create(contentTypeString);
> }
> }
> {noformat}
> There can be all kind of different parameters, though. Instead of checking
> for charset, it should rather check for the existence of a semicolon.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (CAMEL-11509) Cannot set content type with parameters without specifying charset
[
https://issues.apache.org/jira/browse/CAMEL-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074730#comment-16074730
]
onder sezgin edited comment on CAMEL-11509 at 7/5/17 1:27 PM:
--
even if you pass like this,
{noformat}
.setHeader("Content-Type", constant("application/json;odata=verbose"))
{noformat}
the endpoint sees the content-type like "application/json; odata=verbose".
please notice the space after ;
that's why there is a trick in this line;
https://github.com/apache/camel/pull/1805#discussion-diff-125638439R92
was (Author: onders):
even if you pass like this,
{noformat}
.setHeader("Content-Type", constant("application/json;odata=verbose"))
{noformat}
the endpoint sees the content-type like "application/json; odata=verbose".
please notice the space after ;
> Cannot set content type with parameters without specifying charset
> --
>
> Key: CAMEL-11509
> URL: https://issues.apache.org/jira/browse/CAMEL-11509
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 2.19.0, 2.19.1
>Reporter: Steffen F.
>Assignee: onder sezgin
> Fix For: 2.19.2, 2.20.0
>
>
> When setting a content type that does not contain a charset parameter, for
> example this:
> {noformat}
> .setHeader("Content-Type", constant("application/json;odata=verbose"))
> {noformat}
> the route will fail with the following exception:
> {noformat}
> java.lang.IllegalArgumentException: MIME type may not contain reserved
> characters
> at org.apache.http.util.Args.check(Args.java:36)
> at org.apache.http.entity.ContentType.create(ContentType.java:206)
> at org.apache.http.entity.ContentType.create(ContentType.java:218)
> at
> org.apache.camel.component.http4.HttpProducer.createRequestEntity(HttpProducer.java:511)
> {noformat}
> although this is clearly a valid content type according to the RFC:
> https://tools.ietf.org/html/rfc2045#section-5.1
> This only affects version 2.19+, because in version 4.4.6 of the
> httpcomponents-core library, they changed the behavior of {{create}} to check
> the mime type for semicolons, which it previously didn't. If we, however,
> also use a charset parameter, you will call the {{parse}} method instead:
> {noformat}
> if (contentTypeString != null) {
> if (contentTypeString.indexOf("charset") > 0) {
> contentType = ContentType.parse(contentTypeString);
> } else {
> contentType = ContentType.create(contentTypeString);
> }
> }
> {noformat}
> There can be all kind of different parameters, though. Instead of checking
> for charset, it should rather check for the existence of a semicolon.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (CAMEL-11516) FtpConsumerFileSplitTest fails on windows due to platform line.seperator
onder sezgin created CAMEL-11516: Summary: FtpConsumerFileSplitTest fails on windows due to platform line.seperator Key: CAMEL-11516 URL: https://issues.apache.org/jira/browse/CAMEL-11516 Project: Camel Issue Type: Test Components: camel-ftp Affects Versions: 2.19.1 Environment: On Windows Reporter: onder sezgin Assignee: onder sezgin Priority: Trivial Fix For: 2.19.2, 2.20.0 [ERROR] Failures: [ERROR] org.apache.camel.component.file.remote.FtpConsumerFileSplitTest.testFtpR oute(org.apache.camel.component.file.remote.FtpConsumerFileSplitTest) [ERROR] Run 1: FtpConsumerFileSplitTest.testFtpRoute:42 mock://result Body of >essage: 0. Expected: but was: essage: 0. Expected: but was: essage: 0. Expected: but was:
