Good to hear ;-)
Yeah - I meant camel-sjms - I think autocorrect got me on that one - sorry. I
like the way camel-sjms does it’s internal pooling - I don’t need to create
pooled connection factories anymore. You can also just add “transacted=true”
in the URI and you’re using JMS Session
Hi guys,
I'm observing strange behaviour in tests, where I've used to use verbose ids
for routes and processing steps to be able to mock them in tests with
weaveById method. But it seems to me, if id is longer then 18 chars, then
the step in route will not be mocked or, at least not properly
That is just the output of that message history table that limits to a
20 chars in those columns.
There is no id limit in Camel.
On Mon, Feb 8, 2016 at 5:45 PM, trbvm wrote:
> Hi guys,
>
> I'm observing strange behaviour in tests, where I've used to use verbose ids
> for
Env. ActiveMQ v5.9.1, Camel 2.13.1
I am currently generating CSV files from a custom SQL. This works fine, but
they want the headers to be added to the CSV file. I've included my route
below, is there currently any way of doing this?
building.csv
Thanks in advance
Thank You Stephan - that really helps.
I ran the project as-is and saw the failure in the “standard” setup on the
first run - much easier for me ;-)
Then I change transacted to false, and I’ve run it 5-times and it’s succeeded
(i.e. not lost messages ).
Have you been able to make it drop
Hi Stephan -
I have a keen interest in this one because my customers rely very heavily on NO
MESSAGE LOSS - period (they are mostly Healthcare Providers).
I was comparing configurations again, and I came up with one more difference -
can you try setting transacted=false in the “standard”
Oh, our messages overlapped...
Your questions:
"... doing this queue to queue work using one or two ActiveMQ brokers?"
=> One broker
"... you may want to try camel-sims"
=> I guess you mean Camel sJms, that's the closest match I found in the
list of Camel components on GitHub :-) Never heard
Hi
I am looking at using the Rest component to define a Rest endpoint. My camel
application gets packaged as a WAR file which I deploy in to my standalone
tomcat instance.
I am not sure if I can bind this Rest endpoint to HTTP requests that arrive
at the HTTP endpoint on my tomcat instance.
You can use the servlet component with the rest-dsl.
There is already a tomcat example.
https://github.com/apache/camel/tree/master/examples/camel-example-swagger-java
On Mon, Feb 8, 2016 at 10:37 AM, gilboy wrote:
> Hi
>
> I am looking at using the Rest component to
Hello
With camel blueprint you don't use spring-dm and its namespaces. Your
XML describing Camel route should use
http://camel.apache.org/schema/blueprint and
http://www.osgi.org/xmlns/blueprint/v1.0.0 namespaces.
regards
Grzegorz
2016-02-09 8:49 GMT+01:00 gurmehar.kalra
I have looked at the code in org.apache.camel.core.osgi.OsgiServiceRegistry
(camel-core-osgi-2.15.4) and it appears to cache the service references.
This means that if I uninstall/install the bundle supplying the service it
wont automagically 'pick up' the new service.
For what reason(s) are the
Hmmm... not really sure about #2... or do I also need a JTA Tx manager for
working with multiple brokers?
On Tue, Feb 9, 2016 at 8:48 AM, Stephan Burkard wrote:
> Hi Quinn
>
> I found this blog post that explains some things we found out:
>
>
Camel ought to only retry the "step" in the route that failed, eg only
the SQL when you configure its error handler.
On Tue, Feb 9, 2016 at 8:53 AM, NES wrote:
> Thank you for your response.
>
> I use Camel 2.16.1.
>
>
>
> --
> View this message in context:
>
Hello,
I am testing the XML Security component according to the example from the
camel-xmlsecurity website. For example the following producer refers to the
Test.xsd:
I am testing this in the karaf and I have put the Test.xsd in the following
folder:
Hi Quinn
I found this blog post that explains some things we found out:
http://tmielke.blogspot.ch/2012/03/camel-jms-with-transactions-lessons.html
=> See sections 2) and 3) for simple configuration without Tx manager
=> See section 7) for Tx manager with transacted = false
In that blog post
You need to put the test.xsd file together with your Camel application
so they are in the same OSGi bundle, so the classloder can find the
file.
Look at some of the other osgi examples that are in the examples of Camel.
https://github.com/apache/camel/tree/master/examples
On Tue, Feb 9, 2016 at
What version of Camel do you use?
On Tue, Feb 9, 2016 at 6:53 AM, NES wrote:
> Hi, I'm implentnting the function that receive a message from servlet
> endpoint and send it to some endpoints.
>
> like this.
>
>
>
>
>
> />
>
What I meant was if he is using the actual implementation or the test stub
is the second bundle then he can simply refer to in the test scope.
There's one huge caveat there though. It has to be a pure OSGi service
that does not rely on another CamelContext. PojoSR is not capable of
testing
Hi, I'm implentnting the function that receive a message from servlet
endpoint and send it to some endpoints.
like this.
Now, I want to add the retry option to every endpoint.
e.g. if sending message by http4 and
A typical problem with this is that you use some Camel components /
data formats etc in the blueprint xml file, which you have not yet
installed in the karaf container.
Install them using features:install camel-
On Tue, Feb 9, 2016 at 8:49 AM, gurmehar.kalra
Hi,
Facing Issue as :
Bundle is waiting for namespace handlers
[http://www.springframework.org/schema/osgi-compendium,
http://www.springframework.org/schema/context]
and due to this Buleprint bundle is going Grace Pierod
--
Regards,
Gurmehar Singh
#9891999169
Thank you for your response.
I use Camel 2.16.1.
--
View this message in context:
http://camel.465427.n5.nabble.com/Redelivery-per-Endpoint-tp5777413p5777424.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hello
With camel blueprint you don't use spring-dm and its namespaces. Your
XML describing Camel route should use
http://camel.apache.org/schema/blueprint and
http://www.osgi.org/xmlns/blueprint/v1.0.0 namespaces.
regards
Grzegorz Grzybek
2016-02-08 14:37 GMT+01:00 prateek khanna
Hi,
when implementing the bundle in blueprint and deploying in fuse container
then it is showing "grace period" instead of creating .
In fuse logs it is showing as
"Bundle camel-blueprint is waiting for namespace handlers [
http://www.springframework.org/schema/osgi-compendium,
I’m a little confused here - asService take the object implementing the
interface and the service property key/values - I’m not sure how that could
even work as an interface instead of the implementation object. The service
interface is provided earlier in the call ( the key in services.put ),
It depends on what Camel components are used for the http/rest
transport, and what bindings you are using, and if using pojors if
they have annotations and whatnot.
The given example is sparse, so we cannot see how its being used.
I suggest to study the existing rest examples and the rest-dsl
Perhaps I confused matters. The interface canonical name is the key to the
registry and the stub is the implementation. I'm not sure if PojoSR
proxies that as it would be in an actual OSGi environment but I'm guessing
that it does.
As you know the proxy class in OSGi dynamically implements the
@Ranx - With reference to your statement - " If the first bundle is in his
POM with a scope of
test then it should be available during testing. ".
Are you saying that it is possible to invoke the asService method *without
*the the Stub Implementation and the OSGI can invoke the actual
28 matches
Mail list logo