See this FAQ
http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html
On Tue, Mar 8, 2011 at 4:04 AM, Bill wrote:
> Hi,
> The In message contains the request message. and the Out message contains
> the reply message.
>
> But I confused as follows:
>
> When my route : from
On Mon, Mar 7, 2011 at 9:34 PM, lone squirrely
wrote:
> Thank you for pointing this out (and for the tutorial!). I get so
> lost in the documentation for spring and camel.
>
> I now have both my server and client building and coming up. I
> (think) i see them get a ref to the AMQ Broker but what
On Mon, Mar 7, 2011 at 5:35 PM, Marco Crivellaro
wrote:
> thanks,
> the temporary file name we use is also dinamic, which is the Exchange header
> to set the tempFileName uri property?
>
There is no header for that option. But the tempFileName can be set
using simple expression, eg tempFileName=$
Hi,
The In message contains the request message. and the Out message contains
the reply message.
But I confused as follows:
When my route : from() ---> process() ---> fileEndpoint.
In process, I set the file name, when I set the
getIn().setHeader("CamelFileName","test.txt"); It runs
Thanks for the guidance Claus!
I dug further on the capabilities of netty and realized that they already
have what I need.
I configured LengthFieldBasedFrameDecoder for decoding the message and
LengthFieldPrepender for encoding the message. It worked like a charm. I
configured the service endp
Thank you for pointing this out (and for the tutorial!). I get so
lost in the documentation for spring and camel.
I now have both my server and client building and coming up. I
(think) i see them get a ref to the AMQ Broker but what I don't see is
the run happening.
I took the client in the tut
Thanks Claus, that link proved very useful. The only part of this that is
Camel specific is that Camel sets the message expiration for InOut exchanges
based on the request timeout. It would be nice if these two were not tied
together. For instance, the request timeout is simply the time that the
cl
thanks,
the temporary file name we use is also dinamic, which is the Exchange header
to set the tempFileName uri property?
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-caching-producers-tp3412417p3412698.html
Sent from the Camel - Users mailing list archive at Nabble.c
Welcome to the Camel community
The pattern you talk about smells like the composite message processor
http://camel.apache.org/composed-message-processor.html
Its in the EIP book as well.
However in your case you don't split a message beforehand, but send a
message to 2 clients.
In Camel you cou
On Mon, Mar 7, 2011 at 5:13 PM, Marco Crivellaro
wrote:
> problem is I am using a recipientList to serve our endpoints as we are not
> serving only FTP endpoints.
> any way to limit LRU cache?
>
Just send to a bean or whatever instead of directly to ftp. Then in
the bean you can set the filename
problem is I am using a recipientList to serve our endpoints as we are not
serving only FTP endpoints.
any way to limit LRU cache?
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-caching-producers-tp3412417p3412665.html
Sent from the Camel - Users mailing list archive at
On Mon, Mar 7, 2011 at 5:02 PM, Marco Crivellaro
wrote:
> that means that if I need to deliver to 1000 distinct ftp servers I should
> expect space to be allocated even if they are used just once? Isn't there a
> way to get the garbage collected?
>
The cache is LRU based so they will be discarded
that means that if I need to deliver to 1000 distinct ftp servers I should
expect space to be allocated even if they are used just once? Isn't there a
way to get the garbage collected?
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-caching-producers-tp3412417p3412643.htm
For FTP set the filename as a header and reuse the endpoint uri if possible.
That's the way to reuse ftp endpoints.
On Mon, Mar 7, 2011 at 4:56 PM, Marco Crivellaro
wrote:
> even setting cache limit to 10 and disabling camel JMX support
> (-Dorg.apache.camel.jmx.disabled=true)
> I can see the nu
even setting cache limit to 10 and disabling camel JMX support
(-Dorg.apache.camel.jmx.disabled=true)
I can see the number of FTPClient, FTPConfiguration, FTPOperations,
FTPEndpoint and ListenerList growing constantly.
Each exchange I run has a distinct endpoint URI
--
View this message in contex
This is much easier in Camel 2.7. So maybe you can just wait for that
release.
eg in 2.7 you just add the spring context listener
and the camel servlet. And camel don't care if spring or the servlet startup
first. although we recommend setting the load-on-startup configuration on
the servlet.
--
You're absolutely correct Willem, I had to close the inputstream and no
exception more is raised, thanks!
One more question, am I correct to assume that the "moveFailed" folder is
only applied if there is any exception in the processing not the endpoint?
I wanted to move the file directly to the
On Mon, Mar 7, 2011 at 2:42 PM, Marco Crivellaro
wrote:
> I've tested latest snapshot, everything works like a charm!
>
Thanks for testing and reporting back.
> Camel rocks!
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/issue-with-sftp-producer-tp3408052p3412452.ht
You can try to look into the source and patch it to see if you can get
it working.
We love contributions
http://camel.apache.org/contributing.html
Or configure 2 different MailComponent with their own
MailConfiguration and MailSession instances.
That may be a bit verbose in the XML.
On Sun, Mar
I've tested latest snapshot, everything works like a charm!
Camel rocks!
--
View this message in context:
http://camel.465427.n5.nabble.com/issue-with-sftp-producer-tp3408052p3412452.html
Sent from the Camel - Users mailing list archive at Nabble.com.
thanks a lot!
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-caching-producers-tp3412417p3412449.html
Sent from the Camel - Users mailing list archive at Nabble.com.
See
http://camel.apache.org/how-do-i-configure-the-default-maximum-cache-size-for-producercache-or-producertemplate.html
On Mon, Mar 7, 2011 at 2:18 PM, Marco Crivellaro
wrote:
> Hi all,
> having a look the to memory usage of my camel based application; I've found
> out camel is caching producer
Hi all,
having a look the to memory usage of my camel based application; I've found
out camel is caching producers.
I am running a huge amount of deliveries to distinct endpoints, is there a
way to limit the amount of producers cached?
--
View this message in context:
http://camel.465427.n5.nabbl
the client is as follows (and this kind of invocation works for calling other
non MTOM services through the proxy)
public final class RaggiPortType_RaggiPort_Client {
private static final QName SERVICE_NAME = new QName(
"http://it.insiel.raggi/";, "raggiService");
yes MTOM is enabled
http://it.insiel.raggi/"; id="raggiporttype"
implementor="raggi.insiel.it.RaggiPortTypeImpl"
wsdlLocation="wsdl/raggi.wsdl"
endpointName="tns:raggiPort" serviceName="tns:raggiService"
address="/raggiPort">
yes MTOM is enabled
and the service works when called directly, it doesn't when called through
the proxy
--
View this message in context:
http://camel.465427.
Did your server enable the MTOM[1] on the server side?
[1]https://cwiki.apache.org/confluence/display/CXF20DOC/MTOM
On 3/7/11 6:33 PM, avonm wrote:
I printed the message i'm trying to route, it's the following
--uuid:f35eefc8-51d9-45d4-9a97-677536580611
Content-Type: application/xop+xml; chars
please see the message on the site, in the email it isn't rendered correclty
--
View this message in context:
http://camel.465427.n5.nabble.com/http-proxy-and-mtom-attachments-tp3407911p3412227.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I printed the message i'm trying to route, more or less it's the following
(except for line breaks which aren't correctly rendered here)
--uuid:f35eefc8-51d9-45d4-9a97-677536580611
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml";
Content-Transfer-Encoding: binary
Content-ID:
I printed the message i'm trying to route, it's the following
--uuid:f35eefc8-51d9-45d4-9a97-677536580611
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml";
Content-Transfer-Encoding: binary
Content-ID:
_inviaRadiografia_codPaziente1400875
--uuid:f35eefc8-51d9-45d4-9a97-677536580
The defaultOperationName and defaultOperationNamespace should do the
same work, but it only work if you just send one type of message.
On 3/7/11 1:58 PM, Scott Came wrote:
Thanks, Willem. I thought I had tried setting the operation on the endpoint
but still had a problem...I'll try it again t
31 matches
Mail list logo