Thanks. I'll give that a try as soon as we get time to do the upgrade.
--
View this message in context:
http://camel.465427.n5.nabble.com/BeanInfo-collectParameterAnnotations-using-a-great-deal-of-CPU-time-tp5773551p5773593.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I got this working... thank you to Sergey and Kalyan for your assistance. After
following your trails around and learning some more, I found that the main
issue was that I had defined the return type for my REST operation as String,
so Camel was dutifully converting to that and I did not have a
I'm attempting to write a XMPP bot using camel-xmpp and find that each time I
connect to the XMPP server (Atlassian HipChat, in this case) and join a
room, I get a bunch of "old" messages instantly sent to me. I've tried
checking Exchange or XmppMessage timestamps, but they're all new (e.g. not
acc
Thank you, that solved my problem.
On Tue, Nov 10, 2015 at 12:32 PM, John Taylor wrote:
> rwoolf writes:
>
> > My blueprint xml file is my "bundle." I drop the blueprint xml file into
> > the deploy directory. I have two different blueprint xml files for the
> two
> > different contexts. So
No problem. Glad to help.
Best of luck!
~Danny
On Nov 10, 2015, at 4:36 PM, Alex Soto wrote:
> Great, in this case I am not doing any aggregation, so that won’t be a
> problem.
> I just finished testing, and it worked, so thats for the help.
>
> Best regards,
> Alex soto
>
>
>
>> On Nov
Great, in this case I am not doing any aggregation, so that won’t be a problem.
I just finished testing, and it worked, so thats for the help.
Best regards,
Alex soto
> On Nov 10, 2015, at 3:23 PM, Daniel Lamb wrote:
>
> If you do some parallel processing and have an aggregation strategy for
If you do some parallel processing and have an aggregation strategy for the
results, just make sure to put the properties from the old exchange onto the
exchange that you return. Other than that, you’ll be fine.
~Danny
On Nov 10, 2015, at 4:18 PM, Alex Soto wrote:
> Thanks, I will give it a
Thanks, I will give it a try.
Do you know if there is some concern using exchange properties that I should
worry about, perhaps with multi-threading?
Best regards,
Alex soto
> On Nov 10, 2015, at 2:57 PM, Daniel Lamb wrote:
>
> Store the headers as properties on the exchange before filteri
Store the headers as properties on the exchange before filtering them out.
Then you can pull them back out after you get your response from the remote
server and do what you need to do.
~Danny
On Nov 10, 2015, at 3:52 PM, Alex Soto wrote:
> In case its not clear, I need my custom headers fo
In case its not clear, I need my custom headers for after the HTTP request
comes back, I just don’t want these headers to go out to the remote server.
Currently, I am using a headerFilterStrategy, but that seems to remove the
headers entirely, as opposed to filter them, as the name implies.
rwoolf writes:
> My blueprint xml file is my "bundle." I drop the blueprint xml file into
> the deploy directory. I have two different blueprint xml files for the two
> different contexts. So in this regard they are different bundles. But
> they are not packaged as jar based bundles. I'm gue
Hello,
I have a route with some custom headers that I need to preserve after sending
an HTTP client request (HTTP producer), however, I do not want these headers
to be sent as HTTP headers to the remote server.
Is there a way to accomplish this?
Best regards,
Alex soto
I looked at this briefly when I updated a bunch of things to be able to use
Jetty9. In CXF, we were able to use a bit of reflection to allow the CXF web
socket transport to support both Jetty 8 and Jetty 9. However,
camel-websocket uses a LOT LOT more of the web socket API’s than CXF does an
Hi,
i think there is a regression since version 2.15.3.
To reproduce the regression i changed the test
org.apache.camel.test.blueprint.ConfigAdminNoReloadLoadConfigurationFileTest
from the component camel-test-blueprint a bit, respectively the context
"org/apache/camel/test/blueprint/configadmin-
I am trying to use Restlet component with rest dsl but i get "Component
restlet is not a RestApiConsumerFactory"
This route is working fine (camel 2.16):
public void configure() throws Exception {
restConfiguration().component("restlet").apiContextPath("/").port(port);
from(r
My blueprint xml file is my "bundle." I drop the blueprint xml file into
the deploy directory. I have two different blueprint xml files for the two
different contexts. So in this regard they are different bundles. But
they are not packaged as jar based bundles. I'm guessing from what you
said
Yeah I think there is a ticket about upgrading camel-websocket to
jetty 9. We love help so anyone who has the time is welcome to help
with this. It should IMHO be jetty9 by default as 8 is EOL.
On Tue, Nov 10, 2015 at 6:11 PM, Aki Yoshida wrote:
> jetty8 and jetty9 have a different websocket hand
jetty8 and jetty9 have a different websocket handler interface, so you
can't just replace the jetty version unless the component includes two
specific implementations that can be used depending on the available
version.
if you want to choose your own serverlet container (e.g., jetty9,
tomcat8, etc
Hello,
i would use camel 2.16 + jetty9 + camel-websocket but this component depends
from jetty8.
How can i do?
i am trying force to use jetty9 from maven without success.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-16-vs-Jetty9-vs-camel-websocket-tp5773575.html
Hey souciance,
please feel free to look at the code which I uploaded yesterday since I think
it's interesting for more people: https://github.com/NeovaHealth/ARNIE
Have a look at the CamelConnector class. In World() in the stepDefinitions I
create a test environment that sets up its own contex
20 matches
Mail list logo
