On Wed, Dec 4, 2013 at 12:42 PM, Isuru Haththotuwa <[email protected]> wrote:
> On Wed, Dec 4, 2013 at 12:23 PM, Reka Thirunavukkarasu <[email protected]>
> wrote:
>>
>> +1 for the Rest API support for cartridge deployment. Since we can deploy
>> using the Rest API, are we going to get rid of the file based hot deployment
>> of the cartridges?
>
> In my opinion we should provide deployment through the Rest API only. So
> ideally we should remove file system based deployment.

Any particular reason on why this option should be removed? Also all
the other options such as update, undeployment, etc handled via REST?

> However, hot
> deployment should be available.
>>
>>
>> Thanks,
>> Reka
>>
>>
>> On Wed, Dec 4, 2013 at 12:17 PM, Lahiru Sandaruwan <[email protected]>
>> wrote:
>>>
>>> +1. Ultimately we should be able to view, edit, and deploy new cartridge
>>> definitions using UIs.
>>>
>>> Thanks.
>>>
>>>
>>> On Wed, Dec 4, 2013 at 12:08 PM, Isuru Haththotuwa <[email protected]>
>>> wrote:
>>>>
>>>> Hi Devs,
>>>>
>>>> The current Rest API supports operations such as tenant management,
>>>> listing available cartridges, subscribing, unsubscribing, etc. But still 
>>>> the
>>>> cartridge definition deployment happens through the file system. In my view
>>>> it is better if we can do this through the Rest API as well. WDYT?
>>>>
>>>> --
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> Software Engineer, WSO2 Inc.
>>>> +94 716 358 048
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Software Engineer,
>>> Platform Technologies,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: [email protected] cell: (+94) 773 325 954
>>> blog: http://lahiruwrites.blogspot.com/
>>> twitter: http://twitter.com/lahirus
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>
>>
>>
>> --
>> Reka Thirunavukkarasu
>> Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> Software Engineer, WSO2 Inc.
> +94 716 358 048
>
>

Reply via email to