Re: [Dev] UUF based Gadget hot deployment

[Manuranga Perera]

>
> Ideally these custom gadgets should not go inside the portal component

+1


> rather placed as different UUF components.

I think the correct place is the deployment dir. and we should treat it as
an external artifact, just like a MSS service.

UUF based Gadget hot deployment

UUF is anyway hot deployed in dev mode, so I think it's not hard to do
this. But what is hot-deployment story for other artifacts eg: MSS ?

On Wed, Nov 2, 2016 at 6:05 AM, Udara Rathnayake  wrote:

> Hi All,
>
> We need to come up with the $subject for the new UUF based dashboard
> feature.
>
> All default gadgets will be packaged inside the portal component as
> fragments. This is enough for the current ESB/API analytics dashboards.
>
> Future we have to provision end-user's to upload their custom gadgets and
> create gadgets through the gadget generation wizard. Ideally these custom
> gadgets should not go inside the portal component, rather placed as
> different UUF components.
>
> We need to hot deploy these custom gadgets. Since we don't have similar
> support shall we add this to UUF roadmap?
>
> --
> Regards,
> UdaraR
>



-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] UUF based Gadget hot deployment

[Manuranga Perera]

Are we sure we want to dynamically add gadgets via UI ?

1) Have we verified that this is a real use-case from product team,
because  I don't believe it. Let's get the user-stories form the team.
2) Who are going to upload gadgets? Is it developers, then it has to be
done though developer tool, isn't it?
3) How are gadgets getting populated to other containers ?
4) How is the security handled ?
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev