Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
MIME-Version: 1.0
Reply-To: david@davidkarlsen.com
In-Reply-To: 
 <CAGO7Ob3hJtSSJ2CLvnB8Adc-py+ZKK743OJMtM-AOpW6mSwojQ@mail.gmail.com>
References: 
 <CAGO7Ob3hJtSSJ2CLvnB8Adc-py+ZKK743OJMtM-AOpW6mSwojQ@mail.gmail.com>
Date: Fri, 2 Oct 2015 20:02:04 +0200
Message-ID: 
 <CAGO7Ob16uC3QNzxzTEECPT-Rc1Y=KsPDHa_Okiu7uA_XKJpu_A@mail.gmail.com>
Subject: Fwd: Camel WXS component
From: David Karlsen <davidkarlsen@gmail.com>
To: dev@camel.apache.org
Content-Type: multipart/alternative; boundary=047d7bf198ba0bc793052122f649

--047d7bf198ba0bc793052122f649
Content-Type: text/plain; charset=UTF-8

Trying again since the last attempt did not get through...

---------- Forwarded message ----------
From: David Karlsen <davidkarlsen@gmail.com>
Date: 2015-09-29 15:39 GMT+02:00
Subject: Camel WXS component
To: dev@camel.apache.org


I got a bit inspired by the contribution of a camel cics component to camel
extras here the other day, so I whipped up a camel-wxs component:
https://github.com/davidkarlsen/camel-extra/tree/camel-wxs .
Would you care to give feedback (coding style, test approach, naming etc
etc)?

WXS is an elastic caching/grid solution from IBM:
http://www-01.ibm.com/support/knowledgecenter/SSTVLU_8.6.0/
Currently it only contains an implementation
of ExchangeIdempotentRepository .
I thought of extending it in case a generic camel-cache component came to
existence:
http://camel.465427.n5.nabble.com/An-idea-of-new-camel-cache-endpoint-td5753363.html

The tests are currently based on mocks as it would be hard to [legally]
provide integration-tests running on the proper software from IBM as it's
commercial.

What are your thoughts?

-- 
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen


-- 
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

--047d7bf198ba0bc793052122f649--