on Spring
for this ?
Thank you very much in advance
Andreas Gies
Hi,
from your description it sounds that haven't exported the instances
you would like to access as services. It is not sufficient to export the
packages.
The instances that shall be available in other bundle must be exported as
services and then they can be referenced as service in your
Hi there,
for what it's worth - we are using Camel in OSGi with a non-karaf
container.
However - we are not using Spring.
First, our container is completely written in Scala and therefor we are
using
different config mechanisms. Secondly, we prefer a programmatic creation
of our Camel
Hi Gordon
I am using Akka in Combination with Camel within a distributed Retail
application.
All application parts run on top of Karaf. So far I think, the combination of
those
technologies is a good choice with respect to scalability and testability.
I had used Akka in other applications
Hi,
the short answer is: Yes.
A bit more elaborate, I think that is a very common use case and kind of
screams for
something like Camel - if not Camel itself ;)
What you would typically do is:
1) Implement a route that calls out to your core business logic. This
route id your
service
to enable management
access (in terms
of technical management, not your managers) for the routes you develop.
Definitely worth looking at http://hawt.io to see what you can get in
that area.
Andreas
On 10/11/2013 11:22 AM, Andreas Gies wrote:
Hi,
the short answer is: Yes.
A bit more elaborate, I
...
--
View this message in context:
http://camel.465427.n5.nabble.com/Help-with-Dynamic-route-tp5741336.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Andreas Gies
WoQ -- Way of Quality UG
Geschäftsführer CTO
/eMail:/andr...@wayofquality.de mailto:andr
Just noted, that I copied the wrong link in my answer earlier on.
[1]
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/MulticastProcessor.html
Sorry for this
Andreas
On 10/11/2013 01:05 PM, Andreas Gies wrote:
Hi,
if I understand correctly, you want
);
assertEquals(4, five.getKey());
assertEquals(#4, five.getValue());
}
}
--
View this message in context:
http://camel.465427.n5.nabble.com/Help-to-re-write-route-tp5741339.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Andreas Gies
WoQ -- Way of Quality UG
Hi again,
this comes from one of my test classes:
@Test
public void assortmentTest() throws Exception {
final String country = getTestProperties().getProperty(country);
final String location =
headerLocation(getTestProperties().getProperty(location));
CamelTestSupport cts =
Hi,
it might be me, but I think your 2nd route is missing a to-element.
You need to do something with message like drop it to a file or at least
log it.
Otherwise, like others have pointed out, using beans as payload is bad
practice
in integration applications. However, you seem to be happy
Hi,
I am not sure we are looking at a Camel poblem. I am doing something
similar in OSGi.
I listen to changes in a config directory. Any value changes gp into the
Config Admin Service
and most of my routes are implemented as Managed Services.
As far as I can see config changes are picked up
Hi,
this is because JMS temporary Objects are usually bound to the connect
in which they have been created.
Therefore these are invisible elsewhere. You are using contexts and I
would assume you are using the normal setup
and hace 2 connections.
This is why it doesn't work with a temp queue,
Hmmm,
I see your point and can't answer whether the version change is really
required.
I would challenge the claim that camel can't be used in a real OSGi
application.
I am using Camel all the time in OSGi based apps and I would call them
real as they
solve real problems.
This having said,
but
did not see any details about the supported OSGi specs.
Christian
On 09.09.2013 11:48, Andreas Gies wrote:
Hmmm,
I see your point and can't answer whether the version change is
really required.
I would challenge the claim that camel can't be used in a real OSGi
application.
I am using Camel
Hi,
in theory you could configure a generic camel route between two files
and use a property resolver
to route from file1 to file2. Then its a matter of sticking the
properties into the right location on disk
and initialize your Camel route accordingly on startup.
This having said, the JVM
Hmmm,
to me the log output seems to document what you are after.
Maybe you want to rephrase the question and / or provide your route
and a test case ? - A description of what you are trying to achieve might
also help.
I haven't seen answers to the questions that have been asked:
Are you using
I don't want to be nagging, but personally I wouldn't go down the route
(hmm...nice play of words) of
creating routes dynamically from the application. Personally I would
stick to having the route in my
source code and therefore tagged and released and tested etc.
Generating the config can
.
it worked fine in active-mq 5.5
Please kindly help
Issue only in active 5.8 and camel 2.10.3
*Regards*
Prabu.N
On Fri, Sep 6, 2013 at 1:16 PM, Andreas Gies [via Camel]
ml-node+s465427n5738828...@n5.nabble.com wrote:
Hmmm,
to me the log output seems to document what you are after.
Maybe you want
One thing to keep in mind when you are experiencing odering issues is
that you can use ActiveMQ's message groups to make all messages for
one group to the same consumer. Very often that little trick helps
and still allows some form of concurrency for different groups.
Andreas
On 09/05/2013
Works like a charm; as expected ;)
Thx
Andreas
Am 7/22/13(30) 5:22 PM schrieb Claus Ibsen unter claus.ib...@gmail.com:
Hi
Yep set the id of the processors. Then that id is used as part of the JMX
name
http://camel.apache.org/camel-jmx.html
.process( ... ).id(nameOfMyProcessor)
On Mon, Jul
Hi,
It might be my complete ignorance of the problem, but have you considered
to leave your context happily running and take advantage of the many
mechanisms in Camel to leverage Thread pools and the like ?
Just my 2 ct
Andreas
Am 7/23/13(30) 7:26 AM schrieb SyedBhai unter
://www.wayofquality.de/index.php/en/blog/entry/using-the-camel-servlet-
component-in-an-osgi-blueprint-container
I am using pax-web as an HTTP service implementation, but the blog simply
assumes that you some form of http service and hopefully the
pax-web-extender installed.
Hope that helps
Andreas
Andreas
Hi,
Perhaps it's with posting your test as well ?
Best regards
Andreas
Am 7/18/13(29) 11:37 PM schrieb Gershaw, Geoffrey unter
geoffrey.gers...@credit-suisse.com:
I'm running this in a standalone java app using Spring. Its camel 2.11.
I was under the impression from the various samples
Still kind of confused ;)
If I understand correctly you have 3 inbound routes from different
locations all of which point to a Active MQ Queue.
If you have only one consumer the messages will be processed in the order
they arrive in the queue (wellin the simplest case)
regardless where they
Hmmm
Looks good enough to me. Is there any error message to share ? Which
version of Camel are you using ?
If you are willing to post your route I can drop it in my IDE tomorrow .
Regards
Andreas
Am 7/18/13(29) 7:12 PM schrieb Gershaw, Geoffrey unter
geoffrey.gers...@credit-suisse.com:
Elaborating on Claus' answer. The XSLT processor tries to resolve the XSLT
test/test.xsl.
In OSGI words, it has to resolve a package test which contains the
resource test.xsl.
Though exporting the package test would probably work, I would strongly
recommend to have
better qualified package
Depending on how you start your OSGi container, you can always add the
configuration for remote debugging to your launcher script.
For my own development I have written a small wrapper around Pax Exam that
uses a container.properties file to set the JVM's runtime
paramaters (incl. debugging). For
to export a resource in OSGi is to use the
Export-Package instruction?
Thank you,
Cristiano
2013/7/16 Andreas Gies andr...@wayofquality.de
Elaborating on Claus' answer. The XSLT processor tries to resolve the
XSLT
test/test.xsl.
In OSGI words, it has to resolve a package test which contains
Hi,
Have you considered using the camel-blueprint-testing support ?
This is what I use to test my Camel based OSGi bundle and that
gives me good results.
Best regards
Andreas
Andreas Gies
WoQ Way of Quality UG
http://www.wayofquality.de
Geschäftsführer CTO
eMail: andr
Hello,
Is the camel-osgi bundle deprecated ? - The latest version I can find is
2.3.0.
I was trying to create a Camel Context in Java with the
OsgiDefaultCamelContext(bundleContext),
but then my container complains about org.apache.camel.core.osgi not being
found as an import.
Thanks and best
Hi,
Yes, that does the trick. My mistake was that I tried to create the
CamelContext in Java.
Now I am creating it via blueprint and inject a RouteBuilder.
Thanks
Andreas
Andreas Gies
WoQ Way of Quality UG
http://www.wayofquality.de
Geschäftsführer CTO
eMail: andr
with path / --
camel:from uri=servlet:///test /
camel:to uri=file:///tmp/woq-out /
/camel:route
/camel:camelContext
/blueprint
If you think this is usefull, I am happy to stick it in the wiki rather than
in the user's list.
Best regards
Andreas
Andreas Gies
WoQ Way of Quality
33 matches
Mail list logo
