camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Bouska (JIRA)" <>
Subject [jira] [Commented] (CAMEL-9748) Create Openstack Component
Date Thu, 03 Nov 2016 15:32:59 GMT


Jan Bouska commented on CAMEL-9748:

[~ancosen] About testing - Mocking. I mock openstack client and all classes (from openstack4j
library) which my component uses. So I can test that the data are sent to library in correct
But I have another question. I tried to avoid forcing users to use openstack4j API. The reason
is retaining the possibility of changing the library in the future. I created my own API and
before I send data to library I have to map my API (camel openstack) to API of the library
(openstack4j) and vice versa. But it brings me a lot of troubles with mapping these APIs.

Today I have seen that for example camel-facebook component uses facebook4j API without any
Do you think that solving all these problems with mapping is worth it?

> Create Openstack Component
> --------------------------
>                 Key: CAMEL-9748
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Andrea Cosentino
>            Priority: Minor
>             Fix For: Future
> We can create a new big component related to Openstack by using

This message was sent by Atlassian JIRA

View raw message