Re: Will Camel play nice with WebSphere/WAS?

You haven't mentioned what components (http://camel.apache.org/components.html) you're using so it's hard to make a general claim, considering the large number of 3rd party frameworks and libraries that Camel integrates. Nevertheless Camel itself (camel-core) is compatible with WebSphere Applica

Re: Camel CXF Producer should allow setting of BindingOperationInfo

Hi Willem, Thanks for your response. The problem is this: The start of the route is a CXF endpoint, now this refers to a different WSDL. The first endpoint is responsible to only accept the request SOAP request. Now this first (entry of the route) endpoint may or may not process this request SOA

Will Camel play nice with WebSphere/WAS?

I know the post below is a little old, but I'm looking at the prospect of deploy my camel solution onto WebSphere Application Server 6.1. And I won't be able to run an instance locally during development. So I thought I'd try to get a general feel for if I am going to experience some serious hea

Re: is FTP2 asynchrounus?

I did notice the localWorkDirectory option and gave that some thought. But since I am dealing with medical data there HIPPA concerns and then I would have to factor in security concerns related to storing these files on a local directory. I think at this point I am will to pay the performance pe

Re: camel-cxf: exception when parsing cxf:schemaLocation element | 2.6-SNAPSHOT maven problem

sure. this is a condensed version of one of my tests http://pastebin.com/3u7q84ES this is the camel-config.xml file. http://pastebin.com/1UhDV7rw It is referenced from my JunitSpringConfig, which is a Spring JavaConfig @Configuration instance. I am using the latest snapshots of Camel 2.6-SN

Re: Connect with WebSphere MQ / Single Consumer allowed

Well... YES... Now i have an argument to convince my Project-Manager that the Migration from 2.2->2.5 is absolutely necessary... Once again: Thanx -- View this message in context: http://camel.465427.n5.nabble.com/Connect-with-WebSphere-MQ-Single-Consumer-allowed-tp3260184p3261804.html Se

Re: camel-cxf: exception when parsing cxf:schemaLocation element | 2.6-SNAPSHOT maven problem

Can I have a look at your Junit tests code? I just want to asked the same thing in the CXF mailing list. On 11/12/10 6:05 PM, Marco Zapletal wrote: Just something I wanted to add. The patch is working and when deploying my camel/cxf app to tomcat everything goes fine (the services are deployed

Re: Connect with WebSphere MQ / Single Consumer allowed

On Fri, Nov 12, 2010 at 10:56 AM, waterback wrote: > > Get your point... > > i'll try that, hopefully it works, because i read in other posts / forums > that exception listeners are not supported in j2ee-Servers (or at least in > WebSphere AS) > > Hopefully i'm not offensive saying that the Camel-

Re: camel-cxf: exception when parsing cxf:schemaLocation element | 2.6-SNAPSHOT maven problem

Just something I wanted to add. The patch is working and when deploying my camel/cxf app to tomcat everything goes fine (the services are deployed and the schemas are appropriately referenced). however, when running my Junit tests with CXF 2.6-SNAPSHOT and CXF 2.3.0, I am getting NPEs as descr

Re: Connect with WebSphere MQ / Single Consumer allowed

Get your point... i'll try that, hopefully it works, because i read in other posts / forums that exception listeners are not supported in j2ee-Servers (or at least in WebSphere AS) Hopefully i'm not offensive saying that the Camel-Point of view seems to be differing (with the same exception) wh

Re: Connect with WebSphere MQ / Single Consumer allowed

On Fri, Nov 12, 2010 at 10:22 AM, waterback wrote: > > > Claus Ibsen-2 wrote: >> >> Okay I checked the source >> > Thank you... > > Do you have any other idea then, how to control that the route that tries to > connect and is denied by WMQ > is either stopped right away or at least that i could se

Re: Connect with WebSphere MQ / Single Consumer allowed

Claus Ibsen-2 wrote: > > Okay I checked the source > Thank you... Do you have any other idea then, how to control that the route that tries to connect and is denied by WMQ is either stopped right away or at least that i could see that it is not really started, although it declares itself star

Re: Connect with WebSphere MQ / Single Consumer allowed

Okay I checked the source Some endpoints leverages the MultipleConsumersSupport interface which controls if you can have 2+ routes with the same from(xxx) endpoint. And the JMS endpoint only allows that for topics, because that's whats makes sense. And therefore the multipleConsumers option canno

Re: Connect with WebSphere MQ / Single Consumer allowed

Well i did: That's what it says... Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: ibmmq://queue:DEB.VSL.ZIFS.IN.ARE?cacheLevelName=CACHE_NONE&multipleConsumers=true&testConnectionOnStartup=true due to: There are 1 parameters that couldn't be set on the en

Re: Multicast inside splitter

I have created a ticket to look into this https://issues.apache.org/activemq/browse/CAMEL- On Fri, Nov 12, 2010 at 12:15 AM, SlavaC wrote: > > Hi everybody, > > Noticed that the same multicast can behave differently when inside a > splitter. > > Consider the route: > >     >       > >       >

Re: Connect with WebSphere MQ / Single Consumer allowed

On Fri, Nov 12, 2010 at 9:12 AM, waterback wrote: > > Hi Claus, > > maybe i didn't make myself clear enough... > The WMQ-Queue is rightfully configured for single-consumer only (this is > done in WebSphere MQ Message Broker), there should be only one consumer at > any time > > My Camel-App is

Re: Connect with WebSphere MQ / Single Consumer allowed

Hi Claus, maybe i didn't make myself clear enough... The WMQ-Queue is rightfully configured for single-consumer only (this is done in WebSphere MQ Message Broker), there should be only one consumer at any time My Camel-App is destined to be installed in a WebSphere-Cluster (with 2 servers).