bibryam,
HeaderFilterStrategy worked out beautifully. I simply extended the
CxfHeaderFilterStrategy.
Thank you!
--
View this message in context:
http://camel.465427.n5.nabble.com/Message-headers-and-HTTP-tp5742364p5742374.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Willem,
When I stepped through debugger and set includeTestBundle to false I've got
the following error:
java.lang.RuntimeException: Gave up waiting for service
(&(objectClass=org.osgi.service.blueprint.container.BlueprintContainer)(osgi.blueprint.container.symbolicname=*MyTestBundle*))
a
You may wish to also check out the Enrich EIP.
You can call into a route or external system, then aggregate the
response however you'd like (keeping or discarding headers as you
wish)
http://camel.apache.org/content-enricher.html
On Tue, Oct 29, 2013 at 7:17 PM, Bilgin Ibryam wrote:
> Use Header
Use HeaderFilterStrategy to specify which headers should be sent with the
http request.
It will preserve the headers in the exchange
Cheers,
On 30 October 2013 01:27, bocamel wrote:
> In my routes, I use custom message headers to keep track some data. But
> when
> one of the steps in the rou
Hello,
We have set up a Camel route using transacted(). The route comprises
multiple JDBC transactions and we required some kind of transaction
management to be implemented, we decided to use transacted().
The route looks like this :
from("direct:updatebookauthor").tracing()
I think it is depends how your route consume the message from the iccs.request
queue.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
If you just want to test the camel route, you don’t have to start the web
container.
But if you want to test the restlet, I’m afraid you need to do that.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(Engli
One thing should be point out, CXF uses Http URL Connector which is from JDK by
default.
If you are using CXF 2.7.x and enable the async http client setting, it will
use the Apache Http Client 4.x to send the request.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://will
In my routes, I use custom message headers to keep track some data. But when
one of the steps in the route is a HTTP call (for example calling a web
services), all my headers are sent as HTTP headers to the remote HTTP
server. This causes the remote HTTP server (which is not under my control)
to
On 22/10/13 15:06, Amit wrote:
Would you please fixed this issue in 2.11.3 release.
I've attached a patch on your behalf,
https://issues.apache.org/jira/secure/attachment/12610872/camel6878.txt
and hope the team will have no problems with applying it.
thanks for spotting this minor issue;
Che
Great test case, thanks. This is a bug. Can you open a JIRA?
On Mon, Oct 28, 2013 at 10:31 AM, Keith Freeman <8fo...@gmail.com> wrote:
> I'm building my route like this:
>
> //context.setTracing(true);
> errorHandler(loggingErrorHandler("whatever").level(LoggingLevel.ERROR));
> from("direct:s
Hi,
add something like this to your route:
onException(HttpOperationFailedException.class)
.bean(routeErrorHandler)
.end();
You can use .handled(true|false) or .continued() to further tune the exception
handling.
In our case, the routeErrorHandler is a spring bean, that us
You can turn off the throw exception on failure with
throwExceptionOnFailure=false
but that will apply to all error codes.
Otherwise you can use camel error handler to handle the http exception
when its status code 500.
Camel in Action chapter 5, section 5.5 covers that
On Tue, Oct 29, 2013 at
Any particular reason why you're using "message ID as correlationID == true?"
Also, the exchange pattern would be InOut, so you don't need to
explicitly send the message to tpms_from_iccs
I have written a unit test that passes; you should take a look at it here:
https://github.com/christian-posta
alexey-s wrote
> Use cache JAXBContext or Marshaller/Unmarshaller in local beans.
> Sample:
> private SoftReference
>
> refUnmarshaller;
>
> Or sample (use Google Guava):
Started off on your lines but, found out that by changing the input file
format from abc.out file to abc.txt greatly improv
Rules of the game sets the other side - http server.
Two requests are always bad, whether it's on an external authentication
server, or proxy server.
It is necessary to send a file size of 1 MByte. Length of HTTP request is
about 1.3 MByte. Two queries will give 2.6 MByte.
Aleksey
--
View thi
hello,
we are using http4 with camel 2.12.1, posting soap to an external party.
However, the external party seems to exaggerate(?) the usage of REST and
return a status code 500 when our request is not supported. When using e.g.
postman in chrome, I can see that a response is given with the 500 whi
NObody is responding in that thread.
https://community.jboss.org/thread/233981
Any other place where my qs can be answered?
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-cxf-and-activemq-example-tp5742069p5742351.html
Sent from the Camel - Users mailing list archive a
Hi,
Previously we are using ActiveMQConnectionFactory alone, and we observed
that while starting the JBoss Server ActiveMQ is creating multiple threads
and closing (ActiveMQ Task 1, ActiveMQ Task 2, ...), we thought it creating
multiple connections/session are creating and closing.
As a resolutio
Hi,
it happens by design:
" Generally, preemptive authentication can be considered less
* secure than a response to an authentication challenge
* and therefore discouraged."
(see
https://hc.apache.org/httpcomponents-client-4.3.x/httpclient/examples/org/apache/http/examples/client/ClientPreempt
You'll be surprised. CXF uses the same library Apache HttpComponents.
CXF client initially twice sends an HTTP request. The first request without
authorization. Second with authorization.
For a GET request such behavior is acceptable. For a POST request is very
bad.
Aleksey
--
View this messa
I just captured the http request and response and found some thing interesting.
When camel-http send the request to back end server which is protected with
HTTP Basic Authentication,
HttpClient sends a request without Authentication inform first, then it sends
the request with the Authenticatio
Maybe IPF which is based on camel can answer your question.
http://repo.openehealth.org/sites/ipf/manuals/ipf-2.5-rc2/IPF%20reference%20-%20multi.html
--
View this message in context:
http://camel.465427.n5.nabble.com/HL7-v3-tp5732915p5742346.html
Sent from the Camel - Users mailing list arch
I did a quick test with the camel trunk ( I think it’s same with last camel
release 2.12.1), the HTTP Basic Authentication setting is work out of box.
from("direct:endpoint").to("http://localhost:8081?authMethod=Basic&authUsername=user1&authPassword=pwd”);
I think you need to double check if
Must I startup a web container
--
View this message in context:
http://camel.465427.n5.nabble.com/how-to-test-the-restlet-service-without-startup-web-containner-manually-tp5742339p5742343.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I do not understand what the problem is. Within a few years used to.
For 20 seconds, the system waits for the successful outcome of the process.
After 20 seconds, the process has not stopped. Aborting closing Endpoint.
Component throws an exception I/O or NPE. Rollback transaction and original
fil
26 matches
Mail list logo