Re: Ack by the end of WS chain (client WS - [WS - Camel - client WS] - WS) *image inside

2014-11-13 Thread chainbuck
For reference:

It looks like they call it: 
*
Camel CXF Proxy
*

You can use CXF to proxy a real web service.

I found some related threads: 
http://camel.apache.org/cxf-proxy-example.html
https://cwiki.apache.org/confluence/display/CAMEL/CXF+Proxy+Example
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.0/html/Security_Guide/files/CamelCXF-ProxyDemo.html
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html-single/Security_Guide/#CamelCXF-ProxyDemo
http://stackoverflow.com/questions/9644346/how-to-proxy-a-web-service-using-camel
https://developer.jboss.org/thread/246290





--
View this message in context: 
http://camel.465427.n5.nabble.com/Ack-by-the-end-of-WS-chain-client-WS-WS-Camel-client-WS-WS-image-inside-tp5758561p5759062.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: Ack by the end of WS chain (client WS - [WS - Camel - client WS] - WS) *image inside

2014-11-07 Thread chainbuck
Hi hekonsek,

Thank you for the answer. I'm glad to hear I can make it work!

-
Second step now: I need to know how.
-

I did a little bit of research and here is a way (using *Transaction
manager*) I think I could potentially get it done (not confirmed).

 
(in my case, /JMS queue/ and /JDBC/ can be substitute to /Endpoints/)
src:
http://shenghua77.wordpress.com/2012/03/13/an-example-in-camels-distributed-transaction-management/

I also got that piece of info:
As the TransactionErrorHandler also supports to let Camel do redeliveries
you can use both worlds. Letting Camel do some redeliveries and at the end
the backing transaction manager doing other redeliveries. In fact in the end
the transaction manager have the final word. That means if Camel cannot
process the exchange then its thrown back to the transaction manager that
will perform the rollback, and redelivery.

Anyone got an idea on this?



--
View this message in context: 
http://camel.465427.n5.nabble.com/Ack-by-the-end-of-WS-chain-client-WS-WS-Camel-client-WS-WS-image-inside-tp5758561p5758711.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: Ack by the end of WS chain (client WS - [WS - Camel - client WS] - WS) *image inside

2014-11-06 Thread chainbuck
Hi hekonsek,

Thank you for the answer. I'm glad to hear I can make it work!

-
Second step now: I need to know how.
-

I did a little bit of research and here is a way (using *Transaction
manager*) I think I could potentially get it done (not confirmed).

 
src:
http://shenghua77.wordpress.com/2012/03/13/an-example-in-camels-distributed-transaction-management/

I think we can abstract /JMS queue/ and /JDBC/ to simply /Endpoints/
I also got that piece of info:
As the TransactionErrorHandler also supports to let Camel do redeliveries
you can use both worlds. Letting Camel do some redeliveries and at the end
the backing transaction manager doing other redeliveries. In fact in the end
the transaction manager have the final word. That means if Camel cannot
process the exchange then its thrown back to the transaction manager that
will perform the rollback, and redelivery.

Anyone got an idea on this?



--
View this message in context: 
http://camel.465427.n5.nabble.com/Ack-by-the-end-of-WS-chain-client-WS-WS-Camel-client-WS-WS-image-inside-tp5758561p5758613.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: Ack by the end of WS chain (client WS - [WS - Camel - client WS] - WS) *image inside

2014-11-05 Thread Henryk Konsek
Hi,

> In other words, I'm wondering if the following is feasable:

Sending status code after endpoint call is common practice. Looks fair
for me :) .

Cheers.

-- 
Henryk Konsek
http://henryk-konsek.blogspot.com


Re: Ack by the end of WS chain (client WS - [WS - Camel - client WS] - WS) *image inside

2014-11-05 Thread chainbuck
In other words, I'm wondering if the following is feasable:
SYSTEM  CAMEL SYSTEM
   - data -> 
  - data ->
  <- ack -
   <- ack –

Here is what I don't want:
SYSTEM  CAMEL SYSTEM
- data -> 
<- ack -
  - data ->
  <- ack -




--
View this message in context: 
http://camel.465427.n5.nabble.com/Ack-by-the-end-of-WS-chain-client-WS-WS-Camel-client-WS-WS-image-inside-tp5758561p5758562.html
Sent from the Camel - Users mailing list archive at Nabble.com.