On Tue, Sep 27, 2016 at 3:40 PM, Chandana Napagoda
wrote:
> Hi All,
>
> While analyzing store requirements of C5 based products(IoT, APIM), we
> have few areas to be clarified. Based on the current understanding, C5
> based store will not be bound into existing governance aspects. This should
> b
Hi all,
In case If we are going for generic store framework, framework should
capable of retrieving asset metadata from any source (since asset metadata
is maintained differently by each product) by extending metadata retrieval
logic for each asset type.
and for assets searching, I think searching
Do we really need a Store Framework for C5? Rather, isn't it a UI framework
(UUF) we need to build UIs? Apart from API-M and IoTS, are there any other
products which need a Store?
Even if we come up with a Store Framework, I think the facilities it
provides will be minimal isn't it? Since the prod
On Tue, Sep 27, 2016 at 6:14 PM, Nuwan Dias wrote:
> Do we really need a Store Framework for C5?
>
May be store framework is a wrong terminology, but there should be a
reusable store component written by using UUF.
> Rather, isn't it a UI framework (UUF) we need to build UIs? Apart from
> AP
On Tue, Sep 27, 2016 at 6:31 PM, Selvaratnam Uthaiyashankar <
shan...@wso2.com> wrote:
>
> On Tue, Sep 27, 2016 at 6:14 PM, Nuwan Dias wrote:
>
>> Do we really need a Store Framework for C5?
>>
>
>
> May be store framework is a wrong terminology, but there should be a
> reusable store component w
On Tue, Sep 27, 2016 at 6:47 PM, Nuwan Dias wrote:
>
>
> On Tue, Sep 27, 2016 at 6:31 PM, Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>>
>> On Tue, Sep 27, 2016 at 6:14 PM, Nuwan Dias wrote:
>>
>>> Do we really need a Store Framework for C5?
>>>
>>
>>
>> May be store framework is a
Hi All,
Creating a reusable Store component was one of goals we had in our minds at
UUF initial discussions. At that time there was couple of products APIM,
AppM, EMM mobile store, GReg etc. that need a Store UI. So developing a
generalized Store component was a requirement. However with the new p
Hi,
As per my understanding, within WSO2 products there should be some set of
components which are providing generalized and shared features to products
including searching, basic listing, login UI, etc. Otherwise most of the
product team have to duplicate their effort. Ex: IS portal, IoT, and API
On Wed, Sep 28, 2016 at 10:06 AM, Chandana Napagoda
wrote:
> Hi,
>
> As per my understanding, within WSO2 products there should be some set of
> components which are providing generalized and shared features to products
> including searching, basic listing, login UI, etc. Otherwise most of the
>
>
> On Wed, Sep 28, 2016 at 10:06 AM, Chandana Napagoda
> wrote:
> I believe that we should identify commonly used components and implement
> them in a generalized manner. So relevant product team can extend those
> components based on their requirements.
Agreed, this is the mitivation/goal of
If we are not storing trivial artifacts, it is very difficult to use a
common UI for store and especially for publisher. If a store framework is
used, we end up extending it and in many situations it can become more
complex than developing a new UI. Therefore, I agree with Nuwan and
SajithAR that w
On Wed, Sep 28, 2016 at 3:27 PM, Chathura Ekanayake
wrote:
> If we are not storing trivial artifacts, it is very difficult to use a
> common UI for store and especially for publisher. If a store framework is
> used, we end up extending it and in many situations it can become more
> complex than d
12 matches
Mail list logo