On Thu, Mar 28, 2013 at 11:16 AM, Sumedha Rubasinghe <[email protected]>wrote:

> There are cases where some customers want to manually take control of
> publishing process.
>

The customer can be guided through this using a wizard.


>
>
> On Thu, Mar 28, 2013 at 11:06 AM, Afkham Azeez <[email protected]> wrote:
>
>> Is there any specific reason for an API not to be published soon after it
>> is created? Isn't it the case that most of the time the publisher would
>> want to publish the API as soon as he has created it?
>>
>> If that is the case, after the user clicks the "Create" button, it will
>> be nice to see a message such as "The API has been created. Do you want to
>> publish it? (y/n)".
>>
>> I am raising this because several times, I created APIs, and then went to
>> the store only to realize that it is not listed because I forgot to
>> navigate to "Lifecycle -> Publish".
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * <http://www.apache.org/>**
>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919
>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* <http://www.apache.org/>**
email: **[email protected]* <[email protected]>* cell: +94 77 3320919
blog: **http://blog.afkham.org* <http://blog.afkham.org>*
twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to