[SECURITY] New security advisory CVE-2017-12634 released for Apache Camel

[Andrea Cosentino]

A new security advisory has been released for Apache Camel, that is fixed in
the recent 2.19.4 and 2.20.1 releases:

 CVE-2017-12634: Apache Camel's Castor unmarshalling operation is vulnerableto 
Remote Code Execution attacks

The full text of the advisory is the following:

CVE-2017-12634: Apache Camel's Castor unmarshalling operation is vulnerable to 
Remote Code Execution attacks 

Severity: MEDIUM

Vendor: The Apache Software Foundation

Versions Affected: Camel 2.19.0 to 2.19.3 and Camel 2.20.0. The unsupported 
Camel 2.x (2.18 and earlier) versions may be also affected.

Description: Apache Camel's camel-castor component is vulnerable to Java 
objectde-serialisation vulnerability. De-serializing untrusted data can lead to 
security flaws.

Mitigation: 2.19.x users should upgrade to 2.19.4, 2.20.0 users should upgrade 
to 2.20.1. 

The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-11929 refers to 
the various commits that resovoled the issue, and have more details.

Credit: This issue was discovered by Man Yue Mo  from 
Semmle/lgtm.com.On behalf of the Apache Camel PMC

On behalf of the Apache Camel PMC

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd

Re: Inline code snippets in online documentation are broken

[Andrea Cosentino]

We are migrating docs, the official docs is on github.

There is a news in the front page.

http://camel.apache.org/

By the way we are working on a new website, and currently only github is 
official docs.



--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd






On Tuesday, November 14, 2017, 4:00:02 PM GMT+1, Stephane Bailliez 
<sbaill...@gmail.com> wrote: 





FYI, just noticed that all the inline code snippets are broken on the site

For example:
http://camel.apache.org/ftp2.html

Cheers,

-- stephane

R: code formatting missing in manual pages

[Andrea Cosentino]

We are in the process of migrating to a new site based on github docs. The 
official docs is actually under github

Inviato da Yahoo Mail su Android 
 
  Il ven, 10 nov, 2017 alle 17:22, Jarmo Sorvari ha 
scritto:   Hi!

E.g., on page http://camel.apache.org/sql-component.html, formatting is 
missing in code examples. This is true for many (all?) other pages, too.

Especially long examples are a pain  to read. Is this a known problem 
and temporary? Could someone take a look at this, please?

Thanks in advance!

Jarmo

  

Re: Mysql-connector 8.0.8 not in maven, dependency error

[Andrea Cosentino]

Did you try with a different Karaf version?

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd




 
 
 On Thursday, October 12, 2017, 2:19:06 PM GMT+2, Farkas Lajos 
<farkas.la...@globustravel.com> wrote: 





Hello,

it seems that camel-ftp is trying to install 
org.ops4j.pax.logging.pax-logging-api, which needs mysql-connect-8.0.8

Regards,
Lajos Farkas

On 10/12/17 10:16 AM, Claus Ibsen wrote:
> Hi
>
> The camel-ftp does not use mysql at all, so it must be something else
> that you are doing that causes this.
>
> On Wed, Oct 11, 2017 at 7:44 PM, Farkas Lajos
> <farkas.la...@globustravel.com> wrote:
>> Hello Camel users,
>>
>>
>> i'm trying to install camel-ftp on karaf 4.0.4, and i'm getting this error:
>>
>>
>> 2017-10-11 19:24:45,106 | WARN  | ool-379-thread-7 | AetherBasedResolver
>> | 5 - org.ops4j.pax.logging.pax-logging-api - 1.8.5 | Error resolving
>> artifactmysql:mysql-connector-java:jar:8.0.8:Could not find artifact
>> mysql:mysql-connector-java:jar:8.0.8 in central
>> (http://repo1.maven.org/maven2/)
>> shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not
>> find artifact mysql:mysql-connector-java:jar:8.0.8 in central
>> (http://repo1.maven.org/maven2/)
>>
>>
>> in the maven repository, there is no 8.0.8 version for mysql connector, but
>> for version 8.0.8-dmr.
>>
>> Is there a way to install camel-ftp, without this dependency?
>>
>> Thank you.
>>
>>
>>
>
>

Re: Issue with camel-elasticsearch5 component

[Andrea Cosentino]

Here is the JIRA in SM
https://issues.apache.org/jira/browse/SM-3454

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Friday, August 4, 2017, 1:46:13 PM GMT+2, Claus Ibsen 
<claus.ib...@gmail.com> wrote:


Try turning on dynamic import on those ES bundles via
dev:import-dynamic karaf command.

For the issue with the SMX bundle you can log that in the ServiceMix
JIRA ticket or in CAMEL. Then Andreas from the Camel/SMX team can take
a look, and get those packages to be imported|exported.


On Wed, Aug 2, 2017 at 8:17 AM, smanish <manish.shu...@brodos.net> wrote:
> It is about camel-elasticsearch5 component.
> https://github.com/apache/camel/blob/master/platforms/karaf/features/src/main/resources/features.xml#L566-L580
>
> That basically use following bundles.
> 1 . Elasticsearch-Bundle
> http://mvnrepository.com/artifact/org.apache.servicemix.bundles/org.apache.servicemix.bundles.elasticsearch/5.4.3_1
>
> 2. Elasticsearch-Client Bundle
> https://mvnrepository.com/artifact/org.apache.servicemix.bundles/org.apache.servicemix.bundles.elasticsearch-client/5.4.3_1
>
> In order to work with elasticsearch 5 you need TransportClient as mentioned
> in
> https://www.elastic.co/guide/en/elasticsearch/client/java-api/5.5/transport-client.html
> which is available in Elasticsearch bundle
>
> To get the TransportClient for first step you need to use
> PreBuiltTransportClient which is available in Elasticsearch-Client bundle.
>
> Now the problem is that Elasticsearch-Client which is expected to return
> TransportClient does not have it and also not importing it and gives class
> not found exception " Caused by: java.lang.ClassNotFoundException:
> org.elasticsearch.client.transport.TransportClient not found by
> org.apache.servicemix.bundles.elasticsearch-client [127]"
>
> So the question is how it is expected to work?
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Issue-with-camel-elasticsearch5-component-tp5809063.html
> Sent from the Camel - Users mailing list archive at Nabble.com.




-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

R: Re: Re: Streaming Cassandra Table ( Polling every 5s - Near Realtime )

[Andrea Cosentino]

Maybe you need to learn a bit about camel. What camel is and what is a 
consumer.There is a lot of documentation on the website. 
 
  Il mer, 26 lug, 2017 alle 21:15, SenthilKumar K<senthilec...@gmail.com> ha 
scritto:   Not sure if i already have an answer... Still i'm not clear :-( ..

Questions :
    1)  *Can this Cassandra Camel Consumer opt for my Use Case ?*
      2) If Yes ( for above Q) , How to use Cassandra Consumer ?  *It would
be great if i get sample code !*


--Senthil

On Thu, Jul 27, 2017 at 12:41 AM, Andrea Cosentino <ancosen1...@yahoo.com>
wrote:

> You already have an answer.
>
> Il mer, 26 lug, 2017 alle 21:09, SenthilKumar K
> <senthilec...@gmail.com> ha scritto:
> Ping !!!
>
> It would be great if anybody help me here :-) ..
>
> --Senthil
>
> On Wed, Jul 26, 2017 at 4:47 PM, SenthilKumar K <senthilec...@gmail.com>
> wrote:
>
> > Adding Dev Group ...
> >
> >
> > --Senthil
> >
> > On Wed, Jul 26, 2017 at 3:14 PM, SenthilKumar K <senthilec...@gmail.com>
> > wrote:
> >
> >> Hello Camel Users ,  Recently i started exploring possibilities of
> >> streaming data from Cassandra Table for my use case, found *
> https://github.com/apache/camel/tree/master/components/camel-cassandraql
> >> <https://github.com/apache/camel/tree/master/components/
> camel-cassandraql>*
>
> >> . This seems to be good candidate for my use case!
> >>
> >>
> >> Use Case :
> >> ProcessA  --Write---> Cassandra <---READ--- ProcessB ---> Analytics
> System
> >>
> >> ProcessA is responsible to write data continuously to apache cassandra
> >> and in near realtime another process read/parse and send it to
> downstream
> >> system.
> >>
> >> Consumer :
> >> https://github.com/oscerd/camel-cassandra/blob/master/src/
> >> main/java/com/github/oscerd/component/cassandra/CassandraConsumer.java
> >>
> >> I want to start the Consumer Process which should run 24/7 and start
> >> processing unless until it gets Kill Request..
> >>
> >> Here is the Code i tried:
> >> public class CassandraConsumer  {
> >> public static void main(String[] args) throws Exception {
> >>    CassandraEndpoint endpoint = new CassandraEndpoint();
> >>    endpoint.setPort("9042");
> >>    endpoint.setKeyspace("test");
> >>    endpoint.setHost("127.0.0.1");
> >>    endpoint.setTable("stream_data");
> >>    endpoint.setPollingQuery("select * from stream_data");
> >>    Processor p = new Processor() {
> >> public void process(Exchange exchange) throws Exception {
> >> ResultSet body = (ResultSet) exchange.getIn().getBody();
> >> List allRows = body.all();
> >> for(Row r : allRows ){
> >> System.out.println(r.getInt("id")+"  "+r.getString("data"));
> >> }
> >> }
> >> };
> >> endpoint.createConsumer(p).start();
> >> }
> >> }
> >>
> >> This is not working ( I dont know how to use Consumer ).
> >>
> >> Questions :
> >>      1)  Can this Cassandra Camel Consumer opt for my Use Case ?
> >>      2) If Yes ( for above Q) , How to use Cassandra Consumer ?  It
> >> would be great if i get sample code !
> >>
> >>
> >> --Senthil
> >>
> >
> >
>
>
  

R: Re: Streaming Cassandra Table ( Polling every 5s - Near Realtime )

[Andrea Cosentino]

You already have an answer. 
 
  Il mer, 26 lug, 2017 alle 21:09, SenthilKumar K ha 
scritto:   Ping !!!

It would be great if anybody help me here :-) ..

--Senthil

On Wed, Jul 26, 2017 at 4:47 PM, SenthilKumar K 
wrote:

> Adding Dev Group ...
>
>
> --Senthil
>
> On Wed, Jul 26, 2017 at 3:14 PM, SenthilKumar K 
> wrote:
>
>> Hello Camel Users ,  Recently i started exploring possibilities of
>> streaming data from Cassandra Table for my use case, found 
>> *https://github.com/apache/camel/tree/master/components/camel-cassandraql
>> *
>> . This seems to be good candidate for my use case!
>>
>>
>> Use Case :
>> ProcessA  --Write---> Cassandra <---READ--- ProcessB ---> Analytics System
>>
>> ProcessA is responsible to write data continuously to apache cassandra
>> and in near realtime another process read/parse and send it to downstream
>> system.
>>
>> Consumer :
>> https://github.com/oscerd/camel-cassandra/blob/master/src/
>> main/java/com/github/oscerd/component/cassandra/CassandraConsumer.java
>>
>> I want to start the Consumer Process which should run 24/7 and start
>> processing unless until it gets Kill Request..
>>
>> Here is the Code i tried:
>> public class CassandraConsumer  {
>> public static void main(String[] args) throws Exception {
>>    CassandraEndpoint endpoint = new CassandraEndpoint();
>>    endpoint.setPort("9042");
>>    endpoint.setKeyspace("test");
>>    endpoint.setHost("127.0.0.1");
>>    endpoint.setTable("stream_data");
>>    endpoint.setPollingQuery("select * from stream_data");
>>    Processor p = new Processor() {
>> public void process(Exchange exchange) throws Exception {
>> ResultSet body = (ResultSet) exchange.getIn().getBody();
>> List allRows = body.all();
>> for(Row r : allRows ){
>> System.out.println(r.getInt("id")+"  "+r.getString("data"));
>> }
>> }
>> };
>> endpoint.createConsumer(p).start();
>> }
>> }
>>
>> This is not working ( I dont know how to use Consumer ).
>>
>> Questions :
>>      1)  Can this Cassandra Camel Consumer opt for my Use Case ?
>>      2) If Yes ( for above Q) , How to use Cassandra Consumer ?  It
>> would be great if i get sample code !
>>
>>
>> --Senthil
>>
>
>
  

Re: Access Karaf ENV variable from Camel Spring context

[Andrea Cosentino]

If you are using JBoss Fuse you have to ask to RH support.

 
--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd


On Monday, June 26, 2017 2:31 PM, "Leber, Thomas" <thomas.le...@omnetric.com> 
wrote:



Hi all,


I have deployed a Spring Camel context on a stock Karaf container.

I have set a env variable like this:


JBossFuse:admin@devTL> env test

null

JBossFuse:admin@devTL> env test hi_all

JBossFuse:admin@devTL> env test

hi_all

JBossFuse:admin@devTL>


Now I want to access this variable via:


String test = exchange.getContext().resolvePropertyPlaceholders("{{env:test}}");


Unfortunatley this always returns 

java.lang.IllegalArgumentException: Property with key [env:test] using function 
[env] returned null value which is not allowed, from input: {{env:test}}


also I tried {{karaf.test}}

String test = 
exchange.getContext().resolvePropertyPlaceholders("{{karaf.test}}");


But I get


java.lang.IllegalArgumentException: PropertiesComponent with name properties 
must be defined in CamelContext to support property placeholders. Property with 
key [karaf.test] not found in properties from text: {{karaf.test}}


Meanwhile

String test = 
exchange.getContext().resolvePropertyPlaceholders("{{karaf:test}}");

Returns simply "test"



Any suggestions or is this simply not possible?


Best

Thomas Leber

thomas.le...@omnetric.com

Re: Need help on Camel-Ignite Coomponent

[Andrea Cosentino]

You have to use only one URI in the Ignite .to and define the headers you'll 
need in a processor between from and to.

from("mqtt:bar?subscribeTopicName=test=tcp://localhost:1883").process(new 
Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(IgniteConstants.IGNITE_CACHE_KEY, "abcd");
}
})

.to("ignite-cache:cache:myCacheName?operation=PUT");


What you were trying to do is using a component with URI 1234, one with URI 
IgniteConstants.IGNITE_CACHE_KEY and one with URI abcd.
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd


On Wednesday, May 31, 2017 3:15 PM, solomon <austin.solomon...@gmail.com> wrote:



Hi,


I am trying to read the data from Camel-MQTT and PUT the message into

Camel-Ignite' cache within camel context.


I am getting error while doing so...  searched online for examples for

Camel-Ignite component, but I didn't get any examples.


Camel version I'm using is 2.17.2


My code is like this :


private static final String HOST = "localhost:47500..47509";



public static void main(String[] args) throws Exception {



CamelContext context = new DefaultCamelContext();  



TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();

ipFinder.setAddresses(Collections.singletonList(HOST));

   TcpDiscoverySpi discoSpi = new TcpDiscoverySpi();

discoSpi.setIpFinder(ipFinder);

  

IgniteConfiguration cfg1 = new IgniteConfiguration();

cfg1.setDiscoverySpi(discoSpi);

cfg1.setPeerClassLoadingEnabled(false);



CacheConfiguration cacheCfg = new CacheConfiguration<String, String>();

cacheCfg.setName("myCacheName");

cacheCfg.setCacheMode(CacheMode.PARTITIONED);

cfg1.setCacheConfiguration(cacheCfg);

  

IgniteComponent igniteComponent=new IgniteComponent();

  

context.addComponent(getScheme(),

IgniteComponent.fromConfiguration(cfg1));

try {

context.addRoutes(new RouteBuilder() {  

@Override

public void configure() throws Exception {

  

from("mqtt:bar?subscribeTopicName=test=tcp://localhost:1883")

.to("ignite-cache:cache:myCacheName?operation=PUT", "1234",

IgniteConstants.IGNITE_CACHE_KEY, "abcd");

}

});

} catch (Exception e) {

e.printStackTrace();

}



context.start();


// let it run for 5 minutes before shutting down

Thread.sleep(5 * 60 * 1000);

}



private static String getScheme() {

return "ignite-cache";

  }


Error : 


Exception in thread "main" org.apache.camel.FailedToCreateRouteException:

Failed to create route route1 at: >>> To[1234] <<< in route:

Route(route1)[[From[mqtt:bar?subscribeTopicName=test=tc... because of

No endpoint could be found for: 1234, please check your classpath contains

the needed Camel component jar.

at

org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1072)

at

org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:196)

at

org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:974)

at

org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:3301)

at

org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3024)

at

org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:175)

at

org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:2854)

at

org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:2850)

at

org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:2873)

at

org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:2850)

at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)

at

org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:2819)

at com.tg.camelTest.CamelIgnite.main(CamelIgnite.java:81)

Caused by: org.apache.camel.NoSuchEndpointException: No endpoint could be

found for: 1234, please check your classpath contains the needed Camel

component jar.

at

org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:81)

at

org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:211)

at

org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:107)

at

org.apache

Re: Camel-hibernate issue Unable to convert value org.springframework.orm.hibernate4.LocalSessionFactoryBean@59a6b72c to type org.hibernate.SessionFactory

[Andrea Cosentino]

If you are using Fuse you've to ask to Red Hat support.

 
--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd


On Friday, May 26, 2017 8:23 AM, sarada.ch <sarada.sha...@gmail.com> wrote:



Hi All


I am trying camel_hibernate  and ran into compatibility issue. Camel version

2.17 and JBoss Fuse 6.3 I am using Blueprint DSL


/Error message :/ 

*Unable to convert value

org.springframework.orm.hibernate4.LocalSessionFactoryBean@59a6b72c to type

org.hibernate.SessionFactory*


/Camel.xml/




http://www.osgi.org/xmlns/blueprint/v1.0.0;

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;

xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0

https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd   


http://camel.apache.org/schema/blueprint

http://camel.apache.org/schema/blueprint/camel-blueprint.xsd 

http://www.springframework.org/schema/beans

http://www.springframework.org/schema/beans/spring-beans.xsd;>























org.apacheextras.camel.component.hibernate.HibernateComponen*t"

id="hibernate">







org.springframework.orm.hibernate4.LocalSessionFactoryBean*"

id="sessionFactory">







com.x.dto.ReferenceTable









hibernate.dialect=org.hibernate.dialect.SQLServerDialect























http://camel.apache.org/schema/blueprint;>
















Any help is accpreciated





--

View this message in context: 
http://camel.465427.n5.nabble.com/Camel-hibernate-issue-Unable-to-convert-value-org-springframework-orm-hibernate4-LocalSessionFactoryy-tp5800751.html

Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel with SSL and HostNameVerifier

[Andrea Cosentino]

What did you try?

 
--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd


On Friday, May 12, 2017 8:10 AM, Pankaj Kumar <pankaj.bsr2...@gmail.com> wrote:



Hi All,

I'm new to camel. Plese suggest me how Ican change this class into camel

route xml. Plese give me suggestions



import java.io.BufferedReader;

import java.io.InputStream;

import java.io.InputStreamReader;

import java.io.OutputStream;

import java.io.OutputStreamWriter;

import java.io.UnsupportedEncodingException;

import java.net.InetSocketAddress;

import java.net.Proxy;

import java.net.URL;

import java.security.KeyManagementException;

import java.security.NoSuchAlgorithmException;

import java.security.SecureRandom;

import java.security.cert.CertificateException;

import java.security.cert.X509Certificate;


import javax.inject.Named;

import javax.net.ssl.HostnameVerifier;

import javax.net.ssl.HttpsURLConnection;

import javax.net.ssl.KeyManager;

import javax.net.ssl.SSLContext;

import javax.net.ssl.SSLSession;

import javax.net.ssl.SSLSocketFactory;

import javax.net.ssl.TrustManager;

import javax.net.ssl.X509TrustManager;


import org.slf4j.Logger;

import org.slf4j.LoggerFactory;

import org.springframework.beans.factory.annotation.Value;


public class RequestResponseIml implements RequestResponse {

@Value(value = "${proxy.host}")

private String proxyHost;

@Value(value = "${proxy.port}")

private String proxyPort;

@Value(value = "${SSL_CONTEXT}")

private String ssl_context_version;


public String invokeAction(String url, String token) throws Exception {


SSLContext sslcontext = null;

String response = "";

try {

sslcontext = SSLContext.getInstance(ssl_context_version);

sslcontext.init(new KeyManager[0], new TrustManager[] { new

TrustManager() }, new SecureRandom());


} catch (NoSuchAlgorithmException e) {

logger.info("Error NoSuchAlgorithmException " + 
e.getLocalizedMessage());

} catch (KeyManagementException e) {

logger.info("Error KeyManagementException " + 
e.getLocalizedMessage());

} catch (Exception e) {

logger.error("Exception in getting Instance of SSLContext: " +

e.toString());

throw e;

}


try {



SSLSocketFactory factory = sslcontext.getSocketFactory();



logger.info("Creating HttpsURLConnection");

HttpsURLConnection connection = null;

InputStream is = null;



Proxy proxy = new Proxy(Proxy.Type.HTTP, new 
InetSocketAddress(proxyHost,

Integer.parseInt(proxyPort)));



connection = (HttpsURLConnection) new 
URL(url).openConnection(proxy);

logger.info("HttpsURLConnection has created "+connection);  
   

 connection.setRequestMethod("POST");



connection.setRequestProperty("Content-Type","application/x-www-form-urlencoded");


 connection.setRequestProperty("Content-Length", "" +

Integer.toString(token.getBytes().length));

 connection.setRequestProperty("Content-Language", "en-US");
 

 connection.setUseCaches (false);

 connection.setDoInput(true);

 connection.setDoOutput(true);



 connection.setSSLSocketFactory(factory);

 logger.info("connection setSSLSocketFactory");

 connection.setHostnameVerifier(new HostnameVerifier());

 logger.info("connection setHostnameVerifier");



 OutputStream os = connection.getOutputStream();

 OutputStreamWriter osw = new OutputStreamWriter(os);

 osw.write(token);

 osw.flush();

 osw.close();


 is =connection.getInputStream();

  

 BufferedReader in = new BufferedReader(new InputStreamReader(is)); 
   

 response = in.readLine();

 

logger.info("Output from NSDL "+response);

 is.close();

 in.close();



} catch (UnsupportedEncodingException e) {

String encodeException = "Unsupported Encoding Exception - " +

e.getMessage();

logger.error(encodeException);

} catch(Exception e) {

   logger.info("Error in invokeAction - " + 
e.getLocalizedMessage());

   logger.info("Error in invokeAction StactTrace - " +

e.getStackTrace(

Re: camel-cmis: sessionhandling not working as expected

[Andrea Cosentino]

What is the camel version you're currently using? --Andrea Cosentino 
--Apache Camel PMC MemberApache Karaf 
CommitterApache Servicemix PMC MemberEmail: ancosen1985@yahoo.comTwitter: 
@oscerd2Github: oscerd 

On Wednesday, April 5, 2017 12:43 PM, "Meyfarth, Frank" 
<meyfa...@adesso.de> wrote:
 

 Hi everyone,

Maybe I’m just to dumb to get it, but I believe I have found a bug in
camel-cmis.

I use the following URI within a CMIS producer to send a query to the CMIS
system.

cmis:http://rabobank-air-dev01.test-server.ag:8080/alfresco/api/-default-/p
ublic/cmis/versions/1.1/atom?username=admin=admin=-de
fault-=true

As you can see, the server credentials are present as options within the
URI.

Unfortunately I always get HTTP code 401 Unauthorized. Although the
credentials are correct and verified, off course.

I already debugged into the component and found the following code in
org.apache.camel.component.cmis.CMISComponent:

...
00 protected Endpoint createEndpoint(String uri, final String remaining,
final Map<String, Object> parameters) throws Exception {
01    boolean queryMode = removeQueryMode(parameters);
02 
03    CMISSessionFacade sessionFacade = new CMISSessionFacade(remaining);
04    setProperties(sessionFacade, parameters);
05 
06    CMISEndpoint endpoint = new CMISEndpoint(uri, this, new
CMISSessionFacadeFactory() {
07        @Override
08        public CMISSessionFacade create() throws Exception {
09            CMISSessionFacade sessionFacade = new
CMISSessionFacade(remaining);
10            setProperties(sessionFacade, parameters);
11 
12            return sessionFacade;
13        }
14    });
15 
16    endpoint.setQueryMode(queryMode);
17 
18    return endpoint;
19 }

...

At the beginning of the method all options are still present in the
„parameters“ map. After the session facade has been created in line 03 of
the method its parameters get set by calling „setProperties“. This works
fine for the created session facade. But „setProperties“ removes the
properties which have been successfully set from the „parameters“ map.
Therefore parameters „username“ and „password“ are no longer present after
execution of line 04. Later, when the „create“ method of the anonymous
CMISEndpoint created in line 06 gets called, these are still not present
and therefore NULL. And this is what finally leads to the 401 return code.

Either I use the Endpoint in a wrong way. In that case probably someone
can explain to me how to use it.
Or this is actually a bug. In this case I could offer fixing or someone
else does it. Which would be appreciated.

Best regards and thanks for your help

Frank




-- 
Frank Meyfarth    
adesso AG                    T +49 231 7000-2380
Stockholmer Allee 20          F +49 231 7000-1000
44269 Dortmund                E meyfa...@adesso.de
                              www.adesso.de <http://www.adesso.de>
                              blog.adesso.de <http://blog.adesso.de>


---
    >>> business. people. technology. <<<
---

adesso AG mit Sitz in Dortmund
Vorstand: Michael Kenfenheuer (Vors.), Christoph Junge, Andreas Prenneis
Vorsitzender des Aufsichtsrates: Prof. Dr. Volker Gruhn
Amtsgericht Dortmund HRB 20663

https://www.wirmachendasjetzt.de/de/?utm_source=Banner%20_medium=E-Mail_campaign=DGT


   

Re: Exception not thrown on connect failed in Dynamic Routes

[Andrea Cosentino]

Camel 2.10.1 is too old. Try with a new release.
 
--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd


On Monday, March 27, 2017 11:16 AM, Shivu195 
<shivaranjini.shan...@blackrock.com> wrote:



We are facing the following issue. Whenever the camel route is unable to

connect to an endpoint(from a list of endpoints dynamically generated using

"@DynamicRouter"), it stops sftp-ing the files to all endpoints after the

failed endpoint and also it does not throw an error when the said endpoint

fails.


Is there a way to resolve this issue in this version itself, because an

exception doesn't seem to be thrown. (I have added the onException clause to

the camel route to handle any exception thrown)

*

Camel Version used: 2.10.1

JDK: 6*


This was a similar question raised on stack overflow.

http://stackoverflow.com/questions/40966290/apache-camel-dynamic-route-continue-when-exception-occurs





--

View this message in context: 
http://camel.465427.n5.nabble.com/Exception-not-thrown-on-connect-failed-in-Dynamic-Routes-tp5796268.html

Sent from the Camel - Users mailing list archive at Nabble.com.

Re: A simple Web Service consumer and producer using Apache Camel

[Andrea Cosentino]

Once again if you're using JBoss Fuse, please use RH support. --Andrea 
Cosentino --Apache Camel PMC MemberApache Karaf 
CommitterApache Servicemix CommitterEmail: ancosen1985@yahoo.comTwitter: 
@oscerd2Github: oscerd 

On Thursday, March 23, 2017 11:24 AM, anirban.gupta4 
<anirban.gup...@gmail.com> wrote:
 

 Hi,
 
I am new to JBoss Fuse and Apache Camel. In our project we have twoo WSDL of
producer and consumer. For one of the WSDL we have generated the
implementation class and we want to expose the endpoints in POJO dataFormat.
We have couple of questions here:
 
1. In wsdl2java, we find three types of generating Java codes, Client Side
code, Server side code and Implementation code. What are the differences
between those?
2. can I use some other tool like wsimport (not wsdl2java) and generate the
java classes and start from there, or we only need to use Apache CXF's
wsdl2java for generating the implementation classs?
 
Any other sugessions for this type of project will be helpful.
 
Regards,
Anirban.




--
View this message in context: 
http://camel.465427.n5.nabble.com/A-simple-Web-Service-consumer-and-producer-using-Apache-Camel-tp5796012.html
Sent from the Camel - Users mailing list archive at Nabble.com.


   

Re: Camel-JBPM component showing java.lang.NoSuchMethodError: org.kie.services.client.api.RemoteRuntimeEngineFactory.newRestBuilder()

[Andrea Cosentino]

For JBoss Fuse support you have to contact RH support.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, March 13, 2017 9:06 AM, vcamel9 <vcam...@outlook.com> wrote:
I have the following in my camel-context.xml

 

AbcProcess

http://host:8080/business-central?userName=user1=Pass1=com.abc.unit:Artifact:1.0.0-SNAPSHOT"/>





   Here is my Pom.xml setting:
 


org.jboss.resteasy
resteasy-jaxb-provider
2.3.10.Final-redhat-1


org.kie
kie-api
6.2.0.Final-redhat-4


org.kie
kie-internal
6.2.0.Final-redhat-4


org.kie
kie-ci
6.2.0.Final-redhat-4


org.kie.remote
kie-remote-client
provided
6.2.0.Final-redhat-4


org.jbpm
jbpm-audit
6.2.0.Final-redhat-4


org.jbpm
jbpm-runtime-manager
6.2.0.Final-redhat-4




   When I compile it compiles without any problem but when I deploy it gives
error after startup:
   Any leads will be appreciated:

   $ bash fuse
Please wait while JBoss Fuse is loading...
100%
[]
Exception in thread "SpringOsgiExtenderThread-2"
java.lang.NoSuchMethodError:
org.kie.services.client.api.RemoteRuntimeEngineFactory.newRestBuilder()Lorg/kie/remote/client/api/RemoteRestRuntimeEngineBuilder;
at
org.apache.camel.component.jbpm.JBPMEndpoint.createProducer(JBPMEndpoint.java:50)
at
org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:439)
at
org.apache.camel.impl.ProducerCache.acquireProducer(ProducerCache.java:160)
at org.apache.camel.processor.SendProcessor.doStart(SendProcessor.java:243)
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75)
at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:60)
at
org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:104)
at org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:90)
at
org.apache.camel.processor.DelegateAsyncProcessor.doStart(DelegateAsyncProcessor.java:79)
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75)
at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:60)
at
org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:104)
at org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:90)
at
org.apache.camel.processor.RedeliveryErrorHandler.doStart(RedeliveryErrorHandler.java:1372)
at
org.apache.camel.support.ChildServiceSupport.start(ChildServiceSupport.java:44)
at
org.apache.camel.support.ChildServiceSupport.start(ChildServiceSupport.java:31)
at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75)
at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:60)
at
org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:104)
at org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:90)
at
org.apache.camel.processor.interceptor.DefaultChannel.doStart(DefaultChannel.java:156)
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75)
at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:60)
at
org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:104)
at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:62)
at
org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:104)
at org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:90)
at
org.apache.camel.processor.MulticastProcessor.doStart(MulticastProcessor.java:1149)
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75)
at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:60)
at
org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:104)
at org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:90)
at
org.apache.camel.processor.DelegateAsyncProcessor.doStart(DelegateAsyncProcessor.java:79)
at org.apache.camel.support.ServiceSupport.star

Re: Camel for ElasticSearch

[Andrea Cosentino]

If you want to test the new component you can build Camel 2.19.0 from code or 
use the SNAPSHOT
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Tuesday, March 7, 2017 10:33 AM, ajnfde <konank...@gmail.com> wrote:
Ok thank you.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-for-ElasticSearch-tp5794992p5795004.html

Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel for ElasticSearch

[Andrea Cosentino]

In Camel 2.19.0 there will be a component for Elasticsearch 5.x support.

Actually it is not supported.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Tuesday, March 7, 2017 10:04 AM, ajnfde <konank...@gmail.com> wrote:
I want to send data to elasticSearch from camel using camel component
camel-elasticsearch-2.17.5 (and also 2.15.2).

The ElasticSearch version used is 5.2.2

But the ElasticsearchEndpoint.class refers to
org.elasticsearch.node.NodeBuilder and The ElasticsearchConstants interface
refers also to org.elasticsearch.action.WriteConsistencyLevel.

The 2 refered object have been removed from elasticserach-5.2.2.

Is it a bug in the camel component?

What Have I to do ?



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-for-ElasticSearch-tp5794992.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Facebook component Documentation on website

[Andrea Cosentino]

The .adoc are the updated one.

We are migrating all the documentation to .adoc.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Friday, February 17, 2017 10:42 AM, Ravindra Godbole <godbol...@gmail.com> 
wrote:
As per the documentation available for this component on the website [
http://camel.apache.org/facebook.html ] , some endpoints are deprecated.

i.e. activities / checkins / interests / location / notes etc

It will be good if document mentions the Facebook API version with which
endpoint will work.

Also looked at the following page and endpoint information is missing

https://github.com/apache/camel/blob/master/components/camel-facebook/src/main/docs/facebook-component.adoc

Which is the source of truth if I have to update the information ?


-- 
- Ravi

*[ View My Youtube Channel ] <https://www.youtube.com/c/RavindraGodbole>*

Phone: +91 *98 509 760 91*

Re: [HEADS UP] - Camel Maven Plugin can now parse your source code and report invalid endpoints

[Andrea Cosentino]

Great work! 

Thanks!
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Friday, December 9, 2016 9:51 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:
Hi

Just a heads up about a new functionality coming in Camel 2.19.

I wrote a blog entry about it
http://www.davsclaus.com/2016/12/camel-maven-plugin-can-now-parse-your.html

You can find the documentation for the plugin at
https://github.com/apache/camel/blob/master/tooling/maven/camel-maven-plugin/src/main/docs/camel-maven-plugin.adoc

And we have enabled this on the Camel source code itself, where you
can run it at these maven modules

cd camel-core
mvn camel:validate -Pvalidate

cd components
mvn camel:validate -Pvalidate

cd tests/camel-itests
mvn camel:validate -Pvalidate

cd examples
mvn camel:validate -Pvalidate


The tooling uses the camel-route-parser
https://github.com/apache/camel/tree/master/tooling/camel-route-parser

Which can scan both java and xml routes.
Because people can write their java routes in endless ways, then the
parser may need a little nudge / improvement here and there if people
"draw outside the lines". However anyone who feels adventures is
welcome to help improve the parser, or report issues the find.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Cassandra 3/CQL 3.4 support for camel-cassandraql component

[Andrea Cosentino]

And Camel 2.18.0 is already released.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Thursday, December 1, 2016 9:38 AM, Andrea Cosentino <ancosen1...@yahoo.com> 
wrote:
Cassandra 3.x is supported from Camel 2.18.0

The driver used in 2.18.x branch is the 3.1.0
--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd




On Thursday, December 1, 2016 9:33 AM, Shoaib Khan <shoaibrazak...@gmail.com> 
wrote:
Hi,

Have tried camel from version 2.15.0 to 2.17.3 but have found that it still 
doesn't support Cassandra 3 or CQL version 3.4 yet.
Currently I can see camel-cassandraql component supports Cassandra version 
2.2.x  (Ex - apache-cassandra-2.2.8) and CQL Version 3.3.x (Ex - CQL spec 3.3.1)

Newer version such as Cassandra 3.x (Ex - apache-cassandra-3.9) and CQL Version 
3.4.x (Ex - CQL spec 3.4.2) is not yet supported.

Can we get it supported in the next release or is it already on the roadmap for 
coming releases or so, please advise?





Thanks & Regards,
Shoaib R Khan

Re: Cassandra 3/CQL 3.4 support for camel-cassandraql component

[Andrea Cosentino]

Cassandra 3.x is supported from Camel 2.18.0

The driver used in 2.18.x branch is the 3.1.0
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Thursday, December 1, 2016 9:33 AM, Shoaib Khan <shoaibrazak...@gmail.com> 
wrote:
Hi,

Have tried camel from version 2.15.0 to 2.17.3 but have found that it still 
doesn't support Cassandra 3 or CQL version 3.4 yet.
Currently I can see camel-cassandraql component supports Cassandra version 
2.2.x  (Ex - apache-cassandra-2.2.8) and CQL Version 3.3.x (Ex - CQL spec 3.3.1)

Newer version such as Cassandra 3.x (Ex - apache-cassandra-3.9) and CQL Version 
3.4.x (Ex - CQL spec 3.4.2) is not yet supported.

Can we get it supported in the next release or is it already on the roadmap for 
coming releases or so, please advise?





Thanks & Regards,
Shoaib R Khan

Re: Parsing unstructured Text in Camel

[Andrea Cosentino]

+1 for a Grok component :-)
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, November 28, 2016 9:29 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:
Hi

No there is no grok component in Camel. It would be really nice to
have, so you are welcome to log a JIRA ticket and help work on such a
component. We love contributions
http://camel.apache.org/contributing

I guess we can try to see if we can use the grok parser for elasticsearch
https://github.com/elastic/elasticsearch/tree/master/modules/ingest-common/src/main/java/org/elasticsearch/ingest/common






On Mon, Nov 28, 2016 at 9:03 AM, Jan Bernhardt <jbernha...@talend.com> wrote:
> Hi JB,
>
> I know self-coding is always possible, I was just wondering if there is an 
> easier way. For example logstash provides a grok parser for this:
> https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html
>
> I was wondering if camel provides something similar or if it would be a good 
> idea to add a camel-grok component.
>
> Best regards
> Jan
>
>> -Ursprüngliche Nachricht-
>> Von: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
>> Gesendet: Freitag, 25. November 2016 08:23
>> An: users@camel.apache.org
>> Cc: users@camel.apache.org
>> Betreff: Re: Parsing unstructured Text in Camel
>>
>> Hi Jan
>>
>> You can always use a custom processor for that.
>>
>> Regards
>> JB⁣
>>
>> On Nov 25, 2016, 08:16, at 08:16, Jan Bernhardt <jbernha...@talend.com>
>> wrote:
>> >Hi Camel Users,
>> >
>> >
>> >is there any component which helps me to parse plain text? Not JSON,
>> >XML or CSV.
>> >
>> >
>> >My use case is that I receive an E-Mail with multiple keywords in the
>> >Subject as well as in the body.
>> >
>> >I could not find any component that would help me to parse certain
>> >values from my multiline plaintext.
>> >
>> >
>> >I need something like freemarker but the other way around. Getting the
>> >fulltext and parsing certain values from this text (for example with
>> >regex).
>> >
>> >
>> >Any help would be much appreciated.
>> >
>> >
>> >Many thanks
>> >
>> >Jan



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2 

R: Passing a file through camel route

[Andrea Cosentino]

What have you tried? 
 
  Il gio, 24 nov, 2016 alle 16:08, Siddharth 
Patil ha scritto:   I am using camel 2.15.0 
. I want to pass the file through the camel
routes. I have two endpoints as server endpoint and client endpoint and
want to pass the file from server endpoint to client endpoint.
Currently I am able to receive the file at server endpoint, but not able
to pass it to the client endpoint. At server endpoint I am taking the
file in MultipartBody dataType. But the client endpoint is not able to
receive the file. I have wrote CXF route. Could you please suggest how to
receive the attached file at the client endpoint.


Regards,
Siddharth Patil










--
View this message in context: 
http://camel.465427.n5.nabble.com/Passing-a-file-through-camel-route-tp5790489.html
Sent from the Camel - Users mailing list archive at Nabble.com.  

Re: SQS FIFO

[Andrea Cosentino]

Maybe you can raise a JIRA for tracking this feature request.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, November 21, 2016 9:07 AM, "Jagwani, Prakash" 
<prakash.jagw...@bms.com> wrote:
Hi.

It looks like AWS-SQS is going to start supporting FIFO on their queues.

https://aws.amazon.com/about-aws/whats-new/2016/11/amazon-sqs-introduces-fifo-queues-with-exactly-once-processing-and-lower-prices-for-standard-queues/

Any ideas when we can do this with the Camel API or does it already work?


Thanks,
Prakash



This message (including any attachments) may contain confidential, proprietary, 
privileged and/or private information. The information is intended to be for 
the use of the individual or entity designated above. If you are not the 
intended recipient of this message, please notify the sender immediately, and 
delete the message and any attachments. Any disclosure, reproduction, 
distribution or other use of this message or any attachments by an individual 
or entity other than the intended recipient is prohibited. 

Re: camel-xmljson unmarhalling issue Caused by: java.lang.NoClassDefFoundError: Could not initialize class net.sf.json.JsonConfig

[Andrea Cosentino]

Hello,

You've to contact the JBoss Fuse support for problems with JBoss Fuse.

This is just the Apache Camel users mailing list.

 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, November 16, 2016 11:15 AM, bharadwaj <bharadwaj2...@gmail.com> 
wrote:
Hi,


Camel-xmljson is not working and throwing error runtime when enable camel
tracing.

Caused by: java.lang.NoClassDefFoundError: Could not initialize class
net.sf.json.JsonConfig


Jboss fuse 6.1.0

feature added - camel-xmljson

java version - 1.7.0_111





--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-xmljson-unmarhalling-issue-Caused-by-java-lang-NoClassDefFoundError-Could-not-initialize-classg-tp5790168.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-kafka Unknown parameters zookeeperHost, zookeeperPort

[Andrea Cosentino]

Because from 2.17 to 2.18 we upgrade Kafka to 0.10.x

https://github.com/apache/camel/blob/camel-2.18.x/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConfiguration.java

We are now using only the Java API for both producer and consumer.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Friday, November 11, 2016 9:17 AM, Damage_Shadow <sche...@outlook.com> wrote:
Using latest camel-parent / camel-kafka


org.apache.camel
camel-parent
2.18.0


1st problem - Need to explicitly add kafka_2.11 dependency as in camel-kafka
scope was changed to test.
2nd problem - Even if kafka_2.11 added, camel route fails to start :
Route:

from("kafka:{{UIKafkaIPAddress}}:{{KafkaPort}}" +
"?topic={{TopicName}}" +
"={{UIKafkaIPAddress}}" +
"={{ZookeeperPort}}" +
"={{KafkaGroupId}}" +
"=kafka.serializer.StringDecoder")
.log(LoggingLevel.INFO, simple("Raw ${body}").toString())

Exception : 

Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
resolve endpoint:
kafka://10.10.14.127:9092?groupId=group1=kafka.serializer.StringDecoder=topic=10.10.14.127=2181
due to: There are 2 parameters that couldn't be set on the endpoint. Check
the uri if the parameters are spelt correctly and that they are properties
of the endpoint. Unknown parameters=[{zookeeperHost=10.10.14.127,
zookeeperPort=2181}]

Why Zookeeper options were removed?



--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-kafka-Unknown-parameters-zookeeperHost-zookeeperPort-tp5790021.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: MongoDB component returning header "CamelMongoDbRecordsAffected" (2.18)

[Andrea Cosentino]

You're welcome to raise a JIRA for this as a feature request.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Thursday, November 3, 2016 11:57 AM, nbusy <nb...@enfoll.com> wrote:
I wonder if returning headers, like "CamelMongoDbRecordsAffected"
(MongoDbConstants.RECORDS_AFFECTED) will be re-introduced again in the
future release of the component or it's gone for good. It's still documented
as available feature and bringing it back is often just a couple of lines of
code per operation.



--
View this message in context: 
http://camel.465427.n5.nabble.com/MongoDB-component-returning-header-CamelMongoDbRecordsAffected-2-18-tp5789686.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: MongoDB / findById and ObjectId (issue in 2.18)

[Andrea Cosentino]

You're welcome to fill a JIRA for this if you think this is a bug.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Thursday, November 3, 2016 11:56 AM, nbusy <nb...@enfoll.com> wrote:
Hi All,

When using Camel MongoDB component with "operation=findById" and [_id] field
is happened to be a standard ObjectId(), it doesn't work anymore in v.2.18
(worked 2.17.3 and before).
Basically, to test you'd need to send org.bson.types.ObjectId in the message
body but it never finds a document.
The problem lies in MongoDbProducer.createDoFindById().
Fixed by replacing line:
String id =
exchange1.getIn().getMandatoryBody(String.class);
with
Object id = exchange1.getIn().getMandatoryBody();

My apologies if posted in a wrong forum.

Regards,
Nick



--
View this message in context: 
http://camel.465427.n5.nabble.com/MongoDB-findById-and-ObjectId-issue-in-2-18-tp5789685.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel 2.18.0 rabbitmq component fails under Karaf

[Andrea Cosentino]

It seems this is fixed in 3.6.6.

I tested 3.6.6-SNAPSHOT and it works fine.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, November 2, 2016 11:34 AM, souciance 
<souciance.eqdam.ras...@gmail.com> wrote:
Thanks for creating the issue.

On Wed, Nov 2, 2016 at 11:01 AM, Andrea Cosentino-2 [via Camel] <
ml-node+s465427n5789623...@n5.nabble.com> wrote:

> I opened an issue
>
> https://github.com/rabbitmq/rabbitmq-java-client/issues/211
>
>  --
> Andrea Cosentino
> --
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix Committer
> Email: [hidden email]
> <http:///user/SendEmail.jtp?type=node=5789623=0>
> Twitter: @oscerd2
> Github: oscerd
>
>
>
> On Wednesday, November 2, 2016 10:53 AM, Tomohisa Igarashi <[hidden email]
> <http:///user/SendEmail.jtp?type=node=5789623=1>> wrote:
> Yep, I actually can see "junit.framework,org.junit" in Import-Package of
> the amqp-client-3.6.4.jar!META-INF/MANIFEST.MF while it's not in 3.6.3.
> com.rabbitmq.client.test.ssl seems to be using it.
>
>
> On 11/02/2016 05:43 PM, Andrea Cosentino wrote:
>
> > The Rabbitmq-client OSGi bundle comes directly from Rabbitmq
> >
> > https://github.com/rabbitmq/rabbitmq-java-client/blob/
> master/pom.xml#L860-L886
> >
> > Between 3.6.3 and 3.6.4 something changes in the codebase of
> Rabbitmq-client, related to Junit I guess and I don't see changes in our
> component looking at the history
> >
> >
> > https://github.com/apache/camel/commits/master/components/camel-rabbitmq
> >
> > I noticed they are using bundlor
> >
> > https://github.com/rabbitmq/rabbitmq-java-client/tree/rabbitmq_v3_6_3
> >
> > https://github.com/rabbitmq/rabbitmq-java-client/tree/rabbitmq_v3_6_4
> >
> > https://github.com/rabbitmq/rabbitmq-java-client/tree/rabbitmq_v3_6_5
> >
> > --
> > Andrea Cosentino
> > --
> > Apache Camel PMC Member
> > Apache Karaf Committer
> > Apache Servicemix Committer
> > Email: [hidden email]
> <http:///user/SendEmail.jtp?type=node=5789623=2>
> > Twitter: @oscerd2
> > Github: oscerd
> >
> >
> >
> >
> > On Wednesday, November 2, 2016 9:30 AM, souciance <[hidden email]
> <http:///user/SendEmail.jtp?type=node=5789623=3>> wrote:
> > Sorry I didn't quit understand, do you mean camel-rabbitmq introduced
> the
> > dependency to junit or rabbitmq-client? Or is there somewhere we can
> look
> > to see the dependency to junit? Just for my own understanding. Thanks.
> >
> > On Wed, Nov 2, 2016 at 9:07 AM, Andrea Cosentino-2 [via Camel] <
> > [hidden email] <http:///user/SendEmail.jtp?type=node=5789623=4>>
> wrote:
> >
> >> I meant the dependency in the OSGi bundle.
> >>
> >> It should be something related to the maven-bundle-plugin configuration
> in
> >> the rabbitmq-client pom
> >>  --
> >> Andrea Cosentino
> >> --
> >> Apache Camel PMC Member
> >> Apache Karaf Committer
> >> Apache Servicemix Committer
> >> Email: [hidden email]
> >> <http:///user/SendEmail.jtp?type=node=5789615=0>
> >> Twitter: @oscerd2
> >> Github: oscerd
> >>
> >>
> >>
> >> On Wednesday, November 2, 2016 9:04 AM, souciance <[hidden email]
> >> <http:///user/SendEmail.jtp?type=node=5789615=1>> wrote:
> >> I had a look at the maven repo:
> >> https://mvnrepository.com/artifact/com.rabbitmq/amqp-client/3.6.4
> >>
> >> But junit is set as test dependency. It looks similar to 3.6.3. Or is
> that
> >> the wrong place to look?
> >>
> >> On Wed, Nov 2, 2016 at 8:27 AM, Andrea Cosentino-2 [via Camel] <
> >> [hidden email] <http:///user/SendEmail.jtp?type=node=5789615=2>>
>
> >> wrote:
> >>
> >>> It seems the dependency on Junit has been introduced with rabbitmq
> amqp
> >>> client in version 3.6.4
> >>>
> >>> Downgrade to 3.6.3 works fine.
> >>>  --
> >>> Andrea Cosentino
> >>> --
> >>> Apache Camel PMC Member
> >>> Apache Karaf Committer
> >>> Apache Servicemix Committer
> >>> Email: [hidden email]
> >>> <http:///user/SendEmail.jtp?type=node=578

Re: camel 2.18.0 rabbitmq component fails under Karaf

[Andrea Cosentino]

I opened an issue

https://github.com/rabbitmq/rabbitmq-java-client/issues/211

 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, November 2, 2016 10:53 AM, Tomohisa Igarashi 
<tm.igara...@gmail.com> wrote:
Yep, I actually can see "junit.framework,org.junit" in Import-Package of the 
amqp-client-3.6.4.jar!META-INF/MANIFEST.MF while it's not in 3.6.3. 
com.rabbitmq.client.test.ssl seems to be using it.


On 11/02/2016 05:43 PM, Andrea Cosentino wrote:
> The Rabbitmq-client OSGi bundle comes directly from Rabbitmq
>
> https://github.com/rabbitmq/rabbitmq-java-client/blob/master/pom.xml#L860-L886
>
> Between 3.6.3 and 3.6.4 something changes in the codebase of Rabbitmq-client, 
> related to Junit I guess and I don't see changes in our component looking at 
> the history
>
>
> https://github.com/apache/camel/commits/master/components/camel-rabbitmq
>
> I noticed they are using bundlor
>
> https://github.com/rabbitmq/rabbitmq-java-client/tree/rabbitmq_v3_6_3
>
> https://github.com/rabbitmq/rabbitmq-java-client/tree/rabbitmq_v3_6_4
>
> https://github.com/rabbitmq/rabbitmq-java-client/tree/rabbitmq_v3_6_5
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix Committer
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
> On Wednesday, November 2, 2016 9:30 AM, souciance 
> <souciance.eqdam.ras...@gmail.com> wrote:
> Sorry I didn't quit understand, do you mean camel-rabbitmq introduced the
> dependency to junit or rabbitmq-client? Or is there somewhere we can look
> to see the dependency to junit? Just for my own understanding. Thanks.
>
> On Wed, Nov 2, 2016 at 9:07 AM, Andrea Cosentino-2 [via Camel] <
> ml-node+s465427n5789615...@n5.nabble.com> wrote:
>
>> I meant the dependency in the OSGi bundle.
>>
>> It should be something related to the maven-bundle-plugin configuration in
>> the rabbitmq-client pom
>>  --
>> Andrea Cosentino
>> --
>> Apache Camel PMC Member
>> Apache Karaf Committer
>> Apache Servicemix Committer
>> Email: [hidden email]
>> <http:///user/SendEmail.jtp?type=node=5789615=0>
>> Twitter: @oscerd2
>> Github: oscerd
>>
>>
>>
>> On Wednesday, November 2, 2016 9:04 AM, souciance <[hidden email]
>> <http:///user/SendEmail.jtp?type=node=5789615=1>> wrote:
>> I had a look at the maven repo:
>> https://mvnrepository.com/artifact/com.rabbitmq/amqp-client/3.6.4
>>
>> But junit is set as test dependency. It looks similar to 3.6.3. Or is that
>> the wrong place to look?
>>
>> On Wed, Nov 2, 2016 at 8:27 AM, Andrea Cosentino-2 [via Camel] <
>> [hidden email] <http:///user/SendEmail.jtp?type=node=5789615=2>>
>> wrote:
>>
>>> It seems the dependency on Junit has been introduced with rabbitmq amqp
>>> client in version 3.6.4
>>>
>>> Downgrade to 3.6.3 works fine.
>>>  --
>>> Andrea Cosentino
>>> --
>>> Apache Camel PMC Member
>>> Apache Karaf Committer
>>> Apache Servicemix Committer
>>> Email: [hidden email]
>>> <http:///user/SendEmail.jtp?type=node=5789611=0>
>>> Twitter: @oscerd2
>>> Github: oscerd
>>>
>>>
>>>
>>> On Tuesday, November 1, 2016 11:59 AM, souciance <[hidden email]
>>> <http:///user/SendEmail.jtp?type=node=5789611=1>> wrote:
>>> Does anyone know why you need to do that?  It isn't necessary in 2.17.0
>>> and
>>> karaf 4.0.2.
>>>
>>> Den 31 okt. 2016 2:09 em skrev "gustavo.maurizio [via Camel]" <
>>> [hidden email] <http:///user/SendEmail.jtp?type=node=5789611=2>>:
>>
>>>
>>>> Andrea, fantastic!
>>>> Adding this  install -s wrap:mvn:junit/junit/4.12 before installing
>> made
>>>> it work! Thanks!!!
>>>>
>>>>
>>>>
>>>> --
>>>> If you reply to this email, your message will be added to the
>> discussion
>>>> below:
>>>> http://camel.465427.n5.nabble.com/camel-2-18-0-rabbitmq-
>>>> component-fails-under-Karaf-tp5789413p5789514.html
>>>> To start a new topic under Camel - Users, email
>>>> [hidden email] <http:///user/SendEmail.jtp?type=node=5789611=3&

Re: camel 2.18.0 rabbitmq component fails under Karaf

[Andrea Cosentino]

The Rabbitmq-client OSGi bundle comes directly from Rabbitmq

https://github.com/rabbitmq/rabbitmq-java-client/blob/master/pom.xml#L860-L886

Between 3.6.3 and 3.6.4 something changes in the codebase of Rabbitmq-client, 
related to Junit I guess and I don't see changes in our component looking at 
the history


https://github.com/apache/camel/commits/master/components/camel-rabbitmq

I noticed they are using bundlor

https://github.com/rabbitmq/rabbitmq-java-client/tree/rabbitmq_v3_6_3

https://github.com/rabbitmq/rabbitmq-java-client/tree/rabbitmq_v3_6_4

https://github.com/rabbitmq/rabbitmq-java-client/tree/rabbitmq_v3_6_5

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd




On Wednesday, November 2, 2016 9:30 AM, souciance 
<souciance.eqdam.ras...@gmail.com> wrote:
Sorry I didn't quit understand, do you mean camel-rabbitmq introduced the
dependency to junit or rabbitmq-client? Or is there somewhere we can look
to see the dependency to junit? Just for my own understanding. Thanks.

On Wed, Nov 2, 2016 at 9:07 AM, Andrea Cosentino-2 [via Camel] <
ml-node+s465427n5789615...@n5.nabble.com> wrote:

> I meant the dependency in the OSGi bundle.
>
> It should be something related to the maven-bundle-plugin configuration in
> the rabbitmq-client pom
>  --
> Andrea Cosentino
> --
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix Committer
> Email: [hidden email]
> <http:///user/SendEmail.jtp?type=node=5789615=0>
> Twitter: @oscerd2
> Github: oscerd
>
>
>
> On Wednesday, November 2, 2016 9:04 AM, souciance <[hidden email]
> <http:///user/SendEmail.jtp?type=node=5789615=1>> wrote:
> I had a look at the maven repo:
> https://mvnrepository.com/artifact/com.rabbitmq/amqp-client/3.6.4
>
> But junit is set as test dependency. It looks similar to 3.6.3. Or is that
> the wrong place to look?
>
> On Wed, Nov 2, 2016 at 8:27 AM, Andrea Cosentino-2 [via Camel] <
> [hidden email] <http:///user/SendEmail.jtp?type=node=5789615=2>>
> wrote:
>
> > It seems the dependency on Junit has been introduced with rabbitmq amqp
> > client in version 3.6.4
> >
> > Downgrade to 3.6.3 works fine.
> >  --
> > Andrea Cosentino
> > --
> > Apache Camel PMC Member
> > Apache Karaf Committer
> > Apache Servicemix Committer
> > Email: [hidden email]
> > <http:///user/SendEmail.jtp?type=node=5789611=0>
> > Twitter: @oscerd2
> > Github: oscerd
> >
> >
> >
> > On Tuesday, November 1, 2016 11:59 AM, souciance <[hidden email]
> > <http:///user/SendEmail.jtp?type=node=5789611=1>> wrote:
> > Does anyone know why you need to do that?  It isn't necessary in 2.17.0
> > and
> > karaf 4.0.2.
> >
> > Den 31 okt. 2016 2:09 em skrev "gustavo.maurizio [via Camel]" <
> > [hidden email] <http:///user/SendEmail.jtp?type=node=5789611=2>>:
>
> >
> > > Andrea, fantastic!
> > > Adding this  install -s wrap:mvn:junit/junit/4.12 before installing
> made
> > > it work! Thanks!!!
> > >
> > >
> > >
> > > --
> > > If you reply to this email, your message will be added to the
> discussion
> > > below:
> > > http://camel.465427.n5.nabble.com/camel-2-18-0-rabbitmq-
> > > component-fails-under-Karaf-tp5789413p5789514.html
> > > To start a new topic under Camel - Users, email
> > > [hidden email] <http:///user/SendEmail.jtp?type=node=5789611=3>
>
> > > To unsubscribe from Camel - Users, click here
> > > <
> > > .
> > > NAML
> > > <http://camel.465427.n5.nabble.com/template/
> NamlServlet.jtp?macro=macro_
> > viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.
>
> > BasicNamespace-nabble.view.web.template.NabbleNamespace-
> > nabble.view.web.template.NodeNamespace=
> > notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> > 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> > >
> >
> >
> >
> >
> > --
> > View this message in context: http://camel.465427.n5.nabble.
> > com/camel-2-18-0-rabbitmq-component-fails-under-Karaf-
> > tp5789413p5789556.html
> >
> > Sent from the Camel - Users mailing list archive at Nabble.com.
> >
> >
> > --
> > If you reply to this email, your message will be added to the discussion
> > below:
> 

Re: camel 2.18.0 rabbitmq component fails under Karaf

[Andrea Cosentino]

I meant the dependency in the OSGi bundle.

It should be something related to the maven-bundle-plugin configuration in the 
rabbitmq-client pom
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, November 2, 2016 9:04 AM, souciance 
<souciance.eqdam.ras...@gmail.com> wrote:
I had a look at the maven repo:
https://mvnrepository.com/artifact/com.rabbitmq/amqp-client/3.6.4

But junit is set as test dependency. It looks similar to 3.6.3. Or is that
the wrong place to look?

On Wed, Nov 2, 2016 at 8:27 AM, Andrea Cosentino-2 [via Camel] <
ml-node+s465427n578961...@n5.nabble.com> wrote:

> It seems the dependency on Junit has been introduced with rabbitmq amqp
> client in version 3.6.4
>
> Downgrade to 3.6.3 works fine.
>  --
> Andrea Cosentino
> --
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix Committer
> Email: [hidden email]
> <http:///user/SendEmail.jtp?type=node=5789611=0>
> Twitter: @oscerd2
> Github: oscerd
>
>
>
> On Tuesday, November 1, 2016 11:59 AM, souciance <[hidden email]
> <http:///user/SendEmail.jtp?type=node=5789611=1>> wrote:
> Does anyone know why you need to do that?  It isn't necessary in 2.17.0
> and
> karaf 4.0.2.
>
> Den 31 okt. 2016 2:09 em skrev "gustavo.maurizio [via Camel]" <
> [hidden email] <http:///user/SendEmail.jtp?type=node=5789611=2>>:
>
> > Andrea, fantastic!
> > Adding this  install -s wrap:mvn:junit/junit/4.12 before installing made
> > it work! Thanks!!!
> >
> >
> >
> > --
> > If you reply to this email, your message will be added to the discussion
> > below:
> > http://camel.465427.n5.nabble.com/camel-2-18-0-rabbitmq-
> > component-fails-under-Karaf-tp5789413p5789514.html
> > To start a new topic under Camel - Users, email
> > [hidden email] <http:///user/SendEmail.jtp?type=node=5789611=3>
> > To unsubscribe from Camel - Users, click here
> > <
> > .
> > NAML
> > <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_
> viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.
> BasicNamespace-nabble.view.web.template.NabbleNamespace-
> nabble.view.web.template.NodeNamespace=
> notify_subscribers%21nabble%3Aemail.naml-instant_emails%
> 21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> >
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.
> com/camel-2-18-0-rabbitmq-component-fails-under-Karaf-
> tp5789413p5789556.html
>
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/camel-2-18-0-rabbitmq-
> component-fails-under-Karaf-tp5789413p5789611.html
> To start a new topic under Camel - Users, email
> ml-node+s465427n465428...@n5.nabble.com
> To unsubscribe from Camel - Users, click here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code=465428=c291Y2lhbmNlLmVxZGFtLnJhc2h0aUBnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-2-18-0-rabbitmq-component-fails-under-Karaf-tp5789413p5789614.html

Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel 2.18.0 rabbitmq component fails under Karaf

[Andrea Cosentino]

It seems the dependency on Junit has been introduced with rabbitmq amqp client 
in version 3.6.4

Downgrade to 3.6.3 works fine.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Tuesday, November 1, 2016 11:59 AM, souciance 
<souciance.eqdam.ras...@gmail.com> wrote:
Does anyone know why you need to do that?  It isn't necessary in 2.17.0 and
karaf 4.0.2.

Den 31 okt. 2016 2:09 em skrev "gustavo.maurizio [via Camel]" <
ml-node+s465427n5789514...@n5.nabble.com>:

> Andrea, fantastic!
> Adding this  install -s wrap:mvn:junit/junit/4.12 before installing made
> it work! Thanks!!!
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/camel-2-18-0-rabbitmq-
> component-fails-under-Karaf-tp5789413p5789514.html
> To start a new topic under Camel - Users, email
> ml-node+s465427n465428...@n5.nabble.com
> To unsubscribe from Camel - Users, click here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code=465428=c291Y2lhbmNlLmVxZGFtLnJhc2h0aUBnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-2-18-0-rabbitmq-component-fails-under-Karaf-tp5789413p5789556.html

Sent from the Camel - Users mailing list archive at Nabble.com.

R: Re: camel 2.18.0 rabbitmq component fails under Karaf

[Andrea Cosentino]

Non sure. Need to investigate a bit 
 
  Il mar, 1 nov, 2016 alle 11:59, souciance 
ha scritto:   Does anyone know why you need to do that?  It isn't necessary in 
2.17.0 and
karaf 4.0.2.

Den 31 okt. 2016 2:09 em skrev "gustavo.maurizio [via Camel]" <
ml-node+s465427n5789514...@n5.nabble.com>:

> Andrea, fantastic!
> Adding this  install -s wrap:mvn:junit/junit/4.12 before installing made
> it work! Thanks!!!
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/camel-2-18-0-rabbitmq-
> component-fails-under-Karaf-tp5789413p5789514.html
> To start a new topic under Camel - Users, email
> ml-node+s465427n465428...@n5.nabble.com
> To unsubscribe from Camel - Users, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-2-18-0-rabbitmq-component-fails-under-Karaf-tp5789413p5789556.html
Sent from the Camel - Users mailing list archive at Nabble.com.  

Re: Camel-ahc-ws netty runtime problems

[Andrea Cosentino]

If you think the behavior of camel-websocket can be better you can fill a JIRA 
on Camel JIRA.

https://issues.apache.org/jira/browse/CAMEL

 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Sunday, October 30, 2016 5:55 PM, "Ingram, Stuart" <ingra...@upmc.edu> wrote:
Thanks Jim for looking into this.  Confirmation that it's broken vs something 
I'm doing wrong is a big time saver.  Will check back in on the next release.

The 'camel-websockets' package works for me to a certain degree but opens up 
multiple random ports per client connection making it completely unsuitable for 
my purposes unfortunately, hence the interest in 'ahc-ws'.  Didn't find much in 
the way of documentation on the 'camel-websockets' behavior or ways to 
configure it's port behavior beyond the initial connection.




-Original Message-
From: Jim Pirkle [mailto:jim.pir...@gmail.com] 
Sent: Sunday, October 30, 2016 9:55 AM
To: users@camel.apache.org
Subject: Re: Camel-ahc-ws netty runtime problems

I tried the 2.18.0 state packages, but had compile errors. Decided to wait for 
2.18.1 before trying to resolve problems

On Fri, Oct 28, 2016, 8:55 PM Ingram, Stuart <ingra...@upmc.edu> wrote:

> Thanks Claus!  I wasn't aware of the *-starter packages for Camel.  
> Much appreciated for the pointer.
>
> Moving to the 'camel-ahc-ws-starter' package and adjusting all other
> camel* packages I now get a different exception.
>
> Any help/pointers are appreciated.  Thanks
>
>
> java.util.concurrent.ExecutionException: java.lang.IllegalStateException:
> Invalid Status Code 404
> at
> org.asynchttpclient.netty.NettyResponseFuture.done(NettyResponseFuture
> .java:228)
> ~[async-http-client-2.0.15.jar:na]
> at
> org.asynchttpclient.netty.handler.WebSocketHandler$UpgradeCallback.cal
> l(WebSocketHandler.java:100)
> ~[async-http-client-2.0.15.jar:na]
> at
> org.asynchttpclient.netty.handler.AsyncHttpClientHandler.channelRead(A
> syncHttpClientHandler.java:73)
> ~[async-http-client-2.0.15.jar:na]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:366)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:352)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abstrac
> tChannelHandlerContext.java:345) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandler
> Context.fireChannelRead(CombinedChannelDuplexHandler.java:435)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMess
> ageDecoder.java:293) ~[netty-codec-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageD
> ecoder.java:267) ~[netty-codec-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChan
> nelDuplexHandler.java:250) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:366)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:352)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abstrac
> tChannelHandlerContext.java:345) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(Defaul
> tChannelPipeline.java:1294) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:366)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:352)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannel
> Pipeline.java:911) ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(Abstrac
> tNioByteChannel.java:131) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> 

Re: camel 2.18.0 rabbitmq component fails under Karaf

[Andrea Cosentino]

Try this way:

karaf@root()> feature:repo-add camel 2.18.0
Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.18.0/xml/features
karaf@root()> install -s wrap:mvn:junit/junit/4.12
Bundle ID: 52
karaf@root()> feature:install -v camel-rabbitmq 
Adding features: camel-rabbitmq/[2.18.0,2.18.0]
Changes to perform:
Region: root
Bundles to install:
mvn:com.rabbitmq/amqp-client/3.6.5
mvn:org.apache.camel/camel-catalog/2.18.0
mvn:org.apache.camel/camel-commands-core/2.18.0
mvn:org.apache.camel/camel-core/2.18.0
mvn:org.apache.camel/camel-rabbitmq/2.18.0
mvn:org.apache.camel.karaf/camel-karaf-commands/2.18.0
mvn:commons-pool/commons-pool/1.6
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jaxb-impl/2.2.11_1
mvn:org.codehaus.woodstox/stax2-api/3.1.4
mvn:org.codehaus.woodstox/woodstox-core-asl/4.4.1
Installing bundles:
mvn:com.rabbitmq/amqp-client/3.6.5
mvn:org.apache.camel/camel-catalog/2.18.0
mvn:org.apache.camel/camel-commands-core/2.18.0
mvn:org.apache.camel/camel-core/2.18.0
mvn:org.apache.camel/camel-rabbitmq/2.18.0
mvn:org.apache.camel.karaf/camel-karaf-commands/2.18.0
mvn:commons-pool/commons-pool/1.6
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jaxb-impl/2.2.11_1
mvn:org.codehaus.woodstox/stax2-api/3.1.4
mvn:org.codehaus.woodstox/woodstox-core-asl/4.4.1
Starting bundles:
org.apache.servicemix.bundles.jaxb-impl/2.2.11.1
stax2-api/3.1.4
woodstox-core-asl/4.4.1
org.apache.camel.camel-core/2.18.0
org.apache.camel.camel-catalog/2.18.0
org.apache.camel.camel-commands-core/2.18.0
com.rabbitmq.client/3.6.5
org.apache.commons.pool/1.6.0
org.apache.camel.camel-rabbitmq/2.18.0
org.apache.camel.karaf.camel-karaf-commands/2.18.0
Done.

 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Friday, October 28, 2016 7:53 PM, gustavo.maurizio <gmauri...@me.com> wrote:
trying to install camel-rabbitmq under Karaf 4.0.6 fails unable to resolve
com.rabbitmq.client.
Was working fine in 2.17.3
Any ideas or help?


ka...@sis.gt.common()> feature:install  camel-rabbitmq
Error executing command: Unable to resolve root: missing requirement [root]
osgi.identity; osgi.identity=camel-rabbitmq; type=karaf.feature;
version="[2.18.0,2.18.0]";
filter:="(&(osgi.identity=camel-rabbitmq)(type=karaf.feature)(version>=2.18.0)(version<=2.18.0))"
[caused by: Unable to resolve camel-rabbitmq/2.18.0: missing requirement
[camel-rabbitmq/2.18.0] osgi.identity;
osgi.identity=org.apache.camel.camel-rabbitmq; type=osgi.bundle;
version="[2.18.0,2.18.0]"; resolution:=mandatory [caused by: Unable to
resolve org.apache.camel.camel-rabbitmq/2.18.0: missing requirement
[org.apache.camel.camel-rabbitmq/2.18.0] osgi.wiring.package;
filter:="(&(osgi.wiring.package=com.rabbitmq.client)(version>=3.6.0)(!(version>=4.0.0)))"
[caused by: Unable to resolve com.rabbitmq.client/3.6.5: missing requirement
[com.rabbitmq.client/3.6.5] osgi.wiring.package;
filter:="(osgi.wiring.package=junit.framework)"]]]
ka...@sis.gt.common()> 




--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-2-18-0-rabbitmq-component-fails-under-Karaf-tp5789413.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Online-Docs

[Andrea Cosentino]

Currently we maintain the docs directly in github.

https://github.com/apache/camel/blob/master/components/camel-mail/src/main/docs/mail-component.adoc

But the documentation is only for the current codebase and in future it will be 
released for each new version of Camel.

I guess cc and bcc works fine with camel 2.19.0-SNAPSHOT and camel-2.18.0
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Tuesday, October 25, 2016 12:19 PM, Stephan Burkard <sburk...@gmail.com> 
wrote:
Hi

On the page https://camel.apache.org/mail.html is probably a version note
missing. The carbon copy parameter is mentioned as "cc" (lowercase). With
Camel 2.12 this does not work, the parameter is not recognized. Instead I
had to use "CC" (uppercase).

I have not tried it, but perhaps this is the same for "bcc".

PS: Is it possible to add such documentation improvements by myself (for
example on github and send a pull request)?

Regards
Stephan

Re: TransformerException camel xslt error-Jboss fuse service works

[Andrea Cosentino]

You need to ask to the Red Hat support, since you're using JBoss Fuse.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, October 19, 2016 3:46 PM, ravi21588 <ravi21...@gmail.com> wrote:
Hi All,
iam getting below error when deploying switchyard component in Jboss EAP.

14:14:25,683 ERROR [org.apache.camel.builder.xml.XsltErrorListener] (MSC
service thread 1-14) "xml:lang" attribute is not allowed on the soap:Text
element!; Line#: 16; Column#: 32: javax.xml.transform.TransformerException:
"xml:lang" attribute is not allowed on the soap:Text element!
at
org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.java:907)
at
org.apache.xalan.processor.StylesheetHandler.error(StylesheetHandler.java:950)
at
org.apache.xalan.processor.XSLTElementProcessor.setPropertiesFromAttributes(XSLTElementProcessor.java:348)
at
org.apache.xalan.processor.XSLTElementProcessor.setPropertiesFromAttributes(XSLTElementProcessor.java:268)
at
org.apache.xalan.processor.ProcessorLRE.startElement(ProcessorLRE.java:283)
at
org.apache.xalan.processor.StylesheetHandler.startElement(StylesheetHandler.java:626)
at
org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:496)
[xercesImpl-2.9.1.redhat-6.jar:2.9.1.redhat-6]
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:283)
[xercesImpl-2.9.1.redhat-6.jar:2.9.1.redhat-6]
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1653)
[xercesImpl-2.9.1.redhat-6.jar:2.9.1.redhat-6]
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:324)
[xercesImpl-2.9.1.redhat-6.jar:2.9.1.redhat-6]
at
org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:845)
[xercesImpl-2.9.1.redhat-6.jar:2.9.1.redhat-6]
at
org.apache.xerces.parsers.XML11Configuration.parse(XML11Configuration.java:768)
[xercesImpl-2.9.1.redhat-6.jar:2.9.1.redhat-6]
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:108)
[xercesImpl-2.9.1.redhat-6.jar:2.9.1.redhat-6]
at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1196)
[xercesImpl-2.9.1.redhat-6.jar:2.9.1.redhat-6]
at
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:555)
[xercesImpl-2.9.1.redhat-6.jar:2.9.1.redhat-6]
at
org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:926)
at
__redirected.__TransformerFactory.newTemplates(__TransformerFactory.java:140)
[jboss-modules.jar:1.3.3.Final-redhat-1]
at
org.apache.camel.builder.xml.XsltBuilder.setTransformerSource(XsltBuilder.java:329)
[camel-core-2.10.0.redhat-60083.jar:2.10.0.redhat-60083]
at
org.apache.camel.component.xslt.XsltEndpoint.loadResource(XsltEndpoint.java:90)
[camel-core-2.10.0.redhat-60083.jar:2.10.0.redhat-60083]
at
org.apache.camel.component.xslt.XsltEndpoint.doStart(XsltEndpoint.java:99)
[camel-core-2.10.0.redhat-60083.jar:2.10.0.redhat-60083]
at
org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:60)
[camel-core-2.10.0.redhat-60083.jar:2.10.0.redhat-60083]
at
org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:1777)
[camel-core-2.10.0.redhat-60083.jar:2.10.0.redhat-60083]
at
org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:940)
[camel-core-2.10.0.redhat-60083.jar:2.10.0.redhat-60083]
at
org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:901)
[camel-core-2.10.0.redhat-60083.jar:2.10.0.redhat-60083]
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:484)
[camel-core-2.10.0.redhat-60083.jar:2.10.0.redhat-60083]
at
org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:61)
[camel-core-2.10.0.redhat-60083.jar:2.10.0.redhat-60083]
at
org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:187)
[camel-core-2.10.0.redhat-60083.jar:2.10.0.redhat-60083]
at
org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:108)
[camel-core-2.10.0.redhat-60083.jar:2.10.0.redhat-60083]
at
org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:114)
[camel-core-2.10.0.redhat-60083.jar:2.10.0.redhat-60083]
at
org.apache.camel.model.SendDefinition.resolveEndpoint(SendDefinition.java:61)
[camel-core-2.10.0.redhat-60083.jar:2.10.0.redhat-60083]
at
org.apache.camel.model.SendDefinition.createProcessor(SendDefinition.java:55)
[camel-core-2.10.0.redhat-600

Re: OutOfMemoryError: Java heap space when sending large file to jetty endpoint

[Andrea Cosentino]

Is the camel-context deployed as a simple JAR? What are you using inside the 
Debian container? How much memory has your container?
Did you set JVM_OPTS witch specific values for max Heap size and min Heap size?

 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, October 19, 2016 2:00 PM, Vova Shelgunov <vvs...@gmail.com> wrote:
Hi,

I catched this OutOfMemoryError when I sent a 250 MB file to jetty endpoint:

java.lang.OutOfMemoryError: Java heap space
  at java.lang.StringCoding.decode(StringCoding.java:215)
  at java.lang.String.(String.java:463)
  at java.lang.String.(String.java:515)
  at
org.eclipse.jetty.servlets.MultiPartFilter$Wrapper.getParameterBytesAsString(MultiPartFilter.java:390)
  at
org.eclipse.jetty.servlets.MultiPartFilter$Wrapper.getParameterValues(MultiPartFilter.java:337)
  at
org.apache.camel.http.common.DefaultHttpBinding.populateRequestParameters(DefaultHttpBinding.java:219)
  at
org.apache.camel.http.common.DefaultHttpBinding.readHeaders(DefaultHttpBinding.java:174)
  at
org.apache.camel.http.common.DefaultHttpBinding.readRequest(DefaultHttpBinding.java:110)
  at
org.apache.camel.http.common.HttpMessage.(HttpMessage.java:52)
  at
org.apache.camel.component.jetty.CamelContinuationServlet.doService(CamelContinuationServlet.java:161)
  at
org.apache.camel.http.common.CamelServlet.service(CamelServlet.java:74)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
  at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
  at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
  at
org.eclipse.jetty.servlets.MultiPartFilter.doFilter(MultiPartFilter.java:200)
  at
org.apache.camel.component.jetty.CamelFilterWrapper.doFilter(CamelFilterWrapper.java:43)
  at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
  at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
  at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
  at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
  at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
  at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
  at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
  at org.eclipse.jetty.server.Server.handle(Server.java:499)
  at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)
  at
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
  at
org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)
  at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
  at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
  at java.lang.Thread.run(Thread.java:745)

My configuration:


https://storage:8443/data/archive?sslContextParametersRef=sslContextParameters=32768=32768=POST
<https://storage:8443/data/archive?sslContextParametersRef=sslContextParameters=32768=32768=POST>"
/>

























My camel application is running in docker container with limited amount of
memory, and I did not expect, that a file will be read a string instead of
reading from InputStream.

Is there any way to consume large files with small amount of memory?


Regards,

Uladzimir

Re: 2.18-SNAPSHOT download assistance

[Andrea Cosentino]

Hello Scott,

Camel 2.18.0 should be released by the end of September.

Cheers,
Andrea
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Thursday, September 1, 2016 9:21 AM, spurcell <scott_purc...@mastercard.com> 
wrote:
Hello Claus,

Thanks for the information, I was able to put that version into my POM and
it pulled it down. Would you happen to know when this becomes a release?
Just looking for a time-frame.

Thanks
Scott



--
View this message in context: 
http://camel.465427.n5.nabble.com/2-18-SNAPSHOT-download-assistance-tp5787054p5787064.html

Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Kafka SASL PLAIN

[Andrea Cosentino]

What version of Camel do you refer to?


--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Friday, July 29, 2016 1:17 PM, habdank <habd...@gmail.com> wrote:



Dears,

Is the Client part of the Camel Kafka plugin already in use with SASL PLAIN
protocol?
Has anyone this feature end to end tested?
Is there any how to for that kind of scenario for Camel-Kafka?

I see that zookeeper has problems with SSL.
And What I see in the:

  
camel/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConfiguration.java

There is no way to set SSL/SASL and then user name and password, what is
expected by the Kafka  Kafka Documentation
<http://kafka.apache.org/documentation.html>   :


To configure SASL authentication on the clients:

The KafkaClient section describes how the clients like producer and
consumer can connect to the Kafka Broker. The following is an example
configuration for a client for the PLAIN mechanism:

KafkaClient {
org.apache.kafka.common.security.plain.PlainLoginModule required
username="alice"
password="alice-secret";
};

The properties username and password in the KafkaClient section are used
by clients to configure the user for client connections. In this example,
clients connect to the broker as user alice.
Pass the JAAS config file location as JVM parameter to each client JVM:

-Djava.security.auth.login.config=/etc/kafka/kafka_client_jaas.conf

Configure the following properties in producer.properties or
consumer.properties:

security.protocol=SASL_SSL
sasl.mechanism=PLAIN


Best regards,
Seweryn.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Kafka-SASL-PLAIN-tp5785622.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: [camel 2.17] limited performance (not more than 20 req/s)

[Andrea Cosentino]

It should be included in 2.17.2
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Friday, July 15, 2016 1:06 PM, Claus Ibsen <claus.ib...@gmail.com> wrote:
Hi

I found the ticket
https://issues.apache.org/jira/browse/CAMEL-10043

On Fri, Jul 15, 2016 at 1:04 PM, Claus Ibsen <claus.ib...@gmail.com> wrote:
> Hi
>
> Ah yeah there was a bug in camel-jaxb that could impact the
> performance. Try with 2.17.2 or the 2.17.3-SNAPSHOT as I cannot
> remember if the fix made it into the 2.17.2 release.
>
>
> On Fri, Jul 15, 2016 at 12:56 PM, Tarek Jarraya <tarekjarr...@gmail.com> 
> wrote:
>> More info:
>>
>> I saw this log appearing many times:
>> [http-bio-8080-exec-373] DEBUG org.apache.camel.util.ObjectHelper: Cannot
>> find class: java.lang.ObjectFactory
>>
>> The log disappears with 2.16.1.
>>
>> The same log saw by others:
>> http://camel.465427.n5.nabble.com/ClassNotFoundException-ObjectFactory-td5782443.html
>>
>> Similar Performance topic (they use rabbitmq client):
>> https://issues.apache.org/jira/browse/CAMEL-9786
>>
>> Thanks,
>> Tarek
>>
>>
>> On Fri, Jul 15, 2016 at 12:27 PM, Tarek Jarraya <tarekjarr...@gmail.com>
>> wrote:
>>
>>> Hi Claus,
>>>
>>> Sorry for late reply.
>>>
>>> When I downgraded to camel 2.16.1/3 the performance issue disappears.
>>>
>>> Regards,
>>> Tarek
>>>
>>> Le mardi 14 juin 2016, Tarek Jarraya <tarekjarr...@gmail.com> a écrit :
>>>
>>>> Hi Both,
>>>>
>>>> Thanks for your interest.
>>>>
>>>> @Claus,
>>>>
>>>> this toD generates only one endpoint. I try to change it to "to" format
>>>> and let you know.
>>>>
>>>> One more thing, our exposed endpoint is using camel servlet.
>>>>
>>>> >>> uri="servlet://offer/pricing/v1.1">
>>>> 
>>>> 
>>>> 
>>>> 
>>>>
>>>> I saw in the http4 page that if we want to expose an endpoint and attach
>>>> it to route, we use camel-jetty.
>>>> Should we change our exposition?
>>>>
>>>> Some people said that we expose mostly web services with CXF.
>>>> But in that case, we have to implement a class for each endpoint.
>>>> However, with servlet we don't do it, so no more java code.
>>>>
>>>> Any recommendation if the servlet exposition is not adapted for
>>>> concurrent context?
>>>>
>>>> Regards,
>>>> Tarek
>>>>
>>>> On Tue, Jun 14, 2016 at 5:20 PM, Claus Ibsen <claus.ib...@gmail.com>
>>>> wrote:
>>>>
>>>>> On Tue, Jun 14, 2016 at 4:38 PM, owain <owain@integration.technology>
>>>>> wrote:
>>>>> > Is there a typo toD in here?
>>>>> >
>>>>> > >>>> >
>>>>> uri="{{pricing-wsrest-endpoint}}=true=true"
>>>>> > />
>>>>> >
>>>>>
>>>>> toD is a dynamic to.
>>>>>
>>>>> How many unique endpoints does {{pricing-wsrest-endpoint}} generate in
>>>>> your test?
>>>>>
>>>>> If the dynamic part is the context-path and/or uri parameters its
>>>>> better to use  and then use a header (HTTP_PART / HTTP_QUERY etc)
>>>>> to provide the dynamic context-path / uri parameters. Then you reuse
>>>>> same endpoint/producers.
>>>>> http://camel.apache.org/http4
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > View this message in context:
>>>>> http://camel.465427.n5.nabble.com/camel-2-17-limited-performance-not-more-than-20-req-s-tp5783980p5784041.html
>>>>> > Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -
>>>>> http://davsclaus.com @davsclaus
>>>>> Camel in Action 2: https://www.manning.com/ibsen2

>>>>>
>>>>
>>>>
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

R: Re: camel-sql IN query number of parameters mismatch

[Andrea Cosentino]

Did you try with a dinamica endpoint toD? 
 
  Il mer, 13 lug, 2016 alle 12:13, juliaaano ha scritto:   
Hello,

I don't think this is related to the driver. I've extended the existing
camel test case to reproduce the aforementioned scenario. Check it out at 
https://github.com/juliaaano/camel/tree/sql-in-multiple-params

There is not Oracle JBDC driver involved in the unit test as well as with
the setup I run in production. I also experimented with the
"parametersCount" option and no success there.

I've already dig into the sql component implementation and probably found
the source of the problem in that class highlighted in my previous post.

Again, If you guys find this is a bug I'd be happy to report and fix it.

Thanks.



--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-sql-IN-query-number-of-parameters-mismatch-tp5785054p5785067.html
Sent from the Camel - Users mailing list archive at Nabble.com.
  

Re: Moving Objects from one bucket to another in Amazon S3

[Andrea Cosentino]

Looking at the code there are no references to copyObject method from AWS S3 
Client.

You can raise a JIRA for a new feature.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, June 29, 2016 3:50 PM, Debraj Manna <subharaj.ma...@gmail.com> 
wrote:
Hi

Can some one please let me know how can I move objects from one S3 bucket
to another via aws-s3. I could not find the relevant thing in the
documentation <http://camel.apache.org/aws-s3.html>. Basically I want to do
what copyObject
<http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/AmazonS3Client.html#copyObject(java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String)>
does in AmazonS3Client?

Thanks,

Re: Apache Camel + Microsoft Azure Service Bus

[Andrea Cosentino]

As far as I know there are no component related to Azure.

:-)
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, June 22, 2016 4:51 PM, jamie3 <jam...@gmail.com> wrote:
I am wondering if there is a component for Azure Service Bus. IIRC service
bus supports AMQP but I am wondering if there is a native component?





--
View this message in context: 
http://camel.465427.n5.nabble.com/Apache-Camel-Microsoft-Azure-Service-Bus-tp5784320.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel 2.17 supports kafka 0.10?

[Andrea Cosentino]

Camel 2.18 is already on kafka 0.10.x.

You can take a look there.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, June 13, 2016 4:34 PM, Vanshul. Chawla <vanshul.cha...@target.com> 
wrote:
Hello,

Our org is planning to move to Kafka 0.10. We use Camel 2.17 with Kafka 0.9. 
Has anybody tried to migrate to Kafka 0.10 with Camel.?

Vanshul 

Re: Camel-Kafka component configuration type mis-match

[Andrea Cosentino]

Hi Fongys,

Thanks.

I raised a JIRA for this

https://issues.apache.org/jira/browse/CAMEL-9978

Cheers
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Friday, May 20, 2016 11:48 AM, fongys <fongyatsan+ca...@gmail.com> wrote:
Kafka producer properties 'acks' can have value 0, 1, all
Ref: http://kafka.apache.org/documentation.html#producerconfigs

While camel-kafka 2.17.1 code mark the field as Integer which cannot support
'all'
requestRequiredAcks



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Kafka-component-configuration-type-mis-match-tp5782820.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel and Guice - without JNDI and Spring

[Andrea Cosentino]

Hi Jens,

Sorry, missed your first email. I think we don't have examples of this kind.

I think it's interesting.

Let us know your progress :-)

Thanks. 
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Wednesday, May 11, 2016 10:38 AM, jkiddo <jenskristianvillad...@gmail.com> 
wrote:
Hmmm ... Okay ... I've started to figure out some stuff. Should anyone be
interested in following my findings, they can be found @
https://github.com/jkiddo/camel-herder



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-and-Guice-without-JNDI-and-Spring-tp5782401p5782429.html

Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel 2.17 Kafka SSL Producer and Consumer

[Andrea Cosentino]

We migrate Kafka to 0.9.x version and pass completely to the Java API.

The configuration changed in this upgrade.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Tuesday, March 29, 2016 2:32 PM, Vanshul. Chawla <vanshul.cha...@target.com> 
wrote:
Hello All,

When I start my producer and consumer for a SSL enabled topic, I get following 
warning and it doesn't produce or consume anything.

[pache.camel.spring.Main.main()] ConsumerConfig WARN  The 
configuration ssl.truststore.password = changeit was supplied but isn't a known 
config.
[pache.camel.spring.Main.main()] ConsumerConfig WARN  The 
configuration ssl.keymanager.algorithm = SunX509 was supplied but isn't a known 
config.
[pache.camel.spring.Main.main()] ConsumerConfig WARN  The 
configuration sasl.kerberos.ticket.renew.jitter = 0.05 was supplied but isn't a 
known config.
[pache.camel.spring.Main.main()] ConsumerConfig WARN  The 
configuration sasl.kerberos.ticket.renew.window.factor = 0.8 was supplied but 
isn't a known config.
[pache.camel.spring.Main.main()] ConsumerConfig WARN  The 
configuration sasl.kerberos.kinit.cmd = /usr/bin/kinit was supplied but isn't a 
known config.
[pache.camel.spring.Main.main()] ConsumerConfig WARN  The 
configuration ssl.enabled.protocols = TLSv1.2,TLSv1.1,TLSv1 was supplied but 
isn't a known config.
[pache.camel.spring.Main.main()] ConsumerConfig WARN  The 
configuration ssl.keystore.location = C:\Program 
Files\Java\jdk1.7.0_75\jre\lib\security\cacerts was supplied but isn't a known 
config.
[pache.camel.spring.Main.main()] ConsumerConfig WARN  The 
configuration ssl.truststore.location = C:\Program 
Files\Java\jdk1.7.0_75\jre\lib\security\cacerts was supplied but isn't a known 
config.
[pache.camel.spring.Main.main()] ConsumerConfig WARN  The 
configuration ssl.keystore.password = changeit was supplied but isn't a known 
config.
[pache.camel.spring.Main.main()] ConsumerConfig WARN  The 
configuration ssl.protocol = TLS was supplied but isn't a known config.
[pache.camel.spring.Main.main()] ConsumerConfig WARN  The 
configuration sasl.kerberos.min.time.before.relogin = 6 was supplied but 
isn't a known config.
[pache.camel.spring.Main.main()] ConsumerConfig WARN  The 
configuration ssl.trustmanager.algorithm = PKIX was supplied but isn't a known 
config.
[pache.camel.spring.Main.main()] ConsumerConfig WARN  The 
configuration ssl.truststore.type = JKS was supplied but isn't a known config.
[pache.camel.spring.Main.main()] ConsumerConfig WARN  The 
configuration ssl.keystore.type = JKS was supplied but isn't a known config.

What can be issue here?

Vanshul 

Re: [ANNOUNCEMENT] Apache Camel 2.14.4 Released

[Andrea Cosentino]

Thank you very much Gregor :-)
--  Andrea Cosentino  -Apache Camel PMC Member  
Email: ancosen1...@yahoo.com  Twitter: @oscerd2  Github: oscerd  


 On Wednesday, November 11, 2015 11:56 PM, Gregor Zurowski 
<gre...@list.zurowski.org> wrote:
   

 The Apache Camel community announces the immediate availability of the
new patch release Apache Camel 2.14.4. This release contains 18 fixes
applied in the past few weeks by the community on the Camel 2.14.x
maintenance branch. We expect this to be the last patch release for
the 2.14.x branch.

The artifacts are published and ready for you to download [1] either
from the Apache mirrors or from the Maven Central repository. For more
details please take a look at the release notes [2, 3].

Many thanks to all who made this release possible.

On behalf of the Camel PMC,
Gregor Zurowski

[1] http://camel.apache.org/download.html
[2] http://camel.apache.org/camel-2144-release.html
[3] 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211=12332478


  

Re: what is QuickFixJ's version in Apache Camel 2.15.3

[Andrea Cosentino]

Also, in the next release, 2.16.0, there will be an upgrade to version 1.6.1.

-- 
Andrea Cosentino 
-
Apache Camel PMC Member & Committer 
Email: ancosen1...@yahoo.com 
Twitter: @oscerd2 
Github: oscerd



On Tuesday, September 29, 2015 5:57 PM, Claus Ibsen <claus.ib...@gmail.com> 
wrote:
You can find the versions in the parent/pom.xml of the release
https://github.com/apache/camel/blob/camel-2.15.3/parent/pom.xml#L391




On Tue, Sep 29, 2015 at 5:32 PM, kanu_t <kanutripa...@cypatterns.com> wrote:
> I recently started exploring QuickFixJ component in Camel 2.15.3. I cannot
> figure out which version of QuickFixJ is used when I run the quickfixj
> example.
>
> I need the quickfixj 1.6.1 which seem to have support for FIX 5. SP2.
>
> Can anyone tell me the version of quickfix camel refers to? Also, if it is
> not FIX 5, is there is plan to upgrade the camel quickfix component to
> latest version of quickfixj?
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/what-is-QuickFixJ-s-version-in-Apache-Camel-2-15-3-tp5772105.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2nd edition:
https://www.manning.com/books/camel-in-action-second-edition

Re: The new camel-swagger-java module in Apache Camel 2.16

[Andrea Cosentino]

I've upgraded Jackson to 2.6.2 while Claus was working on Camel-swagger-java.. 
I wasn't aware of this problem, but we can downgrade Jackson for the moment and 
bring it back to version 2.6.1.
--Andrea Cosentino  -Apache Camel Committer  
Email: ancosen1...@yahoo.com  Twitter: @oscerd2  Github: oscerd  


 On Friday, September 25, 2015 2:49 PM, Aki Yoshida <elak...@gmail.com> 
wrote:
   

 Hi Claus,
The OSGi sample was included in CXF 3.1.3 and it uses this installer
description at the moment.
https://github.com/apache/cxf/blob/master/distribution/src/main/release/samples/jax_rs/description_swagger2_osgi/src/test/resources/features/features.xml

The same sample is also in 3.0.7-SNAPSHOT.

We haven't updated the cxf's features file with this swagger support
option yet because we are waiting for the 1.5.4 release.

What I noticed was that swagger build itself has some issue with
jackson 2.6.2. I wanted to look into it but haven't done it, so I
don't know if this is an issue with the test code or the code itself.
And this was the reason why I was bringing up this version question.

Thanks.
regards, aki



2015-09-25 14:26 GMT+02:00 Claus Ibsen <claus.ib...@gmail.com>:
> What version of CXF is that?
>
>
> On Fri, Sep 25, 2015 at 1:05 PM, Aki Yoshida <elak...@gmail.com> wrote:
>> Hi Claus,
>> Cool.
>>
>> I wanted to try it out on the Karaf setup that we have for CXF with
>> swagger 1.5.4.
>>
>> Then I noticed that camel-swagger-java is asking for jackson [2.6,3).
>> I am wondering if we could make it down to [2.4,3).
>>
>> swagger itself is currently using 2.4.x and in the CXF's current Karaf
>> setup, we are bringing 2.4.6 in at the moment.
>> So, setting the range down to 2.4 makes life easier.
>> Or do you think we all should be going for 2.6.x?
>>
>> regards, aki
>>
>> 2015-09-23 15:11 GMT+02:00 Claus Ibsen <claus.ib...@gmail.com>:
>>> Hi
>>>
>>> I just recorded a 5 minute video showing this in action
>>> http://www.davsclaus.com/2015/09/apache-camel-216-swagger-java-and-api.html
>>>
>>> At least with this new model the swagger is more light-weight (just
>>> java) and its auto detected easily from Camel, and you can run it in
>>> any JVM (not only servlet).
>>>
>>> I haven't yet tried on karaf, but it ought to work much better than
>>> the scala based.
>>>
>>> --
>>> Claus Ibsen
>>> -
>>> http://davsclaus.com @davsclaus
>>> Camel in Action 2nd edition: https://www.manning.com/books/ibsen2
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2nd edition:
> https://www.manning.com/books/camel-in-action-second-edition


  

Re: How to submit a ticket/bug report to Camel

[Andrea Cosentino]

Hi Michael,
The link I've written on the latest email is wrong.
The link is [1].
Sorry.
Best,Andrea
[1] https://issues.apache.org/jira/browse/CAMEL --Andrea 
Cosentino-Apache Camel CommitterEmail: 
ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd 


 On Wednesday, September 2, 2015 10:19 PM, Andrea Cosentino 
<ancosen1...@yahoo.com.INVALID> wrote:
   

 Hi Michael,
After your login on Camel JIRA [1], you should see a "Create" blu button on the 
site top menu.
Let us know if you have any other problem on creating a ticket.
Thanks in advance for your contribution.
Best,Andrea
[1] https://issues.apache.org/jira/browse/CAMEL/ 
--  Andrea Cosentino   -Apache Camel Committer  
 Email: ancosen1...@yahoo.com   Twitter: @oscerd2  Github: oscerd  


    On Wednesday, September 2, 2015 9:38 PM, michael.esmann 
<camel.michael.esm...@gmail.com> wrote:
  

 Hi,

I am trying to submit a ticket/bug report to Camel. When I follow the link
"Issue Tracker" on http://camel.apache.org/support.html then I am
transferred to an Atlassian JIRA site for Camel. I have created an account
on this site, but I am still having trouble finding out how to create a
ticket for Camel. I think the site is a bit confusing - but maybe its just
me.

Could someone maybe point me to some more detailed instructions about how to
create a ticket against Camel?

Thanks

Michael



--
View this message in context: 
http://camel.465427.n5.nabble.com/How-to-submit-a-ticket-bug-report-to-Camel-tp5771171.html
Sent from the Camel - Users mailing list archive at Nabble.com.




  

Re: How to submit a ticket/bug report to Camel

[Andrea Cosentino]

Hi Michael,
After your login on Camel JIRA [1], you should see a "Create" blu button on the 
site top menu.
Let us know if you have any other problem on creating a ticket.
Thanks in advance for your contribution.
Best,Andrea
[1] https://issues.apache.org/jira/browse/CAMEL/ 
--  Andrea Cosentino   -Apache Camel Committer  
 Email: ancosen1...@yahoo.com   Twitter: @oscerd2  Github: oscerd  


 On Wednesday, September 2, 2015 9:38 PM, michael.esmann 
<camel.michael.esm...@gmail.com> wrote:
   

 Hi,

I am trying to submit a ticket/bug report to Camel. When I follow the link
"Issue Tracker" on http://camel.apache.org/support.html then I am
transferred to an Atlassian JIRA site for Camel. I have created an account
on this site, but I am still having trouble finding out how to create a
ticket for Camel. I think the site is a bit confusing - but maybe its just
me.

Could someone maybe point me to some more detailed instructions about how to
create a ticket against Camel?

Thanks

Michael



--
View this message in context: 
http://camel.465427.n5.nabble.com/How-to-submit-a-ticket-bug-report-to-Camel-tp5771171.html
Sent from the Camel - Users mailing list archive at Nabble.com.


  

Re: HttpProducer to ignore response body avoiding stream caching

[Andrea Cosentino]

Hi, yes, if you want, or I can open a JIRA issue for you. You can also submit a 
patch or a PR to resolve the issue :-)
Bye

Andrea Cosentino

--

Apache Camel Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd 


 On Monday, June 15, 2015 4:09 PM, Marco Crivellaro marco.cr...@gmail.com 
wrote:
   

 Should I take care of opening a JIRA issue to request the feature? Thanks



--
View this message in context: 
http://camel.465427.n5.nabble.com/HttpProducer-to-ignore-response-body-avoiding-stream-caching-tp5767260p5768274.html
Sent from the Camel - Users mailing list archive at Nabble.com.