I have a producer that polls an email inbox, and sends any new messages into
a queue. This queue has a stomp consumer.
for plain text emails, this works just fine. All headers are received, and
the body of the email is the body of the inbound stomp message.
However, for multipart messages, all th
On Mon, Aug 22, 2011 at 2:07 PM, aurelienmasse wrote:
> I'm using 2.8.0
>
I created an unit test on trunk, and it works fine there
http://svn.apache.org/viewvc?rev=1160565&view=rev
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/inProgressRepository-not-cleaned-in-Gene
The defaultOperationNameSpace should be defaultOperationNamespace.
I just update the wiki page entry of it.
But this operation should be used with defaultOperationName at the same
time to help camel-cxf locate the BindingOperationInfo.
On 8/23/11 2:35 PM, xiangqiuzhao wrote:
thanks, i had make
Hi
With the help of Reponse/ ResponseBuilder, you can build the response
for the bookResource like this
Response r =
Response.status(200).entity(bookResource).header(xxx,xxx).build();
exchange.getOut().setBody(r);
On 8/23/11 2:22 AM, bird bird wrote:
Hi all.
How do I set response header
Hello Claus
Ok i've found the problem, it appeared to be a simple mistake on my code.
It works perfectly now using the ConsumerTemplate.
Thanks a lot for your help and for the time you spent.
--
View this message in context:
http://camel.465427.n5.nabble.com/inProgressRepository-not-cleaned-i
Drool is just using the camel processor to integrate it with Camel.
Your drool bean way is another solution which is more easy way to expose
the drool service to camel route.
I'm not sure why do you choice camel-cxf component, can you explain more
about it ?
On 8/23/11 8:33 AM, dunnlow wrot
Hi,
i'm building my first route using the java DSL and i'm running in a small
trouble setting a header field.
I had a spring route looking and working like this:
//incoming:Value[1]/@date
I want to build exactly the same in the java dsl:
.setHeader("incomingDate")
.xpath("//incomi
i need to invoke service operationName decide by program logic.
so i want to config the URI point the service address and not appoint the
special operationName.
but how to know the namespace and the webservice wsdl:message by camel? if i
appoint the operationName,
why camel can't know the wsdl:m
Addition: Camel 2.5.0
--
View this message in context:
http://camel.465427.n5.nabble.com/setHeader-using-xpath-returns-Object-tp4726154p4726178.html
Sent from the Camel - Users mailing list archive at Nabble.com.
On Tue, Aug 23, 2011 at 11:43 AM, heinrichheine
wrote:
> Hi,
>
> i'm building my first route using the java DSL and i'm running in a small
> trouble setting a header field.
>
> I had a spring route looking and working like this:
>
>
> resultType="java.lang.String">//incoming:Value[1]/@da
Hi,
It should be
setHeader("incomingDate", xpath("//incoming:Value[1]/@date",
String.class, ns))
but not
setHeader("incomingDate")
.xpath("//incoming:Value[1]/@date", String.class, ns)
Freeman
On 2011-8-23, at 下午5:43, heinrichheine wrote:
Hi,
i'm building my first route using the java D
Your totally right,
but if i do it, i get:
"The method xpath(String) in the type BuilderSupport is not applicable for
the arguments (String, Class, Namespaces)"
compile error.
--
View this message in context:
http://camel.465427.n5.nabble.com/setHeader-using-xpath-returns-Object-tp4726154p47262
Hi Christian,
I just played with your test case with Camel trunk code.
I found the test can be passed when you remove the route instead of stop
the route.
Please update the setUp() code like this
context.removeRoute(Route2.class.getName());
On 8/23/11 4:36 AM, Christian Müller wrote:
H
Hmm. Thanks for helping me start to think about things.
So it looks like I was originally trying to do this:
1. take RS or WS Object into process method
2. wiretap Object into queue
3. write tapped Object to file
4. return from process method
So, what _should_ I do if all I want is to take an CXF
I have configured camel jmx to combine with my application's jmx console by
doing the below configuration in camel-context.xml
I am successful in doing this.
This is how it is getting displayed in my application's jmx console(see
below).
My requirement is to filter on required type and show o
Hi.
Occationally I get a NPE that seems related to CamelNamespaceHandler
when running under Java 7. Switching back to Java 6 I don't seem to
get this problem.
The problem seems very similar to the one from this thread
http://camel.465427.n5.nabble.com/Occasional-CamelNamespaceHandler-exception-whe
Another option would be to move the "restricted" log4j.properties file into
something like src/test/log4j and then add a system property to surefire
configuration to pick it up from there. When running with maven, it would be
used. When running in your IDE, it wouldn't be picked up and the
Thanks for your response. My application is a web-based, stand-alone Camel
Spring application. I have a separate server for Drools that should:
receive pojo beans from my Camel app via web service, run my business rules,
then return the result to my Camel app.
My thought on the cxf component is
On 8/23/11 8:21 PM, dunnlow wrote:
Thanks for your response. My application is a web-based, stand-alone Camel
Spring application. I have a separate server for Drools that should:
receive pojo beans from my Camel app via web service, run my business rules,
then return the result to my Camel app.
Hi Mick,
I just committed a simple unit test[1] into camel-cxf, you make take a
look and add the missing part that you need.
[1]http://svn.apache.org/viewvc?rev=1160701&view=rev
On 8/23/11 7:43 PM, Mick Knutson wrote:
Hmm. Thanks for helping me start to think about things.
So it looks like I
I made a simple example using Camels FTP component. For that I added
camel-ftp
to my pom.xml file.
Unfortunately when running the code I got some strange error messages.
What solved the problem was adding an additional line to my pom.xml file:
camel-spring
Question: Why does Maven no
What was the error message and what Camel version are you using? camel-ftp
shouldn't require camel-spring.
On Tue, Aug 23, 2011 at 12:45 PM, Tristan23 wrote:
> I made a simple example using Camels FTP component. For that I added
> camel-ftp
> to my pom.xml file.
>
> Unfortunately when runni
Hi, I'm using WebSphere 6.1.0.29 on AIX trying to run Camel 2.6 on it. I'm
getting following exceptions when the app server starts. It seems like I
have some conflicts with xerces ml-apis jars.
[8/23/11 13:29:52:848 EDT] 0016 WebAppE Exception caught while
initializing context
org.a
It would be nice to have the Property Placeholder support recursive
substitution. I use this feature in Spring to configure properties for
various environments. For example:
db.URL= ${${env}.db.URL}
dev.db.URL=jdbc:jtds:sqlserver://S08DX01:7531/UserAcnt
test.db.URL=jdbc:jtds:sqlserver://S08DXK01:
the best way that I've found to do this is to use a default file for common
props and just override the differences in an environment specific file.
Spring has support for this...
classpath:/environments/default.properties
Hello all,
Just to be quick, I've got a camel route that looks something like this:
Basically, a message is delivered to an endpoint and a response is received
which is then transformed using an XSL stylesheet, and the result is given
back to the original requester. This works just
Hi,
try to enable stream caching:
http://camel.apache.org/stream-caching.html
It has worked for me with disappearing messages :)
Mirko
On Tue, Aug 23, 2011 at 9:47 PM, dougman82 wrote:
> Hello all,
>
> Just to be quick, I've got a camel route that looks something like this:
>
>
>
>
>
Ok, I tried giving the stream caching a go, both on the route level, and on
the Camel context level, and neither seemed to alleviate the issue.
Just out of curiosity, I added another step in the route in which the
message gets sent to a method of a Java bean. The method does nothing but
return the
Hello Willem!
Thank you for you reply. Unfortunately it doesn't work for me. I updated me
test to
public class Route1Test extends CamelSpringTestSupport {
@EndpointInject(uri = "mock:foo")
private MockEndpoint mockEndpointFoo;
@Override
@Before
public void setUp() throws Exc
Could you try:
Best,
Christian
Thanks for the test case, but I am having issues following it as it pertains
to the original example.
Here is the processor from the original:
private class MappingProcessor implements Processor {
private Class beanClass;
private Object instance;
public MappingProces
If I add that empty "transform" tag, I get an exception thrown when the
Spring context tries to initialize. Says that the "content of element
'transform' is not complete".
Thanks,
Douglas
Christian Mueller wrote:
>
> Could you try:
>
>
>
>
>
>
>
>
>
>
> Best,
> Christian
>
Hi,
I have a camel route which reads xml messages from a jms queue, performs a
series of steps (decrypts, transforms, enriches, etc.) to the message and
then finally persists the updated object to a database. What I'm trying to
do now is configure a dead letter queue which will route the */origin
Thanks All.
Changing the receiver endpoint to use an "InOnly" exchange pattern solved
the problem. E.g. -
--
View this message in context:
http://camel.465427.n5.nabble.com/JMS-Websphere-MQ-Error-MQJE001-Completion-Code-2-Reason-2027-tp4713509p4728417.html
Sent from the Camel - Users mai
Well, it looks like the camel-netty component won't work for me. It
appears that it opens the connection for each exchange. Am I reading
that right? What I need is a persistent connection with automatic
reconnects. Oh well, back to the drawing board.
On Wed, Aug 17, 2011 at 7:59 AM, James Carm
I have just started learning CAMEL. There are some good basic examples to
learn CAMEL. It seems that, using CAMEL, it is so simple to send a message
from one queue to the other. For example he is one example:
from("activemq:queue1”)
.to("activemq:queue2");
The above two lines will do the job. I h
Try enabling trace: http://camel.apache.org/tracer.html.
One of your route steps might be throwing an exception which is dealt with
by a default error handler:
http://camel.apache.org/error-handler.html
2011/8/23 dougman82
> Hello all,
>
> Just to be quick, I've got a camel route that looks some
when you setup your "activemq" component (generally in spring xml), you have
to specify the broker to connect to. this is generally localhost, but can
be an external broker, etc. So, just setup multiple activemq components
(and give them an appropriate ID)...like this
Hi,
Which version of CXF are you using?
If you are using CXF 2.4.1, you need to upgrade it to CXF 2.4.2.
There is a issue about the holder object checking in the CXF 2.4.1.
On 8/24/11 5:23 AM, Mick Knutson wrote:
Thanks for the test case, but I am having issues following it as it pertains
to t
You can specify the operationName and operationNamespace at the runtime
by setting the message header with those key.
In most case you don't need to specify the operationNamespace if it is
same with the ServiceName namespace.
On Tue Aug 23 17:43:44 2011, xiangqiuzhao wrote:
i need to invoke se
Hi Christian,
I tried to run the test with Camel 2.8.0 and Camel 2.9-SNAPSHOT.
I don't have the issue that you meet.
On 8/24/11 4:28 AM, Christian Müller wrote:
Hello Willem!
Thank you for you reply. Unfortunately it doesn't work for me. I updated me
test to
public class Route1Test extends Ca
I set the keys at runtime, but can't find the service in the server.
Exchange exchange = endpoint.createExchange();
exchange.getIn().setHeader("operationName", "helloService");
exchange.getIn().setHeader("operationNamespace",
"http://www.wstest.sunyard.com/IWSTestService/";);
exchange.getIn().setB
Does you service is provided from CXF ?
There are some unit test in the camel-cxf module that you can take a look.
On 8/24/11 10:11 AM, xiangqiuzhao wrote:
I set the keys at runtime, but can't find the service in the server.
Exchange exchange = endpoint.createExchange();
exchange.getIn().setHea
That doesn't sound right, what have you read? Logs/docs?
And are you using keep-alive?
Taariq
On 24 Aug 2011, at 12:12 AM, James Carman wrote:
> Well, it looks like the camel-netty component won't work for me. It
> appears that it opens the connection for each exchange. Am I reading
> that r
Hi,
You may consider to use the XPathBuilder to setup the expression for the
setHeader().
On 8/23/11 6:06 PM, heinrichheine wrote:
Your totally right,
but if i do it, i get:
"The method xpath(String) in the type BuilderSupport is not applicable for
the arguments (String, Class, Namespaces)"
your means i can set message body like
fldsjaflkjdsa
and invoke helloService in remote?
--
View this message in context:
http://camel.465427.n5.nabble.com/i-use-wsdl-file-and-payload-dataFormat-but-IllegalArgumentException-tp4719896p4729146.html
Sent from the Camel - Users mailing list a
PAYLOAD body is a list of element, you should create the element
yourself and set it into the PAYLOAD.
On Wed Aug 24 11:48:05 2011, xiangqiuzhao wrote:
your means i can set message body like
fldsjaflkjdsa
and invoke helloService in remote?
--
View this message in context:
http://came
Can you try to set the class loader parent first?
It looks like there are some issue loading the sun jaxp dom module.
On 8/24/11 1:42 AM, jackkirsten wrote:
Hi, I'm using WebSphere 6.1.0.29 on AIX trying to run Camel 2.6 on it. I'm
getting following exceptions when the app server starts. It see
it should behave as you described...at first glance, not sure why you are
seeing otherwise...
here is a unit test that I created a while back to validate this...
public class UseOriginalMessageRouteTest extends CamelTestSupport {
private static final Logger logger =
Logger.getLogger(UseO
On Tue, Aug 23, 2011 at 12:06 PM, heinrichheine
wrote:
> Your totally right,
>
> but if i do it, i get:
> "The method xpath(String) in the type BuilderSupport is not applicable for
> the arguments (String, Class, Namespaces)"
>
The xpath should have methods to set the namespace, result type etc.
Hi
You can most likely use a custom ManagementNamingStrategy (for example
extending the default)
and then return null for the mbean types you dont like to be enlisted.
You would need to add a to the camel-context.xml file to have
you custom naming strategy being used by Camel
There is also the
Hi
Thanks for the heads up. We have no official support for JDK7 with Camel.
This is something we will work on in one of the next releases. But
JDK7 has just been released.
Likewise the issue could also steam from Spring-DM and thus harder to
resolve. But thanks for reporting your observations.
52 matches
Mail list logo
