Same number of params each time? Restlet does it easily:
from("restlet:http://localhost:8080/service/inv/{country}/{item}/{store}/{size}";)….
On Aug 23, 2013, at 6:28 PM, gsamy wrote:
> How to extract the URL parameters using Spring DSL?
>
> For example:
> http://localhost:8080/service/inv/US
How to extract the URL parameters using Spring DSL?
For example:
http://localhost:8080/service/inv/US/1000/123456/1K
from the above URL I need to extract the US,1000,123456 and 1K values.
These parameters I have to attach dynamically to the other service URL while
route.
Like below
http://test.c
Christian,
Thank you for your reply; however, it is not that simple. The message
that will continue is dependent on the answer from the component. So think
about it this way, we send to some validation out of that we get a report
with the results which needs to go to the client; however, so
See http://camel.apache.org/multicast.html
Best,
Christian
Am 23.08.2013 20:51 schrieb "abdiels" :
> When I post a message to a component which will give me a distinct out
> message (like http, jdbc, etc.), what is the best way to continue
> processing
> both the in and out messages in parallel?
Set the header:
Exchange.HTTP_URI String URI to call. Will override existing URI set
directly on the endpoint.
http://camel.apache.org/http4.html
As the above says, that'll override whatever address is in the .to. So
.to("http4://nowhere.com") will be replaced by Exchange.HTTP_URI if it
When I post a message to a component which will give me a distinct out
message (like http, jdbc, etc.), what is the best way to continue processing
both the in and out messages in parallel? In other words, how can I send the
response message (out) on a separate thread while I continue the initial
r
They are http endpoints. Headers will definitely do the job but I
haven't find a way to do it.
On Thu, Aug 22, 2013 at 5:37 PM, Christian Posta
wrote:
> What endpoint will you use to fetch the webpage? Might be able to use
> headers...
>
> On Thursday, August 22, 2013, Jose Espinosa wrote:
>
>>
Version 2.10.5
Using via Netty
Limit 1MB
Route
from("netty:tcp://10.44.71.52:4567?allowDefaultCodec=false&textline=false")
.to("netty:tcp://10.44.71.52:5678?textline=false")
--
View this message in context:
http://camel.465427.n5.nabble.com/Not-able-to-transfer-larger-bytes-of-data
There is no limit build in by Camel. Can you provide more details please.
- What version do you use?
- Which component(s) do you use?
- How does your route looks like?
- What's the limit you are facing?
- ...
Best,
Christian
-
Software Integration Specialist
Apache Camel committe
Have you had a look at [1] and [2]?
[1]
http://camel.apache.org/running-camel-standalone-and-have-it-keep-running.html
[2]
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-spring/src/main/java/org/apache/camel/spring/Main.java;h=ba3389d5fcfef2d626670a4d40112998c60b94fa
Good catch!
mina2:tcp://10.5.60.60:9000?disconnectOnNoReply=false;codec=#gilbarcoDecodershould
be mina2:tcp://
10.5.60.60:9000?disconnectOnNoReply=false&codec=#gilbarcoDecoder
Best,
Christian
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
Thanks for reporting. I updated the WIKI page. It should be online in a few
minutes...
Best,
Christian
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.o
Hi
Yeah would be nice if it was easier with camel-http4. Maybe we can add
authenticationPreemptive as a new option explicit on the http
endpoint, and then have logic that setup the authentication.
Seems like a few line of codes from this SO with the 50+ votes (in the
comment section)
http://stack
You are welcome to provide patches and improve the groovy dsl. We love
contributions
http://camel.apache.org/contributing.html
On Mon, Aug 19, 2013 at 8:52 AM, mailingl...@j-b-s.de
wrote:
> Hi Willem,
>
> thanks for your answer, unfortunately overriding eval is not sufficient as
> this method in
Hi
I am using camel. And I am transferring Array list with tree Map as a
response from the camel. Till certain limit, I am able to receive the
response. But once it crosses it, the camel does not send response to the
other camel. Instead, the same camel is called and the same operations gets
exec
I will add some notes to the Camel JAXB WIKI page later today about the fix
and a potential workaround for previous versions.
Best,
Christian
Am 23.08.2013 08:41 schrieb "Hack Kampbjørn" <
camel.us...@list.hack.kampbjorn.com>:
> A workaround is to use a SchemaFactory implementation that is thread
16 matches
Mail list logo