Re: SOAP 1.2 and cxf end point

Hello, If using xml try specifying the version for soap binding or incase of annotations try specifying it as below @SOAPBinding(style = Style.DOCUMENT) Regards, -Yogesh -- View this message in context: http://camel.465427.n5.nabble.com/SOAP-1-2-and-cxf-end-point-tp5771070p5784906.html Sent

Re: SOAP 1.2 and cxf end point

Hi I am facing the same issue now, anybody else able to resolve this? Please share your experience it would be helpful Cheers Sunesh -- View this message in context: http://camel.465427.n5.nabble.com/SOAP-1-2-and-cxf-end-point-tp5771070p5784902.html Sent from the Camel - Users mailing list

Re: CXF component doesn't propagate SOAPAction header

Solved, specify soap version 1.2 do the job. I added the following line to the cxfEndpoint: Regards Alberto On Wed, 2016-07-06 at 10:52 +0200, Alberto wrote: > Hello, > > I'm using the cxf component as producer in dispatch mode as specify > in  > http://camel.apache.org/cxf.htm

Re: Is it possible to make a message header or property immutable?

Hi, It's just an idea off the top of my head, but what about providing a parity check header in company with the header you want to be immutable. I.e. YOUR_HEADER = "Do not change!" YOUR_HEADER_MD5 = "fef4de21954d4b9f1b3e61ed153799da" or YOUR_HEADER_HASH = "md5:fef4de21954d4b9f1b3e61ed153799da"

Re: Camel deployment for micro service

I don't have a lot of insight as I do use Karaf/blueprint but since you ran into problems I'd wanted to know if they were related to akka. That's the sort of thing I would like to know about myself so I don't run into such problems. It appears from the links you sent that the problems have been s

Re: Is it possible to make a message header or property immutable?

I have plenty of endpoints based on POST/PUT where the message body already contains important information, so I've been using headers or properties to add information without needing to make the body itself a map or some other wrapper. If this isn't the proper way to use camel, then I'd like to he

Re: Camel deployment for micro service

Hi Brad It was for another project, not this one, with many components. And It was a mess with spring (the old version) kafka driver osgi bundle was only available for scala 2.10... it was really sticky and causing a lot of friction. We moved to Wildfly and almost all the friction blew away. It wa

Re: Camel deployment for micro service

I'm curious were the dependencies issues in Karaf related to Akka? Were you using ServiceMix/Fuse or just raw karaf? On Wed, Jul 6, 2016 at 10:25 AM, José Luis Pedrosa wrote: > Hi All! > > We are considering start the implementation of micro services based on > apache camel and akka, > > Initia

Camel deployment for micro service

Hi All! We are considering start the implementation of micro services based on apache camel and akka, Initially we were thinking on HTTP for sync and Kafka for async, and dev team is really asking to start working with akka, so there's also an camel-akka component that looks nice. I was thinkin

Re: Is it possible to make a message header or property immutable?

But if you are using CXFRS then you can make the databean itself contain what I'll call initializable data. This isn't a bad example but you get the idea. public void setFirstName(String firstName) { if(this.firstName==null) this.firstName=firstName; //Maybe throw an exception if it is already

Re: Java DSL with FUSE ESB

Hello, Yes off course, but if you just want to test the fuse deploy in the simplest possible way then I think a file in a folder would be ok. Off course all of this depends on how the deploy/build process for an environment is setup. Best Souciance On Wed, Jul 6, 2016 at 2:01 PM, Morgan.Hautman

Re: Java DSL with FUSE ESB

Hi souciance, The deploy folder in Apache Karaf is kind of not the ideal wat of doing it.. The best thing is to deploy it through the Karaf shell with mvn:../../.. for example. Regards, Morgan 2016-07-06 13:55 GMT+02:00 souciance : > I think if you just want to test it locally in your developme

Re: Java DSL with FUSE ESB

I think if you just want to test it locally in your development machine it works the same as Karaf. Just take your bundle (jar that you built) and put in the deploy folder. It should pick up the bundle automatically. On Wed, Jul 6, 2016 at 1:53 PM, Claus Ibsen-2 [via Camel] < ml-node+s465427n57848

Re: Java DSL with FUSE ESB

Just create a blueprint xml file with a and refer to the java route builders as you can do with spring also. See more details at using Java code at: http://camel.apache.org/spring.html On Wed, Jul 6, 2016 at 1:44 PM, Thomas Hehl wrote: > I finally have my Java DSL route working under camel the

Java DSL with FUSE ESB

I finally have my Java DSL route working under camel the way that I want as a standalone app. Now I want to deploy this to JBoss FUSE ESB. How do I do this with a DSL app?

Re: Problem with JT400 DataQueue

I logged a ticket about the missing call to configureConsumer https://issues.apache.org/jira/browse/CAMEL-10128 On Wed, Jul 6, 2016 at 12:34 PM, Claus Ibsen wrote: > Hi > > You should ask the vendor of JBoss Fuse, eg Red Hat. > You can get in touch with them using the customer portal, and log a t

Re: Update camel-smpp dependency on jsmpp to 2.2.1

On 11/05/16 17:51, Bari Rid wrote: > jsmpp version 2.2.0 contains a correction concerning responding correctly to > failed DeliverSM as can be seen here: > https://github.com/opentelecoms-org/jsmpp/commit/575eec44ebf51077870d45385392e30a29c6dfe3 > > The change is made particularly in the file S

SMS Router, a fully functional example with camel-smpp

Hi all, I've recently released the source code for SMS Router[1], which provides a fully functional example of using camel-smpp[2] and a blog[3] discussing SMS Router and Camel. I've created various projects similar to this for various employers, most of them have required more complicated func

Re: Problem with JT400 DataQueue

Hi You should ask the vendor of JBoss Fuse, eg Red Hat. You can get in touch with them using the customer portal, and log a ticket. On Wed, Jul 6, 2016 at 12:23 PM, stijnkoopal wrote: > Hi, > > Currently we are upgrading our environment from Fuse 6.1 to Fuse 6.2. We are > using camel-jt400 to co

Problem with JT400 DataQueue

Hi, Currently we are upgrading our environment from Fuse 6.1 to Fuse 6.2. We are using camel-jt400 to communicate to an IBM AS/400 mainframe. Currently we are having trouble to read from a data queue on the AS/400, and I think the problem is camel related. In Fuse 6.1 we use camel-jt400-2.12.0-r

Re: Error occurred during starting Camel because of cannot look up a processor from registry

No it is not working. I think the issue is not because of the separate xml files. It is because jsonRPCProcessor is using myTemplate and myTemplate is defined in camelContext and camelContext is using jsonRPCProcessor in routes. On Wed, Jul 6, 2016 at 2:16 PM, Tadayoshi Sato wrote: > No, in the

CXF component doesn't propagate SOAPAction header

Hello, I'm using the cxf component as producer in dispatch mode as specify in  http://camel.apache.org/cxf.html. The endpoint: http://hostname/servi ce/soap">; The relevant part of the route:     .setHeader(SoapBindingCon

Re: Error occurred during starting Camel because of cannot look up a processor from registry

No, in the same camelContext.xml file but outside of . Doesn't that work for you? On Wed, Jul 6, 2016 at 5:34 PM, Debraj Manna wrote: > Are you saying to define jsonRPCProcessor inside camelContext. Something > like below:- > > http://camel.apache.org/schema/blueprint"; > useMDCLogging=

Re: Error occurred during starting Camel because of cannot look up a processor from registry

Are you saying to define jsonRPCProcessor inside camelContext. Something like below:- http://camel.apache.org/schema/blueprint"; useMDCLogging="true"> ** *...* ** http://0.0.0.0:/orchestratorservice"; />

Re: Unit test case for XML DSL context and routes

In the CamelTestSupport you can do like this: @Override protected String getBundleFilter() { // don't want the normal bundle to start as it causes conflict to our test return "(!(Bundle-SymbolicName=))"; } @Override protected String getBlueprintDescriptor() { return "blueprint/fake_blueprint.xml";