Hi
Can you tell more about how you run that application? Is it in some
server and if so what is that? And do you run as WAR / OSGi or
something else.
And make sure you do not have mixed version of Camel. As it sounds
like you got both 2.14 and 2.13 etc.
And can you paste the entire stracktrace o
Hello.
I add next maven dependency:
and I have next configuration inside camelContext
when I start my standalone application, I got next exception:
same configuration with jersey or netty-http works as expected.
--
View this message in context:
http://camel.465427.n5.nabble
Deleted ~/.m2/repository and rebuilt everything. Same problem. Going back
to 2.13.2.
cg
On Sat, Sep 20, 2014 at 9:02 AM, Camel Guy wrote:
> Looks like the latest one to me. Also, I ran -U with mvn install and
> also clean.
>
> I will try again in a few hours.
>
> cg
>
>
> On Saturday, September
If you invoke the backend service with PAYLOAD data formate message you need to
setup the BindingOperation for it.
My suggestion if you want to use xslt to the transformation, you can just use
MESSAGE data formate to invoke the back end service.
--
Willem Jiang
Red Hat, Inc.
Web: http://ww
Hi,
I just checked the camel-core.jar of Apache Camel 2.14.0, there is a class of
RestConsumerFactory.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On September
Hi Keshav,
Looking at SftpOperations.java[1] it is obvious that both these
configuration parameters are set automatically when defining a
compression level above 0.
[1]
https://github.com/apache/camel/blob/master/components/camel-ftp/src/main/java/org/apache/camel/component/file/remote/SftpOpera
Hi
Yeah allow to configure those mappings on camel-jackson could be a
good idea. Feel free to log a JIRA ticket.
On Fri, Sep 12, 2014 at 11:35 PM, rickaroni wrote:
> Hi,
>
> JSON libraries like Jackson and XStream provide ways of overriding the
> serializers/deserializers that get used for vario
On Tue, Sep 16, 2014 at 1:06 PM, Baweja, Keshav
wrote:
> Hello
>
> JSch has configuration parameters to set compression algorithm for client to
> server and server to client transport.
>
> compression.c2s
> Compression algorithms for client-to-server transport. The default is
> "none", but t
Hi
Don't you have more in the stacktrace or some other error? There is
maybe some NPE that hides this error.
On Fri, Sep 19, 2014 at 1:53 PM, David Karlsen wrote:
> With the config:
>
>
>
>
> I get:
>
> .. because of Failed to set property: prettyPrint on:
> org.ap
Looks like the latest one to me. Also, I ran -U with mvn install and
also clean.
I will try again in a few hours.
cg
On Saturday, September 20, 2014, Willem Jiang
wrote:
> Hi,
>
> Can you check if you camel-core jar is the latest one.
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> Web: http://www.
Hi,
Can you check if you camel-core jar is the latest one.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On September 20, 2014 at 2:08:34 PM, Camel Guy (ca...@dev
if the call to the original web service, the change will dataFormat MESSAGE
by PAYLOAD, The error is:
The PayLoad elements cannot fit with the message parts of the
BindingOperation. Please check the BindingOperation and PayLoadMessage.
I make the first transformation successfully receiving the
Do the conversion after:
Henrique Viecili
On 20 September 2014 00:00, aioria3077 wrote:
> *thanks for replying, really like right before calling xsl transformer, I
> have this line*
>
>
> * *
>
>
> will try to put it back then see what happens.
>
> any
13 matches
Mail list logo