On Tue, Jul 19, 2011 at 9:54 PM, dlj wrote:
> Unfortunately that didn't work. It looks like the problem may lay in
> GenericFileProducer.createTempFileName(). The method attempts to normalizes
> the filename, but the normalizePath( filename ) method on the
> RemoteFileProducer doesn't do anything
Yes I am quite sure a temp queue can only be used for replies.
Btw. when you do not set the replyTo option you will automatically use a
temporary queue.
In fact to not use a reply queue you have to make sure the message
exchange pattern for the endpoint that sends to jms is InOnly.
Christian
Hi Ashwin and Dana,
I looked up the jms spec for the temp queue API. See:
http://download.oracle.com/javaee/1.4/api/javax/jms/Session.html#createTemporaryQueue%28%29
This clearly shows that you can not specify the name of the temp queue
when creating it. So I can not imagine it to be used as a
camel:run doesn't support to provide the OSGi services like you used in
the ServiceMix.
If you want support the camel:run with your osgi application bundle. You
may consider to provide your camel context with two layer.
one is for the pure Spring configuration without any OSGi service, you
s
camel-jms is based on Spring JMS which supports lots of JMS implementers.
You just need to provide an JMS connector which can talk to the JBoss
Messaging broker for the JMS component.
On 7/18/11 4:57 PM, Don Doffe wrote:
Hi,
does anybody have a example how to configure camel with JBoss Messag
Hmm, I am not so sure about that.
The only difference between a temporary and a regular queue is that the
messages on temporary queues do not outlive the broker and/or active
connections. If there are no active producers/consumers to the temporary
destination, the destination is removed by the bro
would you mind showing the details of config.cfg. I believe there is some
config issue in your end that you need to specify somethig like below
statement. Also, If you can show me the stack trace of your null pointer,
then it could help me to see where and how you are experiencing the issue.
to(
Thanks for the reply Christian,
Yea I was a bit confused because the camel documentation describes the jms
uri as jms:[temp:][queue:|topic:]destinationName[?options].
I'll try the replyTo option and see how that goes.
But just to confirm temporary queues can only be replied to, not as sources
o
Hi Dana,
as far as I know you can not directly use a temp queue as a destination.
Temp queues are special in jms as you ask jms to create a temp queue for
you and then get its name.
So in camel you can use temp queues only for replies. I have no idea why
there is a temp: syntax in the jms comp
I'm still pretty new to camel and activemq.
//env
java 1.5
spring 3.0.5
camel 2.6.0
activemq 5.4.2
I'm trying to create a route from a regular activemq queue to a temp queue.
I'm not 100% sure where I'm going wrong.
If I set my camel route from -> to to use a regular queue everything works
f
Unfortunately that didn't work. It looks like the problem may lay in
GenericFileProducer.createTempFileName(). The method attempts to normalizes
the filename, but the normalizePath( filename ) method on the
RemoteFileProducer doesn't do anything except return the path as-is. At this
point, the file
On Mon, Jul 18, 2011 at 4:05 PM, pvenini wrote:
> Hi, I finally managed to go forward a few steps by modifying the quickfix
> converter. The route I'm building looks like this:
>
> from("quickfix:config.cfg").
> filter(
>
> header(QuickfixjEndpoint.MESSAGE_TYPE_KEY).isEqualTo(MsgType.ORDER_SINGLE)
Thanks very much for the help.
Everything to work now.. I had an issue with an odlder version of camel not
working with spring 3.0 (transaction not rolling back), but it seems to work
with 2.7 and 3.0.5 (spring)
Thanks again...
--
Albert Friedland
(212) 816-
On Tue, Jul 19, 2011 at 11:29 AM, Naira & Kobo wrote:
> Hi,
>
> I 'd like to process a message (basically modify an exchange body) based on
> an identifier (which is also part of the message).
>
> The processing on the exchange body can be quite handful and may involve
> manipulating bytes (which
If I understand correctly part from("jbi:endpoint") causes registration of
endpoint in the bus. It doesn't have a external interface, so the
"http://localhost:8889/MyService"; points only to namespace and endpoint
identifier, not to jetty port or something like that. If you wish expose HTTP
end
On 2011-7-19, at 下午8:56, rrino Gazeta.pl wrote:
Hi
I want to start my old route which was started by timer
from("timer://tutorial?fixedRate=true&delay=3000&period=2")
.setBody(constant(msg))
.to("jbi:endpoint:urn:com:example:prototype:jms:provider");
with webservice invocation eg ;
Hi
I want to start my old route which was started by timer
from("timer://tutorial?fixedRate=true&delay=3000&period=2")
.setBody(constant(msg))
.to("jbi:endpoint:urn:com:example:prototype:jms:provider");
with webservice invocation eg ;
from("jbi:endpoint:http://localhost:8889/MySer
Hi,
Yes, you can configure a cron scheduled route policy which starts a route
with a Camel JMS consumer at 9:00 am and brings it down at 12:00 am with a
graceful shutdown...
Should have thought of that :)...
Cheers,
Ashwin...
-
-
Ashw
On Tue, Jul 19, 2011 at 01:23:32PM +0200, Claus Ibsen wrote:
> > Shall I file a Jira?
> >
>
> Yep you bet, and you are welcome to work on a patch as well.
>
Will do, when I get some time.
Only seems right, given that I submitted the TraceEventHandler stuff in the
first place :)
As usual, the f
On Tue, Jul 19, 2011 at 1:21 PM, James Talbut wrote:
> That's it!
> The org.apache.camel.processor.interceptor.TraceInterceptor doesn't work
> properly for Async processing.
>
> It has:
> try {
> // special for interceptor where we need to keep booking how
> far we have
That's it!
The org.apache.camel.processor.interceptor.TraceInterceptor doesn't work
properly for Async processing.
It has:
try {
// special for interceptor where we need to keep booking how
far we have routed in the intercepted processors
if (node.getP
On Tue, Jul 19, 2011 at 1:10 PM, James Talbut wrote:
> Willem,
>
> I think I've narrowed it down to saying that when it's asynchronous the
> TraceHandler is being called before the Out message is available, whereas
> when it is synchronous
> the TraceHandler is not called until the Out message i
Willem,
I think I've narrowed it down to saying that when it's asynchronous the
TraceHandler is being called before the Out message is available, whereas when
it is synchronous
the TraceHandler is not called until the Out message is ready.
I suspect this means it's called as soon as the CXF mes
Hi
Just noticed from Ashwin's blog
http://opensourceknowledge.blogspot.com/2010/09/developed-capability-in-camel-to.html
Could http://camel.apache.org/cronscheduledroutepolicy.html this be used?
I'm using spring based DSL.
rgds
srimin
--
View this message in context:
http://camel.465427.n5.
Willem,
Yes, that works (obviously missing out on the benefits of Asynch).
The two MessageLoggers are based on the code in the CXF message loggers - they
use the same techniques to capture the on-the-wire message and then:
MessageLoggerOut simply logs the message along with a correlation ID foun
What are the MessageLogger{In|Out}bound doing ?
Can you try to change your route like this to see if the error goes out?
uri="cxf:bean:serviceGroups?dataFormat=PAYLOAD&synchronous=false"/>
uri="cxf:bean:targetGroups?dataFormat=PAYLOAD&synchronous=true"/>
On 7/19/11 6:20 PM, Jam
Willem,
I'm afraid I can't give you the actual WSDL and URLs (they're from a third
party), but I don't think they'll make a difference, they just return a
soap:Fault.
The route (and associated config) is:
http://camel.apache.org/schema/cxf"/>
http://camel.apache.org/schema/cxf"/>
Can you post your route, or submit a simple test case to show the error ?
It look like a time issue of CXF endpoint which is working in async
module by default. But I cannot tell more just by looking up the
description that you gave in the mail.
On 7/19/11 4:43 PM, James Talbut wrote:
Hi,
Hi all!
I would like to ask you which would be the best way of attempting a
redelivery after a recipient list timeout.
I currently have a route which receives a message from JMS with a list of
recipients and through a processor it changes the payload of the message and
builds the recipientlist hea
Hi,
I 'd like to process a message (basically modify an exchange body) based on
an identifier (which is also part of the message).
The processing on the exchange body can be quite handful and may involve
manipulating bytes (which seem to influence my decision to use groovy).
Is there a way I c
Hi,
I'm using a combination of a Camel TraceHandler and a CXF interceptor to
capture on-the-wire messages and log them with the Camel message.
In normal use this all works, but when I have an error the Camel TraceHandler
isn't being called (the rest of the route is picking up the error correctly
FWIW this is what I did for a transactional route to stop messages disappearing
from the original queue if the broker went down:
http://activemq.apache.org/schema/core";
id="matrixBrokerID"
brokerName="matrixBroke
32 matches
Mail list logo
