Thinking about the problem in another way (and assuming request-reply on
topic not possible) - how best to mark an exchange as incomplete until
another JMS message has been received in another queue?
So I am thinking along the lines of having two routes:
Route (1) sending JMS messages to topic, a
Dear,
As per my opinion and need if consumer SMSC node is not up while amq starts
camel context then, AMQ should start and consumer will try reconnect till
it's up. By this we don't have to remain stuck to start application
manually. It should be done similar as producer does.
Thanks & Reg
FYI, I used the SOAP URL directly as I was getting few errors regarding http
component and binding OperationInfo so making a cxf end point to soap call
is redundant in xml.
--
View this message in context:
http://camel.465427.n5.nabble.com/Not-able-to-call-a-direct-http-soap-service-using-rest-
I just need to call a soap url using a rest service, it is quite urgent but
no success even after some reading and searching on web.
The rest service is just for calling soap service with getHelloWorldAsString
method.
I have followed many thread but no success, my soap service is running file
and
Hello,
To integrate SaxonEE into Camel
in Version 2.14.3 I used this workaround:
camel-saxon not installed
wrap:mvn:saxon/saxonee/9.5.1.8 (Saxon9ee.jar with valid license)
...
...
...
this worked fine.
Now I migrated to 2.16.1
and I receive the following error-message:
Could not find a suit
Try with #
See more here about # syntax
http://camel.apache.org/how-do-i-configure-endpoints.html
On Thu, Dec 31, 2015 at 4:03 PM, Thomas Freihalter
wrote:
> Hello,
>
> To integrate SaxonEE into Camel
> in Version 2.14.3 I used this workaround:
>
> camel-saxon not installed
> wrap:mvn:saxon/s
