On Wed, May 6, 2009 at 6:53 AM, Xasima Xirohata wrote:
> Thanks! Will try. Curious, is it available any camel instruction
> (spring based or java dsl) that may allow to process all classes in a
> specified packages to automatically find out all camel annotation to
> process.
>
> Smth like
> xmlns
Thanks! Will try. Curious, is it available any camel instruction
(spring based or java dsl) that may allow to process all classes in a
specified packages to automatically find out all camel annotation to
process.
Smth like
http://activemq.apache.org/camel/schema/spring";>
If there are a lot
Hi Marc,
After digging the code for a while , I find the camel-cxf of the
camel-1.x branch doesn't copy the protocol headers into the camel
message header, so you can't get the content-type from the camel-cxf
consumer.
Here is the JIRA[1] which traces for this issue.
I will commit the quick fix f
Hi
Could you create a .zip with a sample project that shows the problem?
And create a JIRA ticket and attach the file there?
http://camel.apache.org/support.html
Then we have a project to use to dig into the matter. Much appreciated.
On Tue, May 5, 2009 at 7:46 AM, arhan wrote:
>
> Willem, su
Hi
Ah its Camel that inject its own annotations, so @EndpointInjected is
handled by Camel.
Its the CamelBeanPostProcessor that is a Spring BeanPostProcessor.
And since your SimpleProducer is nor known by Spring or Camel its not
injected at all.
So define it as a Spring bean
And Camel should be
Hi Marc,
After digging the code for a while , I find the camel-cxf of the
camel-1.x branch doesn't copy the protocol headers into the camel
message header, so you can't get the content-type from the camel-cxf
consumer.
Here is the JIRA[1] which traces for this issue.
I will commit the quick fix f
Sorry, it's not the NPE inside camel or geronimo. I mean none of the
@EndpointInject(uri="jms:queue:SendReceiveQueue")
ProducerTemplate producer;
@EndpointInject(uri="jms:SendReceiveQueue")
ProducerTemplate producer2;
@EndpointInject(uri="activemq:SendReceiveQueue")
ProducerTemplat
On Wed, May 6, 2009 at 12:53 AM, angeloNZ wrote:
>
> Hi,
>
> I'm using Camel alongside ServiceMix to do content based routing. I'm
> trying out using the @RecipientList annotation in my code to do a dynamic
> lookup of my intended endpoints from an external properties file.
>
> This is my camel m
Hi
Can you show the NPE stacktrace?
And which producer is it that causes the NPE?
On Tue, May 5, 2009 at 7:15 PM, Xasima Xirohata wrote:
> Hi. I'm using geronimo-jetty-2.1.4 running with jdk1.6. This geronimo
> has an activemq (4.1.2) running on 61616. I have created queue
> 'SendReceiveQueue'
Hi,
I'm using Camel alongside ServiceMix to do content based routing. I'm
trying out using the @RecipientList annotation in my code to do a dynamic
lookup of my intended endpoints from an external properties file.
This is my camel method:
@RecipientList
public String getTarget(@XPath("//re
Hi
I have run into a problem that I will *really* appreciate some suggestions
on:
I have a single message that arrives in a ActiveMQ queue. The message
contains an ID that is used by a bean to perform a database lookup. The
lookup can contain anything up to around one million records. Each of th
Hi. I'm using geronimo-jetty-2.1.4 running with jdk1.6. This geronimo
has an activemq (4.1.2) running on 61616. I have created queue
'SendReceiveQueue' using geronimo and it works. Generally, I would
like to add camel as mediation engine which will connect Http, Cometd,
Restlet , and geronimo JMS
Hi Marc,
It maybe a bug of camel-cxf component, I will look it tommorrow.
Please feel free to fill a JIRA[1] for it.
[1] https://issues.apache.org/activemq/browse/CAMEL
Willem
Marc Giger wrote:
> Hi Willem,
>
> In my case the entry point is a cxfEndpoint. My route looks
> like the following:
>
Many thanks Claus,
Based on the link provided and feedback received from Costin Leau, here is
what I have done to resolve the issue :
To work with the following uri :
file://d:/temp/data/?move=d:/temp/done/${file.name}
in your camel route and define it in a property file,
here is what you have
Gert-Jan,
It seems like a reasonable use case so I'd like to give it a shot to
fix this. Do you think you can create a unit test or something that
demonstrates the problem? That would make it a lot easier to
troubleshoot and fix your issue.
Regards,
Gert Vanthienen
Ope
The only alternative seems to be to pass the filename in the header
and then use the document function to get the xml fragment:
in Java:
.setHeader("agents.xml",
constant(getCacheLocation() + "/agents.xml"))
in the xsl:
On 5 mei 2009, at 12:
Hi Willem,
In my case the entry point is a cxfEndpoint. My route looks
like the following:
from("cxf:bean:routerEndpoint?dataFormat=MESSAGE").
processRef("uniqueIDProcessor").
processRef("decryptProcessor").
processRef("idProcessor").
Whatever I convert it to, it makes no difference. If I create an
explicit NodeSet and set it, I get
Invalid conversion from NodeSet to node-set
I use Camel 1.6.0
It makes no difference running Java 1.5 or 1.6.
On 4 mei 2009, at 22:47, Gert-Jan van de Streek wrote:
I want to pass an xml f
Hi Marc,
I'm sorry that I misunderstand your question.
Since we don't use CXFMessage to store CXF message for better support
routing the message between cxf and other endpoints, the original CXF
message context maybe lost between the CXF endpoints.
If you just want to Camel route work as proxy,
Hi
I would not go down the AsyncProcessor route :) Its @deprecated and
will be replaced by a new API in 2.0.
The AsyncProcessor was an experiment that was added in Camels early
days and the JDK API itself has much better solutions
for handling async tasks. Hence why we are replacing it totally in
I see both jms consumer and seda consumer uses getProcessor().process()
instead of the getAsyncProcessor().process(exchange, callback). I am
concerned whether it will block even though I have an async
producer(implemented the AsyncProcessor) down the route. If this were the
case, seda consumer woul
Hi
Last time we checked it required Spring 3.0 as Spring 2.5 did not
support the property placeholders in custom namespace handlers.
There is a ticket in Camel JIRA that has a link to the ticket in Spring JIRA.
However if you define you endpoints with the
then you can use property placeholders.
Hi,
I would like to know if something is planned to support uri declaration for
Camel routes using variable like by example : ${my_Uri}
e.g.
file
and
osgix:cm-properties like this
file://c:/temp/data/?move=c:/temp/done/${file:name}
(2)
queuingservice:queue:in (
23 matches
Mail list logo
