Thanks! I tried cobertura too, however the report seems to be generated for
the java classes alone and not for the route in itself. I am not sure if I
am missing something or if this is what is expected.
Thanks
Rakesh
--
View this message in context:
Hi,
I tried testing an upgrade from SMX 4.5.3 to 5.0.0 using a functioning
python test client that sends a STOMP message through ActiveMQ to a
functioning Camel route (updated dependencies for the new version of
camel and such) using the Java DSL to forward it through a processor.
However,
On Tue, Apr 8, 2014 at 8:35 AM, ayilliath ayilli...@gmail.com wrote:
Thanks! I tried cobertura too, however the report seems to be generated for
the java classes alone and not for the route in itself. I am not sure if I
am missing something or if this is what is expected.
There is no tooling
Hi
You may need to set a charset to support reading the file with a given
charset that supports those extended charachters
http://camel.apache.org/file2
Or set the jvm -D file.encoding option or something.
Also java.util.Scanner parsing with those special chars is likely a
common problem, so
Hi
You can try with mapMailMessage=false, and then use Camel's error
handler if parsing the body / attachments of the mail fails.
Though there was a bug in Camel when using mapMailMessage=false. You
may need to use next release of Camel and/or latest release if the bug
was fixed in that release.
Guys any advice?
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-use-CAMEL-to-send-the-acknowledgement-and-xml-output-to-vendors-on-different-platform-tp5749906p5749941.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi
Thanks Claus, you are right it is an encoding issue !
And a simple :
from(file://[...]charset=iso-8859-1)
Solve it.
I am never used java.util.Scanner to program file parsing (opencsv, old
bufferreaader etc .) but I have never add this kind of encoding problem ...
By the way, thank
Hi,
I have a unique problem with a value created in one of the sub-routes in a
multicast to be used in another.
Eg:
multicast stopOnException=true
to uri=direct:archive/
to uri=direct:validate/
to uri=direct:process1/
to uri=direct:process2/
to
Thanks Claus, I'll give that a try.
--
View this message in context:
http://camel.465427.n5.nabble.com/test-coverage-tp5749876p5749944.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hello,
You can try with mapMailMessage=false, and then use Camel's error
handler if parsing the body / attachments of the mail fails.
this would only prevent this special error, but perhaps there will others rise
in the future.
Though there was a bug in Camel when using mapMailMessage=false.
You are using multicast so its a copy of the message that is being
processed by each one. If you want to share something then you can use
an aggregation strategy on the multicast to merge in results as you
want.
Maybe you can just use a pipes and filters style instead of multicast,
then its the
Hello,
I need urgent help regarding the output payload of a restlet being
truncated.
I have a route 'ABC' which uses a restlet to accept a valid JSON from its
client (Android App) and calls another route 'XYZ' (using direct-vm
component), which is deployed as part of another bundle. This route
Hi
See
http://camel.apache.org/how-to-remove-the-http-protocol-headers-in-the-camel-message.html
And you can try removing content length header
from uri=restlet:xxx/
removeHeader headerName=Content-Header/
As it may be from the incoming message
On Tue, Apr 8, 2014 at 2:26 PM, abhijit.kulkarni
Hi All,
I am new to Apache camel framework and am getting the below error when
trying to decode a attachement using Base64Decoder. I am using IMAP
protocol.
com.sun.mail.util.DecodingException: BASE64Decoder: Error in encoded stream:
needed at least 2 valid base64 characters, but only got 0
Thank you very much ! It made my day !!!
The Header Content-Length was set when the route 'XYZ' called the external
URL using the http4 component. Basically this external URL returned an ID
which was 5 character long in its payload.
I modified the route 'ABC' to remove the header after the
For the HTTP, Web Service, as the Message Exchange Pattern is InOut, you can
send the acknowledgement by setting the out message of the exchange in your
processor.
For the JMS and File system, the Message Exchange pattern is InOnly, the camel
route could be litter different.
For the JMS
Hello all! I'm working on this problem a lot of time now and can't seem to
find any final solution to it.
I have a message producer that should work as a broadcaster, posting
messages on two different topics. The publisher's posting process follows
the flow :
-Creating connection to the factory
Hi,
You can't use regular Java in a simple expression, as the latter is supposed
to be simple :) . Consider using Groovy expressions [1] instead.
Cheers.
[1] http://camel.apache.org/groovy.html
--
View this message in context:
Ok, I got it ! It was due to:
a mistake in my wsdl: soap:address location was incorrect
and
wrong address in my cxf endpoint.
Best,
Nicolas.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-cxf-wsdl-first-pojo-Can-t-find-the-BindingOperationInfo-tp5749822p5749967.html
Hi
I wonder if you could help me. I am getting the exception below when trying
to use sslContextParameter. I am well aware that this has been fixed (
https://issues.apache.org/jira/browse/CAMEL-6700), which was committed to
camel 2.11. I am currently using Camel 2.10 version with Fuse ESB 6.0. Is
Hi
Thanks for reporting and providing a better solution.
On Mon, Apr 7, 2014 at 1:51 PM, sbo13 sb...@gmx.de wrote:
Hi,
When looking into the JaxbDataFormat I saw that the Schema is parsed for
every method call, which dosn't make sense, since the Schema is threadsafe
(see it's javadoc)
I
Hi,
I would like to add a WSS4JOutInterceptor to my CXF endpoint.
I do not use a samlPropFile.
I configure my interceptor as follows:
cxf:outInterceptors
bean id=wssOutInterceptor
On 08/04/14 05:59, vrahul wrote:
Cxf with camel always surprised me. ExceptionMapper is a basic requirement
expected from the restfull server. Please let me know once you are done with
the investigation :) .
This is a urgency for me to have a exception mapper or similar alternate.
I guess the
Hi,
Is connection pooling needed when sending to an _embedded_ ActiveMQ broker
from Camel using the VM protocol vm://? If so, why?
According to page 288 of the Camel In Action book the VM protocol bypasses
the TCP stack tends to make me think not.
The example given here
Thanks Willem. I was looking for something like below configuration(from
http://camel.apache.org/walk-through-another-example.html). But i am not
sure which method of validateOrder bean will be called as no specific method
has been specified here. Any idea?
route
from uri=jms:queue:order/
As described in http://camel.apache.org/bean-binding.html (which is refered
in http://camel.apache.org/walk-through-another-example.html) there is no
special method and choosing the right method (from Camel) is complicated.
The easiest POJO you could have is
public class ValidateOrder {
I found my problem: https://issues.apache.org/jira/browse/CAMEL-5172
So with 2.6.0, I didn't see exception but null.
I want to use the old behavior. So I implemented TypeConverter and custom
genericFileToString with the old behavior. My converter return null but
after
27 matches
Mail list logo