[kapua-dev] Binding a Kapua service api to its implementation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[kapua-dev] Binding a Kapua service api to its implementation

From: "Morson, Stefano" <stefano.morson@xxxxxxxxxxxx>
Date: Tue, 20 Dec 2016 09:50:08 +0000
Accept-language: en-US
Delivered-to: kapua-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/kapua-dev>
List-help: <mailto:kapua-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/kapua-dev>, <mailto:kapua-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/kapua-dev>, <mailto:kapua-dev-request@eclipse.org?subject=unsubscribe>
Thread-index: AQHSWqUMuSSP6zLVnEqtfkP8bMUtLQ==
Thread-topic: Binding a Kapua service api to its implementation

Hi all,

after the merge of PR #149, "Enable dependency injection for Kapua services", there are few simple changes in the way a Kapua service api is bound to its implementation.

For anyone interested in this topic I spent some time to describe this in github issue #94.

Thanks,

Stefano

Stefano Morson | EUROTECH | tel.: +39 0433 485411

Prev by Date: [kapua-dev] Project documentation
Next by Date: Re: [kapua-dev] Project documentation
Previous by thread: [kapua-dev] Project documentation
Next by thread: [kapua-dev] failing on installing Kapua
Index(es):
- Date
- Thread

Breadcrumbs