Re: activemq replyTo not working sometimes
Hi We have created a web app to create camel stations(endpoints) and routes dynamically. So users can add new stations and then create routes based on that stations. For one of our use case we need to create a web service with different operations. So we decided to use cxf ,content Router and JMS We have created one CXF station , two JMS stations(one for each operation). Then three routes has been created. Route 1 (Parent) : CXF station --- Content router -- two JMS stations (based on operation(XPATH)) Route 2 (Child) : JMS(1) ---chain of processors Route 3 (Child): JMS(2) ---chain of processors We have options to start and stop routes in web via jmx. Start operation includes adding the route to context and starting. Stop operation stops the route and removes it from context. In normal scenario when all three routes are started then cxf is able to receive responses processed by child routes. But suppose if we are restarting the child routes then cxf is not able to receive responses and default Jms timeout is happening. Observation : When child route is restarted then consumers on Reply queue is getting deleted. Note: In Both JMS exclusive reply queue has been set. - Regards kiran Reddy -- View this message in context: http://camel.465427.n5.nabble.com/activemq-replyTo-not-working-sometimes-tp5733682p5733917.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: MailComponent/MailConsumer misses Mails
A general question: Is the camel mail consumer transaction secure? kind regards, Christoph -- View this message in context: http://camel.465427.n5.nabble.com/MailComponent-MailConsumer-misses-Mails-tp5733010p5733918.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Setting a requestTimeout for a shared/Exclusive reply does not take effect for multiple concurrent users
How have you configured the jms component and your connection factory et all? On Wed, Jun 5, 2013 at 5:29 PM, Siva B kbsiva...@yahoo.com.sg wrote: *OS *- RHEL 5.3 *Tomcat *- 7.0.39 *JDK *- 1.7 *Spring *- 3.0.2 *WebSphere MQ* - 7.0 *Camel version* - 2.10.4 *Component/s:* camel-core, camel-jms -- View this message in context: http://camel.465427.n5.nabble.com/Setting-a-requestTimeout-for-a-shared-Exclusive-reply-does-not-take-effect-for-multiple-concurrent-us-tp5733811p5733897.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - www.camelone.org: The open source integration conference. Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Re: Restful services using camel
Hi
On 05/06/13 17:33, Tarun Kumar wrote:
I am writing restful webservices using camel cxfrs components. I want to
expose 10 services and my service interface looks like this:
@Path(/employees)
public interface EmployeeService {
@Post
@path(/account)
someMethod1();
@Get
@Path(/books)
someMethod2();
...
...
}
For each endPoint, i don't want to create one cxf:rsServer server (because
it won't be scalable solution). I want to expose all the services with one
cxf:rsServer. So, here is what i did:
cxf:rsServer id=rsServer address=http://localhost:8080/employee-service/
serviceClass=com.abc. EmployeeServiceImpl loggingFeatureEnabled=true
loggingSizeLimit=20
/cxf:rsServer
Route for each service is different. i.e. from().to().to().end() for each
of these services is different. How can i make sure that when i invoke
http://localhost:8080/employee-service/employees/account, route for
someMethod1() should get called?
As far as I understand you may want to have a single cxf:rsServer
endpoint which has up to 10 resource classes/beans.
With the regular CXF jaxrs:server, one can do something like this:
jaxrs:server address=/company
jaxrs:serviceBeans
ref bean=bean1/
!-- ... --
ref bean=bean10/
/jaxrs:serviceBeans
/jaxrs:server
where bean1 to bean10 represent individual root resources, once starting
with /employees, another one with /managers, etc
I guess you may want to do something like this too with cxf:rsServer
Cheers, Sergey
Re: Trying to set JaxbDataFormat on CdiCamelContext
Hi Claus, Thanks for your answer. That was not the problem, I found the correct way to do it. Solution: use the marshal method passing the 'dataTypeRef' match with the existent on the CdiCamelContext: from(jms:queue:EP_QUEUE_JOURNAL) .marshal(jaxb) .bean(journalEventProcessor); -- View this message in context: http://camel.465427.n5.nabble.com/Trying-to-set-JaxbDataFormat-on-CdiCamelContext-tp5733512p5733935.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Problem with runTimeException handling.
Hi Claus, Thanks for the quick reply but I think I explained my problem incorrectly. So here I try again: 1) My route flows like HTTP Req - Jetty - Bean1 - Bean 2 - Route END. After this a HTTP reply goes back to sender. 2) Now say for e.g. during bean 1 I encounter a timer expiry. I handle this using runtime exception in which I want to do a HTTP reply back to sender to tell him of this expiry. Question is, can I get the Jetty context on a ad-hoc basis. Also can the route continue to Bean 2 after I send this reply. Hope I have done a better job this time -- View this message in context: http://camel.465427.n5.nabble.com/Problem-with-runTimeException-handling-tp5733659p5733939.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: SSH using dynamic slip
GVvenkat, I'd be curious what your workaround is. Curious if there's a change needed in camel-ssh to make it easier... Scott On Tue, Jun 4, 2013 at 3:04 PM, Gvvenkat gvvenkat...@yahoo.com wrote: I found a work around for this... Thanks, if anyone had spent any time on it. -- View this message in context: http://camel.465427.n5.nabble.com/SSH-using-dynamic-slip-tp5733752p5733822.html Sent from the Camel - Users mailing list archive at Nabble.com.
camel-cdi behavior bean vs beanRef
Hello,
I am suffering a (to me) strange behavior using camel-cdi 2.11.0 ... i'll
appreciate if you could put some light on it to help me understand.
We are using camel-cdi on project and i am performing some testing to fully
understand mechanism and discover potential problems in an early stage.
I am observing @PostConstruct lifecycle events on this route
@Override
public void configure() throws Exception {
from(direct://startEndpoint)
.routeId(firstRoute)
.beanRef(DeScopeTestVO.class)
.to(direct://endEndpoint);
from(direct://endEndpoint)
.routeId(secondRoute)
.beanRef(DeScopeTestVO.class)
.to(direct://finalEndpoint);
}
Where DeScopeTestVO is annotated with @Named, and i am testing both beanRef,
and bean. What i've observed is that using bean method the
DeScopeTestVO.postConstruct is called two times (one each route) on the
camel context startup ... but when using beanRef this is duplicated and
those are being called 4 times (two each route).
Also i have a lack of knowledge in the way those mechanism works ... are
those DeScopeTestVO introduced in the camel registry/context and looked out
there? ... or are they instantiated directly?
Thanks in advance!
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-cdi-behavior-bean-vs-beanRef-tp5733944.html
Sent from the Camel - Users mailing list archive at Nabble.com.
RE: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF producer using Payload dataformat
Hi William,
I had tried specifying the wsdlURL but did not work. Not sure if my path was
not wrong. I had put in web-app\wsdl\my.wsdl. Does it need to be under web-inf?
Finally I tried generating client classes from the wsdl (using maven code gen
plugin) and specified the serviceClass attribute pointing to the generated
service class. It worked after that.
Just wondering, are those fields not optional for producer? The request was
going through fine just response handling was failing.
Thanks
Sunita
-Original Message-
From: Willem jiang [mailto:willem.ji...@gmail.com]
Sent: Wednesday, June 05, 2013 10:11 PM
To: users@camel.apache.org
Subject: Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Hi,
I just found you didn't specify the wsdlURL or serviceClass attributes in you
CxfEndpoint element.
They are useful when CXF is trying to build up ServiceModel for handling the
request and response.
Can you add either one of them to your CxfEndpoint definition?
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Wednesday, June 5, 2013 at 10:23 PM, sunita wrote:
Hi William,
Thanks for your response. I was initially posting only on camel user
group but since I did not get any responses to my earlier posts, I
decided to post on both since it may have different audiences.
Do you know why I am getting this error when I wrap the response in
soap envelope. I had posted this question earlier as well.
org.apache.cxf.interceptor.Fault: Unexpected element
{http://model.webservices.ihe.adapters.ccg.dataexchange.hcit.ge.com/
CcdaXdrService}ccdaResponse
found. Expected
{http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse.
at
org.apache.cxf.interceptor.DocLiteralInInterceptor.validatePart(DocL
iteralInInterceptor.java:258)
at
org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(Doc
LiteralInInterceptor.java:200)
see the Post with following tittle for more details
Camel 2.9.2 - Error parsing custom CXF response -
org.apache.cxf.interceptor.Fault: Unexpected element
{http://CcdaXdrService}ccdaResponse found. Expected
{http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-9-2-CXF-2-6-2-How-should-the
-response-look-for-CXF-producer-using-Payload-dataformat-tp5733748p573
3881.html Sent from the Camel - Users mailing list archive at
Nabble.com (http://Nabble.com).
Re: idempotentConsumer is not idempotent?
Although you may be wishing for a strict interpretation of idempotent, there are also practical interpretations, e.g. the idempotent option for the file:// component - the whole purpose of this option is to read the file only once, even if it remains in the directory. On Thu, Jun 6, 2013 at 10:07 AM, jannecamel jann...@iki.fi wrote: At first look I was getting excited about idempotentConsumer - this would help me nicely in creating idempotent services. But looking closer, it does not seem to do what it says? Looks like it takes first request and processes it. Then if duplicate messages come, it just discards those. A true idempotent consumer would discard the duplicate messages AND return the same (cached) response as the first one got. For example if I have service add(x,y) and I call add(2,5) multiple times, each call should return 7. Now first returns 7 and duplicate ones return nothing. Or did I understand it wrong? http://www.enterpriseintegrationpatterns.com/IdempotentReceiver.html The term idempotent is used in mathematics to describe a function that produces the same result if it is applied to itself, i.e. f(x) = f(f(x)). In Messaging this concepts translates into the a message that has the same effect whether it is received once or multiple times. This means that a message can safely be resent without causing any problems even if the receiver receives duplicates of the same message. -- View this message in context: http://camel.465427.n5.nabble.com/idempotentConsumer-is-not-idempotent-tp5733945.html Sent from the Camel - Users mailing list archive at Nabble.com.
RE: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF producer using Payload dataformat
I am using CXF 2.6.2. We use IPF jars for IHE profile which depend on CXF 2.6.2
Did you test with Camel 2.9.2 and CXF 2.6.2 by any chance?
Thanks
Sunita
-Original Message-
From: Aki Yoshida [mailto:elak...@gmail.com]
Sent: Thursday, June 06, 2013 9:58 AM
To: users@camel.apache.org
Subject: Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Actually, the payload check by DocLiteranInInterceptor is disabled by default
for the generic dispatcher mode.
So it is strange.
I thought there could be some version interoperability issue between cxf and
camel and just ran a test with camel-2.9.2 and cxf-2.6.4.
but it's working for me.
so it is strange that sunita is getting this error.
2013/6/6 Willem jiang willem.ji...@gmail.com
Hi,
I just found you didn't specify the wsdlURL or serviceClass attributes
in you CxfEndpoint element.
They are useful when CXF is trying to build up ServiceModel for
handling the request and response.
Can you add either one of them to your CxfEndpoint definition?
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com
(http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Wednesday, June 5, 2013 at 10:23 PM, sunita wrote:
Hi William,
Thanks for your response. I was initially posting only on camel user
group
but since I did not get any responses to my earlier posts, I decided
to
post
on both since it may have different audiences.
Do you know why I am getting this error when I wrap the response in
soap envelope. I had posted this question earlier as well.
org.apache.cxf.interceptor.Fault: Unexpected element {
http://model.webservices.ihe.adapters.ccg.dataexchange.hcit.ge.com/Ccd
aXdrService}ccdaResponse
found. Expected
{http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse.
at
org.apache.cxf.interceptor.DocLiteralInInterceptor.validatePart(DocLit
eralInInterceptor.java:258)
at
org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLi
teralInInterceptor.java:200)
see the Post with following tittle for more details
Camel 2.9.2 - Error parsing custom CXF response -
org.apache.cxf.interceptor.Fault: Unexpected element
{http://CcdaXdrService}ccdaResponse found. Expected
{http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-9-2-CXF-2-6-2-How-should-the
-response-look-for-CXF-producer-using-Payload-dataformat-tp5733748p573
3881.html
Sent from the Camel - Users mailing list archive at Nabble.com (
http://Nabble.com).
Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF producer using Payload dataformat
2013/6/6 Monga, Sunita (GE Healthcare) sunita.mo...@ge.com
Hi William,
I had tried specifying the wsdlURL but did not work. Not sure if my path
was not wrong. I had put in web-app\wsdl\my.wsdl. Does it need to be under
web-inf?
Finally I tried generating client classes from the wsdl (using maven code
gen plugin) and specified the serviceClass attribute pointing to the
generated service class. It worked after that.
Just wondering, are those fields not optional for producer? The request
was going through fine just response handling was failing.
yeah. actually they are indeed optional for the producer part since 2.8.0.
so I replied to the earlier mail by saying it's strange that you are
getting this error.
and when I ran a test with the same combination of camel and cxf versions,
it works fine.
So I suspect that you might be picking up another version of camel or cxf
that has some interoperability issue.
Thanks
Sunita
-Original Message-
From: Willem jiang [mailto:willem.ji...@gmail.com]
Sent: Wednesday, June 05, 2013 10:11 PM
To: users@camel.apache.org
Subject: Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Hi,
I just found you didn't specify the wsdlURL or serviceClass attributes in
you CxfEndpoint element.
They are useful when CXF is trying to build up ServiceModel for handling
the request and response.
Can you add either one of them to your CxfEndpoint definition?
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Wednesday, June 5, 2013 at 10:23 PM, sunita wrote:
Hi William,
Thanks for your response. I was initially posting only on camel user
group but since I did not get any responses to my earlier posts, I
decided to post on both since it may have different audiences.
Do you know why I am getting this error when I wrap the response in
soap envelope. I had posted this question earlier as well.
org.apache.cxf.interceptor.Fault: Unexpected element
{http://model.webservices.ihe.adapters.ccg.dataexchange.hcit.ge.com/
CcdaXdrService}ccdaResponse
found. Expected
{http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse.
at
org.apache.cxf.interceptor.DocLiteralInInterceptor.validatePart(DocL
iteralInInterceptor.java:258)
at
org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(Doc
LiteralInInterceptor.java:200)
see the Post with following tittle for more details
Camel 2.9.2 - Error parsing custom CXF response -
org.apache.cxf.interceptor.Fault: Unexpected element
{http://CcdaXdrService}ccdaResponse found. Expected
{http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-9-2-CXF-2-6-2-How-should-the
-response-look-for-CXF-producer-using-Payload-dataformat-tp5733748p573
3881.html Sent from the Camel - Users mailing list archive at
Nabble.com (http://Nabble.com).
Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF producer using Payload dataformat
Sunita,
I seem to have picked the wrong version.
I'll test it again.
regards, aki
2013/6/6 Monga, Sunita (GE Healthcare) sunita.mo...@ge.com
I am using CXF 2.6.2. We use IPF jars for IHE profile which depend on CXF
2.6.2
Did you test with Camel 2.9.2 and CXF 2.6.2 by any chance?
Thanks
Sunita
-Original Message-
From: Aki Yoshida [mailto:elak...@gmail.com]
Sent: Thursday, June 06, 2013 9:58 AM
To: users@camel.apache.org
Subject: Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Actually, the payload check by DocLiteranInInterceptor is disabled by
default for the generic dispatcher mode.
So it is strange.
I thought there could be some version interoperability issue between cxf
and camel and just ran a test with camel-2.9.2 and cxf-2.6.4.
but it's working for me.
so it is strange that sunita is getting this error.
2013/6/6 Willem jiang willem.ji...@gmail.com
Hi,
I just found you didn't specify the wsdlURL or serviceClass attributes
in you CxfEndpoint element.
They are useful when CXF is trying to build up ServiceModel for
handling the request and response.
Can you add either one of them to your CxfEndpoint definition?
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com
(http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Wednesday, June 5, 2013 at 10:23 PM, sunita wrote:
Hi William,
Thanks for your response. I was initially posting only on camel user
group
but since I did not get any responses to my earlier posts, I decided
to
post
on both since it may have different audiences.
Do you know why I am getting this error when I wrap the response in
soap envelope. I had posted this question earlier as well.
org.apache.cxf.interceptor.Fault: Unexpected element {
http://model.webservices.ihe.adapters.ccg.dataexchange.hcit.ge.com/Ccd
aXdrService}ccdaResponse
found. Expected
{http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse.
at
org.apache.cxf.interceptor.DocLiteralInInterceptor.validatePart(DocLit
eralInInterceptor.java:258)
at
org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLi
teralInInterceptor.java:200)
see the Post with following tittle for more details
Camel 2.9.2 - Error parsing custom CXF response -
org.apache.cxf.interceptor.Fault: Unexpected element
{http://CcdaXdrService}ccdaResponse found. Expected
{http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-9-2-CXF-2-6-2-How-should-the
-response-look-for-CXF-producer-using-Payload-dataformat-tp5733748p573
3881.html
Sent from the Camel - Users mailing list archive at Nabble.com (
http://Nabble.com).
unmarshal().xstream() not working
I'm trying to unmarshal an xml file with camel. File is created with xStream and simple model. When I change my route to: it reads the file and I get this output: But when I try to unmarshal the xml I get nothing, I don't even hit the breakpoint on this line: ---EXECUTABLE CODE-- -- View this message in context: http://camel.465427.n5.nabble.com/unmarshal-xstream-not-working-tp5733953.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Issues with ftp in the 2.11.0 version of camel.
Downgrading worked, Thanks -- View this message in context: http://camel.465427.n5.nabble.com/Issues-with-ftp-in-the-2-11-0-version-of-camel-tp5733824p5733956.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Issues with ftp in the 2.11.0 version of camel.
I have approx. 600 files on the ftp server. We actually do need, to support sorting, my example was just a very simple case showing the performance issues. -- View this message in context: http://camel.465427.n5.nabble.com/Issues-with-ftp-in-the-2-11-0-version-of-camel-tp5733824p5733957.html Sent from the Camel - Users mailing list archive at Nabble.com.
RE: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF producer using Payload dataformat
Thanks Aki for your response.
I think IPF version we use depends on Camel 2.9.2 CXF 2.6.2, so don’t think
we can change the camel version either.
Any way I have it working by specifying the serviceClass. Something to keep in
mind in the future when we upgrade I guess.
Thanks so much for your help
Sunita
-Original Message-
From: Aki Yoshida [mailto:elak...@gmail.com]
Sent: Thursday, June 06, 2013 10:57 AM
To: users@camel.apache.org
Subject: Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Sunita,
not working indeed with cxf-2.6.2 and camel-2.9.2.
but it's working with cxf-2.6.2 and camel-2.9.4 (it also works with
camel-2.9.3).
I previously misquoted the micro version and also got mixed up which one was 4
:-( So this time, I doubled checked the versions.
and it is also working with the latest cxf-2.6.x and camel-2.9.x versions,
which are cxf-2.6.8 and camel-2.9.7.
so you may consider upgrading at least the camel part if you want to stick to
the simple generic dispatcher mode.
regards, aki
2013/6/6 Aki Yoshida elak...@gmail.com
Sunita,
I seem to have picked the wrong version.
I'll test it again.
regards, aki
2013/6/6 Monga, Sunita (GE Healthcare) sunita.mo...@ge.com
I am using CXF 2.6.2. We use IPF jars for IHE profile which depend on
CXF
2.6.2
Did you test with Camel 2.9.2 and CXF 2.6.2 by any chance?
Thanks
Sunita
-Original Message-
From: Aki Yoshida [mailto:elak...@gmail.com]
Sent: Thursday, June 06, 2013 9:58 AM
To: users@camel.apache.org
Subject: Re: Camel 2.9.2, CXF 2.6.2 - How should the response look
for CXF producer using Payload dataformat
Actually, the payload check by DocLiteranInInterceptor is disabled by
default for the generic dispatcher mode.
So it is strange.
I thought there could be some version interoperability issue between
cxf and camel and just ran a test with camel-2.9.2 and cxf-2.6.4.
but it's working for me.
so it is strange that sunita is getting this error.
2013/6/6 Willem jiang willem.ji...@gmail.com
Hi,
I just found you didn't specify the wsdlURL or serviceClass
attributes in you CxfEndpoint element.
They are useful when CXF is trying to build up ServiceModel for
handling the request and response.
Can you add either one of them to your CxfEndpoint definition?
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com
(http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Wednesday, June 5, 2013 at 10:23 PM, sunita wrote:
Hi William,
Thanks for your response. I was initially posting only on camel
user
group
but since I did not get any responses to my earlier posts, I
decided to
post
on both since it may have different audiences.
Do you know why I am getting this error when I wrap the response
in soap envelope. I had posted this question earlier as well.
org.apache.cxf.interceptor.Fault: Unexpected element {
http://model.webservices.ihe.adapters.ccg.dataexchange.hcit.ge.com/
Ccd
aXdrService}ccdaResponse
found. Expected
{http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse.
at
org.apache.cxf.interceptor.DocLiteralInInterceptor.validatePart(Doc
Lit
eralInInterceptor.java:258)
at
org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(Do
cLi
teralInInterceptor.java:200)
see the Post with following tittle for more details
Camel 2.9.2 - Error parsing custom CXF response -
org.apache.cxf.interceptor.Fault: Unexpected element
{http://CcdaXdrService}ccdaResponse found. Expected
{http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-9-2-CXF-2-6-2-How-should-
the
-response-look-for-CXF-producer-using-Payload-dataformat-tp5733748p
573
3881.html
Sent from the Camel - Users mailing list archive at Nabble.com (
http://Nabble.com).
Re: A little problem with annotation @CsvRecord
Hi Claus, Thanks for fast response. I tried outside osgi and works fine. I didn´t tried in Karaf (I have to invest some time trying it). I moved to camel-beanio and It´s working inside osgi too, so appears to be a problem of bind with osgi. I´m just starting with osgi stuffs, when I´ll could figure out the full picture (or almost full) picture I´ll try to contribute if it´s really a bug (i´m not sure if I was doing something wrong). thank you very much, Walter -- View this message in context: http://camel.465427.n5.nabble.com/A-little-problem-with-annotation-CsvRecord-tp5728109p5733960.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Setting a requestTimeout for a shared/Exclusive reply does not take effect for multiple concurrent users
Here is the camel-context XML configuration. WebSphereDestinationResolver
implements Camel's DestinationResolver and overrides resolveDestination
method.
camelContext xmlns=http://camel.apache.org/schema/spring;
template id=camelTemplate /
/camelContext
bean id=wmq class=org.apache.camel.component.jms.JmsComponent
property name=connectionFactory ref=credentials /
property name=destinationResolver
ref=webSphereDestinationResolver /
property name=receiveTimeout
value=${receiveTimeout}/property
property name=requestTimeout
value=${requestTimeout} /
/bean
bean id=webSphereDestinationResolver
class=XX.WebSphereDestinationResolver /
bean id=credentials
class=org.springframework.jms.connection.UserCredentialsConnectionFactoryAdapter
property name=targetConnectionFactory
ref bean=cachingConnectionFactory /
/property
property name=username
value=${username}
/property
property name=password
value=${password}
/property
/bean
bean id=cachedConnectionFactory
class=org.springframework.jms.connection.CachingConnectionFactory
p:targetConnectionFactory-ref=queueConnectionFactory
p:reconnectOnException=true
p:sessionCacheSize=75 /
bean id=queueConnectionFactory
class=org.springframework.jndi.JndiObjectFactoryBean lazy-init=true
property name=jndiName
value=java:comp/env/jms/MQConnectionFactory /
/bean
--
View this message in context:
http://camel.465427.n5.nabble.com/Setting-a-requestTimeout-for-a-shared-Exclusive-reply-does-not-take-effect-for-multiple-concurrent-us-tp5733811p5733958.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Header and java.util.Date
Hi All, I want to set the value of an header to a java.util.Date with current value. How can I do in XML DSL? setHeader headerName=messageTime ...whichLanguage?which Value?/...whichLanguage? /setHeader My preference is for languages in camel-core if possible... Thanks!! Cristiano
inherit\extend camel context?
I have some boiler plate code that is needed in several camel context's, is there a way to inherit\extend from a parent camel context? If not, is there any other way to include boiler plate stuff, perhaps with aspects? I have something like this copied across many routes: onException exceptionjava.lang.Throwable/exception redeliveryPolicy redeliveryDelay=1000 maximumRedeliveries=1 / bean ref=exceptionToAlertConverter / to uri=direct:alerter / /onException route id=alerterRoute from uri=direct:alerter / transacted ref=propagationNotSupportedTransactionPolicy / to uri=someBroker://Alerter / /route -- View this message in context: http://camel.465427.n5.nabble.com/inherit-extend-camel-context-tp5733964.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Transactional test assertions timing issue
If you have to do it by yourself (as we have to do it some time), you could
do it in this way (template is an instance of Springs JDBCTemplate):
private void assertDatabaseCount(int count) throws InterruptedException {
long timeout = System.currentTimeMillis() + 1;
while (timeout System.currentTimeMillis()
template.queryForInt(SELECT COUNT(*) FROM FOO_TABLE) count) {
Thread.sleep(200);
}
assertEquals(count, statisticMock.size());
}
Best,
Christian Müller
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Tue, Jun 4, 2013 at 5:31 PM, Alex Sherwin alex.sher...@gmail.com wrote:
When unit (integration) testing a transacted route, such as (pseudo):
route
from uri=activemq:some queue/
transacted/
camel:process ref=someBeanProcessor/
/route
Where someBeanProcessor does some DB work and participates in a JTA
transaction with the JMS message on this route
The problem is, what is a reliable way to apply an assertion on the work
that someBeanProcessor has done in the DB? I've tried both of the
following:
1. Add to: uri=log:some.logger.success?level=DEBUG/, get a MockEndpoint
ref and use an expected message count of 1, and wait on
mock.assertIsSatisified()
2. Use a NotifyBuilder on the route and use whenComplete(1), and wait on
builder.matchesMockWaitTime()
Both have the same result, where my test code is told about the success
before the JTA transaction has finished comitting, so when the test thread
performs a SQL select, it is doing so too early since the JTA tx of the
route hasn't actually completed.
This scenario works OK if the end result is something like to
uri=activemq:out queue/ and I use a MockEndpoint on the JMS output URI,
which makes sense since it'd be waiting on the TX to commit here; but what
about routes where this isn't an option?
Do I just need to suck it up and use Thread.sleep(..) on the test thread?
Thanks,
--
Alexander Sherwin
Re: how to pass an XML string to the unmarshal in the route definition
You are looking for something like:
.process(new Processor() {
public void process(Exchange exchange) throws Exception {
Map map = exchange.getIn().getBody(Map.class);
String entry = (String) map.get(KEY);
MyJaxbObject object =
exchange.getContext().getTypeConverter().convertTo(MyJaxbObject.class,
entry);
exchange.getIn().setHeader(MY_UNMARSHALLED_XML, object);
}
})
Best,
Christian Müller
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Wed, Jun 5, 2013 at 3:27 PM, Vegi, Vamsi (MAN-Corporate-CON)
vamsi.v...@manheim.com wrote:
Willem
I am not trying to unmarshal the whole HashMap
I need to unmarshal only one of the item in the Hashmap
I do know the key,
So I am looking for something like below
from(INB_Q_URI)
.routeId(ROUTE_ID_INB_RID)
.log( START -)
.unmarshal(jaxb(${body.myHashMap.get(OBJ_FOR_UNMARSHAL)}))
-thanks
-Original Message-
From: Willem jiang [mailto:willem.ji...@gmail.com]
Sent: Tuesday, June 04, 2013 10:23 PM
To: users@camel.apache.org
Subject: Re: how to pass an XML string to the unmarshal in the route
definition
If you are using JAXB to do the unmarshal work, you need to define a
adapter in the map class[1], as JAXB doesn't support the map directly.
Once you finished your map class, you can set it into your JAXB data
format context and your route should work as expected.
[1]
http://javaevangelist.blogspot.com/2011/12/java-tip-of-day-generic-jaxb-map-v.html
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Wednesday, June 5, 2013 at 2:03 AM, Vegi, Vamsi (MAN-Corporate-CON)
wrote:
Hello
I have the exchange body as a hashmap
The hashmap has several key, value pairs, of which one needs to be
unmarshalled.
How can I pass that particular value (which is XML String) to the
unmarshal In the following route
from(INB_Q_URI)
.routeId(ROUTE_ID_INB_RID)
.log( START -)
.unmarshal(jaxb)
-thank you
Re: inherit\extend camel context?
Can you use the Java DSL? In this case, you can use inheritance... Best, Christian Müller - Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/foundation/ Apache Member: https://www.apache.org/foundation/members.html https://www.linkedin.com/pub/christian-mueller/11/551/642 On Thu, Jun 6, 2013 at 8:30 PM, javamonkey79 javamonke...@gmail.com wrote: I have some boiler plate code that is needed in several camel context's, is there a way to inherit\extend from a parent camel context? If not, is there any other way to include boiler plate stuff, perhaps with aspects? I have something like this copied across many routes: onException exceptionjava.lang.Throwable/exception redeliveryPolicy redeliveryDelay=1000 maximumRedeliveries=1 / bean ref=exceptionToAlertConverter / to uri=direct:alerter / /onException route id=alerterRoute from uri=direct:alerter / transacted ref=propagationNotSupportedTransactionPolicy / to uri=someBroker://Alerter / /route -- View this message in context: http://camel.465427.n5.nabble.com/inherit-extend-camel-context-tp5733964.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: inherit\extend camel context?
I can from a technical perspective, but from a time perspective I don't have time to go back and re-write it all in java dsl. Are there plans on adding this as a feature, I'm not seeing it in Jira? -- View this message in context: http://camel.465427.n5.nabble.com/inherit-extend-camel-context-tp5733964p5733972.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: unmarshal().xstream() not working
You are using Camel 2.11.0? Best, Christian Müller - Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/foundation/ Apache Member: https://www.apache.org/foundation/members.html https://www.linkedin.com/pub/christian-mueller/11/551/642 On Thu, Jun 6, 2013 at 5:42 PM, mchimirev mchimi...@gilt.com wrote: I'm trying to unmarshal an xml file with camel. File is created with xStream and simple model. When I change my route to: it reads the file and I get this output: But when I try to unmarshal the xml I get nothing, I don't even hit the breakpoint on this line: ---EXECUTABLE CODE-- -- View this message in context: http://camel.465427.n5.nabble.com/unmarshal-xstream-not-working-tp5733953.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: SSH using dynamic slip
No I did not have to go that far :) ... I introduced a bean that sets up the
command to be executed on the exchange body ( exchnage.getIn() and on
exchange.getOut). Luckily in my case, I did not have to chnage the to uri.
But I am sure, you can achieve a dynamic SSH to uri using bean's get
method. I have done similar one in another project for file to uri as
shown below.
e.g
to
uri=file:{{FILECOPY_OUTPUTDIR}}?fileName=${bean:fileCopyMapper.getFullPath}/
Technically I am not using the Slip but achieving the same output.
Hope this helps.
regards
--
View this message in context:
http://camel.465427.n5.nabble.com/SSH-using-dynamic-slip-tp5733752p5733965.html
Sent from the Camel - Users mailing list archive at Nabble.com.
