On Fri, Dec 10, 2010 at 7:16 AM, mak wrote:
>
> Hi, I have the following route defined -
>
>
>
> from("timer://foo?period=5000").setBody(constant("select top 500 * from
> MyTable where processed = 0"))
> .to("jdbc:dataSource").split(body()).parallelProcessing()
> .pr
Hi,
If you use a TCP connection to your broker, then you need to set keep-alives
on your broker connection and alter the default settings for
connectionTimeout etc as appropriate.
Please check out the link below and alter your connection URI appropriately.
http://activemq.apache.org/tcp-transpo
Hi,
Can you please provide more details. Your posting is very vague and does not
give any kind of leads or useful information to even attempt an answer.
Cheers,
Ashwin...
-
-
Ashwin Karpe
Apache Camel Committer & Sr Principal Consulta
Hi,
The mail component does not inspect every payload to determine the
contentType and encoding. These need to be set in the URI and be in effect
for every request sent/received on an smtp connection.
Please check out the contentType and defaultEncoding properties on the mail
component and set a
On Fri, Dec 10, 2010 at 1:12 PM, Ashwin Karpe wrote:
>
> Hi,
>
> Can you please provide more details. Your posting is very vague and does not
> give any kind of leads or useful information to even attempt an answer.
>
Ashwin its false alarm. This guy is talking about the Apache HTTP
server (the w
Hi Ashwin,
Thanks for your response. I tried that before, but setting
"defaultEncoding=base64" in
the smtp URI does not seem to have any effect. It is still encoded as 7bit
(-Dmail.debug=true):
Content-Type: multipart/mixed;
boundary="=_Part_1_22750429.1291987863341"
firedTime: Fr
Hi
Try using the charset on the content type according to the spec
http://www.w3.org/International/O-HTTP-charset
On Fri, Dec 10, 2010 at 2:45 PM, Alfred Hiebl wrote:
>
> Hi Ashwin,
>
> Thanks for your response. I tried that before, but setting
> "defaultEncoding=base64" in
> the smtp URI does
https://issues.apache.org/jira/browse/SMX4NMR-239
--
View this message in context:
http://camel.465427.n5.nabble.com/Serialization-CamelAuthentication-is-null-tp3290948p3300369.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hello,
thanks for your help. The suggested workaround works fine as long as both
cxf:components are bound to the same WSDL.
What are the recommended steps, if an existing web service should be
provided by a new contract (WSDL of first cxf:component differs from WSDL
of second cxf:component).
I have a route setup that looks like this:
It's purpose is to run once at startup to get an intial value (in this
example I just have sending to out instead of doing anything with the reply)
and never run again.
The shutdownRequestor bean has a handler that looks like this:
public
Hello all!
I'm using Camel 2.2.0 with Java 1.6.20, but this problem also exists in
Camel 2.5.0:
It looks like the streaming() mode did not work (for me) in conjunction with
xpath. I created a simple unit test:
{code}
public class StreamingTest extends CamelTestSupport {
@Test
publi
I'd really recommend using VTD or something similar to split large XML. Much
faster and more memory efficient.
Define a bean that does the split and returns an iterator and supply it as
the method for split.
Simple example using VTD to split XML:
http://stackoverflow.com/questions/1640472/java-ho
Hi,
I'm using camel 2.2 to create an aggregation route with an onException.
Unfortunately it appears the onException.end() and
aggregate().groupExchanges() are exclusive? I know the .end() is required on
the onException, but adding it causes the groupExchanges to warn "the method
groupExchanges i
@Christian. Perhaps Smooks can help in this scenario? The upcoming 1.4
release offers Camel support out of the box. Processing huge (gigabyte)
files is where Smooks is suppose to excel.
http://blog.smooks.org/2010/10/26/smooks-v1-4-beta1-available-for-download/
--
View this message in context:
14 matches
Mail list logo