Are we registering the service manually or are we going to use the SPIfly
to achieve the same purpose?
Thanks
Thusitha
On Mon, Aug 21, 2017 at 10:00 PM, Abimaran Kugathasan
wrote:
> Hi Asanka,
>
> As I checked offline with Niranjan, this SPI service introduced in C5. I'm
> checking on this furt
Hi Asanka,
As I checked offline with Niranjan, this SPI service introduced in C5. I'm
checking on this further.
On Mon, Aug 21, 2017 at 11:03 AM, Asanka Abeyweera
wrote:
> Hi Abimaran and all,
>
> Is the requirement to expose as SPI service something introduced in
> Carbon 5? I am curious on ho
Hi Abimaran and all,
Is the requirement to expose as SPI service something introduced in Carbon
5? I am curious on how it worked with APIM 2.1.0. Can't we do the same
thing?
On Mon, Aug 21, 2017 at 10:48 AM, Abimaran Kugathasan
wrote:
> Hi,
>
> We are embedding Message Broker feature into API M
+Thusitha, +Jayanga
On Mon, Aug 21, 2017 at 10:48 AM, Abimaran Kugathasan
wrote:
> Hi,
>
> We are embedding Message Broker feature into API Manager 3.0 core, now API
> Manager will function as both MB server and client to manage its artifacts
> such as API, application, subscription, throttling
Hi,
We are embedding Message Broker feature into API Manager 3.0 core, now API
Manager will function as both MB server and client to manage its artifacts
such as API, application, subscription, throttling etc between its nodes
and Gateway. andes-client [1] will function as JMS client for embedded