Re: [Dev] [PRODUCT_EI] Class Loading issue with latest andes client

[Nandika Jayawardana]

Adding DEV

Nandika

On Fri, Mar 31, 2017 at 9:51 PM, Vijitha Ekanayake 
wrote:

> Hi All,
>
> We Observe class loading issue with latest andes client (3.2.4) in MSMP
> scenarios. The issue occurs while consuming message from the message store
> where it continuously prints message[1]. I change the code a bit and got
> exact stack trace [2].It seems to be OSGI issue and this issue isn't there
> if we use previous andes client version(3.1.4).
>
> Did anyone come across this kind of OSGI issue before?
>
>
> [1].
>
> [2017-03-31 20:57:01,076] [EI-Core] ERROR - JmsConsumer [
> PaymentRequestJMSMessageStore-C-1] cannot receive message from store.
> Error:Could not deserialize message: java.lang.ClassNotFoundException:
> org.apache.synapse.message.store.impl.commons.StorableMessage cannot be
> found by andes_client_3.2.4_1.0.0
>
> [2].
> javax.jms.MessageFormatException: Could not deserialize message:
> java.lang.ClassNotFoundException: org.apache.synapse.message.
> store.impl.commons.StorableMessage cannot be found by
> andes_client_3.2.4_1.0.0
> at org.wso2.andes.client.message.JMSObjectMessage.getObject(
> JMSObjectMessage.java:154)
> at org.apache.synapse.message.store.impl.jms.JmsConsumer.
> receive(JmsConsumer.java:99)
> at org.apache.synapse.message.processor.impl.sampler.
> SamplingService.fetch(SamplingService.java:188)
> at org.apache.synapse.message.processor.impl.sampler.
> SamplingService.execute(SamplingService.java:120)
> at org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(
> NTaskAdapter.java:98)
> at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.
> execute(TaskQuartzJobAdapter.java:67)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException: org.apache.synapse.message.
> store.impl.commons.StorableMessage cannot be found by
> andes_client_3.2.4_1.0.0
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(
> BundleLoader.java:501)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(
> BundleLoader.java:421)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(
> BundleLoader.java:412)
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(
> DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at org.wso2.andes.client.util.ClassLoadingAwareObjectInputStream.load(
> ClassLoadingAwareObjectInputStream.java:64)
> at org.wso2.andes.client.util.ClassLoadingAwareObjectInputSt
> ream.resolveClass(ClassLoadingAwareObjectInputStream.java:38)
> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1613)
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1518)
> at java.io.ObjectInputStream.readOrdinaryObject(
> ObjectInputStream.java:1774)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
> at org.wso2.andes.client.message.JMSObjectMessage.getObject(
> JMSObjectMessage.java:143)
>
>
> Thanks.
>
> --
> Vijitha Ekanayake
> Software Engineer*, *WSO2, Inc.; http://wso2.com/
> Mobile : +94 777 24 73 39 | +94 718 74 44 08
> lean.enterprise.middleware
>



-- 
Nandika Jayawardana
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MSF4J] Interceptor#preCall method stopped serving HTTP GET randomly.

[Abimaran Kugathasan]

Hi All,

RESTAPISecurityInterceptor is used to bypass the authentication for swagger
json via /api/am/admin/v1/policies/swagger.json. There should be a
microservice registered in /api/am/admin/v1/policies, but there weren't. So
this issue occurred.

Any MSF4J interception will be invoked if there are matching path
registered in the MSF4J registry.

On Wed, Mar 29, 2017 at 12:09 PM, Abimaran Kugathasan 
wrote:

> Hi Thusitha,
>
>
> On Wed, Mar 29, 2017 at 12:04 PM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Abimaran,
>>
>> In API Manager 3.0, We have RESTAPISecurityInterceptor which implements
>>> org.wso2.msf4j.Interceptor.
>>> When I send HTTP Get request, I'm getting 405, for HTTP POST and PUT it
>>> works correctly.
>>> I debugged MSF4JMessageProcessor, there is a method named
>>> 'receive(CarbonMessage carbonMessage, CarbonCallback carbonCallback)' which
>>> haven't hit when I send GET.
>>
>> This is the entry point for MSF4J. If that doesn't get hit, it implies
>> due to some reason the http message doesn't reach to MSF4J side through the
>> transport. But that is strange. COuold you please verify that?
>>
>
> I'm getting 405 for GET, who is responding with 405? How can I verify? I
> thought MSF4J uses carbon-transport as underlying framework for HTTP
> transport.
>
>
>
>>
>> Thanks
>> Thusitha
>>
>> On Wed, Mar 29, 2017 at 12:01 PM, Abimaran Kugathasan 
>> wrote:
>>
>>> Hi Dev,
>>>
>>> In API Manager 3.0, We have RESTAPISecurityInterceptor which implements
>>> org.wso2.msf4j.Interceptor.
>>>
>>> When I send HTTP Get request, I'm getting 405, for HTTP POST and PUT it
>>> works correctly.
>>>
>>> I debugged MSF4JMessageProcessor, there is a method named
>>> 'receive(CarbonMessage carbonMessage, CarbonCallback carbonCallback)' which
>>> haven't hit when I send GET.
>>>
>>> Which component calls this method? Also is there any configuration to
>>> decide which HTTP verb should be served?
>>>
>>> Appreciate your responses.
>>>
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer - API Technologies
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820 <+94%2077%20392%202820>
>>>
>>> 
>>> 
>>>   
>>> 
>>>
>>>
>>
>>
>> --
>> Thusitha Dayaratne
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> Mobile  +94712756809 <+94%2071%20275%206809>
>> Blog  alokayasoya.blogspot.com
>> Abouthttp://about.me/thusithathilina
>> 
>>
>>
>
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer - API Technologies
>
> Email : abima...@wso2.com
> Mobile : +94 773922820 <+94%2077%20392%202820>
>
> 
> 
>   
> 
>
>


-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer - API Technologies

Email : abima...@wso2.com
Mobile : +94 773922820


  
  
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] More Information about GSOC Project Environments Support for WSO2 API Manager

[ridmal madushanka]

Hi ,

I would like to work on Environments support for WSO2 Api manager gsoc
project. I locally configure the Api manager and it worked fine. I would
like to know more information about this project and What are the changes
need to be done base on environment?



Thank You.

Ridmal Madushanka,

Undergraduate of Faculty of Information Technology,

Moratuwa University,

Sri Lanka.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Introducing myself to mentors for GSOC Project CLI tool for WSO2 API Manager

[Vinujan Shangarapillai]

Hi Pubudu,

Yeah that is a good idea. It will give users more flexibility. In some
cases users may forget some parameters ( 7 +- chunk memory  property ) ,
this solution will help for those scenarios. I am thinking to implement
both flag and query method. Thank you for the idea.

Do i am thinking to implement security measures such as encryption or
hashing when storing application configurations and credentials? What ia
your opinion on this ?.

Regards,
Vinujan.S

On Fri, 31 Mar 2017, 6:31 p.m. Pubudu Gunatilaka,  wrote:

> HI Vinujan,
>
> IMHO, we should have the capability to support the both scenarios. Maybe
> the initial version we can stick with option 2. But it would be better if
> we can have both scenarios.
>
> Also, we need to consider the environment when logging. Environments could
> be Dev, QA, Prod, Cloud, etc. CLI tool should be able to work with
> different environments.
>
> Thank you!
>
> On Fri, Mar 31, 2017 at 6:03 PM, Vinujan Shangarapillai <
> vinujan...@cse.mrt.ac.lk> wrote:
>
> Hi pubudu,
>
> What is expected/suitable for for this scenario
>
> 1. APIManager login -u admin -p admin
> Or
> 2. APIManager login
> > username:
> >password:
>
> Most command tool application uses flags instead of querying parameters
> one by one. What is suitable for this application.
>
> Regards,
> Vinujan.S
>
> On Fri, 31 Mar 2017, 4:59 p.m. Vinujan Shangarapillai, <
> vinujan...@cse.mrt.ac.lk> wrote:
>
> Thank you for the reply. I am looking into it.
>
> On Fri, 31 Mar 2017, 4:25 p.m. Pubudu Gunatilaka, 
> wrote:
>
> Hi Vinujan,
>
> Yes, it is. The user needs to have an access token to invoke a subscribed
> API. You can read more about token API in [1].
>
> [1] - https://docs.wso2.com/display/AM210/Token+API
>
> Thank you!
>
> On Fri, Mar 31, 2017 at 3:58 PM, Vinujan Shangarapillai <
> vinujan...@cse.mrt.ac.lk> wrote:
>
> Hi pubudu!
>
> I have implemented login and exporting api functionality for the cli
> prototype. Currently I am working on proposal. What is meant by "Key
> generation" in proposal document ?, is it retrieving access token for
> subscriber after subscribing for an api?
>
> best regards,
> Vinujan.S
>
> On 6 March 2017 at 22:32, Vinujan Shangarapillai  > wrote:
>
> Hi pubudu!
>
> Thank you for your information. I will contact here if there any issues.
>
> Reagards,
> Vinujan.s
>
> On Mon, 6 Mar 2017, 10:38 a.m. Pubudu Gunatilaka, 
> wrote:
>
> Hi Vinujan,
>
> Thank you for your interest and you can call us by name.
>
> As described in the project description you need to develop a CLI tool for
> API Manager. First of all, you can check WSO2 API Manager 2.1.0 and get
> familiar with the product [1] and the concepts [2]. Additionally, you can
> try out API export/import feature [3] and the API Manager 2.1.0 REST APIs
> [4] to tryout the product.
>
> Currently, WSO2 API Manager team is working on Carbon 5(C5) based API
> Manager implementation and you can find the relevant repos in [5] and [6].
> When you are developing the CLI, you should use the C5 REST APIs. API
> Manager team has already added most important REST APIs and we are working
> on adding new REST APIs based on the functionalities.
>
> If you need any help when trying the product, please do send an email to
> the WSO2 developers' mailing list. You can also use this mailing list to
> communicate further about the project.
>
> [1] - http://wso2.com/products/api-manager/
> [2] - https://docs.wso2.com/display/AM210/Key+Concepts
> [3] -
> https://docs.wso2.com/display/AM210/Migrating+the+APIs+to+a+Different+Environment
> [4] - https://docs.wso2.com/display/AM210/WSO2+APIs
> [5] - https://github.com/wso2/carbon-apimgt/tree/C5
> [6] - https://github.com/wso2/product-apim/tree/C5
>
> Thank you!
>
> On Mon, Mar 6, 2017 at 12:24 AM, Vinujan Shangarapillai <
> vinujan...@cse.mrt.ac.lk> wrote:
>
> Dear sir!
>
> I am vinujan, currently studying in 4th year computer science and
> engineering, University of Moratuwa.
>
> I am interested in developing command line tool for WSO2 API manager. I
> have tried implementing login, exporting and importing api. Here
>  is the link for the
> repository. further I want to clarify the requirements for this
> application.
>
> regards,
> Vinujan Shangarapillai
> *Undergraduate*
> Computer Science And Engineering
> University of Moratuwa
> m: 0771224344
> e: vinujan...@cse.mrt.ac.lk
> 
>
>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
>
>
> --
> Vinujan Shangarapillai
> *Undergraduate*
> Computer Science And Engineering
> University of Moratuwa
> m: 0771224344
> e: vinujan...@cse.mrt.ac.lk
>    
>
>
>
>
>
> --
> *Pubudu 

Re: [Dev] Display only Production Services in Governance Registry Store

[Ayesha Dissanayaka]

Hi Denson,

Yes, you can achieve this via the extension model[1] in GREG-5.3.0.
You can find a sample on how to do so in this blogpost

.

Regards.
-Ayesha

[1]
http://asadistechspace.blogspot.com/2016/05/wso2greg-510-store-extension-model.html#.WN57kEF97Tc
[2]
http://asadistechspace.blogspot.com/2017/03/wso2greg-530-enable-visibility-of.html#.WN6CG0cvDTc


On Thu, Mar 30, 2017 at 10:40 PM, Denson, Ed  wrote:

> Hello All,
>
>
>
> We are running GREG 5.3.0 and I am wondering if there is a way to limit
> the display of Services (REST/SOAP) to only those is a lifecycle state of
> Production to be displayed in the Store. I want to allow the developers to
> update their services using the Publisher, but not have it readily
> available to the general public until it reaches the Production state.
>
>
>
> Is there a configuration file or files that would allow this functionality
> to happen?
>
>
>
> Thanks,
>
> *Ed Denson* | IT Information & Integration | API Management
> *Pacific Gas and Electric Company* | Office 8.415.6485 or 925.415.6485
> <(925)%20415-6485> | Cell 408.316.5315 <(408)%20316-5315>
> Email ed.den...@pge.com
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ayesha Dissanayaka*
Senior Software Engineer,
WSO2, Inc : http://wso2.com

20, Palm grove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC 2017] Proposal 4: Idea Plugin for Siddhi

[Menuka Warushavithana]

Hi Tishan,
Recently I got to know that I will not be allowed to do the GSoC project
(Idea Plugin for Siddhi) and participate in the WSO2 internship at the same
time. Since I've been meaning to apply for the WSO2 internship for quite
some time now, I will not be submitting the final proposal for the GSoC
project. I would've preferred if I could do both. However, as I am forced
to choose one of the two, I will drop out of the GSoC project. Thank you
for all your support.

Regards
Menuka

On 29 March 2017 at 22:53, Menuka Warushavithana 
wrote:

> Thank you very much. I'll improve it accordingly.
>
> On 29 March 2017 at 22:43, Tishan Dahanayakage  wrote:
>
>> Feedback provided. Please check
>>
>> /Tishan
>>
>> On Tue, Mar 28, 2017 at 10:26 AM, Tishan Dahanayakage 
>> wrote:
>>
>>> Thanks for the update Menuka. Will review and provide feedback.
>>>
>>> Thanks
>>> /Tishan
>>>
>>> On Mon, Mar 27, 2017 at 6:47 PM, Menuka Warushavithana <
>>> menuka...@cse.mrt.ac.lk> wrote:
>>>
 Hi Tishan,
 I have shared my proposal draft on the official GSoC site. I kindly
 request your feedback on improving it.

 Thank you

 On 27 March 2017 at 15:53, Menuka Warushavithana <
 menuka...@cse.mrt.ac.lk> wrote:

> Hi Tishan,
> I have shared my proposal draft on the official GSoC site. I kindly
> request your feedback on improving it.
>
> Thank you
> Menuka
>
> On 27 March 2017 at 13:01, Menuka Warushavithana <
> menuka...@cse.mrt.ac.lk> wrote:
>
>> Hi Tishan,
>>
>> I used ANTLR 4.6 on the file [1] to generate the Lexers and Parsers.
>> Then I took the sample plugin provided by ANTLR creators [2] along with 
>> the
>> Jetbrains plugin adapters provided by ANTLR mentioned here [3]. (Of 
>> course,
>> I found these resources thanks to the conversations in the dev mailing
>> list). I forked the sample plugin on GitHub and changed the code to work
>> with SiddhiQL.g4.
>> My fork can be accessed through [4].
>>
>> There were some dependency issues with the Sample Plugin because it
>> had used ANTLR 4.5.1 and the version I used for generation of Lexers and
>> Parsers was the latest (ANTLR 4.6). I couldn't entirely fix the 
>> dependency
>> issues. However, the plugin works with syntax highlighting for the most
>> part.. I'm working on implementing a basic code completion functionality.
>> Now I have a base level understanding of how ANTLR generates the classes.
>>
>> And by the way, I will share my draft proposal with you later today.
>>
>> Thank You
>>
>> [1] https://github.com/wso2/siddhi/blob/master/modules/siddh
>> i-query-compiler/src/main/antlr4/org/wso2/siddhi/query/compi
>> ler/SiddhiQL.g4
>> [2] https://github.com/antlr/jetbrains-plugin-sample
>> [3] https://github.com/antlr/jetbrains
>> [4] https://github.com/menuka94/jetbrains-plugin-sample
>>
>>
>>
>> On 27 March 2017 at 11:24, Tishan Dahanayakage 
>> wrote:
>>
>>> Hi Menuka,
>>>
>>> Great progress Menuka. Can you please explain how did you achieve
>>> this and resources used.
>>> How can we try this plugin? Can you please provide the required
>>> resources?
>>>
>>> Thanks,
>>> /Tishan
>>>
>>> On Mon, Mar 27, 2017 at 12:42 AM, Menuka Warushavithana <
>>> menuka...@cse.mrt.ac.lk> wrote:
>>>
 Hi Tishan,
 I was able to implement a simple syntax highlighting plugin for
 Siddhi queries with the help of [1] and Antlr. (A screenshot is 
 attached
 herewith)

 ​
 I set up the WSO2 CEP locally and started studying Siddhi in more
 detail.
 Also, I have started drafting a proposal for the project. Your
 advice and constructive criticism on this idea is greatly appreciated.

 [1] https://github.com/wso2/siddhi/blob/master/modules/siddh
 i-query-compiler/src/main/antlr4/org/wso2/siddhi/query/compi
 ler/SiddhiQL.g4


 Thank You
 --
 Menuka Warushavithana
 LinkedIn: https://www.linkedin.com/in/menukawarushavithana
 GitHub: https://www.github.com/menuka94

>>>
>>>
>>>
>>> --
>>> Tishan Dahanayakage
>>> Senior Software Engineer
>>> WSO2, Inc.
>>> Mobile:+94 716481328 <+94%2071%20648%201328>
>>>
>>> Disclaimer: This communication may contain privileged or other
>>> confidential information and is intended exclusively for the 
>>> addressee/s.
>>> If you are not the intended recipient/s, or believe that you may have
>>> received this communication in error, please reply to the sender 
>>> indicating
>>> that fact and delete the copy you received and in addition, you should 
>>> not
>>> print, copy, 

Re: [Dev] Introducing myself to mentors for GSOC Project CLI tool for WSO2 API Manager

[Pubudu Gunatilaka]

HI Vinujan,

IMHO, we should have the capability to support the both scenarios. Maybe
the initial version we can stick with option 2. But it would be better if
we can have both scenarios.

Also, we need to consider the environment when logging. Environments could
be Dev, QA, Prod, Cloud, etc. CLI tool should be able to work with
different environments.

Thank you!

On Fri, Mar 31, 2017 at 6:03 PM, Vinujan Shangarapillai <
vinujan...@cse.mrt.ac.lk> wrote:

> Hi pubudu,
>
> What is expected/suitable for for this scenario
>
> 1. APIManager login -u admin -p admin
> Or
> 2. APIManager login
> > username:
> >password:
>
> Most command tool application uses flags instead of querying parameters
> one by one. What is suitable for this application.
>
> Regards,
> Vinujan.S
>
> On Fri, 31 Mar 2017, 4:59 p.m. Vinujan Shangarapillai, <
> vinujan...@cse.mrt.ac.lk> wrote:
>
>> Thank you for the reply. I am looking into it.
>>
>> On Fri, 31 Mar 2017, 4:25 p.m. Pubudu Gunatilaka, 
>> wrote:
>>
>> Hi Vinujan,
>>
>> Yes, it is. The user needs to have an access token to invoke a subscribed
>> API. You can read more about token API in [1].
>>
>> [1] - https://docs.wso2.com/display/AM210/Token+API
>>
>> Thank you!
>>
>> On Fri, Mar 31, 2017 at 3:58 PM, Vinujan Shangarapillai <
>> vinujan...@cse.mrt.ac.lk> wrote:
>>
>> Hi pubudu!
>>
>> I have implemented login and exporting api functionality for the cli
>> prototype. Currently I am working on proposal. What is meant by "Key
>> generation" in proposal document ?, is it retrieving access token for
>> subscriber after subscribing for an api?
>>
>> best regards,
>> Vinujan.S
>>
>> On 6 March 2017 at 22:32, Vinujan Shangarapillai <
>> vinujan...@cse.mrt.ac.lk> wrote:
>>
>> Hi pubudu!
>>
>> Thank you for your information. I will contact here if there any issues.
>>
>> Reagards,
>> Vinujan.s
>>
>> On Mon, 6 Mar 2017, 10:38 a.m. Pubudu Gunatilaka, 
>> wrote:
>>
>> Hi Vinujan,
>>
>> Thank you for your interest and you can call us by name.
>>
>> As described in the project description you need to develop a CLI tool
>> for API Manager. First of all, you can check WSO2 API Manager 2.1.0 and get
>> familiar with the product [1] and the concepts [2]. Additionally, you can
>> try out API export/import feature [3] and the API Manager 2.1.0 REST APIs
>> [4] to tryout the product.
>>
>> Currently, WSO2 API Manager team is working on Carbon 5(C5) based API
>> Manager implementation and you can find the relevant repos in [5] and [6].
>> When you are developing the CLI, you should use the C5 REST APIs. API
>> Manager team has already added most important REST APIs and we are working
>> on adding new REST APIs based on the functionalities.
>>
>> If you need any help when trying the product, please do send an email to
>> the WSO2 developers' mailing list. You can also use this mailing list to
>> communicate further about the project.
>>
>> [1] - http://wso2.com/products/api-manager/
>> [2] - https://docs.wso2.com/display/AM210/Key+Concepts
>> [3] - https://docs.wso2.com/display/AM210/Migrating+the+APIs+to+a+
>> Different+Environment
>> [4] - https://docs.wso2.com/display/AM210/WSO2+APIs
>> [5] - https://github.com/wso2/carbon-apimgt/tree/C5
>> [6] - https://github.com/wso2/product-apim/tree/C5
>>
>> Thank you!
>>
>> On Mon, Mar 6, 2017 at 12:24 AM, Vinujan Shangarapillai <
>> vinujan...@cse.mrt.ac.lk> wrote:
>>
>> Dear sir!
>>
>> I am vinujan, currently studying in 4th year computer science and
>> engineering, University of Moratuwa.
>>
>> I am interested in developing command line tool for WSO2 API manager. I
>> have tried implementing login, exporting and importing api. Here
>>  is the link for the
>> repository. further I want to clarify the requirements for this
>> application.
>>
>> regards,
>> Vinujan Shangarapillai
>> *Undergraduate*
>> Computer Science And Engineering
>> University of Moratuwa
>> m: 0771224344
>> e: vinujan...@cse.mrt.ac.lk
>> 
>>
>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>>
>>
>> --
>> Vinujan Shangarapillai
>> *Undergraduate*
>> Computer Science And Engineering
>> University of Moratuwa
>> m: 0771224344
>> e: vinujan...@cse.mrt.ac.lk
>> 
>>    
>>
>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>


-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Introducing myself to mentors for GSOC Project CLI tool for WSO2 API Manager

[Vinujan Shangarapillai]

Hi pubudu,

What is expected/suitable for for this scenario

1. APIManager login -u admin -p admin
Or
2. APIManager login
> username:
>password:

Most command tool application uses flags instead of querying parameters one
by one. What is suitable for this application.

Regards,
Vinujan.S

On Fri, 31 Mar 2017, 4:59 p.m. Vinujan Shangarapillai, <
vinujan...@cse.mrt.ac.lk> wrote:

> Thank you for the reply. I am looking into it.
>
> On Fri, 31 Mar 2017, 4:25 p.m. Pubudu Gunatilaka, 
> wrote:
>
> Hi Vinujan,
>
> Yes, it is. The user needs to have an access token to invoke a subscribed
> API. You can read more about token API in [1].
>
> [1] - https://docs.wso2.com/display/AM210/Token+API
>
> Thank you!
>
> On Fri, Mar 31, 2017 at 3:58 PM, Vinujan Shangarapillai <
> vinujan...@cse.mrt.ac.lk> wrote:
>
> Hi pubudu!
>
> I have implemented login and exporting api functionality for the cli
> prototype. Currently I am working on proposal. What is meant by "Key
> generation" in proposal document ?, is it retrieving access token for
> subscriber after subscribing for an api?
>
> best regards,
> Vinujan.S
>
> On 6 March 2017 at 22:32, Vinujan Shangarapillai  > wrote:
>
> Hi pubudu!
>
> Thank you for your information. I will contact here if there any issues.
>
> Reagards,
> Vinujan.s
>
> On Mon, 6 Mar 2017, 10:38 a.m. Pubudu Gunatilaka, 
> wrote:
>
> Hi Vinujan,
>
> Thank you for your interest and you can call us by name.
>
> As described in the project description you need to develop a CLI tool for
> API Manager. First of all, you can check WSO2 API Manager 2.1.0 and get
> familiar with the product [1] and the concepts [2]. Additionally, you can
> try out API export/import feature [3] and the API Manager 2.1.0 REST APIs
> [4] to tryout the product.
>
> Currently, WSO2 API Manager team is working on Carbon 5(C5) based API
> Manager implementation and you can find the relevant repos in [5] and [6].
> When you are developing the CLI, you should use the C5 REST APIs. API
> Manager team has already added most important REST APIs and we are working
> on adding new REST APIs based on the functionalities.
>
> If you need any help when trying the product, please do send an email to
> the WSO2 developers' mailing list. You can also use this mailing list to
> communicate further about the project.
>
> [1] - http://wso2.com/products/api-manager/
> [2] - https://docs.wso2.com/display/AM210/Key+Concepts
> [3] -
> https://docs.wso2.com/display/AM210/Migrating+the+APIs+to+a+Different+Environment
> [4] - https://docs.wso2.com/display/AM210/WSO2+APIs
> [5] - https://github.com/wso2/carbon-apimgt/tree/C5
> [6] - https://github.com/wso2/product-apim/tree/C5
>
> Thank you!
>
> On Mon, Mar 6, 2017 at 12:24 AM, Vinujan Shangarapillai <
> vinujan...@cse.mrt.ac.lk> wrote:
>
> Dear sir!
>
> I am vinujan, currently studying in 4th year computer science and
> engineering, University of Moratuwa.
>
> I am interested in developing command line tool for WSO2 API manager. I
> have tried implementing login, exporting and importing api. Here
>  is the link for the
> repository. further I want to clarify the requirements for this
> application.
>
> regards,
> Vinujan Shangarapillai
> *Undergraduate*
> Computer Science And Engineering
> University of Moratuwa
> m: 0771224344
> e: vinujan...@cse.mrt.ac.lk
> 
>
>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
>
>
> --
> Vinujan Shangarapillai
> *Undergraduate*
> Computer Science And Engineering
> University of Moratuwa
> m: 0771224344
> e: vinujan...@cse.mrt.ac.lk
>    
>
>
>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Yasassri Ratnayake]

Hi Thilina,

As explained offline. You can decouple the docker image creation logic from
the web app. But the image creation should be automated. Please have a look
at existing Docker file creation scripts.

Please let us know if you have more queries.

With Regards,
Yasassri

On Fri, Mar 31, 2017 at 3:51 PM, Thilina Manamgoda 
wrote:

> Hi Yasassri,
>
> What If we configure the web app such that we can add Deployment profiles
> as we go on. We can build this for existing profiles and if there is a
> profile we can build docker images and Kubernetes artifacts and configure
> them in the web app. Is this approach acceptable ?
>
> regards,
> Thilina
>
> On Fri, Mar 31, 2017 at 8:32 AM, Yasassri Ratnayake 
> wrote:
>
>> On Thu, Mar 30, 2017 at 6:19 PM, Thilina Manamgoda > > wrote:
>>
>>> Hi Yasassri,
>>>
>>> I think if we can build docker files  for each profile and kept in a
>>> private registry it would be easy. If this is possible no need to build
>>> Docker images in web app. Also we need to build Kubernetes artifacts for
>>> those profile as well.
>>>
>>
>> What you need to take into cosideration is, that the pack (e.g : ESB
>> 4.9.0) is going to change, we are planning to use this to Test packs
>> released with WUM (WSO2 Update Manager) as well. WUM gives a new
>> distribution pack with the latest fixes. So we need to cater this as well.
>>
>>
>>>
>>> regards,
>>> Thilina
>>>
>>> On Mon, Mar 27, 2017 at 8:49 AM, Yasassri Ratnayake 
>>> wrote:
>>>
 Hi Thilina,

 On Sun, Mar 26, 2017 at 4:07 AM, Thilina Manamgoda <
 maanafun...@gmail.com> wrote:

> Hi Yasassri,
>
> Please find my comments inline.
>
> On Wed, Mar 22, 2017 at 8:12 PM, Yasassri Ratnayake  > wrote:
>
>> Hi Thilina,
>>
>> We have missed some requirements. Please consider the following as
>> well.
>>
>> 1. We need a Tomcat instance to host the Backends(Weapps) which are
>> required by the Test Scripts. So we need another instance spawned with
>> Tomcat. After spawning the instance you can deploy the prerequisite web
>> apps. (These web apps will be available in the Test-Repo under resources)
>>
>
>  Yes of course we can archieve this as well.
>
> 2. Also when deploying Jmeter we need to copy 3rd party Jars to
>> Jmeter. (These are also available in the repository)
>>
>
>
>> This can be done by copying these files to docker image in Jmeter
>> docker image building stage.
>>
>
>
>> Also answering your question about the Deployment profiles. We have
>> identified several components to make the scope manageable.
>>
>> *Products*
>> ESB | V4.9 & V5.0
>> APIM | V1.9 & V2.0
>>
>> *JDK*
>> JAVA | V1.7 & V1.8
>>
>> *DataBase*
>> MySQL
>>
>> *Third Party Servers*
>> Brokers | ActiveMQ 5.10 | WSO2 MB 3.1 (Only applicable when ESB is
>> used)
>>
>> So a Sample Profile would be, *ESB 4.9 + JAVA 1.7 + MYSQL + ActiveMQ*.
>> For now, you can concentrate on the above components when determining a
>> deployment profile. But your solution should be scalable.
>>
>> Is this a profile described here:https://docs.wso2.com/dis
> play/KA100/Clustered+Deployment+of+WSO2+Products+on+Kubernetes . If
> it is, then do I need to configure the product with third party servers or
> it's already done and I only have to deploy selected profile's servers 
> into
> kubernetes cluster. For example let's take the above profile, in order to
> run this delpoyment ESB should be configured with MYSQL and Active MQ API
> endpoints. Do i need to change the configuration files of ESB or it's
> already taken care of and deployment is done once i deploy Kubernetes
> artifacts under the selected profile.
>

 Existing scripts doesn't allow us to configure thirdparty dependencies
 like Message Brokers. So yes we need to change ESB configurations depending
 on the Broker, you can refer [1
 ] for
 ActiveMQ configurations.


>
> Is this a profile of ESB : https://github.com/wso2/kube
> rnetes-artifacts/tree/master/wso2esb ?
>

 Yes this script supports two profiles, default ESB profile and worker
 manager profile, but as mentioned we neeed to tweek these scripts to
 support mesage brokers as well.


> Also can't we have a private docker registry to hold our deplyment's
> images instead of building docker images via the web app ?.
>
>>
>>
 We can use a private registry to store the docker images but you need
 to comeup with some scripts to Auomate the process in that case.


 [1] - https://docs.wso2.com/display/ESB490/Configure+with+ActiveMQ
 --
 

Re: [Dev] Introducing myself to mentors for GSOC Project CLI tool for WSO2 API Manager

[Vinujan Shangarapillai]

Thank you for the reply. I am looking into it.

On Fri, 31 Mar 2017, 4:25 p.m. Pubudu Gunatilaka,  wrote:

> Hi Vinujan,
>
> Yes, it is. The user needs to have an access token to invoke a subscribed
> API. You can read more about token API in [1].
>
> [1] - https://docs.wso2.com/display/AM210/Token+API
>
> Thank you!
>
> On Fri, Mar 31, 2017 at 3:58 PM, Vinujan Shangarapillai <
> vinujan...@cse.mrt.ac.lk> wrote:
>
> Hi pubudu!
>
> I have implemented login and exporting api functionality for the cli
> prototype. Currently I am working on proposal. What is meant by "Key
> generation" in proposal document ?, is it retrieving access token for
> subscriber after subscribing for an api?
>
> best regards,
> Vinujan.S
>
> On 6 March 2017 at 22:32, Vinujan Shangarapillai  > wrote:
>
> Hi pubudu!
>
> Thank you for your information. I will contact here if there any issues.
>
> Reagards,
> Vinujan.s
>
> On Mon, 6 Mar 2017, 10:38 a.m. Pubudu Gunatilaka, 
> wrote:
>
> Hi Vinujan,
>
> Thank you for your interest and you can call us by name.
>
> As described in the project description you need to develop a CLI tool for
> API Manager. First of all, you can check WSO2 API Manager 2.1.0 and get
> familiar with the product [1] and the concepts [2]. Additionally, you can
> try out API export/import feature [3] and the API Manager 2.1.0 REST APIs
> [4] to tryout the product.
>
> Currently, WSO2 API Manager team is working on Carbon 5(C5) based API
> Manager implementation and you can find the relevant repos in [5] and [6].
> When you are developing the CLI, you should use the C5 REST APIs. API
> Manager team has already added most important REST APIs and we are working
> on adding new REST APIs based on the functionalities.
>
> If you need any help when trying the product, please do send an email to
> the WSO2 developers' mailing list. You can also use this mailing list to
> communicate further about the project.
>
> [1] - http://wso2.com/products/api-manager/
> [2] - https://docs.wso2.com/display/AM210/Key+Concepts
> [3] -
> https://docs.wso2.com/display/AM210/Migrating+the+APIs+to+a+Different+Environment
> [4] - https://docs.wso2.com/display/AM210/WSO2+APIs
> [5] - https://github.com/wso2/carbon-apimgt/tree/C5
> [6] - https://github.com/wso2/product-apim/tree/C5
>
> Thank you!
>
> On Mon, Mar 6, 2017 at 12:24 AM, Vinujan Shangarapillai <
> vinujan...@cse.mrt.ac.lk> wrote:
>
> Dear sir!
>
> I am vinujan, currently studying in 4th year computer science and
> engineering, University of Moratuwa.
>
> I am interested in developing command line tool for WSO2 API manager. I
> have tried implementing login, exporting and importing api. Here
>  is the link for the
> repository. further I want to clarify the requirements for this
> application.
>
> regards,
> Vinujan Shangarapillai
> *Undergraduate*
> Computer Science And Engineering
> University of Moratuwa
> m: 0771224344
> e: vinujan...@cse.mrt.ac.lk
> 
>
>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
>
>
> --
> Vinujan Shangarapillai
> *Undergraduate*
> Computer Science And Engineering
> University of Moratuwa
> m: 0771224344
> e: vinujan...@cse.mrt.ac.lk
>    
>
>
>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Preventing API Developers from updating an API once its Published

[Fazlan Nazeem]

Hi,

According to the discussion, there are concerns of making a published API
editable. As Chamin, Shani suggested we can get over this by clearly
defining what fields we make editable. But that itself is an additional
complexity we are introducing and we have to book-keep on new fields we
introduce thereafter. But this would be the way to go if we are allowing
this.

IMO we shouldn't allow users to do something wrong just because most users
want to do it. I think we should enforce the best practice on users via our
design so that they will have to follow it without choice.

quoting from the swagger article Shani pointed out

"A published API definition is a stable version ready for consuming from
client applications. It is not supposed to be changed, and any changes will
be introduced as a new version of the API."



On Fri, Mar 31, 2017 at 3:45 PM, Chamin Dias  wrote:

> Hi,
>
> I think we need to carefully identify the fields that we are going to make
> editable, if we are going to support this. Think of an example where a
> consumer is using a particular API (based on his roles). If we change the
> eligible role list for that API (i.e - visible roles), then some of the
> earlier consumers might loose their existing subscription after
> re-publishing the API. So IMAO, I think we need to first identify what are
> the things that can be edited after publishing an API.
>
> Thanks.
>
> On Fri, Mar 31, 2017 at 12:41 PM, Shani Ranasinghe  wrote:
>
>> Hi,
>>
>> I don't think we should allow the API to be edited once it is published.
>> If there is a bug in the API , then it should be fixed and released as a
>> new version IMO.  I was referring to this [1]. And they say that "Publishing
>> is a way to show that the API is in a stable state and its endpoints can be
>> reliably called from other applications." And I agree with this too.
>> This is the general perception towards a published API.
>>
>> But if we must support it, then shall we simply change our state name
>> "CREATED" to "UNPUBLISHED" like what [1] uses. Then it wouldn't create
>> confusions.
>>
>> Or else, we could allow them to edit the published api by bringing it
>> back to the created/unpublished LC state but we control what fields they
>> will be able to change without creating a new version? We will have to
>> think what fields, if changed would not need to have a new version of an
>> API. If they want to change any other field they HAVE to go for a new API
>> version.
>> [1] https://app.swaggerhub.com/help/apis/publishing-api
>>
>> On Fri, Mar 31, 2017 at 10:50 AM, Prasanna Dangalla 
>> wrote:
>>
>>> Hi All,
>>>
>>> On Fri, Mar 31, 2017 at 7:00 AM Chamalee De Silva 
>>> wrote:
>>>
 Hi,
 Agree with Raj and Nuwan.

 But considering the user PoV,
 In a situation where we change state of an Published API to maintenance
 state, make the change and published back,
 what if the subscriber is not happy with the updates which makes to the
 Published API ? (Assume that the changes are some technical information and
 not merely a bug fix).


 Because subscriber is not knowing what will be the change that will
 happen to the API.
 Adding to what Sajith has pointed out,
 I also think there should be a proper notification mechanism and *also*
 there should be a way of handling this user experience issue as well.



 Thanks,
 Chamalee



 On Fri, Mar 31, 2017 at 10:10 AM, Rajkumar Rajaratnam <
 rajkum...@wso2.com> wrote:

 I completely agree with Nuwan. We should support updating published API
 without increasing the version. Think about a banking industry. If there is
 a critical bug in the mediation logic (lets say a masking logic), they
 should be able to fix the issue in the same version transparently without
 even letting customer know that there is a bug. Publishing a minor version
 with a minor backward compatible fix and asking customers to update their
 app to call latest minor version is not an option for these kind of
 industries.

 Another example, what if we want to make some minor changes in API
 documentation? New API release for this kind of scenario is an over kill.

 Thanks.

 On Fri, Mar 31, 2017 at 12:04 AM Nuwan Dias  wrote:

 Hi Malintha,

 Yes, the workflow you have mentioned is the same one I'm proposing too.
 My only concern is on a new state, because implementing that is a bit
 complicated and this particular use case is not very common and therefore
 there's little ROI :).

 Let's say we call this new state "MAINTENANCE", what's the difference
 between bringing an API to "MAINTENANCE" vs "CREATED"? If we bring an API
 to "MAINTENANCE", does it mean that there is a copy of the API left which
 is in "PUBLISHED" state?

 

Re: [Dev] Introducing myself to mentors for GSOC Project CLI tool for WSO2 API Manager

[Pubudu Gunatilaka]

Hi Vinujan,

Yes, it is. The user needs to have an access token to invoke a subscribed
API. You can read more about token API in [1].

[1] - https://docs.wso2.com/display/AM210/Token+API

Thank you!

On Fri, Mar 31, 2017 at 3:58 PM, Vinujan Shangarapillai <
vinujan...@cse.mrt.ac.lk> wrote:

> Hi pubudu!
>
> I have implemented login and exporting api functionality for the cli
> prototype. Currently I am working on proposal. What is meant by "Key
> generation" in proposal document ?, is it retrieving access token for
> subscriber after subscribing for an api?
>
> best regards,
> Vinujan.S
>
> On 6 March 2017 at 22:32, Vinujan Shangarapillai  > wrote:
>
>> Hi pubudu!
>>
>> Thank you for your information. I will contact here if there any issues.
>>
>> Reagards,
>> Vinujan.s
>>
>> On Mon, 6 Mar 2017, 10:38 a.m. Pubudu Gunatilaka, 
>> wrote:
>>
>>> Hi Vinujan,
>>>
>>> Thank you for your interest and you can call us by name.
>>>
>>> As described in the project description you need to develop a CLI tool
>>> for API Manager. First of all, you can check WSO2 API Manager 2.1.0 and get
>>> familiar with the product [1] and the concepts [2]. Additionally, you can
>>> try out API export/import feature [3] and the API Manager 2.1.0 REST APIs
>>> [4] to tryout the product.
>>>
>>> Currently, WSO2 API Manager team is working on Carbon 5(C5) based API
>>> Manager implementation and you can find the relevant repos in [5] and [6].
>>> When you are developing the CLI, you should use the C5 REST APIs. API
>>> Manager team has already added most important REST APIs and we are working
>>> on adding new REST APIs based on the functionalities.
>>>
>>> If you need any help when trying the product, please do send an email to
>>> the WSO2 developers' mailing list. You can also use this mailing list to
>>> communicate further about the project.
>>>
>>> [1] - http://wso2.com/products/api-manager/
>>> [2] - https://docs.wso2.com/display/AM210/Key+Concepts
>>> [3] - https://docs.wso2.com/display/AM210/Migrating+the+APIs+to+a+
>>> Different+Environment
>>> [4] - https://docs.wso2.com/display/AM210/WSO2+APIs
>>> [5] - https://github.com/wso2/carbon-apimgt/tree/C5
>>> [6] - https://github.com/wso2/product-apim/tree/C5
>>>
>>> Thank you!
>>>
>>> On Mon, Mar 6, 2017 at 12:24 AM, Vinujan Shangarapillai <
>>> vinujan...@cse.mrt.ac.lk> wrote:
>>>
>>> Dear sir!
>>>
>>> I am vinujan, currently studying in 4th year computer science and
>>> engineering, University of Moratuwa.
>>>
>>> I am interested in developing command line tool for WSO2 API manager. I
>>> have tried implementing login, exporting and importing api. Here
>>>  is the link for the
>>> repository. further I want to clarify the requirements for this
>>> application.
>>>
>>> regards,
>>> Vinujan Shangarapillai
>>> *Undergraduate*
>>> Computer Science And Engineering
>>> University of Moratuwa
>>> m: 0771224344
>>> e: vinujan...@cse.mrt.ac.lk
>>> 
>>>
>>>
>>>
>>>
>>> --
>>> *Pubudu Gunatilaka*
>>> Committer and PMC Member - Apache Stratos
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> mobile : +94774078049 <%2B94772207163>
>>>
>>>
>
>
> --
> Vinujan Shangarapillai
> *Undergraduate*
> Computer Science And Engineering
> University of Moratuwa
> m: 0771224344
> e: vinujan...@cse.mrt.ac.lk
>    
>
>



-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Introducing myself to mentors for GSOC Project CLI tool for WSO2 API Manager

[Vinujan Shangarapillai]

Hi pubudu!

I have implemented login and exporting api functionality for the cli
prototype. Currently I am working on proposal. What is meant by "Key
generation" in proposal document ?, is it retrieving access token for
subscriber after subscribing for an api?

best regards,
Vinujan.S

On 6 March 2017 at 22:32, Vinujan Shangarapillai 
wrote:

> Hi pubudu!
>
> Thank you for your information. I will contact here if there any issues.
>
> Reagards,
> Vinujan.s
>
> On Mon, 6 Mar 2017, 10:38 a.m. Pubudu Gunatilaka, 
> wrote:
>
>> Hi Vinujan,
>>
>> Thank you for your interest and you can call us by name.
>>
>> As described in the project description you need to develop a CLI tool
>> for API Manager. First of all, you can check WSO2 API Manager 2.1.0 and get
>> familiar with the product [1] and the concepts [2]. Additionally, you can
>> try out API export/import feature [3] and the API Manager 2.1.0 REST APIs
>> [4] to tryout the product.
>>
>> Currently, WSO2 API Manager team is working on Carbon 5(C5) based API
>> Manager implementation and you can find the relevant repos in [5] and [6].
>> When you are developing the CLI, you should use the C5 REST APIs. API
>> Manager team has already added most important REST APIs and we are working
>> on adding new REST APIs based on the functionalities.
>>
>> If you need any help when trying the product, please do send an email to
>> the WSO2 developers' mailing list. You can also use this mailing list to
>> communicate further about the project.
>>
>> [1] - http://wso2.com/products/api-manager/
>> [2] - https://docs.wso2.com/display/AM210/Key+Concepts
>> [3] - https://docs.wso2.com/display/AM210/Migrating+the+APIs+to+a+
>> Different+Environment
>> [4] - https://docs.wso2.com/display/AM210/WSO2+APIs
>> [5] - https://github.com/wso2/carbon-apimgt/tree/C5
>> [6] - https://github.com/wso2/product-apim/tree/C5
>>
>> Thank you!
>>
>> On Mon, Mar 6, 2017 at 12:24 AM, Vinujan Shangarapillai <
>> vinujan...@cse.mrt.ac.lk> wrote:
>>
>> Dear sir!
>>
>> I am vinujan, currently studying in 4th year computer science and
>> engineering, University of Moratuwa.
>>
>> I am interested in developing command line tool for WSO2 API manager. I
>> have tried implementing login, exporting and importing api. Here
>>  is the link for the
>> repository. further I want to clarify the requirements for this
>> application.
>>
>> regards,
>> Vinujan Shangarapillai
>> *Undergraduate*
>> Computer Science And Engineering
>> University of Moratuwa
>> m: 0771224344
>> e: vinujan...@cse.mrt.ac.lk
>> 
>>
>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>


-- 
Vinujan Shangarapillai
*Undergraduate*
Computer Science And Engineering
University of Moratuwa
m: 0771224344
e: vinujan...@cse.mrt.ac.lk
   

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC][Siddhi][CEP]: Siddhi Pattern for Absence of Events

[Gobinath]

Hi all,

Thanks Suho for your feedback. I have made the changes based on your
suggestions and submitted the final proposal. Started working on a
prototype and will update you soon with the results.


Thanks & Regards,
Gobinath

On Thu, Mar 30, 2017 at 12:28 PM, Sriskandarajah Suhothayan 
wrote:

> I have given some feedback on the gsoc site.
>
> Suho
>
> On Mon, Mar 27, 2017 at 9:03 PM, Gobinath  wrote:
>
>> Hi all,
>>
>> Thanks. I have shared the draft of my proposal titled "Non-Occurrence of
>> Events for Siddhi Patterns" with WSO2 through GSoC dashboard and requesting
>> your feedback on this.
>>
>>
>> Thanks & Regards,
>> Gobinath
>>
>> On Wed, Mar 15, 2017 at 1:30 PM, Sriskandarajah Suhothayan > > wrote:
>>
>>> Thanks for the GSoC idea, I hope this will be a good way to improve the
>>> Siddhi language and make it more powerfull.
>>> If time permits we can also add other use-cases of patterns & sequences
>>> and improve it further.
>>>
>>> Since you are still not a commuter I hope these contributions will help
>>> you be a committer to Siddhi as well :)
>>> I'll make this as a formal idea, do work on a proposal as well.
>>>
>>> Regards
>>> Suho
>>>
>>>
>>> On Wed, Mar 15, 2017 at 6:09 PM, Gobinath  wrote:
>>>
 Hi team,

 This is Gobinath a former software engineer at WSO2 currently doing
 masters at Western University. This time I plan to do GSoC with WSO2 and
 this is the basic idea of what I have discussed with Suho.
 Based on Suho's suggestion, I come up with a proposal to implement
 detecting non-occurring events using Siddhi patterns. The current Siddhi
 patterns allow identifying the patterns that present.

 See an example:
 from every e1=Stream1[price>20] -> e2=Stream2[price>e1.price] within 1
 sec
 select e1.symbol as symbol1, e2.symbol as symbol2
 insert into OutputStream;

 Detecting the absence of a pattern is not natively supported by Siddhi
 patterns for the moment. In other words, identifying event_a not followed
 by event_b within 2 minutes is not possible using the current patterns
 implementation (Note that a time frame is required otherwise we have to
 wait for infinite time to say event_b has not arrived). The current
 workaround [1] to detect non-delivered items is shown below:

 from arrivals_stream#window.time(2 minutes)
 select *
 insert expired events into overdue_deliveries_stream;

 from every arrivalEvent = arrivals_stream ->
 deliveryEvent = deliveries_stream[arrivalEvent.trackingId ==
 trackingId]
 or overdue_delivery = overdue_deliveries_stream[arrivalEvent.trackingId
 == trackingId]
 select arrivalEvent.trackingId as trackingId, arrivalEvent.customerName
 as customerName, arrivalEvent.telephoneNo as telephoneNo,
 deliveryEvent.trackingId as deliveryId
 insert into filter_stream;

 from filter_stream [ (deliveryId is null)]
 select trackingId, customerName, telephoneNo
 insert into alert_stream;

 This solution requires a time window and it is inefficient if we are
 interested only on one occurrence of such a pattern (In other words same
 query without every keyword). Further, the query is more complex and not
 user-friendly.

 If we provide patterns to detect absence of patterns, the above query
 can be rewritten as below:

 from every arrivalEvent = arrivals_stream ->  (not
 deliveries_stream[arrivalEvent.trackingId == trackingId] within 2 min )
 select arrivalEvent.trackingId as trackingId, arrivalEvent.customerName
 as customerName, arrivalEvent.telephoneNo as telephoneNo
 insert into alert_stream;

 As you can see, we can use the existing language components like not &
 within. This can be achieved by extending the existing
 StreamPreStateProcessors and StreamPostStateProcessors with an internal
 timer so that they can expire their internal list of events based on the
 time limit. It is somewhat similar to time windows but the processor can
 turn off the timer and ignore the events if it is a one time pattern
 detection.

 I hope it gives the basic idea and I am waiting for your suggestions
 and feedback.

 [1] https://docs.wso2.com/display/CEP400/Sample+0111+-+Detec
 ting+non-occurrences+with+Patterns


 Thanks & Regards,
 Gobinath
 --
 *Gobinath** Loganathan*
 Graduate Student,
 Electrical and Computer Engineering,
 Western University.
 Email  : slgobin...@gmail.com
 Mobile : (+1) 416-895-0721
 Blog: javahelps.com 


>>>
>>>
>>>
>>> --
>>>
>>> *S. Suhothayan*
>>> Associate Director / Architect & Team Lead of WSO2 Complex Event
>>> Processor
>>> *WSO2 Inc. *http://wso2.com
>>> * *
>>> lean . enterprise . middleware
>>>
>>>

Re: [Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Thilina Manamgoda]

Hi Yasassri,

What If we configure the web app such that we can add Deployment profiles
as we go on. We can build this for existing profiles and if there is a
profile we can build docker images and Kubernetes artifacts and configure
them in the web app. Is this approach acceptable ?

regards,
Thilina

On Fri, Mar 31, 2017 at 8:32 AM, Yasassri Ratnayake 
wrote:

> On Thu, Mar 30, 2017 at 6:19 PM, Thilina Manamgoda 
> wrote:
>
>> Hi Yasassri,
>>
>> I think if we can build docker files  for each profile and kept in a
>> private registry it would be easy. If this is possible no need to build
>> Docker images in web app. Also we need to build Kubernetes artifacts for
>> those profile as well.
>>
>
> What you need to take into cosideration is, that the pack (e.g : ESB
> 4.9.0) is going to change, we are planning to use this to Test packs
> released with WUM (WSO2 Update Manager) as well. WUM gives a new
> distribution pack with the latest fixes. So we need to cater this as well.
>
>
>>
>> regards,
>> Thilina
>>
>> On Mon, Mar 27, 2017 at 8:49 AM, Yasassri Ratnayake 
>> wrote:
>>
>>> Hi Thilina,
>>>
>>> On Sun, Mar 26, 2017 at 4:07 AM, Thilina Manamgoda <
>>> maanafun...@gmail.com> wrote:
>>>
 Hi Yasassri,

 Please find my comments inline.

 On Wed, Mar 22, 2017 at 8:12 PM, Yasassri Ratnayake 
 wrote:

> Hi Thilina,
>
> We have missed some requirements. Please consider the following as
> well.
>
> 1. We need a Tomcat instance to host the Backends(Weapps) which are
> required by the Test Scripts. So we need another instance spawned with
> Tomcat. After spawning the instance you can deploy the prerequisite web
> apps. (These web apps will be available in the Test-Repo under resources)
>

  Yes of course we can archieve this as well.

 2. Also when deploying Jmeter we need to copy 3rd party Jars to Jmeter.
> (These are also available in the repository)
>


> This can be done by copying these files to docker image in Jmeter
> docker image building stage.
>


> Also answering your question about the Deployment profiles. We have
> identified several components to make the scope manageable.
>
> *Products*
> ESB | V4.9 & V5.0
> APIM | V1.9 & V2.0
>
> *JDK*
> JAVA | V1.7 & V1.8
>
> *DataBase*
> MySQL
>
> *Third Party Servers*
> Brokers | ActiveMQ 5.10 | WSO2 MB 3.1 (Only applicable when ESB is
> used)
>
> So a Sample Profile would be, *ESB 4.9 + JAVA 1.7 + MYSQL + ActiveMQ*.
> For now, you can concentrate on the above components when determining a
> deployment profile. But your solution should be scalable.
>
> Is this a profile described here:https://docs.wso2.com/dis
 play/KA100/Clustered+Deployment+of+WSO2+Products+on+Kubernetes . If it
 is, then do I need to configure the product with third party servers or
 it's already done and I only have to deploy selected profile's servers into
 kubernetes cluster. For example let's take the above profile, in order to
 run this delpoyment ESB should be configured with MYSQL and Active MQ API
 endpoints. Do i need to change the configuration files of ESB or it's
 already taken care of and deployment is done once i deploy Kubernetes
 artifacts under the selected profile.

>>>
>>> Existing scripts doesn't allow us to configure thirdparty dependencies
>>> like Message Brokers. So yes we need to change ESB configurations depending
>>> on the Broker, you can refer [1
>>> ] for
>>> ActiveMQ configurations.
>>>
>>>

 Is this a profile of ESB : https://github.com/wso2/kube
 rnetes-artifacts/tree/master/wso2esb ?

>>>
>>> Yes this script supports two profiles, default ESB profile and worker
>>> manager profile, but as mentioned we neeed to tweek these scripts to
>>> support mesage brokers as well.
>>>
>>>
 Also can't we have a private docker registry to hold our deplyment's
 images instead of building docker images via the web app ?.

>
>
>>> We can use a private registry to store the docker images but you need to
>>> comeup with some scripts to Auomate the process in that case.
>>>
>>>
>>> [1] - https://docs.wso2.com/display/ESB490/Configure+with+ActiveMQ
>>> --
>>> Yasassri Ratnayake
>>> Senior Software Engineer - QA
>>> WSO2 Inc ; http://wso2.com
>>> lean.enterprise.middleware
>>> *Mobile : +94715933168 <+94%2071%20593%203168>*
>>> *Blogs : http://yasassriratnayake.blogspot.com
>>> *
>>> *http://wso2logs.blogspot.com *
>>>
>>
>>
>
>
> --
> Yasassri Ratnayake
> Senior Software Engineer - QA
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
> *Mobile : +94715933168 

Re: [Dev] Preventing API Developers from updating an API once its Published

[Chamin Dias]

Hi,

I think we need to carefully identify the fields that we are going to make
editable, if we are going to support this. Think of an example where a
consumer is using a particular API (based on his roles). If we change the
eligible role list for that API (i.e - visible roles), then some of the
earlier consumers might loose their existing subscription after
re-publishing the API. So IMAO, I think we need to first identify what are
the things that can be edited after publishing an API.

Thanks.

On Fri, Mar 31, 2017 at 12:41 PM, Shani Ranasinghe  wrote:

> Hi,
>
> I don't think we should allow the API to be edited once it is published.
> If there is a bug in the API , then it should be fixed and released as a
> new version IMO.  I was referring to this [1]. And they say that "Publishing
> is a way to show that the API is in a stable state and its endpoints can be
> reliably called from other applications." And I agree with this too. This
> is the general perception towards a published API.
>
> But if we must support it, then shall we simply change our state name
> "CREATED" to "UNPUBLISHED" like what [1] uses. Then it wouldn't create
> confusions.
>
> Or else, we could allow them to edit the published api by bringing it back
> to the created/unpublished LC state but we control what fields they will be
> able to change without creating a new version? We will have to think what
> fields, if changed would not need to have a new version of an API. If they
> want to change any other field they HAVE to go for a new API version.
> [1] https://app.swaggerhub.com/help/apis/publishing-api
>
> On Fri, Mar 31, 2017 at 10:50 AM, Prasanna Dangalla 
> wrote:
>
>> Hi All,
>>
>> On Fri, Mar 31, 2017 at 7:00 AM Chamalee De Silva 
>> wrote:
>>
>>> Hi,
>>> Agree with Raj and Nuwan.
>>>
>>> But considering the user PoV,
>>> In a situation where we change state of an Published API to maintenance
>>> state, make the change and published back,
>>> what if the subscriber is not happy with the updates which makes to the
>>> Published API ? (Assume that the changes are some technical information and
>>> not merely a bug fix).
>>>
>>>
>>> Because subscriber is not knowing what will be the change that will
>>> happen to the API.
>>> Adding to what Sajith has pointed out,
>>> I also think there should be a proper notification mechanism and *also*
>>> there should be a way of handling this user experience issue as well.
>>>
>>>
>>>
>>> Thanks,
>>> Chamalee
>>>
>>>
>>>
>>> On Fri, Mar 31, 2017 at 10:10 AM, Rajkumar Rajaratnam <
>>> rajkum...@wso2.com> wrote:
>>>
>>> I completely agree with Nuwan. We should support updating published API
>>> without increasing the version. Think about a banking industry. If there is
>>> a critical bug in the mediation logic (lets say a masking logic), they
>>> should be able to fix the issue in the same version transparently without
>>> even letting customer know that there is a bug. Publishing a minor version
>>> with a minor backward compatible fix and asking customers to update their
>>> app to call latest minor version is not an option for these kind of
>>> industries.
>>>
>>> Another example, what if we want to make some minor changes in API
>>> documentation? New API release for this kind of scenario is an over kill.
>>>
>>> Thanks.
>>>
>>> On Fri, Mar 31, 2017 at 12:04 AM Nuwan Dias  wrote:
>>>
>>> Hi Malintha,
>>>
>>> Yes, the workflow you have mentioned is the same one I'm proposing too.
>>> My only concern is on a new state, because implementing that is a bit
>>> complicated and this particular use case is not very common and therefore
>>> there's little ROI :).
>>>
>>> Let's say we call this new state "MAINTENANCE", what's the difference
>>> between bringing an API to "MAINTENANCE" vs "CREATED"? If we bring an API
>>> to "MAINTENANCE", does it mean that there is a copy of the API left which
>>> is in "PUBLISHED" state?
>>>
>>> @Fazlan, in theory it is true that updating a published API is wrong.
>>> But in practice it sometimes happens because not everyone adheres to the
>>> best practices 100% always. Users may opt to make backwards compatible
>>> changes on the same minor version and some users don't even use minor
>>> versions at all. So forcing to create a new version of the API and forcing
>>> their clients to move to the newer version always is a bit too restrictive
>>> IMO
>>>
>>>
>> Yes this is what my idea as well. +1 for the notification mecanism too.
>> But I have a doubt about how we garntee that doing a change will not affect
>> the existing API functionality?
>>
>> Thanks
>> Prasanna
>>
>>> .
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Fri, Mar 31, 2017 at 8:41 AM, Rukshan Premathunga 
>>> wrote:
>>>
>>> Hi malintha,
>>>
>>> in c5 we decided to keep in the gateway even in the create state for
>>> purpose of creator's testing.
>>> so this will be fine. but keeping additional info in the create 

[Dev] IoT server connected cup sample agent failing to connect to MQTT broker

[Predrag Rakic]

Hi,
I have imported the Connected Cup sample device agent into Eclipse IDE, and 
when it tries to connect  to MQTT broker a MQTTSecurityException is thrown 
which states that the user name or password in not valid. I see that user name 
is created from the token attribute in the request, but I don't know how to 
support a right one, i.e. one that would be accepted by the OAuth2 service. 
There isn't any hint in the documentation on this topic, so I would appreciate 
any advice.
Also, I would like to take a more deep insight into the VirtualFireAlarm sample 
code, so please could you tell me where to find the code?

Best regards,
Predrag Rakic

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [CEP] GSoC Project - Siddhi Extension Doc Auto Generation

[Sriskandarajah Suhothayan]

I have given some update in the proposal please fix and submit.

On Mon, Mar 27, 2017 at 4:24 PM, Nadun De Silva  wrote:

> Hi,
>
> I have prepared a proposal and I have shared it with WSO2 via the GSoC web
> portal.
>
> In the proposal, I have not gone into detail about the design and
> implementation of the "combination of documentation" part (deliverable
> 3) since we have not completely finalised details on how we should do that.
> Would that be enough for the proposal?
>
> Please let me know if there are any changes required in the proposal. I am
> hoping to submit the final proposal based any suggestions received from you.
>
> Thank you.
>
> On Fri, Mar 17, 2017 at 7:09 PM, Nadun De Silva 
> wrote:
>
>> Hi,
>>
>> For HTML pages we can use Handlebars JS. I'm not sure if we can do so for
>> MD files.
>>
>> I will research further and try out both template engines.
>>
>> Thank you.
>>
>> On Fri, Mar 17, 2017 at 5:48 PM, Nirmal Fernando  wrote:
>>
>>> You can try handlebars JS as well. https://github.com/wycat
>>> s/handlebars.js/
>>>
>>> On Fri, Mar 17, 2017 at 12:44 PM, Nadun De Silva 
>>> wrote:
>>>
 Hi,

 Thank you for the information.

 I have started to create a prototype for this project. My approach is
 as follows,

- Loading the Siddhi extension classes using ClassIndex library
used by siddhi annotations.
- Generating a simple HTML skeleton using Apache FreeMarker [1] as
the template engine.
- Running the above logic from a Mojo.

 Please correct me if my approach is not what is expected. I have pushed
 the above implementation to a GitHub repository. [2]

 I will also start working on the proposal.

 [1] http://freemarker.org/
 [2] https://github.com/nadundesilva/wso2-siddhi-extension-do
 cumentation-generator

 Thank you.

 On Wed, Mar 15, 2017 at 1:00 AM, Sriskandarajah Suhothayan <
 s...@wso2.com> wrote:

>
>
> On Tue, Mar 14, 2017 at 7:38 PM, Nadun De Silva 
> wrote:
>
>> Hi,
>>
>> Thank you for the response. I have researched a bit more and have few
>> more follow-up questions
>>
>> It will not be in the current Siddhi format, we are thinking of a
>>> plain HTML and MD files which can be part of Siddhi Docs in Github.
>>
>>
>> Then I think when the Mojo is executed, I should create the HTML and
>> MD files inside the maven project so that with each push, the
>> GitHub repos are updated. Is this what is expected?
>>
> Yes
>
>>
>> Can have multiple pages (one per namespace) and having index and
>>> navigation across is good. Please present your suggestion we can discuss
>>> and come to a conclusion on this.
>>>
>>
>> Since by the time the combination happens, all the documentation is
>> in GitHub repos, my suggestion would be to get the content of the 
>> generated
>> HTML files using the GitHub contents API [1] and then combine them. But
>> this will be a separate program which will be run for the combination 
>> alone.
>>
>> If we decide to use this approach, I would suggest implementing one
>> of the following or any other method for rerunning the combination 
>> process.
>>
>>- A server listening to GitHub webhooks [2]
>>- A scheduled task
>>
>> What is your opinion about this approach?
>>
>> We are moving extensions to wso2-extensions repo[5] and going to host
> all of them in the extension store[6] so each extension will have it's own
> doc, and siddhi-core might have one with the predefined functions. We 
> might
> not need to combine multiple repos together at this point, but when there
> are multiple extsnsions within the same repo they need to be properly
> organized. If time permits we can explore how we can merge then, but it's
> not a requirement at this point.
>
> [5]https://github.com/wso2-extensions/?q=siddhi==
> [6]https://store.wso2.com/store/assets/analyticsextension/list
>
>
>> I also have a question about the Siddhi annotations. At the moment,
>> all the details are in one annotation called "@Extension" [3] and it does
>> not contain the "return value" of the extension. How can I fetch the 
>> return
>> value of functions from the current annotation system?
>>
>> We have to change the previous implementation to bring all into one
> annotation as we did some improvements to optimize extension class
> loading and that needed a single extension annotation.
> To identify the return value use the "returnAttributes()":  for
> functions this will have only the return type and no names, for windows
> this will return empty, and for stream processors this can have some
> attributes 

Re: [Dev] [IoTS] Cannot enroll new device with the new created account

[Shavindri Dissanayake]

Hi Zhanwen,

That is correct! Hope the following documentation will help you [1].

[1] https://docs.wso2.com/display/IoTS300/Registering+with+IoTS

Thanks & Regards
Shavindri Dissanayake
Senior Technical Writer

WSO2 Inc.
lean.enterprise.middleware

On Tue, Mar 14, 2017 at 8:50 AM, 云展智创  wrote:

> Hi Harshan,
>
> I just created the account in the register link. I can’t select the role
> by myself. In the previous IoTS version, the server will provide a default
> role (maybe devicemgt-user) to the new registered user but not in IoTS
> 3.0.0.
>
> I need to manually create a new role and assign the user to the role with
> admin user so that the new user can enroll new device. Is that right?
>
> Thanks.
>
>
> －－
> Zhanwen Zhou (Jason)
> +86 13922218435 <+86%20139%202221%208435>
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API
>
> 在 2017年3月9日，下午6:15，Harshan Liyanage  写道：
>
> Hi Zhanwen,
>
> If the user created at first doesn't have the required permissions to
> enroll a device, the UI won't show up the "Enroll new device" button in the
> UI. If that's the case it's the expected behaviour. But if the user has all
> the required permissions then there's a problem. Could you please tell us
> what permissions were given to the new role (which did not had in the
> beginning)?
>
> Thanks,
>
> Harshan Liyanage
> EMM/IoT TG
> Mobile: *+94765672894*
> Email: hars...@wso2.com
> Blog : http://harshanliyanage.blogspot.com/
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>
> On Thu, Mar 9, 2017 at 2:36 PM, 云展智创  wrote:
>
>> Hi team,
>>
>> I deployed the WSO2 IOT pack plugins and started the IoTS server
>> successfully. But I could not enroll new device with the new created
>> account and got the following errors in the backend server:
>>
>> 
>>
>> I tried to use IP instead of localhost but the URL will redirect to
>> localhost:9443 and got the same error. I couldn’t find the “Enroll new
>> device” button below.
>> 
>>
>> But after I created a new role with necessary permissions and assigned
>> the above user to that role, then I could enroll a new device with that
>> user. Is that right?
>>
>> －－
>> Zhanwen Zhou (Jason)
>> +86 13922218435 <+86%20139%202221%208435>
>> zhanwen.z...@smartcloudex.com
>> Guangzhou Smart Cloudex Technology Co., Ltd.
>> Business: IOT, API
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Preventing API Developers from updating an API once its Published

[Shani Ranasinghe]

Hi,

I don't think we should allow the API to be edited once it is published. If
there is a bug in the API , then it should be fixed and released as a new
version IMO.  I was referring to this [1]. And they say that "Publishing is
a way to show that the API is in a stable state and its endpoints can be
reliably called from other applications." And I agree with this too. This
is the general perception towards a published API.

But if we must support it, then shall we simply change our state name
"CREATED" to "UNPUBLISHED" like what [1] uses. Then it wouldn't create
confusions.

Or else, we could allow them to edit the published api by bringing it back
to the created/unpublished LC state but we control what fields they will be
able to change without creating a new version? We will have to think what
fields, if changed would not need to have a new version of an API. If they
want to change any other field they HAVE to go for a new API version.
[1] https://app.swaggerhub.com/help/apis/publishing-api

On Fri, Mar 31, 2017 at 10:50 AM, Prasanna Dangalla 
wrote:

> Hi All,
>
> On Fri, Mar 31, 2017 at 7:00 AM Chamalee De Silva 
> wrote:
>
>> Hi,
>> Agree with Raj and Nuwan.
>>
>> But considering the user PoV,
>> In a situation where we change state of an Published API to maintenance
>> state, make the change and published back,
>> what if the subscriber is not happy with the updates which makes to the
>> Published API ? (Assume that the changes are some technical information and
>> not merely a bug fix).
>>
>>
>> Because subscriber is not knowing what will be the change that will
>> happen to the API.
>> Adding to what Sajith has pointed out,
>> I also think there should be a proper notification mechanism and *also*
>> there should be a way of handling this user experience issue as well.
>>
>>
>>
>> Thanks,
>> Chamalee
>>
>>
>>
>> On Fri, Mar 31, 2017 at 10:10 AM, Rajkumar Rajaratnam > > wrote:
>>
>> I completely agree with Nuwan. We should support updating published API
>> without increasing the version. Think about a banking industry. If there is
>> a critical bug in the mediation logic (lets say a masking logic), they
>> should be able to fix the issue in the same version transparently without
>> even letting customer know that there is a bug. Publishing a minor version
>> with a minor backward compatible fix and asking customers to update their
>> app to call latest minor version is not an option for these kind of
>> industries.
>>
>> Another example, what if we want to make some minor changes in API
>> documentation? New API release for this kind of scenario is an over kill.
>>
>> Thanks.
>>
>> On Fri, Mar 31, 2017 at 12:04 AM Nuwan Dias  wrote:
>>
>> Hi Malintha,
>>
>> Yes, the workflow you have mentioned is the same one I'm proposing too.
>> My only concern is on a new state, because implementing that is a bit
>> complicated and this particular use case is not very common and therefore
>> there's little ROI :).
>>
>> Let's say we call this new state "MAINTENANCE", what's the difference
>> between bringing an API to "MAINTENANCE" vs "CREATED"? If we bring an API
>> to "MAINTENANCE", does it mean that there is a copy of the API left which
>> is in "PUBLISHED" state?
>>
>> @Fazlan, in theory it is true that updating a published API is wrong. But
>> in practice it sometimes happens because not everyone adheres to the best
>> practices 100% always. Users may opt to make backwards compatible changes
>> on the same minor version and some users don't even use minor versions at
>> all. So forcing to create a new version of the API and forcing their
>> clients to move to the newer version always is a bit too restrictive IMO
>>
>>
> Yes this is what my idea as well. +1 for the notification mecanism too.
> But I have a doubt about how we garntee that doing a change will not affect
> the existing API functionality?
>
> Thanks
> Prasanna
>
>> .
>>
>> Thanks,
>> NuwanD.
>>
>> On Fri, Mar 31, 2017 at 8:41 AM, Rukshan Premathunga 
>> wrote:
>>
>> Hi malintha,
>>
>> in c5 we decided to keep in the gateway even in the create state for
>> purpose of creator's testing.
>> so this will be fine. but keeping additional info in the create state not
>> something good. because create state is the state very first state when an
>> api is create.
>>
>> because of that I'm +1 for additional state.
>>
>> Thanks and Regards
>>
>> On Mar 31, 2017 8:10 AM, "Malintha Amarasinghe" 
>> wrote:
>>
>> Hi Nuwan,
>>
>> On Fri, Mar 31, 2017 at 12:12 AM, Nuwan Dias  wrote:
>>
>> Hi Pubudu,
>>
>> The API will reside on the Gateway irrespective of its state. So this
>> action doesn't interrupt existing subscribers or existing consumers of the
>> API. It only prevents any new subscribers from seeing the API on the store
>> until republished.
>>
>> I have thought about introducing a new LC state as well. But that only
>> 

[Dev] WSO2 Message Broker 3.2.0-Beta Released!

[Manorama Perera]

Hi All,

WSO2 Message Broker team is pleased to announce the beta release of WSO2
Message Broker (MB) 3.2.0.

Source & binary distribution files of WSO2 Message Broker can be found in:
https://github.com/wso2/product-mb/releases/tag/v3.2.0-BETA

All the known issues identified are listed at
https://wso2.org/jira/browse/MB-1881?filter=13655

Regards,
~MB Team~

-- 
Manorama Perera
Software Engineer
WSO2, Inc.;  http://wso2.com/
Mobile : +94716436216
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to write test cases for microservices registered via uuf app

[Chanaka Cooray]

Hi Denuwanthi,

If you continue to use kernel 5.1.0, then you have to manually copy the uuf
app and relevant artifact to the correct path inside the carbon.home as
mention in the example[1].

[1]
https://github.com/wso2/carbon-kernel/blob/v5.1.0/tests/osgi-tests/src/test/java/org/wso2/carbon/osgi/jmx/JMXOSGiTest.java#L73

Thanks,
Chanaka.

On Fri, Mar 31, 2017 at 10:10 AM, Niranjan Karunanandham 
wrote:

> Hi Denuwanthi,
>
> In C 5.2.0-m3, we have introduced pax exam container level testing [1].
> Did you check if we can test it via it?
>
> [1] - https://github.com/wso2/carbon-kernel/blob/master/
> docs/DeveloperTools/UsingIn-ContainerOSGiTesting.md
>
> Regards,
> Nira
>
> On Tue, Mar 28, 2017 at 11:05 PM, Denuwanthi De Silva  > wrote:
>
>> Hi,
>>
>> 1. I have a micro service registered in a uuf app via component.yaml
>>
>> apis:
>>   - className: 
>> "org.wso2.is.portal.user.client.api.micro.PasswordUtilityMicroService"
>> uri: "/passwordUtil-micro-service/"
>>
>> Now, the url for the micorservice is in the form of
>>
>> /admin-portal/root/apis/passwordUtil-micro-service/validatePassword
>>
>> 2. Inside the microservice I call an OSGI service.
>>
>> BundleContext bundleContext = 
>> FrameworkUtil.getBundle(PasswordValidationService.class).getBundleContext();
>>
>>
>> 3.When writing a test case with 'MicroServicesRunner' since it is a
>> non-osgi environment, my OSGI service is not fetched.
>>
>> 4.Then we tried to write as an osgi test. Then it says it cannot find
>> 'admin-portal' app
>>
>>
>> Is there a way we can deploy the uuf app when running the tests?(We are
>> on kernel 5.1.0)
>>
>>
>> Thanks
>> --
>> Denuwanthi De Silva
>> Senior Software Engineer;
>> WSO2 Inc.; http://wso2.com,
>> Email: denuwan...@wso2.com
>> Blog: https://denuwanthi.wordpress.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
>
> *Niranjan Karunanandham*
> Associate Technical Lead - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>
>


-- 
Chanaka Cooray
Software Engineer, WSO2 Inc. http://wso2.com
Email: chana...@wso2.com
Mobile: +94713149860

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Findings] JMX access control : readOnly and readWrite access

[Asma Jabir]

Hi,

You can try out the sample in the github repo [1].

[1] https://github.com/azinneera/JMX-access-control

Thank you

Regards,
Asma

On Fri, Mar 31, 2017 at 9:15 AM, Imesh Gunaratne  wrote:

> On Thu, Mar 30, 2017 at 3:02 PM, Asma Jabir  wrote:
>
>> Hi
>>
>> I have been looking into the $subject issue in the github c5 repo [1] and
>> following is the summary of the findings till date.
>>
>> - There is a simple inbuilt authentication and authorization mechanism in
>> JMX using password and access files. Roles can be specified with either
>> readOnly or readWrite privileges [2].
>>
>>- *readOnly* does not allow to change values or to invoke operations
>>but can monitor
>>- *readWrite *gives the total control over the server which allows to
>>change values and invoke operations
>>
>> Great work Asma!
> ​Will you be able to share the sample application that you implemented for
> verifying this functionality?
>
> Thanks
> Imesh
>
>
>> - Both password and access files are properties based text files for
>> specifying username/password pairs and username/access pairs respectively.
>>
>> - The password and access files could reside anywhere in the server and
>> should be provided upon server startup.
>>
>> - SSL is enabled by default for remote monitoring and thus the SSL should
>> be configured properly after setting up a digital certificate. System
>> properties for keystore and truststore should be set in the server.
>>
>> [1] https://github.com/wso2/carbon-kernel/issues/1247
>> [2] http://docs.oracle.com/javase/7/docs/technotes/guides/ma
>> nagement/agent.html
>> 
>>
>>
>> Thanks.
>>
>> Regards,
>> Asma
>> --
>> Asma Zinneera Jabir
>> Software Engineer
>> WSO2 Inc: http://wso2.com/
>> Contact No: +94 77 332 4752 <+94%2077%20332%204752>
>>
>>
>>
>
>
> --
> *Imesh Gunaratne*
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057 <+94%2077%20374%202057>
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>


-- 
Asma Zinneera Jabir
Software Engineer
WSO2 Inc: http://wso2.com/
Contact No: +94 77 332 4752 <+94%2077%20332%204752>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev