Oh so you are using _ in the getters, try with
:#${body.getVrow_id()}"
I wonder if the getter detection has a glitch when you use underscores.
On Thu, Apr 7, 2016 at 7:30 AM, onders wrote:
> Here it is;
>
> import java.io.Serializable;
>
> public class MyBean implements Serializable {
>
>
Here it is;
import java.io.Serializable;
public class MyBean implements Serializable {
/**
*
*/
private static final long serialVersionUID = 1L;
private String vrow_id;
public String getVrow_id() {
return vrow_id
What is the bean code for that bean ?
On Thu, Apr 7, 2016 at 7:22 AM, onders wrote:
> I think the code snippet i sent earlier had outputClass option missing.
> (I was playing it around).
>
> So what i meant to describe was as the following...
>
> from("sql:select rowid vrow_id fro
I think the code snippet i sent earlier had outputClass option missing.
(I was playing it around).
So what i meant to describe was as the following...
from("sql:select rowid vrow_id from myTable where nstatus =
0?*outputClass=" + MyBean.class.getName()
+ "*&onCons
Hi
Ah can you log that in the JIRA
On Wed, Apr 6, 2016 at 10:42 PM, Tim Dudgeon wrote:
> I'm hit a wierd problem when trying to upgrade from 2.16.2 to 2.17.0
>
> I have routes built using REST DSL, and this includes swagger definitions.
> With 2.1.6.2 all was good.
> On switching to 2.17.0 I fin
The output from the from is a Map, so you should refer to the value by
referring to the column name.
where VROW_ID = :#vrow_id
On Thu, Apr 7, 2016 at 6:44 AM, onders wrote:
> Hi,
>
> This is the route code.
>
> from("sql:select rowid vrow_id from myTable where nstatus =
>
Camel 2.15.1, using aggregator2 with JPA endpoint, the timeout appears to be
forcing hibernate to increment the transaction count every 5 seconds, even
if the agreggator is empty; is that normal?
true
Hi Greg,
I am using XML DSL to configure the CXF component.
There isnt much online help for XML DSL for CXF_MESSAGE configuration for
processing soap attachments.
Below is my current configuration with dataformat as MESSAGE.
camel-context file:
Basic ZzRzLmludGVncmF0aW9u
Hi,
This is the route code.
from("sql:select rowid vrow_id from myTable where nstatus = 0" +
MyBean.class.getName()
+ "&onConsume=update myTable set nstatus = 1
where VROW_ID =
:#${body.vrow_id}")
.r
Hi
I am trying to setup a ZooKeeper route policy like this
ZooKeeperRoutePolicy policy = new
ZooKeeperRoutePolicy("zookeeper:localhost/regexTest1?create=true", 1);
from("direct:start").routePolicy(policy).to(“mock:end”);
And when I run my unit test to trigger the route, I get the following exce
I'm hit a wierd problem when trying to upgrade from 2.16.2 to 2.17.0
I have routes built using REST DSL, and this includes swagger definitions.
With 2.1.6.2 all was good.
On switching to 2.17.0 I find that having a swagger query parameter
definition causes a header property to be defined as an e
Great, thanks.
Updating to Camel 2.17.0 fixed the need to specify the context name, and
setting the custom thread pool also works now.
I updated the example to reflect this.
Thanks
Tim
On 06/04/2016 18:07, Antonin Stefanutti wrote:
Tim,
For the second problem, I’ve just looked at how Camel l
I was able to make it work with a older version of camel 2.13.2. But with the
2.16.1 version it is throwing this issue. Ideally I would be happy to
upgrade to a newer version of Camel if this issue could be addressed using
any higher version, instead of reverting back to a previous one.
--
View
I was able to make it work with a older version of camel 2.13.2. But with the
2.16.1 version it is throwing this issue.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Hive-Issue-tp5780522p5780613.html
Sent from the Camel - Users mailing list archive at Nabble.com.
It is camel 2.16.1 version
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Hive-Issue-tp5780522p5780612.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Tim,
For the second problem, I’ve just looked at how Camel looks up for the custom
ExecutorService and it actually looks up the CDI registry for a named bean of
type ExecutorService, so you can just produce your custom ExecutorService
instead of a ThreadPoolProfile bean. Otherwise, it falls bac
Hi Tim,
I see that it uses Camel 2.16.2. The Camel CDI component has been rewritten and
improved in Camel 2.17.0.
Could you upgrade your Camel dependencies to 2.17.0 version? That should solve
the issues.
Antonin
> On 06 Apr 2016, at 18:13, Tim Dudgeon wrote:
>
> Hi Antonin
>
> I tried you
Hi Antonin
I tried your suggestion for problem 2, but couldn't get it to work.
I've put an example that illustrates both problems here:
https://github.com/tdudgeon/camel-cdi-servlet-example
To reproduce the first problem just remove the @ContextName annotation
from the HelloRoute class.
To re
Hello,I need to implement a split/aggregate route same as in official
documentation example but with little bit more complex logic:
Form docs: http://camel.apache.org/composed-message-processor.html
from("direct:start").split(body().tokenize("@"), new MyOrderStrategy())
.to("bean:MyOrd
I tried flatten=true still the same issue.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-ftp-550-directory-not-found-tp5780588p5780599.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi, I have a problem with infinispanIdempotent.
This is my config :
/ag_02:Messaggio/ag_02:Data_Giro
CamelDuplicateMessage
I have two EAP server in domain mode w
Hi Tim,
> On 06 Apr 2016, at 16:19, Tim Dudgeon wrote:
>
> I've found a couple of things I don't understand when using the camel-cdi
> component.
>
> 1. The @ContextName("customname") annotation can be used to specify a custom
> name for the camel context. But I'm finding that this annotation
Zip file already exists in the FTP server folder
Zip file exists in the ftp server folder : C:\gtech with the name
HUT_Week54_09Apr-15Apr.zip
My task is to unzip it and process the csv files in the unzipped folder.
I am trying to unzip it in the folder : C:\gtech\unzip
--
View this mes
Hi,
I am using a Camel CFXRS server, configured with the SimpleConsumer binding
style, to expose REST services from my web application. Although I have seen no
issues with Camel injecting into the exchange message header the path
parameters that are defined on the REST interface, the query para
I've found a couple of things I don't understand when using the
camel-cdi component.
1. The @ContextName("customname") annotation can be used to specify a
custom name for the camel context. But I'm finding that this annotation
is essential.
e.g. if my app comprise just of a couple of classes e
Is this with uploading the file to the FTP server?
As the file name header may heave leading paths from the consumer /
zip data format, you can set flattern=true on the ftp uri to strip any
leading paths.
On Wed, Apr 6, 2016 at 4:04 PM, saverineni wrote:
> Claus, thanks for the reply.
>
> I am g
Claus, thanks for the reply.
I am getting the same exception after adding the stepwise=false.
This is the log from filezilla server interface :
(000299)06/04/2016 14:59:03 - (not logged in) (127.0.0.1)> USER testftp
(000299)06/04/2016 14:59:03 - (not logged in) (127.0.0.1)> 331 Password
required
Try set stepwise=false
http://camel.apache.org/ftp2
On Wed, Apr 6, 2016 at 3:38 PM, saverineni wrote:
> Hi Guys
>
> My camel route is trying to download and unzip a zip file from ftp server
> (Filezilla).
>
> My Ftp configuration :
>
> Root directory(home directory) is set to c:\
> thg.ftp.incomi
Hi Guys
My camel route is trying to download and unzip a zip file from ftp server
(Filezilla).
My Ftp configuration :
Root directory(home directory) is set to c:\
thg.ftp.incomingDir=/fileprocessor
thg.ftp.toDir=/unzip
ftp://${thg.ftp.username}@${thg.ftp.server}/${thg.ftp.incomingDir}/?passwor
As suggested always configure each class name in that file. That makes
the discovery easier at runtime as there is no package scanning
happening which is not as good to perform, when you run in various
different containers and environments with different class loading
mehanism.
All the Camel compo
Can you post the route code again - it seems you cut out some details
or it was formatted poorly.
On Wed, Apr 6, 2016 at 1:50 PM, onders wrote:
> Did anybody have a chance to look at it?
>
> Regards
> Önder
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/DefaultSq
Did anybody have a chance to look at it?
Regards
Önder
--
View this message in context:
http://camel.465427.n5.nabble.com/DefaultSqlPrepareStatementStrategy-lookupParameter-when-onConsume-used-in-SQL-component-tp5780437p5780585.html
Sent from the Camel - Users mailing list archive at Nabble.co
ok,
instead of full class name now i insert only the package in TypeConverter
file.
So if i add a new converter i only must annotate class and method with
@Converter
an save in the configured package.
-
kh
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-17-Co
Hello,
I have a route that should process request from CXF endpoint and return
results as JSON:
public class MyRoute extends RouteBuilder
{
// ... Autowired:
// msgRequestProcessor - converts json {string,string} to String of "\n"
delimited json string: {string}\n{string}
// RangeProcessor, Sin
As before, you need that file to tell Camel which classes or java
packages have type converters.
We recommend listing all the type coverter classes so you avoid
package scanning.
The class and methods must also be annotated with @Converter etc.
So you still need that file.
On Wed, Apr 6, 2016 a
In a version before i insert class of my converters under
/resources/META-INF/services/org/apache/camel/TypeConverter file
and works fine.
Now i delete this file and annotated classes with @Converter.
But i get this error 'Caused by:
org.apache.camel.NoTypeConversionAvailableException: No type
36 matches
Mail list logo
