[jira] [Comment Edited] (CAMEL-1077) tcp client mode / server mode determined by "to" or "from" elements limits usability.

[Dima (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15701131#comment-15701131
 ] 

Dima edited comment on CAMEL-1077 at 11/29/16 12:31 AM:


I have the same issue, Is it possible to configure "To" adapter in 
server-socket mode. I need to set up one-way communication level.
"From" connects to a remote service as client socket and starts receiving text 
stream, then I need to forward this stream into server socket. No 
request-response logic just streaming

 
from("netty4:tcp://remote:54321?textline=true=false=true=1000")
.to("netty4:tcp://0.0.0.0:12345?transferExchange=true=true=false=false")

For "From" instruction it works, but "To" instruction does not want to an open 
server socket, it tries to connect localhost:12345 while I want to open the 
server socket on port 12345


was (Author: tsigelnik):
I have the same issue, Is it possible to configure "To" adapter in 
server-socket mode. I need to set up one-way communication level.
"From" connects to a remote service as client socket and starts receiving text 
stream, then I need to forward this stream into server socket. No 
request-response logic just streaming

 
from("netty4:tcp://remote:54321?textline=true=false=true=1000")
.to("netty4:tcp://localhost:12345?transferExchange=true=true=false=false")

For "From" instruction it works, but "To" instruction does not want to an open 
server socket, it tries to connect localhost:12345 while I want to open the 
server socket on port 12345

> tcp client mode / server mode determined by "to" or "from" elements limits 
> usability.
> -
>
> Key: CAMEL-1077
> URL: https://issues.apache.org/jira/browse/CAMEL-1077
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-mina
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0
>Reporter: Jeff Vienneau
>Assignee: Willem Jiang
> Fix For: 2.15.0
>
>
> Internally, 
> MinaProducer is coded to create a Mina connector (client mode socket).
> MinaConsumer is coded to create a Mina acceptor (server mode socket).
> Additionally, it appears a producer (client mode socket) is created for a 
> "to" route mapping and a consumer (server mode socket) is created for a 
> "from" route mapping.
> This means an endpoint cannot be created in which the session is initiated by 
> a client and messages are routed "to" the client. 
> The opposite is also true, an endpoint with a "from" route mapping cannot 
> establish a connection to a tcp server.
> This is a major limitation, as we do not often have control over the systems 
> with which we are interfacing.
> Perhaps, the mina::tcp URI could have a parameter the sets the socket mode: 
> tcp.mode=server or tcp.mode=client.
> Hope this make sense, thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10300) camel-salesforce component missing salesforce fields

[Rajesh A (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703045#comment-15703045
 ] 

Rajesh A commented on CAMEL-10300:
--

Zoran, I am in vacation, will be back in two days. Once I am back, will
test your suggestion and let you know if that helps.

Thanks
Rajesh

On Sun, Nov 27, 2016 at 10:24 AM, Zoran Regvart (JIRA) 



> camel-salesforce component missing salesforce fields
> 
>
> Key: CAMEL-10300
> URL: https://issues.apache.org/jira/browse/CAMEL-10300
> Project: Camel
>  Issue Type: Bug
>  Components: camel-salesforce
>Affects Versions: 2.18.0
>Reporter: Rajesh A
>Assignee: Zoran Regvart
>
> All my queries using camel-salesforce component 2.18.x misses all fields 
> except 'ID'.
> For example the below query should result Account objects populated with ID, 
> name, company.
> Select id, name, company from Account
> But, the resultant Account objects contain only ID field populated.
> I looked the log and did debug the code, this is what I found:
> 2.18.x version uses com.fasterxml.jackson version
> where as 2.17.x uses org.codehaus.jackson version.
> com.fasterxml.jackson version parses string to Object but just includes the 
> ID field and ignores other fields.
> Here is the piece of code that does this -> SalesforceConsumer.java
> // create the expected SObject
> in.setBody(OBJECT_MAPPER.readValue(
> new StringReader(sObjectString), sObjectClass));
> Please fix this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10086) Remove Pattern.compile usages

[Alexandru Enache (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702975#comment-15702975
 ] 

Alexandru Enache commented on CAMEL-10086:
--

I did some digging on this ticket and I've come up with 2 scenarios:

1) There are usages of Pattern.compile that can benefit from the proposed 
approach (as per the description, making pattern a static variable). The cases 
when this can take place is when the regex to compile is hardcoded
examples:
{code:title=ArquillianPackager.java}
L472: Pattern propPattern = Pattern.compile("(\\$\\{[^}]*\\})");{code}
{code:title=JsonTokenExtractor.java}
L32: accessTokenPattern = 
Pattern.compile("\"access_token\":\\s*\"(\\S*?)\"");{code}

2) There are usages of Pattern.compile that cannot be fixed as per the proposed 
solution (making them static). Both of the examples provided in the description 
fall in this category. The reason behind this is that the static pattern would 
be shared by all instances so in a setup like this:
{code}
from("file://target1/?exclude=^.*xml$").to("mock:result");

from("file://target2/?exclude=^.*txt$").to("mock:result");
{code}
the second route would override the pattern that the first route setted up and 
all messages send to the first route will use the same exclude pattern as the 
second route. I've also done a test for this specific setup with the static 
pattern in GenericFileConsumer and I confirm it works as described.

I am still in progress with finding all the places that fall into the 1st 
category and fixing them, but I will come back with a PR on this.

> Remove Pattern.compile usages
> -
>
> Key: CAMEL-10086
> URL: https://issues.apache.org/jira/browse/CAMEL-10086
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Mateusz Nowakowski
>Priority: Minor
> Fix For: Future
>
>
> Please heck Pattern.compile usage across Camel source code - also *not* 
> direct usage.
> For example: 
> Whenever one of these methods are used from String class a Pattern.compile() 
> is utilized:
> - matches
> - replaceFirst
> - replaceAll
> - replace
> - split: has an optimization and for certain characters it doesn’t use 
> Pattern.compile.
> For example:
> GenericFileConsumer.isMatched calls name.matches(endpoint.getExclude())
> GenericFileEndpoint could contain also excludePattern as well.
> Possible solution:
> Walk through the code and replace usages of these methods with static Pattern 
> variables.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10543) New Apache Camel Logo

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-10543:
---

 Summary: New Apache Camel Logo
 Key: CAMEL-10543
 URL: https://issues.apache.org/jira/browse/CAMEL-10543
 Project: Camel
  Issue Type: Improvement
  Components: website
Reporter: Luca Burgazzoli
 Fix For: Future


The Apache Camel logo is a bit out dated so we have discussed in the community 
to come up with a new one. We encourage anyone to participate by submitting a 
PR on GitHub and share thoughts.

- images should be added to docs/img
- each PR should contains a single logo



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10509) ManagedCamelContextMBean - additional namespaces are removed

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702540#comment-15702540
 ] 

ASF GitHub Bot commented on CAMEL-10509:


GitHub user jamesnetherton opened a pull request:

https://github.com/apache/camel/pull/1318

CAMEL-10509: ManagedCamelContextMBean - additional namespaces are removed

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

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jamesnetherton/camel CAMEL-10509

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1318.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1318


commit 500a92733b6380c05531222ebb2563aab0c21157
Author: Claus Ibsen 
Date:   2016-11-23T13:22:52Z

CAMEL-10509: dump model to xml should include namespaces. Work in progress.

commit 0b393b88e38edb1fd1a52bcce99b83538a1264a4
Author: James Netherton 
Date:   2016-11-25T15:25:22Z

CAMEL-10509: Handle namespaces on XML dump and load operations




> ManagedCamelContextMBean - additional namespaces are removed
> 
>
> Key: CAMEL-10509
> URL: https://issues.apache.org/jira/browse/CAMEL-10509
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.18.0
>Reporter: Aurelien Pupier
> Fix For: 2.19.0
>
>
> - Use a specific namespace, declared at CamelContext level, in an Xpath 
> expression of a When
> something like:
> {noformat}
> 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;>
> 
>  xmlns="http://camel.apache.org/schema/blueprint; 
> xmlns:order="http://fabric8.com/examples/order/v7;>
> 
> 
> 
> 
> 
> 
>  id="_xpath1">/order:order/order:customer/order:country = 'UK'
> 
> 
> 
> 
>  id="_xpath2">/order:order/order:customer/order:country = 'US'
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> {noformat}
> - Deploy the project
> - Using MBean retrieve dumpRoutesAsXml is providing a route without the 
> additional xml namespace provided 
> xmlns:order="http://fabric8.com/examples/order/v7;
> {noformat}
> 
>  xmlns="http://camel.apache.org/schema/spring;>
> 
> 
> 
> 
> 
> /order:order/order:customer/order:country 
> = 'UK'
> 
> 
> 
> 
> /order:order/order:customer/order:country 
> = 'US'
> 
> 
> 
> 
> 
>  uri="file:work/cbr/output/others"/>
> 
> 
> 
> 
> 
> {noformat}
> - Then use addOrUpdateRoutesFromXml to upload the exact same xml, you will 
> get exceptions when the When code is invoked:
> {noformat}
> Message History
> ---
> RouteId  ProcessorId  Processor   
>  Elapsed (ms)
> [cbr-route ] [cbr-route ] [file://work/cbr/input  
>] [ 1]
> [cbr-route ] [_log1 ] [log
>] [ 0]
> [cbr-route ] [_choice1  ] [when[xpath{XPath: 
> /order:order/order:customer/order:country = 'UK'}]choice[whe] [ 1]
> Stacktrace
> ---
> org.apache.camel.builder.xml.InvalidXPathExpression: Invalid xpath: 
> /order:order/order:customer/order:country = 'UK'. Reason: 
> javax.xml.xpath.XPathExpressionException: 
> com.sun.org.apache.xpath.internal.domapi.XPathStylesheetDOM3Exception: Prefix 
> must resolve to a namespace: order
>   at 
> 

[jira] [Closed] (CAMEL-10541) DataFormat from registry is used for every dataformat operation (marshal/unmarshal)

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-10541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli closed CAMEL-10541.
---
Resolution: Duplicate

> DataFormat from registry is used for every dataformat operation 
> (marshal/unmarshal)
> ---
>
> Key: CAMEL-10541
> URL: https://issues.apache.org/jira/browse/CAMEL-10541
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Reporter: Luca Burgazzoli
>
> While working on an issue related to spring-boot I found out that if a data 
> format is registered in camel registry with the same name as the one camel 
> looks-up with the help of DefaultDataFormatResolver, this object is then 
> re-configured for each data format definition so one definition may override 
> previous configuration with an undefined behavior.
> So assume you have an xml route definitions as:
> {code:xml}
> http://camel.apache.org/schema/spring;>
>   
> 
> 
>   
> 
>   
>   
> 
> 
>   
> 
>   
> 
> {code}
> And some code like:
> {code:java}
> InputStream is = getClass().getResourceAsStream("...");
> SimpleRegistry reg = new SimpleRegistry();
> reg.put("csv-dataformat", new CsvDataFormat());
> DefaultCamelContext ctx = new DefaultCamelContext(reg);
> ctx.addRouteDefinitions(ctx.loadRoutesDefinition(is).getRoutes());
> ctx.start();
> ProducerTemplate template = ctx.createProducerTemplate();
> String result = template.requestBody(
> "direct:marshal",
> Arrays.asList(Arrays.asList( "A1", "B1", "C1" )),
> String.class);
> assertEquals("A1,B1,C1", result);
> ctx.stop
> {code}
> Then this test fails with:
> {code}
> Expected :A1,B1,C1
> Actual   :A1;B1;C1
> {code}
> It fails because the object added to the SimpleRegistry is shared among the 
> two csv dataformats  so it is configured to have delimiter = ';' 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-10542) DataFormat from registry is used for every dataformat operation (marshal/unmarshal)

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-10542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli updated CAMEL-10542:

Fix Version/s: 2.19.0
   2.18.2

> DataFormat from registry is used for every dataformat operation 
> (marshal/unmarshal)
> ---
>
> Key: CAMEL-10542
> URL: https://issues.apache.org/jira/browse/CAMEL-10542
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Reporter: Luca Burgazzoli
> Fix For: 2.18.2, 2.19.0
>
>
> While working on an issue related to spring-boot I found out that if a data 
> format is registered in camel registry with the same name as the one camel 
> looks-up with the help of DefaultDataFormatResolver, this object is then 
> re-configured for each data format definition so one definition may override 
> previous configuration with an undefined behavior.
> So assume you have an xml route definitions as:
> {code:xml}
> http://camel.apache.org/schema/spring;>
>   
> 
> 
>   
> 
>   
>   
> 
> 
>   
> 
>   
> 
> {code}
> And some code like:
> {code:java}
> InputStream is = getClass().getResourceAsStream("...");
> SimpleRegistry reg = new SimpleRegistry();
> reg.put("csv-dataformat", new CsvDataFormat());
> DefaultCamelContext ctx = new DefaultCamelContext(reg);
> ctx.addRouteDefinitions(ctx.loadRoutesDefinition(is).getRoutes());
> ctx.start();
> ProducerTemplate template = ctx.createProducerTemplate();
> String result = template.requestBody(
> "direct:marshal",
> Arrays.asList(Arrays.asList( "A1", "B1", "C1" )),
> String.class);
> assertEquals("A1,B1,C1", result);
> ctx.stop
> {code}
> Then this test fails with:
> {code}
> Expected :A1,B1,C1
> Actual   :A1;B1;C1
> {code}
> It fails because the object added to the SimpleRegistry is shared among the 
> two csv dataformats  so it is configured to have delimiter = ';' 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10542) DataFormat from registry is used for every dataformat operation (marshal/unmarshal)

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-10542:
---

 Summary: DataFormat from registry is used for every dataformat 
operation (marshal/unmarshal)
 Key: CAMEL-10542
 URL: https://issues.apache.org/jira/browse/CAMEL-10542
 Project: Camel
  Issue Type: Bug
  Components: camel-core
Reporter: Luca Burgazzoli


While working on an issue related to spring-boot I found out that if a data 
format is registered in camel registry with the same name as the one camel 
looks-up with the help of DefaultDataFormatResolver, this object is then 
re-configured for each data format definition so one definition may override 
previous configuration with an undefined behavior.

So assume you have an xml route definitions as:

{code:xml}
http://camel.apache.org/schema/spring;>
  


  

  
  


  

  

{code}

And some code like:

{code:java}
InputStream is = getClass().getResourceAsStream("...");

SimpleRegistry reg = new SimpleRegistry();
reg.put("csv-dataformat", new CsvDataFormat());

DefaultCamelContext ctx = new DefaultCamelContext(reg);
ctx.addRouteDefinitions(ctx.loadRoutesDefinition(is).getRoutes());
ctx.start();

ProducerTemplate template = ctx.createProducerTemplate();
String result = template.requestBody(
"direct:marshal",
Arrays.asList(Arrays.asList( "A1", "B1", "C1" )),
String.class);

assertEquals("A1,B1,C1", result);

ctx.stop
{code}

Then this test fails with:

{code}
Expected :A1,B1,C1
Actual   :A1;B1;C1
{code}

It fails because the object added to the SimpleRegistry is shared among the two 
csv dataformats  so it is configured to have delimiter = ';' 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10541) DataFormat from registry is used for every dataformat operation (marshal/unmarshal)

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-10541:
---

 Summary: DataFormat from registry is used for every dataformat 
operation (marshal/unmarshal)
 Key: CAMEL-10541
 URL: https://issues.apache.org/jira/browse/CAMEL-10541
 Project: Camel
  Issue Type: Bug
  Components: camel-core
Reporter: Luca Burgazzoli


While working on an issue related to spring-boot I found out that if a data 
format is registered in camel registry with the same name as the one camel 
looks-up with the help of DefaultDataFormatResolver, this object is then 
re-configured for each data format definition so one definition may override 
previous configuration with an undefined behavior.

So assume you have an xml route definitions as:

{code:xml}
http://camel.apache.org/schema/spring;>
  


  

  
  


  

  

{code}

And some code like:

{code:java}
InputStream is = getClass().getResourceAsStream("...");

SimpleRegistry reg = new SimpleRegistry();
reg.put("csv-dataformat", new CsvDataFormat());

DefaultCamelContext ctx = new DefaultCamelContext(reg);
ctx.addRouteDefinitions(ctx.loadRoutesDefinition(is).getRoutes());
ctx.start();

ProducerTemplate template = ctx.createProducerTemplate();
String result = template.requestBody(
"direct:marshal",
Arrays.asList(Arrays.asList( "A1", "B1", "C1" )),
String.class);

assertEquals("A1,B1,C1", result);

ctx.stop
{code}

Then this test fails with:

{code}
Expected :A1,B1,C1
Actual   :A1;B1;C1
{code}

It fails because the object added to the SimpleRegistry is shared among the two 
csv dataformats  so it is configured to have delimiter = ';' 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-10540) GROK Parser

[Jan Bernhardt (JIRA)]

Jan Bernhardt created CAMEL-10540:
-

 Summary: GROK Parser
 Key: CAMEL-10540
 URL: https://issues.apache.org/jira/browse/CAMEL-10540
 Project: Camel
  Issue Type: New Feature
Reporter: Jan Bernhardt


As discussed on the mailing list [1], it would be great to have a grok filter 
for camel, to parse text with multiple named regex expressions resulting in a 
Map containing the named key as well as the parsed value.

[1] 
http://camel.465427.n5.nabble.com/Parsing-unstructured-Text-in-Camel-td5790513.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10492) Camel Servlet, attachment object is empty

[Fabrizio Spataro (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15701770#comment-15701770
 ] 

Fabrizio Spataro commented on CAMEL-10492:
--

I found a workaround to fix my problem:

Updating my software to 2.18 version my attachments aren't available, now my 
servlet code is:

{code:xml}

{code}

i am using two parameters:
 - disableStreamCache, *is original problem*. With streamcache enable 
attachment files aren't available to jetty multicast parser
 - attachmentMultipartBinding, to enable AttachmentHttpBinding into servlet 
endpoint 

my old code is:

{code:xml}

{code}

[~davsclaus] evaluate you what to do with this issue!

> Camel Servlet, attachment object is empty
> -
>
> Key: CAMEL-10492
> URL: https://issues.apache.org/jira/browse/CAMEL-10492
> Project: Camel
>  Issue Type: Bug
>  Components: camel-http-common, camel-servlet
>Affects Versions: 2.18.0
>Reporter: Fabrizio Spataro
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: Future
>
> Attachments: camel-example-servlet-attachment.zip
>
>
> I send a multipart form data to my camel servlet, before camel 2.18 
> attachment object is ok now is empty!
> Now i have an *header* every form field but every field is java.lang.String
> So, I can not post any binary file.
> This is my web.xml filter
> {code:xml}
>   
>   MultipartFilter
>   
> org.eclipse.jetty.servlets.MultiPartFilter
>   
>   
>   MultipartFilter
>   CamelServlet
>   
> {code}
> Into zip file, you can found an example.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-10536) camel-servlet-starter - Test failure

[Nicola Ferraro (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-10536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicola Ferraro resolved CAMEL-10536.

Resolution: Fixed

The test required the dependent auto-configuration. Added common profiles also 
to starters.

> camel-servlet-starter - Test failure
> 
>
> Key: CAMEL-10536
> URL: https://issues.apache.org/jira/browse/CAMEL-10536
> Project: Camel
>  Issue Type: Test
>  Components: camel-servlet, camel-spring-boot
>Affects Versions: 2.19.0
>Reporter: Claus Ibsen
>Assignee: Nicola Ferraro
> Fix For: 2.19.0
>
>
> I got this test failure
> Failed tests:
>   ServletMappingAutoConfigurationTest.testServletMapping:63 
> expected:<[Hello]> but 
> was:<[{"timestamp":1480150540485,"status":404,"error":"Not 
> Found","message":"No message available","path":"/camel/thepath"}]>
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> Also the tests should not run when I do a 
>mvn clean install -Pfastinstall
> Which should not run the unit tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10536) camel-servlet-starter - Test failure

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15701647#comment-15701647
 ] 

Claus Ibsen commented on CAMEL-10536:
-

I added an @Ignore for those tests so we can have this working for people until 
its fixed.

> camel-servlet-starter - Test failure
> 
>
> Key: CAMEL-10536
> URL: https://issues.apache.org/jira/browse/CAMEL-10536
> Project: Camel
>  Issue Type: Test
>  Components: camel-servlet, camel-spring-boot
>Affects Versions: 2.19.0
>Reporter: Claus Ibsen
>Assignee: Nicola Ferraro
> Fix For: 2.19.0
>
>
> I got this test failure
> Failed tests:
>   ServletMappingAutoConfigurationTest.testServletMapping:63 
> expected:<[Hello]> but 
> was:<[{"timestamp":1480150540485,"status":404,"error":"Not 
> Found","message":"No message available","path":"/camel/thepath"}]>
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> Also the tests should not run when I do a 
>mvn clean install -Pfastinstall
> Which should not run the unit tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10529) The "exchange" keyword in LogEIP was incorrectly evaluated as a Camel Exchange type even without "${ }"

[Joe Luo (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15701591#comment-15701591
 ] 

Joe Luo commented on CAMEL-10529:
-

Hi Claus,
Thanks a lot for the explanation. Yeah, I agree that it was indeed a backward 
compatibility issue as my test results confirmed it. 

However, I still think there is a bug here, although it might be a small one. 
The document says
{code}
The ${ } placeholders can be omitted if the expression is only the token itself.
{code}
In this case, it was not that it stands on it's own, rather, it was part of a 
log message but with the token/keyword in the beginning of the log message. We 
should not evaluate it as a property placeholder without "${ }". And it causes 
trouble.

I have tested with more tokens and with this use case (the token being in the 
beginning of the LogEIP's log message), camel either prints an empty string 
(with most other tokens/keywords) or throws an exception (with "exchange" 
keyword).

> The "exchange" keyword in LogEIP was incorrectly evaluated as a Camel 
> Exchange type even without "${ }"
> ---
>
> Key: CAMEL-10529
> URL: https://issues.apache.org/jira/browse/CAMEL-10529
> Project: Camel
>  Issue Type: Bug
>  Components: camel-language
>Affects Versions: 2.17.0
>Reporter: Joe Luo
>
> I have a very simple camel route:
> {code}
> http://camel.apache.org/schema/blueprint;>
> 
> 
> 
> hello Camel!
> 
> 
> 
> 
> {code}
> Then I am getting the following error:
> {code}
> 16:09:32,724 | WARN | #3 - timer://foo | TimerConsumer | 232 - 
> org.apache.camel.camel-core - 2.17.0.redhat-630187 | Error processing 
> exchange. Exchange[ID-jluomac-54194-1480090135878-3-4]. Caused by: 
> [org.apache.camel.RuntimeCamelException - 
> org.apache.camel.component.bean.MethodNotFoundException: Method with name: is 
> triggered not found on bean: Exchange[ID-jluomac-54194-1480090135878-3-4] of 
> type: org.apache.camel.impl.DefaultExchange]
> org.apache.camel.RuntimeCamelException: 
> org.apache.camel.component.bean.MethodNotFoundException: Method with name: is 
> triggered not found on bean: Exchange[ID-jluomac-54194-1480090135878-3-4] of 
> type: org.apache.camel.impl.DefaultExchange
> {code}
> It looks like it was incorrectly evaluated as a Camel Exchange type for some 
> reason.
> Furthermore, it is only causing the problem when it is in the beginning of 
> the LogEIP message. If it is not, it works fine. For instance, following line 
> will cause problem:
> {code}
> 
> {code}
> But this will work:
> {code}
> 
> {code}
> As long as you are not placing the keyword "exchange" in the beginning of the 
> LogEIP message, it will be fine.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-10521) Camel-Rabbitmq: Support RabbitMQ AMQP client 4.x

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-10521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-10521.
--
Resolution: Fixed

> Camel-Rabbitmq: Support RabbitMQ AMQP client 4.x
> 
>
> Key: CAMEL-10521
> URL: https://issues.apache.org/jira/browse/CAMEL-10521
> Project: Camel
>  Issue Type: Task
>  Components: camel-rabbitmq
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.19.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10492) Camel Servlet, attachment object is empty

[Fabrizio Spataro (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15701561#comment-15701561
 ] 

Fabrizio Spataro commented on CAMEL-10492:
--

I have found a bug into this code. 

I am trying to fix it!

{code:java}

final class AttachmentHttpBinding extends DefaultHttpBinding {
..
protected void populateAttachments(HttpServletRequest request, HttpMessage 
message) {
try {
Collection parts = request.getParts();
for (Part part : parts) {
DataSource ds = new PartDataSource(part);
Attachment attachment = new DefaultAttachment(ds);
for (String headerName : part.getHeaderNames()) {
for (String headerValue : part.getHeaders(headerName)) {
attachment.addHeader(headerName, headerValue);
}
}
message.addAttachmentObject(part.getName(), attachment);
}
} catch (Exception e) {
throw new RuntimeCamelException("Cannot populate attachments", e);
}
}
...
}
{code}

> Camel Servlet, attachment object is empty
> -
>
> Key: CAMEL-10492
> URL: https://issues.apache.org/jira/browse/CAMEL-10492
> Project: Camel
>  Issue Type: Bug
>  Components: camel-http-common, camel-servlet
>Affects Versions: 2.18.0
>Reporter: Fabrizio Spataro
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: Future
>
> Attachments: camel-example-servlet-attachment.zip
>
>
> I send a multipart form data to my camel servlet, before camel 2.18 
> attachment object is ok now is empty!
> Now i have an *header* every form field but every field is java.lang.String
> So, I can not post any binary file.
> This is my web.xml filter
> {code:xml}
>   
>   MultipartFilter
>   
> org.eclipse.jetty.servlets.MultiPartFilter
>   
>   
>   MultipartFilter
>   CamelServlet
>   
> {code}
> Into zip file, you can found an example.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10536) camel-servlet-starter - Test failure

[Nicola Ferraro (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15701543#comment-15701543
 ] 

Nicola Ferraro commented on CAMEL-10536:


This should have been fixed by CAMEL-10524. I'm going to check why the profile 
is ignored. 

> camel-servlet-starter - Test failure
> 
>
> Key: CAMEL-10536
> URL: https://issues.apache.org/jira/browse/CAMEL-10536
> Project: Camel
>  Issue Type: Test
>  Components: camel-servlet, camel-spring-boot
>Affects Versions: 2.19.0
>Reporter: Claus Ibsen
>Assignee: Nicola Ferraro
> Fix For: 2.19.0
>
>
> I got this test failure
> Failed tests:
>   ServletMappingAutoConfigurationTest.testServletMapping:63 
> expected:<[Hello]> but 
> was:<[{"timestamp":1480150540485,"status":404,"error":"Not 
> Found","message":"No message available","path":"/camel/thepath"}]>
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
> Also the tests should not run when I do a 
>mvn clean install -Pfastinstall
> Which should not run the unit tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-10524) Components not created because of unsatisfied conditions

[Nicola Ferraro (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-10524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicola Ferraro resolved CAMEL-10524.

Resolution: Fixed

Sorting was not working... Until I figured out that there was a typo in the 
package name ;)

> Components not created because of unsatisfied conditions
> 
>
> Key: CAMEL-10524
> URL: https://issues.apache.org/jira/browse/CAMEL-10524
> Project: Camel
>  Issue Type: Bug
>  Components: camel-spring-boot
>Affects Versions: 2.19.0
>Reporter: Nicola Ferraro
>Assignee: Nicola Ferraro
> Fix For: 2.19.0
>
>
> Probably after CAMEL-10412, component beans are not created automatically so 
> property-based configuration and other features are disabled.
> Running 'mvn spring-boot:run -Ddebug=true' on camel-spring-boot-example I see 
> the following log among the others:
> {code}
> ...
> TimerComponentAutoConfiguration:
>   Did not match:
>  - @ConditionalOnBean (types: 
> org.apache.camel.springboot.CamelAutoConfiguration; SearchStrategy: all) did 
> not find any beans (OnBeanCondition)
> ...
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-10539) When bridging http endpoints and end users do not enable the bridgeEndpoint option they may get a NPE exception

[Frank Wein (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-10539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Frank Wein updated CAMEL-10539:
---
Description: 
I noticed that you get a NullPointerException when you forget the 
bridgeEndpoint=true option when bridging two HTTP endpoints (first endpoint is 
a REST Jetty endpoint, second one also uses Jetty). Maybe Camel can warn in 
this case that the bridgeEndpoint parameter is missing.

Simplified basic code (Java):
{noformat}
 restConfiguration().component("jetty").host("0.0.0.0").port(8080)
.dataFormatProperty("prettyPrint", "true")
.bindingMode(RestBindingMode.auto);

rest("/API/").get("/{ID}/").to("jetty:http://www.google.com;);
{noformat}

HTTP Request to http://localhost:8080/API/1/ results in NullPointerException.

Stacktrace:
java.lang.NullPointerException
at org.eclipse.jetty.client.HttpClient.send(HttpClient.java:521)
at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:694)
at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:678)
at 
org.apache.camel.component.jetty9.JettyContentExchange9.send(JettyContentExchange9.java:228)
at 
org.apache.camel.component.jetty.JettyHttpProducer.processInternal(JettyHttpProducer.java:247)
at 
org.apache.camel.component.jetty.JettyHttpProducer.process(JettyHttpProducer.java:86)
at 
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)
at 
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
at 
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:163)
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
at 
org.apache.camel.component.jetty.CamelContinuationServlet.doService(CamelContinuationServlet.java:191)
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.doHandle(ServletHandler.java:587)
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)


This issue is probably a bit related to the already resolved CAMEL-4242.

  was:
I noticed that you get a NullPointerException when you forget the 
bridgeEndpoint=true option when bridging two HTTP endpoints (first endpoint is 
a REST Jetty endpoint, second one also uses Jetty). Maybe Camel can warn in 
this case that the bridgeEndpoint parameter is missing.

Simplified basic code (Java):
 restConfiguration().component("jetty").host("0.0.0.0").port(8080)
.dataFormatProperty("prettyPrint", "true")
.bindingMode(RestBindingMode.auto);

rest("/API/").get("/{ID}/").to("jetty:http://www.google.com;);

HTTP Request to http://localhost:8080/API/1/ results in NullPointerException.

Stacktrace:
java.lang.NullPointerException
at org.eclipse.jetty.client.HttpClient.send(HttpClient.java:521)
at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:694)
at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:678)
at 
org.apache.camel.component.jetty9.JettyContentExchange9.send(JettyContentExchange9.java:228)
at 
org.apache.camel.component.jetty.JettyHttpProducer.processInternal(JettyHttpProducer.java:247)
at 
org.apache.camel.component.jetty.JettyHttpProducer.process(JettyHttpProducer.java:86)
at 

[jira] [Updated] (CAMEL-10539) When bridging http endpoints and end users do not enable the bridgeEndpoint option they may get a NPE exception

[Frank Wein (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-10539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Frank Wein updated CAMEL-10539:
---
Description: 
I noticed that you get a NullPointerException when you forget the 
bridgeEndpoint=true option when bridging two HTTP endpoints (first endpoint is 
a REST Jetty endpoint, second one also uses Jetty). Maybe Camel can warn in 
this case that the bridgeEndpoint parameter is missing.

Simplified basic code (Java):
 restConfiguration().component("jetty").host("0.0.0.0").port(8080)
.dataFormatProperty("prettyPrint", "true")
.bindingMode(RestBindingMode.auto);

rest("/API/").get("/{ID}/").to("jetty:http://www.google.com;);

HTTP Request to http://localhost:8080/API/1/ results in NullPointerException.

Stacktrace:
java.lang.NullPointerException
at org.eclipse.jetty.client.HttpClient.send(HttpClient.java:521)
at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:694)
at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:678)
at 
org.apache.camel.component.jetty9.JettyContentExchange9.send(JettyContentExchange9.java:228)
at 
org.apache.camel.component.jetty.JettyHttpProducer.processInternal(JettyHttpProducer.java:247)
at 
org.apache.camel.component.jetty.JettyHttpProducer.process(JettyHttpProducer.java:86)
at 
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)
at 
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
at 
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:163)
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
at 
org.apache.camel.component.jetty.CamelContinuationServlet.doService(CamelContinuationServlet.java:191)
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.doHandle(ServletHandler.java:587)
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)


This issue is probably a bit related to the already resolved CAMEL-4242.

  was:
I noticed that you get a NullPointerException when you forget the 
bridgeEndpoint=true option when bridging two HTTP endpoints (first endpoint is 
a REST Jetty endpoint, second one also uses Jetty). Maybe Camel can warn in 
this case that the bridgeEndpoint parameter is missing.

Simplified basic code (Java):
 restConfiguration().component("jetty").host("0.0.0.0").port(8080)
.dataFormatProperty("prettyPrint", "true")
.bindingMode(RestBindingMode.auto);

rest("/API/")
.get("/{ID}/")
.to("jetty:http://www.google.com;);

HTTP Request to http://localhost:8080/API/1/ results in NullPointerException.

Stacktrace:
java.lang.NullPointerException
at org.eclipse.jetty.client.HttpClient.send(HttpClient.java:521)
at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:694)
at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:678)
at 
org.apache.camel.component.jetty9.JettyContentExchange9.send(JettyContentExchange9.java:228)
at 
org.apache.camel.component.jetty.JettyHttpProducer.processInternal(JettyHttpProducer.java:247)
at 
org.apache.camel.component.jetty.JettyHttpProducer.process(JettyHttpProducer.java:86)
at 

[jira] [Created] (CAMEL-10539) When bridging http endpoints and end users do not enable the bridgeEndpoint option they may get a NPE exception

[Frank Wein (JIRA)]

Frank Wein created CAMEL-10539:
--

 Summary: When bridging http endpoints and end users do not enable 
the bridgeEndpoint option they may get a NPE exception
 Key: CAMEL-10539
 URL: https://issues.apache.org/jira/browse/CAMEL-10539
 Project: Camel
  Issue Type: Bug
  Components: camel-http, camel-jetty
Affects Versions: 2.18.0
Reporter: Frank Wein
Priority: Minor


I noticed that you get a NullPointerException when you forget the 
bridgeEndpoint=true option when bridging two HTTP endpoints (first endpoint is 
a REST Jetty endpoint, second one also uses Jetty). Maybe Camel can warn in 
this case that the bridgeEndpoint parameter is missing.

Simplified basic code (Java):
 restConfiguration().component("jetty").host("0.0.0.0").port(8080)
.dataFormatProperty("prettyPrint", "true")
.bindingMode(RestBindingMode.auto);

rest("/API/")
.get("/{ID}/")
.to("jetty:http://www.google.com;);

HTTP Request to http://localhost:8080/API/1/ results in NullPointerException.

Stacktrace:
java.lang.NullPointerException
at org.eclipse.jetty.client.HttpClient.send(HttpClient.java:521)
at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:694)
at org.eclipse.jetty.client.HttpRequest.send(HttpRequest.java:678)
at 
org.apache.camel.component.jetty9.JettyContentExchange9.send(JettyContentExchange9.java:228)
at 
org.apache.camel.component.jetty.JettyHttpProducer.processInternal(JettyHttpProducer.java:247)
at 
org.apache.camel.component.jetty.JettyHttpProducer.process(JettyHttpProducer.java:86)
at 
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)
at 
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
at 
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:163)
at 
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:542)
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
at 
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:197)
at 
org.apache.camel.component.jetty.CamelContinuationServlet.doService(CamelContinuationServlet.java:191)
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.doHandle(ServletHandler.java:587)
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)


This issue is probably a bit related to the already resolved CAMEL-4242.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-10452) camel-salesforce: Add an option to simulate SELECT * from

[Luca Burgazzoli (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15701344#comment-15701344
 ] 

Luca Burgazzoli commented on CAMEL-10452:
-

Another option is to generate such "query" while generating the DTO (by maven)
I also found http://sfdcbeginner.com/select-all-fields-in-soql.html, do not 
know if it is applicable here.


> camel-salesforce: Add an option to simulate SELECT * from
> -
>
> Key: CAMEL-10452
> URL: https://issues.apache.org/jira/browse/CAMEL-10452
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-salesforce
>Reporter: Luca Burgazzoli
>Assignee: Zoran Regvart
>Priority: Minor
> Fix For: 2.19.0
>
>
> As today it is not possible to run a query like SELECT * from but one is 
> forced to list all the field he want.
> It would be nice to auto generate a statement using SObject meta data so one 
> can write:
> from("salesforce:stream?SObjectName=Case=true")
> to get all the fields the SObjectName supports.
> [~dhirajsb] what do you think ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)