On Tue, Aug 25, 2009 at 1:47 PM, dmurat wrote:
>
> I'm having this same problem. Since I'm targeting embedded deployment in
> desktop app, it is kind of serious issue for me.
>
It is a harder problem to solve than at first though as Spring JMS
does not expose good methods to graceful / nicely shut
Martin
Thanks for the patch.
I assume it just works around whens bundle are not STARTED. And in
case its STARTED later it wont be picked up?
Maybe the overall strategy should be to listen for bundle activity and
be able to register type converters when a bundle changes it stare to
STARTED.
And w
Hi
Could you go ask at the MINA user forum and check the mina
documentation / google it.
And then come back with your findings. Then we can see if there is a
missing option needed in Camel.
You can always use your own "protocol" and thus configure a TextLine
protocol that has a bigger buffer if t
On Wed, Aug 26, 2009 at 4:09 AM, William Tam wrote:
> Hi Todd and Willem,
>
> Willem's suggestion would work. We do support multiple URI templates
> on a same route.
>
> So, you could do something like: (also see
> http://cwiki.apache.org/confluence/display/CAMEL/Restlet)
>
>
>
> /blah.com
Hi
If you use maven then you wont have all this trouble with .jar hunt.
Here is the dependecy:list used for testing camel-jms which uses ActiveMQ.
Mind the list is for Camel 2.1-SNAPSHOT but it should give you an idea
which jars you may need.
Or look in your /lib folder which jars it have.
[IN
Hi
And the Camel tutorials have a CXF based wsdl first as well
http://camel.apache.org/tutorial-example-reportincident.html
On Wed, Aug 26, 2009 at 2:36 AM, Willem Jiang wrote:
> Hi,
>
> You can find some useful documents about the WSDL first approach on the CXF
> wiki site[1].
>
> [1] http://cxf
The Camel riders are pleased to introduce the Apache Camel 2.0.0
release [1]. This is a major overhaul of Camel that took more than a
year of efforts and is coming with about 760 issues resolved. We are
grateful to the entire community for its involvement. Your hard work
and constant atten
Hi Todd and Willem,
Willem's suggestion would work. We do support multiple URI templates
on a same route.
So, you could do something like: (also see
http://cwiki.apache.org/confluence/display/CAMEL/Restlet)
/blah.com/people/{id}
/blah.com/people/{id}.json
from("restlet:http:
Hi,
Maybe you need to set the receiveTimeout (MILLISECONDS) option on the
jms endpoint to let camel wait for the response longer.
BTW, you can check the Debug log for the exception.
long requestTimeout = endpoint.getConfiguration().getRequestTimeout();
try {
Message me
Yeah, you already find the answer yourself.
Here is the example[1] that you may need :)
[1]
https://svn.apache.org/repos/asf/camel/trunk/components/camel-http/src/main/java/org/apache/camel/component/http/BasicAuthenticationHttpClientConfigurer.java
Willem
Srivatsa Katta wrote:
Oh I believe
Hi,
I don't think current camel supports two froms within a single route.
But you can use the direct endpoint to reuse the route like this
from("restlet:blah.com/people/{id}").to("direct://myRoute");
from("restlet:blah.com/people/{id}.json").to("direct://myRoute");
from("direct://myRoute")...
Hi,
You can find some useful documents about the WSDL first approach on the
CXF wiki site[1].
[1] http://cxf.apache.org/docs/jax-ws.html
Willem
bgoetzmann wrote:
Thank you, I see that there a generation wsdl2java in the pom:
http://svn.apache.org/viewvc/camel/trunk/components/camel-cxf/pom
Hi
I just started to put Camel into our project and hit this exception which I
couldn't find a solution from googling many hours and I wonder if I didn't
something wrong since others is not complaining.
I used spring bean configuration files to config camel context, etc. When I
start my applica
Hello.
I'm sending messages with InOut pattern to a JMS topic and set the replyTo
to a predefined queue.
Most of the time everything works fine but...
I have a suspicious situation that under certain conditions, camel wont read
replies from that queue and fail with ExchangeTimedOutException.
I can
Oh I believe httpClientConfigurerRef option can be used.. will give it a
shot..
Srivatsa Katta wrote:
>
> Hi,
>
> Am using http component and the route looks something like this.
>
> from("direct:client").to("http://myhost:8080/?
> throwExceptionOnFailure=false");
>
> If the server is down/
Hi,
Am using http component and the route looks something like this.
from("direct:client").to("http://myhost:8080/?
throwExceptionOnFailure=false");
If the server is down/not reachable, the http component does retry for 3
times (as observed from the logs) and then throws up the connection time
I started to create a blog to talk about what I am trying to do. I also talk
about the current issues I have for testing.
http://www.baselogic.com/blog/java/testing-activemq-virtualtopics-using-camel-and-junit
---
Thank You…
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, De
Hi Fintan,
Thanks for clarifying. I thought that when TransactionErrorHandler is
used, there is no dead letter queue, and when exception is thrown it
is propagated back.
Claus has suggested to use 'transferException=true' param to
accomplish what I want, however I think it is available only since
Hi Ilya,
>>Route 2:
>>...
>>I was hoping this exception will be propagated up to my producer.
>>However, by default, with deadLetterQueue, the exception does not seem
>>to be propageted.
Oh, if the exception in this route actually gets raised, it looks like the
message is progressing further tha
Claus,
I think 'transferException' option is only available in Camel 2.0? I
have to use 1.6.1...
On Tue, Aug 25, 2009 at 8:50 AM, Claus Ibsen wrote:
> See transferException option on Camel JMS
>
>
> On Tue, Aug 25, 2009 at 5:47 PM, Ilya S wrote:
>> Hi Claus,
>>
>> Yes, I believe I am using reques
See transferException option on Camel JMS
On Tue, Aug 25, 2009 at 5:47 PM, Ilya S wrote:
> Hi Claus,
>
> Yes, I believe I am using request/reply over JMS.
>
> Is there a way to ask Camel to commit a TX at some point in my route?
>
> I just sent a clarification on what I'm actually trying to accom
Hi Claus,
Yes, I believe I am using request/reply over JMS.
Is there a way to ask Camel to commit a TX at some point in my route?
I just sent a clarification on what I'm actually trying to accomplish:
if some endpoint in the middle failed, I would the the error to be
propagated back to the origi
Hi Fintan,
I basically took Camel spring example from 1.6.1
(apache-camel-1.6.1\examples\camel-example-spring-jms) and modified
it.
I would like camel to propagate my exception (or jms fault) that
happen in some nested route up to the original producer(client). I
thought I can do this with transa
Hi,
I'm trying to route messages from TCP to SOAP using this route:
from("mina:tcp://172.xx.xx.xx:9123?textline=true&sync=true").process(new
MyProcessor(true))
.to("http://127.0.0.1:9001/SoapService";);
But I get an exception when I send an xml string with size 1994 bytes. Is
there a way to increa
Thank you, I see that there a generation wsdl2java in the pom:
http://svn.apache.org/viewvc/camel/trunk/components/camel-cxf/pom.xml
So I realize that the test is a case of WSDL first approach.
Can you suggest me a good tutorial link on this approach with Camel?
Thank you.
Bertrand.
Claus
Just took a peek at the doc. The PAYLOAD mode doc in that area needs
improvement, too. I will look into it.
On Tue, Aug 25, 2009 at 11:01 AM, William Tam wrote:
> Will do, Claus. :-) Getting SOAP headers and body have been
> documented for PAYLOAD mode (both 1.x and 2.x). For MESSAGE mode, i
Will do, Claus. :-) Getting SOAP headers and body have been
documented for PAYLOAD mode (both 1.x and 2.x). For MESSAGE mode, it
is not applicable as there is no SOAP processing (but we will mention
it). We just have to add doc for POJO mode.
On Tue, Aug 25, 2009 at 10:49 AM, Claus Ibsen wrote
When using the Restlet component to expose tidy URIs, what would you
recommend regarding exposing routes as multiple endpoints? For instance, a
single endpoint returns JSON (e.g. /people/toddf returns a JSON object
describing person ID 'toddf'). Now suppose I want to expose the same
endpoint wit
On Tue, Aug 25, 2009 at 4:38 PM, William Tam wrote:
> In 1.x, we don't copy the Headers.list to Camel headers. You can get
> the Headers.list by first getting the CXF Message from Camel Message.
> And then, you can get the header list from CXF message.
>
> org.apache.camel.Message in = exchange.ge
In 1.x, we don't copy the Headers.list to Camel headers. You can get
the Headers.list by first getting the CXF Message from Camel Message.
And then, you can get the header list from CXF message.
org.apache.camel.Message in = exchange.getIn();
org.apache.camel.component.cxf.CxfMessage body =
(org.
And dropped in src/generated or something like that.
On Tue, Aug 25, 2009 at 4:36 PM, Claus Ibsen wrote:
> I think they are auto generated by maven tooling.
>
> Try running mvn install
>
> On Tue, Aug 25, 2009 at 4:08 PM, bgoetzmann
> wrote:
>>
>> Hello,
>>
>> Looking at the CxfMtomConsumerTest.j
I think they are auto generated by maven tooling.
Try running mvn install
On Tue, Aug 25, 2009 at 4:08 PM, bgoetzmann wrote:
>
> Hello,
>
> Looking at the CxfMtomConsumerTest.java test case in
> http://svn.apache.org/viewvc/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component
Are you using 2.x? (My reply was assuming you were using 2.x).
On Tue, Aug 25, 2009 at 10:16 AM, William Tam wrote:
> In POJO mode, the SOAP headers are copied to Camel IN headers as
> "org.apache.cxf.headers.Headers.list." The header value is a List of
> CXF Header objects
> (http://svn.apache.
In POJO mode, the SOAP headers are copied to Camel IN headers as
"org.apache.cxf.headers.Headers.list." The header value is a List of
CXF Header objects
(http://svn.apache.org/repos/asf/cxf/trunk/api/src/main/java/org/apache/cxf/headers/Header.java).
That's how you can read request SOAP headers.
Hello,
Looking at the CxfMtomConsumerTest.java test case in
http://svn.apache.org/viewvc/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/
I see that file uses org.apache.camel.cxf.mtom_feature.HelloService and
org.apache.camel.cxf.mtom_feature.Hello classes, but I c
On Tue, Aug 25, 2009 at 3:03 PM, S. Ali Tokmen wrote:
> Hello
>
> Claus Ibsen a écrit :
>>
>> On Tue, Aug 25, 2009 at 2:07 PM, S. Ali Tokmen
>> wrote:
>> Do you use that header often? If e.g. more end users start to use it
>> we can add it however often people use FILENAME or FILENAME_ONLY etc.
>>
Hello
Claus Ibsen a écrit :
On Tue, Aug 25, 2009 at 2:07 PM, S. Ali Tokmen wrote:
Do you use that header often? If e.g. more end users start to use it
we can add it however often people use FILENAME or FILENAME_ONLY etc.
We use it in the logs, simply because we need full path names on o
On Tue, Aug 25, 2009 at 2:07 PM, S. Ali Tokmen wrote:
> Hello
>
> If it is by design, it's OK.
Do you use that header often? If e.g. more end users start to use it
we can add it however often people use FILENAME or FILENAME_ONLY etc.
>
> Apart from that, CAMEL 2.0.0 is working like a charm :)
Th
Hello
If it is by design, it's OK.
Apart from that, CAMEL 2.0.0 is working like a charm :)
Thanks
S. Ali Tokmen
savas-ali.tok...@bull.net
Office: +33 4 76 29 76 19
GSM:+33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
Claus Ibsen a écrit :
Hi
We have only adde
I'm having this same problem. Since I'm targeting embedded deployment in
desktop app, it is kind of serious issue for me.
Best regards,
Damir Murat
--
View this message in context:
http://www.nabble.com/Garceful-shutdown-bug-in-2.0M3--tp25113519p25132762.html
Sent from the Camel - Users mailing
Here is the route that I configured + aggregator
${body} != null
public class QueueAggregator implements AggregationStrategy {
private static final transien
Hi Ilya,
That's an interesting routing example. I have a couple of observations about
your routes, based on my understanding of Camel transactions (which is by no
means perfect!).
Route 1:
from("jms:queue:numbers")
.policy(pp)
.to("jms:queue:mybadqueue?transactedInOut=tr
And use the google search box on the Camel front page.
Enter "pollEnrich" and find the camel document
Eg read this:
http://camel.apache.org/content-enricher.html
On Tue, Aug 25, 2009 at 10:47 AM, Claus Ibsen wrote:
> On Tue, Aug 25, 2009 at 9:44 AM, Charles Moulliard
> wrote:
>> Hi,
>>
>> I ha
On Tue, Aug 25, 2009 at 9:44 AM, Charles Moulliard wrote:
> Hi,
>
> I have the following question concerning the usage of pollEnrich processor
> with queue and quartz endpoints.
>
> Is the following route correctly configured to pickup messages from a queue
> every x minutes
>
> from(quartz:schedul
Camel provides 2 kind of delayers
a)
.delay in the EIP (eg you insert .delay somewhere in the route)
This will delay when a message reached this point and at this point only.
So if a message arrives at 08:13:57 and you have a delay of 3 (30 sec)
then the message is delayed for 30 sec using Th
My idea was not at all to use delay or delayer but quartz or timer. As I
have been confronted to problems with the following route :
from ( quartz)
. to (activemq:queue:A)
I have tested the option of delayer/delay which was not the my first choice.
In the meantime, I try pollEnrich (see my last p
On Tue, Aug 25, 2009 at 10:10 AM, Charles Moulliard wrote:
> The delay defined in my example is 1 hour (60) and not 1 minute (6)
> ;-)
>
Crazy as you will hold a thread waiting for 1 hour.
> Do you confirm that the correct hypothesis is the case B and not the A ?
I do not understand what
The delay defined in my example is 1 hour (60) and not 1 minute (6)
;-)
Do you confirm that the correct hypothesis is the case B and not the A ?
Regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*
blog : http://cmoulliard.blogspot.
On Tue, Aug 25, 2009 at 9:18 AM, trivedi kumar
b wrote:
>
> Hi,
>
> This is working but with small issue, my bean (forex: y) is throwing an
> exception which is why the transaction is getting rollbacked. However, this
> exception is propagated to the client, instead I want to handle the
> exception
The delay occurs before the next processor, eg in your case .to
It just delays, eg using 6 will delay for 1 minute.
On Tue, Aug 25, 2009 at 9:08 AM, Charles Moulliard wrote:
> Quick question.
>
> When delayer or delay are used in route. Is it the process (defined after
> the delayer or delay)
Hi,
I have the following question concerning the usage of pollEnrich processor
with queue and quartz endpoints.
Is the following route correctly configured to pickup messages from a queue
every x minutes
from(quartz:scheduler)
.pollEnrich(uri=Activemq:queue:MessagesToBeProcessed)
.to(bean:compon
You can play with the exceptions like this :
// Here is the
reference to the bean component who will handle the transaction exception
// activemq
queue endpoint
// route as
transacted with NEW as transaction policy
Hi,
This is working but with small issue, my bean (forex: y) is throwing an
exception which is why the transaction is getting rollbacked. However, this
exception is propagated to the client, instead I want to handle the
exception. I have added onException() in my route, which didnt worked.
Thank
Quick question.
When delayer or delay are used in route. Is it the process (defined after
the delayer or delay) who will be processed every x seconds/minutes
(depending on what has been defined) or the messages ?
e.g.
from(queue).delay(60).to()
Case A : processor is delayed every x seconds/
54 matches
Mail list logo
