Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

[Sagara Gunathunga]

On Wed, Jan 6, 2016 at 4:02 PM, Afkham Azeez  wrote:

> You may have to build the whole product because the POM is not hosted yet
>

The simplest solution is temporally add staging repo [1] into the sample
POM file.

[1] - http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-274/


Thanks !

>
> On Wed, Jan 6, 2016 at 3:56 PM, Udara Liyanage  wrote:
>
>> Hi,
>>
>> I get following error when I tried building hello world sample inside the
>> product. Is this a known issue?
>>
>> Non-resolvable parent POM for
>> org.wso2.carbon.mss.sample:helloworld:[unknown-version]: Could not find
>> artifact org.wso2.carbon.mss:mss-lite-parent:pom:1.0.0 in central (
>> https://repo.maven.apache.org/maven2) and 'parent.relativePath' points
>> at wrong local POM @ line 22, column 13
>>
>> On Wed, Jan 6, 2016 at 3:29 PM, Samiyuru Senarathne 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 2nd Release Candidate of WSO2 Microservices Server 1.0.0.
>>>
>>> Please download, test the product and vote.
>>>
>>> *​Source and binary distribution files:*
>>> https://github.com/wso2/product-mss/releases/tag/v1.0.0-RC2
>>> 
>>>
>>> *Maven staging repository:*
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-274
>>>
>>> *The tag to be voted upon:*
>>> *https://github.com/wso2/product-mss/tree/v1.0.0-RC2
>>> *
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>> Note: Since the artifacts that have to be uploaded to the maven central
>>> are not yet uploaded please make sure to first build the project from the
>>> source in order to make all artifacts available in the maven local
>>> repository.
>>>
>>> Thank you,
>>> Carbon Team
>>>
>>> --
>>> Samiyuru Senarathne
>>> *Software Engineer*
>>> Mobile : +94 (0) 71 134 6087
>>> samiy...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> web: http://udaraliyanage.wordpress.com
>> phone: +94 71 443 6897
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sagara Gunathunga

Architect; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Enterprise Mobility Manager 2.0.0 RC3

[Geeth Munasinghe]

Hi all,

We are canceling this vote due to a missing property file [1], We will
start new vote soon.

[1] https://wso2.org/jira/browse/EMM-1170

Thanks
Geeth


*G. K. S. Munasinghe*
*Senior Software Engineer,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: ge...@wso2.com
phone:(+94) 777911226

On Mon, Jan 4, 2016 at 4:50 PM, Prabath Abeysekera 
wrote:

> Hi Devs,
>
> This is the third release candidate of WSO2 Enterprise Mobility Manager
> 2.0.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12592
>
> Please download, test and vote.
>
> Source & binary distribution files:
> https://github.com/wso2/product-mdm/releases/tag/v2.0.0-RC3
>
> The tag to be voted upon:
> https://github.com/wso2/product-mdm/tree/v2.0.0-RC3
>
> Known issues
> https://wso2.org/jira/issues/?filter=12593
>
>
> [ ]  Stable - go ahead and release
> [ ]  Broken - do not release (explain why)
>
>
> Thanks and Regards,
> EMM/IoTS Team
>
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>
> ___
> 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] Issue when installing MB features in products that use carbon.event.core

[Hemika Kodikara]

Yeah, I'll look into the proposed change.

Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com

Mobile : +9477762

On Wed, Jan 6, 2016 at 3:00 PM, Ramith Jayasinghe  wrote:

> I propose changing the file name at MB side. so the changes are minimal.
> we plan to further optimize this area in upcoming versions.
> @Hemika, shall we do this?
>
> On Wed, Jan 6, 2016 at 2:52 PM, Ruwan Yatawara  wrote:
>
>> Hi All,
>>
>> We ran to in to the above problem when trying to install MB features in
>> the IOTServer. As we discovered when investigating, root cause of the
>> problem was the use of event-broker.xml, which is used for loading
>> configurations in both components.
>>
>> MB uses the andes.event.core component which has now come to replace the
>> event.core from back in the day (event.core is still referred to from
>> governance components and synapse). Since both components refer to the same
>> file, each try to load contradictory (internal) classes that lead to class
>> not found exceptions.
>>
>> As a workaround to overcome this problem, we will have to rename the
>> event-broker.xml file from event.core feature to something like
>> carbon-event-core.xml to ensure the co-existing of both components in
>> harmony. In addition we will also have to remove specific checks for
>> andes/qpid packages inside of the event.core.
>>
>> I have done the changes against the 4.4.8 tag in a separate branch on my
>> personal repository [1]. Can we get a 4.4.9 version released with this
>> change [2] for us to move forward with the milestone?
>>
>> [1] - https://github.com/ruwany/carbon-commons/tree/IoTS-1.0.0-M1
>> [2] -
>> https://github.com/ruwany/carbon-commons/commit/4ea0f1f52b7fa9bc57b856e2271ffcad25eb965a
>>
>> Thanks and Regards,
>>
>> Ruwan Yatawara
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> email : ruw...@wso2.com
>> mobile : +94 77 9110413
>> blog : http://ruwansrants.blogspot.com/
>> www: :http://wso2.com
>>
>>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 777542851
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue when installing MB features in products that use carbon.event.core

[Ramith Jayasinghe]

I propose changing the file name at MB side. so the changes are minimal. we
plan to further optimize this area in upcoming versions.
@Hemika, shall we do this?

On Wed, Jan 6, 2016 at 2:52 PM, Ruwan Yatawara  wrote:

> Hi All,
>
> We ran to in to the above problem when trying to install MB features in
> the IOTServer. As we discovered when investigating, root cause of the
> problem was the use of event-broker.xml, which is used for loading
> configurations in both components.
>
> MB uses the andes.event.core component which has now come to replace the
> event.core from back in the day (event.core is still referred to from
> governance components and synapse). Since both components refer to the same
> file, each try to load contradictory (internal) classes that lead to class
> not found exceptions.
>
> As a workaround to overcome this problem, we will have to rename the
> event-broker.xml file from event.core feature to something like
> carbon-event-core.xml to ensure the co-existing of both components in
> harmony. In addition we will also have to remove specific checks for
> andes/qpid packages inside of the event.core.
>
> I have done the changes against the 4.4.8 tag in a separate branch on my
> personal repository [1]. Can we get a 4.4.9 version released with this
> change [2] for us to move forward with the milestone?
>
> [1] - https://github.com/ruwany/carbon-commons/tree/IoTS-1.0.0-M1
> [2] -
> https://github.com/ruwany/carbon-commons/commit/4ea0f1f52b7fa9bc57b856e2271ffcad25eb965a
>
> Thanks and Regards,
>
> Ruwan Yatawara
>
> Senior Software Engineer,
> WSO2 Inc.
>
> email : ruw...@wso2.com
> mobile : +94 77 9110413
> blog : http://ruwansrants.blogspot.com/
> www: :http://wso2.com
>
>


-- 
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC3

[Chamila Adhikarinayake]

Hi all,
We are canceling the vote due to the issue raised in [1] and will start a
new vote for WSO2 API Manager 1.10.0 RC4 shortly.

[1] https://wso2.org/jira/browse/APIMANAGER-4463

On Mon, Jan 4, 2016 at 11:29 PM, Chamila Adhikarinayake 
wrote:

> Hi Devs,
>
> This is the third release candidate of WSO2 API Manager 1.10.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12597
>
> Please download, test and vote.
>
> Binary distribution files:
> http://svn.wso2.org/repos/wso2/people/chamilaa/apim-1.10.0-rc3/
>
> The tag to be voted upon:
> https://github.com/wso2/product-apim/tree/v1.10.0-rc3
>
>
> [ ]  Stable - go ahead and release
> [ ]  Broken - do not release (explain why)
>
> Thanks and Regards,
> WSO2 API Manager Team
>
> --
> Regards,
> Chamila Adhikarinayake
> Software Engineer
> WSO2, Inc.
> Mobile - +94712346437
> Email  - chami...@wso2.com
> Blog  -  http://helpfromadhi.blogspot.com/
>



-- 
Regards,
Chamila Adhikarinayake
Software Engineer
WSO2, Inc.
Mobile - +94712346437
Email  - chami...@wso2.com
Blog  -  http://helpfromadhi.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

[Afkham Azeez]

You may have to build the whole product because the POM is not hosted yet

On Wed, Jan 6, 2016 at 3:56 PM, Udara Liyanage  wrote:

> Hi,
>
> I get following error when I tried building hello world sample inside the
> product. Is this a known issue?
>
> Non-resolvable parent POM for
> org.wso2.carbon.mss.sample:helloworld:[unknown-version]: Could not find
> artifact org.wso2.carbon.mss:mss-lite-parent:pom:1.0.0 in central (
> https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
> wrong local POM @ line 22, column 13
>
> On Wed, Jan 6, 2016 at 3:29 PM, Samiyuru Senarathne 
> wrote:
>
>> Hi Devs,
>>
>> This is the 2nd Release Candidate of WSO2 Microservices Server 1.0.0.
>>
>> Please download, test the product and vote.
>>
>> *​Source and binary distribution files:*
>> https://github.com/wso2/product-mss/releases/tag/v1.0.0-RC2
>> 
>>
>> *Maven staging repository:*
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-274
>>
>> *The tag to be voted upon:*
>> *https://github.com/wso2/product-mss/tree/v1.0.0-RC2
>> *
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> Note: Since the artifacts that have to be uploaded to the maven central
>> are not yet uploaded please make sure to first build the project from the
>> source in order to make all artifacts available in the maven local
>> repository.
>>
>> Thank you,
>> Carbon Team
>>
>> --
>> Samiyuru Senarathne
>> *Software Engineer*
>> Mobile : +94 (0) 71 134 6087
>> samiy...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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

[Dev] [VOTE] Release WSO2 Enterprise Mobility Manager 2.0.0 RC4

[Geeth Munasinghe]

Hi Devs,

This is the fourth release candidate of WSO2 Enterprise Mobility Manager
2.0.0.

This release fixes the following issues:
https://wso2.org/jira/issues/?filter=12592

Please download, test and vote.

Source & binary distribution files:
https://github.com/wso2/product-mdm/releases/tag/v2.0.0-RC4

The tag to be voted upon:
https://github.com/wso2/product-mdm/tree/v2.0.0-RC4

Known issues
https://wso2.org/jira/issues/?filter=12593


[ ]  Stable - go ahead and release
[ ]  Broken - do not release (explain why)


Thanks and Regards,
EMM/IoTS Team




*G. K. S. Munasinghe*
*Senior Software Engineer,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: ge...@wso2.com
phone:(+94) 777911226
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Maven Build for Application Server 6.0

[Miraj Abeysekara]

Hi,

The tomcat distribution is new downloading from the maven dependency. Also
the directory structure of the build was changed as following,

[image: Inline image 1]

Thanks

On Wed, Dec 23, 2015 at 5:11 PM, Kishanthan Thangarajah  wrote:

> We need to use the same configs location as how it is found in tomcat. For
> example, the catalina-server.xml should be used for default server.xml and
> copied to /conf directory. There are other config files (context.xml,
> web.xml) that should follow the same approach. The custom extensions
> (Valves, WebappClassLoaders, etc) may come from different repos. So the
> product build should take it dependency when assembling them with the final
> distribution.
>
> Can we also check whether we could use the tomcat maven dependency to
> download the distribution with the build?
>
> On Sat, Dec 5, 2015 at 1:23 PM, Miraj Abeysekara  wrote:
>
>> Hi Kishanthan,
>>
>> Are there any specific folder structure which I follow when adding the
>> custom configuration files to the build?
>>
>> Currently the configuration files are copied from
>> *{AS_DEV_HOME}/extensions/conf/* directory to
>> *{AS_HOME}/conf/app-server/* directory after the build.
>>
>> Thanks.
>>
>> On Fri, Dec 4, 2015 at 6:24 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> Hi Miraj,
>>>
>>> This is a good starting point and your are on the right path. Next steps
>>> are to see how to use our own tomcat configuration files, integrate our own
>>> extensions developed for tomcat and pack them with AS/Tomcat distribution
>>> with the build.
>>>
>>> It's better to use @dev for these type of mails.
>>>
>>> On Sun, Nov 29, 2015 at 1:31 PM, Miraj Abeysekara 
>>> wrote:
>>>
 Hi all,

 I am currently working on creating a maven build for Application Server
 6.0. Up-to now the following features are included with the maven build,

- Automatically download and extract tomcat server distribution
given by the maven properties.
- Repack the tomcat server distribution by adding extensions in the
extensions directory (currently including lib's and webapps as 
 extensions)

 Any feedback and suggestions are highly appreciated.

 Thanks.
 --
 Miraj Abeysekara
 Intern (Software Engineering)
 Mobile: +94775690822
 Twitter: https://twitter.com/MiRAGECreator
 GooglePlus: https://plus.google.com/u/0/+MirageAbeysekara

>>>
>>>
>>>
>>> --
>>> *Kishanthan Thangarajah*
>>> Associate Technical Lead,
>>> Platform Technologies Team,
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - +94773426635
>>> Blog - *http://kishanthan.wordpress.com
>>> *
>>> Twitter - *http://twitter.com/kishanthan
>>> *
>>>
>>
>>
>>
>> --
>> Miraj Abeysekara
>> Intern (Software Engineering)
>> Mobile: +94775690822
>> Twitter: https://twitter.com/MiRAGECreator
>> GooglePlus: https://plus.google.com/u/0/+MirageAbeysekara
>>
>
>
>
> --
> *Kishanthan Thangarajah*
> Associate Technical Lead,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com *
> Twitter - *http://twitter.com/kishanthan *
>



-- 
Miraj Abeysekara
Intern (Software Engineering)
Mobile: +94775690822
Twitter: https://twitter.com/MiRAGECreator
GooglePlus: https://plus.google.com/u/0/+MirageAbeysekara
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Issue when installing MB features in products that use carbon.event.core

[Ruwan Yatawara]

Hi All,

We ran to in to the above problem when trying to install MB features in the
IOTServer. As we discovered when investigating, root cause of the problem
was the use of event-broker.xml, which is used for loading configurations
in both components.

MB uses the andes.event.core component which has now come to replace the
event.core from back in the day (event.core is still referred to from
governance components and synapse). Since both components refer to the same
file, each try to load contradictory (internal) classes that lead to class
not found exceptions.

As a workaround to overcome this problem, we will have to rename the
event-broker.xml file from event.core feature to something like
carbon-event-core.xml to ensure the co-existing of both components in
harmony. In addition we will also have to remove specific checks for
andes/qpid packages inside of the event.core.

I have done the changes against the 4.4.8 tag in a separate branch on my
personal repository [1]. Can we get a 4.4.9 version released with this
change [2] for us to move forward with the milestone?

[1] - https://github.com/ruwany/carbon-commons/tree/IoTS-1.0.0-M1
[2] -
https://github.com/ruwany/carbon-commons/commit/4ea0f1f52b7fa9bc57b856e2271ffcad25eb965a

Thanks and Regards,

Ruwan Yatawara

Senior Software Engineer,
WSO2 Inc.

email : ruw...@wso2.com
mobile : +94 77 9110413
blog : http://ruwansrants.blogspot.com/
www: :http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue when installing MB features in products that use carbon.event.core

[Ruwan Yatawara]

Thanks Ramith and Hemaka. On a side note, we will still have to do code
change in event.core to take out the check for andes/qpid packages, for the
fix to work properly.

Thanks and Regards,

Ruwan Yatawara

Senior Software Engineer,
WSO2 Inc.

email : ruw...@wso2.com
mobile : +94 77 9110413
blog : http://ruwansrants.blogspot.com/
www: :http://wso2.com


On Wed, Jan 6, 2016 at 3:08 PM, Hemika Kodikara  wrote:

> Yeah, I'll look into the proposed change.
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>
> On Wed, Jan 6, 2016 at 3:00 PM, Ramith Jayasinghe  wrote:
>
>> I propose changing the file name at MB side. so the changes are minimal.
>> we plan to further optimize this area in upcoming versions.
>> @Hemika, shall we do this?
>>
>> On Wed, Jan 6, 2016 at 2:52 PM, Ruwan Yatawara  wrote:
>>
>>> Hi All,
>>>
>>> We ran to in to the above problem when trying to install MB features in
>>> the IOTServer. As we discovered when investigating, root cause of the
>>> problem was the use of event-broker.xml, which is used for loading
>>> configurations in both components.
>>>
>>> MB uses the andes.event.core component which has now come to replace the
>>> event.core from back in the day (event.core is still referred to from
>>> governance components and synapse). Since both components refer to the same
>>> file, each try to load contradictory (internal) classes that lead to class
>>> not found exceptions.
>>>
>>> As a workaround to overcome this problem, we will have to rename the
>>> event-broker.xml file from event.core feature to something like
>>> carbon-event-core.xml to ensure the co-existing of both components in
>>> harmony. In addition we will also have to remove specific checks for
>>> andes/qpid packages inside of the event.core.
>>>
>>> I have done the changes against the 4.4.8 tag in a separate branch on my
>>> personal repository [1]. Can we get a 4.4.9 version released with this
>>> change [2] for us to move forward with the milestone?
>>>
>>> [1] - https://github.com/ruwany/carbon-commons/tree/IoTS-1.0.0-M1
>>> [2] -
>>> https://github.com/ruwany/carbon-commons/commit/4ea0f1f52b7fa9bc57b856e2271ffcad25eb965a
>>>
>>> Thanks and Regards,
>>>
>>> Ruwan Yatawara
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>>
>>> email : ruw...@wso2.com
>>> mobile : +94 77 9110413
>>> blog : http://ruwansrants.blogspot.com/
>>> www: :http://wso2.com
>>>
>>>
>>
>>
>> --
>> Ramith Jayasinghe
>> Technical Lead
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> E: ram...@wso2.com
>> P: +94 777542851
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue when installing MB features in products that use carbon.event.core

[Isuruwan Herath]

Hi Ruwan,

event.core modules in carbon-commons does not have an owner and will be
deprecated since we moved the implementations into carbon-registry [1].
Might not be a good idea to commit changes to that?


[1] subject: Moving carbon-commons eventing components to registry

On Wed, Jan 6, 2016 at 3:16 PM, Ruwan Yatawara  wrote:

> Thanks Ramith and Hemaka. On a side note, we will still have to do code
> change in event.core to take out the check for andes/qpid packages, for the
> fix to work properly.
>
> Thanks and Regards,
>
> Ruwan Yatawara
>
> Senior Software Engineer,
> WSO2 Inc.
>
> email : ruw...@wso2.com
> mobile : +94 77 9110413
> blog : http://ruwansrants.blogspot.com/
> www: :http://wso2.com
>
>
> On Wed, Jan 6, 2016 at 3:08 PM, Hemika Kodikara  wrote:
>
>> Yeah, I'll look into the proposed change.
>>
>> Hemika Kodikara
>> Software Engineer
>> WSO2 Inc.
>> lean . enterprise . middleware
>> http://wso2.com
>>
>> Mobile : +9477762
>>
>> On Wed, Jan 6, 2016 at 3:00 PM, Ramith Jayasinghe 
>> wrote:
>>
>>> I propose changing the file name at MB side. so the changes are minimal.
>>> we plan to further optimize this area in upcoming versions.
>>> @Hemika, shall we do this?
>>>
>>> On Wed, Jan 6, 2016 at 2:52 PM, Ruwan Yatawara  wrote:
>>>
 Hi All,

 We ran to in to the above problem when trying to install MB features in
 the IOTServer. As we discovered when investigating, root cause of the
 problem was the use of event-broker.xml, which is used for loading
 configurations in both components.

 MB uses the andes.event.core component which has now come to replace
 the event.core from back in the day (event.core is still referred to from
 governance components and synapse). Since both components refer to the same
 file, each try to load contradictory (internal) classes that lead to class
 not found exceptions.

 As a workaround to overcome this problem, we will have to rename the
 event-broker.xml file from event.core feature to something like
 carbon-event-core.xml to ensure the co-existing of both components in
 harmony. In addition we will also have to remove specific checks for
 andes/qpid packages inside of the event.core.

 I have done the changes against the 4.4.8 tag in a separate branch on
 my personal repository [1]. Can we get a 4.4.9 version released with this
 change [2] for us to move forward with the milestone?

 [1] - https://github.com/ruwany/carbon-commons/tree/IoTS-1.0.0-M1
 [2] -
 https://github.com/ruwany/carbon-commons/commit/4ea0f1f52b7fa9bc57b856e2271ffcad25eb965a

 Thanks and Regards,

 Ruwan Yatawara

 Senior Software Engineer,
 WSO2 Inc.

 email : ruw...@wso2.com
 mobile : +94 77 9110413
 blog : http://ruwansrants.blogspot.com/
 www: :http://wso2.com


>>>
>>>
>>> --
>>> Ramith Jayasinghe
>>> Technical Lead
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> E: ram...@wso2.com
>>> P: +94 777542851
>>>
>>>
>>
>


-- 
Isuruwan Herath
Technical Lead

Contact: +94 776 273 296
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

[Samiyuru Senarathne]

Hi Devs,

This is the 2nd Release Candidate of WSO2 Microservices Server 1.0.0.

Please download, test the product and vote.

*​Source and binary distribution files:*
https://github.com/wso2/product-mss/releases/tag/v1.0.0-RC2


*Maven staging repository:*
http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-274

*The tag to be voted upon:*
*https://github.com/wso2/product-mss/tree/v1.0.0-RC2
*


[ ] Broken - do not release (explain why)
[ ] Stable - go ahead and release

Note: Since the artifacts that have to be uploaded to the maven central are
not yet uploaded please make sure to first build the project from the
source in order to make all artifacts available in the maven local
repository.

Thank you,
Carbon Team

-- 
Samiyuru Senarathne
*Software Engineer*
Mobile : +94 (0) 71 134 6087
samiy...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

[Udara Liyanage]

Hi,

I get following error when I tried building hello world sample inside the
product. Is this a known issue?

Non-resolvable parent POM for
org.wso2.carbon.mss.sample:helloworld:[unknown-version]: Could not find
artifact org.wso2.carbon.mss:mss-lite-parent:pom:1.0.0 in central (
https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at
wrong local POM @ line 22, column 13

On Wed, Jan 6, 2016 at 3:29 PM, Samiyuru Senarathne 
wrote:

> Hi Devs,
>
> This is the 2nd Release Candidate of WSO2 Microservices Server 1.0.0.
>
> Please download, test the product and vote.
>
> *​Source and binary distribution files:*
> https://github.com/wso2/product-mss/releases/tag/v1.0.0-RC2
> 
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-274
>
> *The tag to be voted upon:*
> *https://github.com/wso2/product-mss/tree/v1.0.0-RC2
> *
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Note: Since the artifacts that have to be uploaded to the maven central
> are not yet uploaded please make sure to first build the project from the
> source in order to make all artifacts available in the maven local
> repository.
>
> Thank you,
> Carbon Team
>
> --
> Samiyuru Senarathne
> *Software Engineer*
> Mobile : +94 (0) 71 134 6087
> samiy...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Enterprise Mobility Manager 2.0.0 RC4

[Geeth Munasinghe]

Hi all,

We are canceling this vote due to above issue, we will share the new pack
after fixing the issue.

Thanks
Geeth


*G. K. S. Munasinghe*
*Senior Software Engineer,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: ge...@wso2.com
phone:(+94) 777911226

On Wed, Jan 6, 2016 at 6:16 PM, Sashika Wijesinghe  wrote:

> Hi All,
>
> found below blocking issue in the pack.
>
> [1] https://wso2.org/jira/browse/EMM-1174
>
> Regards,
>
> On Wed, Jan 6, 2016 at 5:31 PM, Geeth Munasinghe  wrote:
>
>> Hi Devs,
>>
>> This is the fourth release candidate of WSO2 Enterprise Mobility Manager
>> 2.0.0.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12592
>>
>> Please download, test and vote.
>>
>> Source & binary distribution files:
>> https://github.com/wso2/product-mdm/releases/tag/v2.0.0-RC4
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-mdm/tree/v2.0.0-RC4
>>
>> Known issues
>> https://wso2.org/jira/issues/?filter=12593
>>
>>
>> [ ]  Stable - go ahead and release
>> [ ]  Broken - do not release (explain why)
>>
>>
>> Thanks and Regards,
>> EMM/IoTS Team
>>
>>
>>
>>
>> *G. K. S. Munasinghe*
>> *Senior Software Engineer,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: ge...@wso2.com
>> phone:(+94) 777911226
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Sashika WijesingheSoftware Engineer - QA Team*
> Mobile : +94 (0) 774537487
> sash...@wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC4

[Chamila Adhikarinayake]

Hi Devs,

This is the fourth release candidate of WSO2 API Manager 1.10.0.

This release fixes the following issues:
https://wso2.org/jira/issues/?filter=12597

Please download, test and vote.

Binary distribution files:
http://svn.wso2.org/repos/wso2/people/chamilaa/apim-1.10.0-rc4/

The tag to be voted upon:
https://github.com/wso2/product-apim/tree/v1.10.0-rc4


[ ]  Stable - go ahead and release
[ ]  Broken - do not release (explain why)

Thanks and Regards,
WSO2 API Manager Team

-- 
Regards,
Chamila Adhikarinayake
Software Engineer
WSO2, Inc.
Mobile - +94712346437
Email  - chami...@wso2.com
Blog  -  http://helpfromadhi.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Enterprise Mobility Manager 2.0.0 RC4

[Sashika Wijesinghe]

Hi All,

found below blocking issue in the pack.

[1] https://wso2.org/jira/browse/EMM-1174

Regards,

On Wed, Jan 6, 2016 at 5:31 PM, Geeth Munasinghe  wrote:

> Hi Devs,
>
> This is the fourth release candidate of WSO2 Enterprise Mobility Manager
> 2.0.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12592
>
> Please download, test and vote.
>
> Source & binary distribution files:
> https://github.com/wso2/product-mdm/releases/tag/v2.0.0-RC4
>
> The tag to be voted upon:
> https://github.com/wso2/product-mdm/tree/v2.0.0-RC4
>
> Known issues
> https://wso2.org/jira/issues/?filter=12593
>
>
> [ ]  Stable - go ahead and release
> [ ]  Broken - do not release (explain why)
>
>
> Thanks and Regards,
> EMM/IoTS Team
>
>
>
>
> *G. K. S. Munasinghe*
> *Senior Software Engineer,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ge...@wso2.com
> phone:(+94) 777911226
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Sashika WijesingheSoftware Engineer - QA Team*
Mobile : +94 (0) 774537487
sash...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][PPaaS] Puppet modules for WSO2 Products

[Isuru Haththotuwa]

Completed and pushed BRS 2.2.0 puppet module.

On Wed, Dec 23, 2015 at 12:42 PM, Chamila De Alwis 
wrote:

> Hi,
>
> I've started working on the the Puppet module for WSO2 Application Server
> on [1]. This is based on the generic WSO2 Base Puppet module and will
> follow the same pattern as the other modules.
>
> If you have started working on a module, please update with the latest
> status.
>
> [1] - https://github.com/wso2/puppet-modules
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [IS] How to configure policy criteria for role name

[Sashika Wijesinghe]

Hi IS team,

I have configured an active directory to EMM product. In the AD there are
few roles with a space in between role name (ex: Enterprise Admin). However
according the policy in carbon console, spaces are not allowed when
creating role names. Is there a standard in wso2 products not to allow
spaces in between role name? Or is there any way to configure these through
a configuration file?

Any help is highly appreciated.

Thanks and Regards,
-- 

*Sashika WijesingheSoftware Engineer - QA Team*
Mobile : +94 (0) 774537487
sash...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC4

[Harsha Kumara]

Tested the prototype APIs in Tenant and Super Tenant. No issue found.

[x]  Stable - go ahead and release

Thanks
Harsha

On Wed, Jan 6, 2016 at 9:28 PM, Tharindu Dharmarathna 
wrote:

> Tested the IS as a Keymanager and SSO . No issue found.
>
> [x]  Stable - go ahead and release
>
> Thanks
> Tharindu
>
>
> On Wed, Jan 6, 2016 at 9:22 PM, Bhathiya Jayasekara 
> wrote:
>
>> Smoke tested. No issues found.
>>
>> [x]  Stable - go ahead and release
>>
>> Thanks,
>> Bhathiya
>>
>> On Wed, Jan 6, 2016 at 6:28 PM, Chamila Adhikarinayake > > wrote:
>>
>>> Hi Devs,
>>>
>>> This is the fourth release candidate of WSO2 API Manager 1.10.0.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=12597
>>>
>>> Please download, test and vote.
>>>
>>> Binary distribution files:
>>> http://svn.wso2.org/repos/wso2/people/chamilaa/apim-1.10.0-rc4/
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/product-apim/tree/v1.10.0-rc4
>>>
>>>
>>> [ ]  Stable - go ahead and release
>>> [ ]  Broken - do not release (explain why)
>>>
>>> Thanks and Regards,
>>> WSO2 API Manager Team
>>>
>>> --
>>> Regards,
>>> Chamila Adhikarinayake
>>> Software Engineer
>>> WSO2, Inc.
>>> Mobile - +94712346437
>>> Email  - chami...@wso2.com
>>> Blog  -  http://helpfromadhi.blogspot.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Senior Software Engineer,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185 <%2B94715478185>*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Tharindu Dharmarathna*Associate Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94779109091 <%2B94779109091>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Governance Registry - Where to define a new handlebars helper ?

[Arnaud Charpentier]

Hi,

We are working on the publisher of governance registry.

We are trying to internationalize some text chains with jaggery and the 
Handlebars template engine.
We understood that we have to define a new helper with the function 
registerHelper of the template engine Handlebars but we can't figure out in 
which Javascript file we should use this function ?

We tried to do it in caramel.handlebars.client.js (path : 
/wso2greg-5.1.0/repository/deployment/server/jaggeryapps/publisher/themes/default/js/caramel.handlebars.client.js
 ) and some others js files but it didn't work.


Regards

Arnaud Charpentier

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

Re: [Dev] [IS] How to configure policy criteria for role name

[Nadeesha Meegoda]

Hi Sashika,

In the user-store configuration there is a Regular expression where you can
configure this AFAIK.  [a-zA-Z0-9._-|//]{3,30}$. Please edit
the Regex to accept space characters and check.

Regards,
Nadeesha

On Wed, Jan 6, 2016 at 7:56 PM, Sashika Wijesinghe  wrote:

> Hi IS team,
>
> I have configured an active directory to EMM product. In the AD there are
> few roles with a space in between role name (ex: Enterprise Admin). However
> according the policy in carbon console, spaces are not allowed when
> creating role names. Is there a standard in wso2 products not to allow
> spaces in between role name? Or is there any way to configure these through
> a configuration file?
>
> Any help is highly appreciated.
>
> Thanks and Regards,
> --
>
> *Sashika WijesingheSoftware Engineer - QA Team*
> Mobile : +94 (0) 774537487
> sash...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nadeesha Meegoda*
Software Engineer - QA
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
email : nadees...@wso2.com
mobile: +94783639540
<%2B94%2077%202273555>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC4

[Tharindu Dharmarathna]

Tested the IS as a Keymanager and SSO . No issue found.

[x]  Stable - go ahead and release

Thanks
Tharindu


On Wed, Jan 6, 2016 at 9:22 PM, Bhathiya Jayasekara 
wrote:

> Smoke tested. No issues found.
>
> [x]  Stable - go ahead and release
>
> Thanks,
> Bhathiya
>
> On Wed, Jan 6, 2016 at 6:28 PM, Chamila Adhikarinayake 
> wrote:
>
>> Hi Devs,
>>
>> This is the fourth release candidate of WSO2 API Manager 1.10.0.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12597
>>
>> Please download, test and vote.
>>
>> Binary distribution files:
>> http://svn.wso2.org/repos/wso2/people/chamilaa/apim-1.10.0-rc4/
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-apim/tree/v1.10.0-rc4
>>
>>
>> [ ]  Stable - go ahead and release
>> [ ]  Broken - do not release (explain why)
>>
>> Thanks and Regards,
>> WSO2 API Manager Team
>>
>> --
>> Regards,
>> Chamila Adhikarinayake
>> Software Engineer
>> WSO2, Inc.
>> Mobile - +94712346437
>> Email  - chami...@wso2.com
>> Blog  -  http://helpfromadhi.blogspot.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Bhathiya Jayasekara*
> *Senior Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <%2B94715478185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
> *Blog: http://movingaheadblog.blogspot.com
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Tharindu Dharmarathna*Associate Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC4

[Bhathiya Jayasekara]

Smoke tested. No issues found.

[x]  Stable - go ahead and release

Thanks,
Bhathiya

On Wed, Jan 6, 2016 at 6:28 PM, Chamila Adhikarinayake 
wrote:

> Hi Devs,
>
> This is the fourth release candidate of WSO2 API Manager 1.10.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12597
>
> Please download, test and vote.
>
> Binary distribution files:
> http://svn.wso2.org/repos/wso2/people/chamilaa/apim-1.10.0-rc4/
>
> The tag to be voted upon:
> https://github.com/wso2/product-apim/tree/v1.10.0-rc4
>
>
> [ ]  Stable - go ahead and release
> [ ]  Broken - do not release (explain why)
>
> Thanks and Regards,
> WSO2 API Manager Team
>
> --
> Regards,
> Chamila Adhikarinayake
> Software Engineer
> WSO2, Inc.
> Mobile - +94712346437
> Email  - chami...@wso2.com
> Blog  -  http://helpfromadhi.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Bhathiya Jayasekara*
*Senior Software Engineer,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Governance Registry - Where to define a new handlebars helper ?

[Sajith Ariyarathna]

Hi Arnaud,

You can register custom Handlebars helpers in "theme.js" file. In your
case, it should be in
"/wso2greg-5.1.0/repository/deployment/server/jaggeryapps/publisher/themes/default/theme.js"
path. Refer [1] as an example.

[1]
https://github.com/wso2/carbon-appmgt/blob/80839ee805c72cc6b2c6d1a39f0ecfecbf81/features/org.wso2.carbon.appmgt.publisher.feature/src/main/resources/publisher/themes/mobileapp/theme.js#L6

Thanks.

On Wed, Jan 6, 2016 at 9:08 PM, Arnaud Charpentier <
arnaud.charpent...@student.ecp.fr> wrote:

> Hi,
>
> We are working on the publisher of governance registry.
>
> We are trying to internationalize some text chains with jaggery and the
> Handlebars template engine.
> We understood that we have to define a new helper with the function
> registerHelper of the template engine Handlebars but we can't figure out in
> which Javascript file we should use this function ?
>
> We tried to do it in caramel.handlebars.client.js (path
> : 
> /wso2greg-5.1.0/repository/deployment/server/jaggeryapps/publisher/themes/default/js/caramel.handlebars.client.js
> ) and some others js files but it didn't work.
>
>
> Regards
>
> Arnaud Charpentier
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sajith Ariyarathna
Software Engineer; WSO2, Inc.;  http://wso2.com/
mobile: +94 77 6602284, +94 71 3951048
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

[Afkham Azeez]

DimuthuL reported that in the case of deployable jar mode, the classes
coming from OSGi bundles in the enviroment are not visible to the classes
inside the deployable jar. I think this is a blocker for the release.

On Wed, Jan 6, 2016 at 3:29 PM, Samiyuru Senarathne 
wrote:

> Hi Devs,
>
> This is the 2nd Release Candidate of WSO2 Microservices Server 1.0.0.
>
> Please download, test the product and vote.
>
> *​Source and binary distribution files:*
> https://github.com/wso2/product-mss/releases/tag/v1.0.0-RC2
> 
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-274
>
> *The tag to be voted upon:*
> *https://github.com/wso2/product-mss/tree/v1.0.0-RC2
> *
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Note: Since the artifacts that have to be uploaded to the maven central
> are not yet uploaded please make sure to first build the project from the
> source in order to make all artifacts available in the maven local
> repository.
>
> Thank you,
> Carbon Team
>
> --
> Samiyuru Senarathne
> *Software Engineer*
> Mobile : +94 (0) 71 134 6087
> samiy...@wso2.com
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC4

[Roshan Wijesena]

Hi,

Tested API create/subscribe/invoke flow and map existing auth app with
pre-generated keys by creating a service provider manually in
carbon-console.
No issues found.

[x]  Stable - go ahead and release.

-Roshan

On Wed, Jan 6, 2016 at 10:27 AM, Shani Ranasinghe  wrote:

> Tested HTTP redirect in super tenant & tenant mode. No issues found,
> Tested sample API. No issues found.
>
> [x]  Stable - go ahead and release
>
> On Wed, Jan 6, 2016 at 9:50 PM, Harsha Kumara  wrote:
>
>> Tested the prototype APIs in Tenant and Super Tenant. No issue found.
>>
>> [x]  Stable - go ahead and release
>>
>> Thanks
>> Harsha
>>
>> On Wed, Jan 6, 2016 at 9:28 PM, Tharindu Dharmarathna > > wrote:
>>
>>> Tested the IS as a Keymanager and SSO . No issue found.
>>>
>>> [x]  Stable - go ahead and release
>>>
>>> Thanks
>>> Tharindu
>>>
>>>
>>> On Wed, Jan 6, 2016 at 9:22 PM, Bhathiya Jayasekara 
>>> wrote:
>>>
 Smoke tested. No issues found.

 [x]  Stable - go ahead and release

 Thanks,
 Bhathiya

 On Wed, Jan 6, 2016 at 6:28 PM, Chamila Adhikarinayake <
 chami...@wso2.com> wrote:

> Hi Devs,
>
> This is the fourth release candidate of WSO2 API Manager 1.10.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12597
>
> Please download, test and vote.
>
> Binary distribution files:
> http://svn.wso2.org/repos/wso2/people/chamilaa/apim-1.10.0-rc4/
>
> The tag to be voted upon:
> https://github.com/wso2/product-apim/tree/v1.10.0-rc4
>
>
> [ ]  Stable - go ahead and release
> [ ]  Broken - do not release (explain why)
>
> Thanks and Regards,
> WSO2 API Manager Team
>
> --
> Regards,
> Chamila Adhikarinayake
> Software Engineer
> WSO2, Inc.
> Mobile - +94712346437
> Email  - chami...@wso2.com
> Blog  -  http://helpfromadhi.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Bhathiya Jayasekara*
 *Senior Software Engineer,*
 *WSO2 inc., http://wso2.com *

 *Phone: +94715478185 <%2B94715478185>*
 *LinkedIn: http://www.linkedin.com/in/bhathiyaj
 *
 *Twitter: https://twitter.com/bhathiyax *
 *Blog: http://movingaheadblog.blogspot.com
 *

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


>>>
>>>
>>> --
>>>
>>> *Tharindu Dharmarathna*Associate Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94779109091 <%2B94779109091>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Harsha Kumara
>> Software Engineer, WSO2 Inc.
>> Mobile: +94775505618
>> Blog:harshcreationz.blogspot.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards
> *,Shani Ranasinghe*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 77 2273555
> Blog: http://waysandmeans.blogspot.com/
> linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Roshan Wijesena.
Senior Software Engineer-WSO2 Inc.
Mobile: *+94719154640*
Email: ros...@wso2.com
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC4

[Shani Ranasinghe]

Tested HTTP redirect in super tenant & tenant mode. No issues found,
Tested sample API. No issues found.

[x]  Stable - go ahead and release

On Wed, Jan 6, 2016 at 9:50 PM, Harsha Kumara  wrote:

> Tested the prototype APIs in Tenant and Super Tenant. No issue found.
>
> [x]  Stable - go ahead and release
>
> Thanks
> Harsha
>
> On Wed, Jan 6, 2016 at 9:28 PM, Tharindu Dharmarathna 
> wrote:
>
>> Tested the IS as a Keymanager and SSO . No issue found.
>>
>> [x]  Stable - go ahead and release
>>
>> Thanks
>> Tharindu
>>
>>
>> On Wed, Jan 6, 2016 at 9:22 PM, Bhathiya Jayasekara 
>> wrote:
>>
>>> Smoke tested. No issues found.
>>>
>>> [x]  Stable - go ahead and release
>>>
>>> Thanks,
>>> Bhathiya
>>>
>>> On Wed, Jan 6, 2016 at 6:28 PM, Chamila Adhikarinayake <
>>> chami...@wso2.com> wrote:
>>>
 Hi Devs,

 This is the fourth release candidate of WSO2 API Manager 1.10.0.

 This release fixes the following issues:
 https://wso2.org/jira/issues/?filter=12597

 Please download, test and vote.

 Binary distribution files:
 http://svn.wso2.org/repos/wso2/people/chamilaa/apim-1.10.0-rc4/

 The tag to be voted upon:
 https://github.com/wso2/product-apim/tree/v1.10.0-rc4


 [ ]  Stable - go ahead and release
 [ ]  Broken - do not release (explain why)

 Thanks and Regards,
 WSO2 API Manager Team

 --
 Regards,
 Chamila Adhikarinayake
 Software Engineer
 WSO2, Inc.
 Mobile - +94712346437
 Email  - chami...@wso2.com
 Blog  -  http://helpfromadhi.blogspot.com/

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


>>>
>>>
>>> --
>>> *Bhathiya Jayasekara*
>>> *Senior Software Engineer,*
>>> *WSO2 inc., http://wso2.com *
>>>
>>> *Phone: +94715478185 <%2B94715478185>*
>>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>>> *
>>> *Twitter: https://twitter.com/bhathiyax *
>>> *Blog: http://movingaheadblog.blogspot.com
>>> *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Tharindu Dharmarathna*Associate Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94779109091 <%2B94779109091>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618
> Blog:harshcreationz.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks and Regards
*,Shani Ranasinghe*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 77 2273555
Blog: http://waysandmeans.blogspot.com/
linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Cleaning up ML REST API

[Thamali Wijewardhana]

Thanks Frank, Joseph for your comments and we have started working on the
swagger definition.

On Tue, Jan 5, 2016 at 3:19 PM, Nirmal Fernando  wrote:

> Thanks Frank. I sent an invite.
>
> On Tue, Jan 5, 2016 at 2:01 PM, Frank Leymann <
> frank.leym...@iaas.uni-stuttgart.de> wrote:
>
>> Hi Nimal, 3:30pm is fine. Talk to you then.
>>
>> Gruss/Regards,
>> Frank
>> (sent from my mobile - excuse typos & brevity)
>>
>> Am 05.01.2016 um 04:03 schrieb Nirmal Fernando :
>>
>> Hi Frank,
>>
>> Are you ok to have it at 3.30pm on 6th ? If not we can have it at 4pm
>> too.
>>
>> On Mon, Jan 4, 2016 at 9:43 PM, Frank Leymann  wrote:
>>
>>> ​Hi Nirmal,
>>>
>>> during our last call on the ML REST API we said that we want to continue
>>> our walkthru of the commented API document.  By mail we tentatively agreed
>>> on Wednesday, January 6th, 4pm Colombo time we another Skype Call or
>>> Hangout.  Should we take that time slot?  I would be available for an hour
>>> that time...​
>>>
>>>
>>> Best regards,
>>> Frank
>>>
>>> 2015-12-13 12:22 GMT+01:00 Frank Leymann :
>>>
 Dear Thamali,

 I added a bunch of comments.  For each of the methods (get, post,)
 I suggested modifications to your API that you may want to use as template
 for the other APIs; of course, I argued why I suggested individual pieces.
 I also started to make use of Swagger Paramters: and Definitions: sections
 to better ensure reuse of the different declarations of the API.

 Finally: I need to much better understand the ML data model. See my
 comments for clarification need I have :-)  This understanding is key to be
 able to recommend the use of "processing function resources" or not.

 I am looking forward to our discussion on Wednesday...


 Best regards,
 Frank

 2015-12-01 12:55 GMT+01:00 Thamali Wijewardhana :

> Link for the swagger definition:
>
>
> https://docs.google.com/a/wso2.com/document/d/1KYmXyuEFJMhFMy6p-SjRztVrgW8mr83LZR2U4BK4d-M/edit?usp=sharing
>
>
> On Tue, Dec 1, 2015 at 4:32 PM, Thamali Wijewardhana  > wrote:
>
>>
>>
>> On Thu, Nov 26, 2015 at 7:40 PM, Frank Leymann 
>> wrote:
>>
>>> Dear all, sorry for the delay  :-(
>>>
>>> What about one of the following time slots:
>>>
>>> Tuesday, Dec 1, 4pm Colombo Time
>>> Wednesday, Dec 2, 4pm Colombo Time
>>> Friday, Dec 4, 4pm Colombo Time
>>>
>>> I will be available later than 4pm but this won't be convenient for
>>> you in Colombo.
>>>
>>>
>>>
>>> Best regards,
>>> Frank
>>>
>>> 2015-11-25 8:43 GMT+01:00 Nirmal Fernando :
>>>
 Hi Frank,

 Could you please let us know few time slots?

 On Mon, Nov 23, 2015 at 9:29 AM, Nirmal Fernando 
 wrote:

> Absolutely. We'll wait till Frank confirms a time. Thanks.
>
> On Sun, Nov 22, 2015 at 10:18 PM, Sanjeewa Malalgoda <
> sanje...@wso2.com> wrote:
>
>> Hi nirmal,
>> please invite apim rest api team as well. we would like to join
>> this discussion.
>>
>> Thanks
>> sanjeewa.
>>
>> sent from my phone
>> On Nov 22, 2015 7:00 PM, "Nirmal Fernando" 
>> wrote:
>>
>>> Thanks Frank for the response. +1 for having a call. Could you
>>> please propose few time slots?
>>>
>>> On Sun, Nov 22, 2015 at 6:55 PM, Frank Leymann 
>>> wrote:
>>>
 Dear Thamali,

 we (APIM, ES Publisher,... teams) developed some guidelines on
 making all of our APIs more consistent. For example, versioning 
 (major,
 minor, patch) as part of the URL context etc.  Also, you are not 
 using PUT
 but always POST - this has some implications a bunch of REST-folks 
 are
 serious about. Similarly, the use of proper HTTP headers is a REST 
 issue to
 reduce the amount of data transferred, to avoid potential 
 concurrency
 problems etc.

 Should we have a call to discuss the API and check where we can
 help?



 Best regards,
 Frank

 2015-11-18 12:10 GMT+01:00 Nirmal Fernando :

> Thanks Thamali! Please try to generate the Swagger definition
> for ML API as the next step.
>
> On Wed, Nov 18, 2015 at 12:21 PM, Thamali Wijewardhana <
> tham...@wso2.com> wrote:
>
>> REST API standards 

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC4

[Sam Sivayogam]

Tested SSO & JWT Claims in Super Tenant and Tenant mode

 [x]  Stable - go ahead and release

On Thu, Jan 7, 2016 at 3:13 AM, Abimaran Kugathasan 
wrote:

> Tested Following
>
> 1. Default Endpoint
> 2. API Subscription/deletion/blocking/unblocking with H2 and MySQL
>
> [x]  Stable - go ahead and release.
>
> On Wed, Jan 6, 2016 at 9:02 AM, Roshan Wijesena  wrote:
>
>> Hi,
>>
>> Tested API create/subscribe/invoke flow and map existing auth app with
>> pre-generated keys by creating a service provider manually in
>> carbon-console.
>> No issues found.
>>
>> [x]  Stable - go ahead and release.
>>
>> -Roshan
>>
>> On Wed, Jan 6, 2016 at 10:27 AM, Shani Ranasinghe  wrote:
>>
>>> Tested HTTP redirect in super tenant & tenant mode. No issues found,
>>> Tested sample API. No issues found.
>>>
>>> [x]  Stable - go ahead and release
>>>
>>> On Wed, Jan 6, 2016 at 9:50 PM, Harsha Kumara  wrote:
>>>
 Tested the prototype APIs in Tenant and Super Tenant. No issue found.

 [x]  Stable - go ahead and release

 Thanks
 Harsha

 On Wed, Jan 6, 2016 at 9:28 PM, Tharindu Dharmarathna <
 tharin...@wso2.com> wrote:

> Tested the IS as a Keymanager and SSO . No issue found.
>
> [x]  Stable - go ahead and release
>
> Thanks
> Tharindu
>
>
> On Wed, Jan 6, 2016 at 9:22 PM, Bhathiya Jayasekara  > wrote:
>
>> Smoke tested. No issues found.
>>
>> [x]  Stable - go ahead and release
>>
>> Thanks,
>> Bhathiya
>>
>> On Wed, Jan 6, 2016 at 6:28 PM, Chamila Adhikarinayake <
>> chami...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the fourth release candidate of WSO2 API Manager 1.10.0.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=12597
>>>
>>> Please download, test and vote.
>>>
>>> Binary distribution files:
>>> http://svn.wso2.org/repos/wso2/people/chamilaa/apim-1.10.0-rc4/
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/product-apim/tree/v1.10.0-rc4
>>>
>>>
>>> [ ]  Stable - go ahead and release
>>> [ ]  Broken - do not release (explain why)
>>>
>>> Thanks and Regards,
>>> WSO2 API Manager Team
>>>
>>> --
>>> Regards,
>>> Chamila Adhikarinayake
>>> Software Engineer
>>> WSO2, Inc.
>>> Mobile - +94712346437
>>> Email  - chami...@wso2.com
>>> Blog  -  http://helpfromadhi.blogspot.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Senior Software Engineer,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185 <%2B94715478185>*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax
>> *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Tharindu Dharmarathna*Associate Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94779109091 <%2B94779109091>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Harsha Kumara
 Software Engineer, WSO2 Inc.
 Mobile: +94775505618
 Blog:harshcreationz.blogspot.com

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


>>>
>>>
>>> --
>>> Thanks and Regards
>>> *,Shani Ranasinghe*
>>> Senior Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 77 2273555
>>> Blog: http://waysandmeans.blogspot.com/
>>> linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Roshan Wijesena.
>> Senior Software Engineer-WSO2 Inc.
>> Mobile: *+94719154640 <%2B94719154640>*
>> Email: ros...@wso2.com
>> *WSO2, Inc. :** wso2.com *
>> lean.enterprise.middleware.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks
> Abimaran Kugathasan
>
> Software Engineer | WSO2 Inc
> Data & APIs Technologies Team
> Mobile 

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

[Dimuthu Leelarathne]

Hi,

Additionally I don't think the MSS samples are very developer friendly. I
think we have gone too far to minimize pom.xmls.

1 - In deployble-jar sample I was trying to figure out which plugin is
copying the property "Microservices" to the MANIFEST.MF file. The following
very important plugin is missing in the immediate pom file and hence the
sample is not very useful.


org.apache.maven.plugins
maven-jar-plugin



$
{microservice.resourceClasses}







2 - Bunle sample is worse. I had to trace back to following pom to take the
bundle plugin (with Samiyuru's help).

org.wso2
wso2
2


thanks,

Dimuthu



On Wed, Jan 6, 2016 at 11:18 PM, Afkham Azeez  wrote:

> DimuthuL reported that in the case of deployable jar mode, the classes
> coming from OSGi bundles in the enviroment are not visible to the classes
> inside the deployable jar. I think this is a blocker for the release.
>
> On Wed, Jan 6, 2016 at 3:29 PM, Samiyuru Senarathne 
> wrote:
>
>> Hi Devs,
>>
>> This is the 2nd Release Candidate of WSO2 Microservices Server 1.0.0.
>>
>> Please download, test the product and vote.
>>
>> *​Source and binary distribution files:*
>> https://github.com/wso2/product-mss/releases/tag/v1.0.0-RC2
>> 
>>
>> *Maven staging repository:*
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-274
>>
>> *The tag to be voted upon:*
>> *https://github.com/wso2/product-mss/tree/v1.0.0-RC2
>> *
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> Note: Since the artifacts that have to be uploaded to the maven central
>> are not yet uploaded please make sure to first build the project from the
>> source in order to make all artifacts available in the maven local
>> repository.
>>
>> Thank you,
>> Carbon Team
>>
>> --
>> Samiyuru Senarathne
>> *Software Engineer*
>> Mobile : +94 (0) 71 134 6087
>> samiy...@wso2.com
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 
Dimuthu Leelarathne
Director

WSO2, Inc. (http://wso2.com)
email: dimut...@wso2.com
Mobile : 0773661935

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

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC4

[Nuwan Dias]

Tested a Federation Scenario (with Faebook) with IS as Key Manager and a
round of smoke tests. No issues found.

[X] Stable - go ahead and release.

Thanks,
NuwanD.

On Thu, Jan 7, 2016 at 10:56 AM, Lakmali Baminiwatta 
wrote:

> Tested followings in ST and Tenant modes
>
>- Grant Types (Authorization Code, Implicit, Password, Client
>Credentials)
>- Documentation Indexing and Search
>- API Tags with API visibility
>
> [X] Stable - go ahead and release.
>
> Thanks,
> Lakmali
>
> On 7 January 2016 at 09:59, Rukshan Premathunga  wrote:
>
>> Hi,
>>
>> Smoke tested including statistics and throttling. No issues found.
>>
>> [x]  Stable - go ahead and release.
>>
>> Thanks and Regards.
>>
>> On Thu, Jan 7, 2016 at 9:24 AM, Praminda Jayawardana 
>> wrote:
>>
>>> Hi,
>>> Tested workflows and workflow clean up with BPS. No issues found.
>>>
>>> [x] Stable - go ahead and release
>>>
>>> Thanks,
>>> Praminda
>>>
>>> On Thu, Jan 7, 2016 at 7:59 AM, Sam Sivayogam  wrote:
>>>
 Tested SSO & JWT Claims in Super Tenant and Tenant mode

  [x]  Stable - go ahead and release

 On Thu, Jan 7, 2016 at 3:13 AM, Abimaran Kugathasan 
 wrote:

> Tested Following
>
> 1. Default Endpoint
> 2. API Subscription/deletion/blocking/unblocking with H2 and MySQL
>
> [x]  Stable - go ahead and release.
>
> On Wed, Jan 6, 2016 at 9:02 AM, Roshan Wijesena 
> wrote:
>
>> Hi,
>>
>> Tested API create/subscribe/invoke flow and map existing auth app
>> with pre-generated keys by creating a service provider manually in
>> carbon-console.
>> No issues found.
>>
>> [x]  Stable - go ahead and release.
>>
>> -Roshan
>>
>> On Wed, Jan 6, 2016 at 10:27 AM, Shani Ranasinghe 
>> wrote:
>>
>>> Tested HTTP redirect in super tenant & tenant mode. No issues found,
>>> Tested sample API. No issues found.
>>>
>>> [x]  Stable - go ahead and release
>>>
>>> On Wed, Jan 6, 2016 at 9:50 PM, Harsha Kumara 
>>> wrote:
>>>
 Tested the prototype APIs in Tenant and Super Tenant. No issue
 found.

 [x]  Stable - go ahead and release

 Thanks
 Harsha

 On Wed, Jan 6, 2016 at 9:28 PM, Tharindu Dharmarathna <
 tharin...@wso2.com> wrote:

> Tested the IS as a Keymanager and SSO . No issue found.
>
> [x]  Stable - go ahead and release
>
> Thanks
> Tharindu
>
>
> On Wed, Jan 6, 2016 at 9:22 PM, Bhathiya Jayasekara <
> bhath...@wso2.com> wrote:
>
>> Smoke tested. No issues found.
>>
>> [x]  Stable - go ahead and release
>>
>> Thanks,
>> Bhathiya
>>
>> On Wed, Jan 6, 2016 at 6:28 PM, Chamila Adhikarinayake <
>> chami...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the fourth release candidate of WSO2 API Manager 1.10.0.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=12597
>>>
>>> Please download, test and vote.
>>>
>>> Binary distribution files:
>>> http://svn.wso2.org/repos/wso2/people/chamilaa/apim-1.10.0-rc4/
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/product-apim/tree/v1.10.0-rc4
>>>
>>>
>>> [ ]  Stable - go ahead and release
>>> [ ]  Broken - do not release (explain why)
>>>
>>> Thanks and Regards,
>>> WSO2 API Manager Team
>>>
>>> --
>>> Regards,
>>> Chamila Adhikarinayake
>>> Software Engineer
>>> WSO2, Inc.
>>> Mobile - +94712346437
>>> Email  - chami...@wso2.com
>>> Blog  -  http://helpfromadhi.blogspot.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Senior Software Engineer,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185 <%2B94715478185>*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax
>> *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC4

[Lakmali Baminiwatta]

Tested followings in ST and Tenant modes

   - Grant Types (Authorization Code, Implicit, Password, Client
   Credentials)
   - Documentation Indexing and Search
   - API Tags with API visibility

[X] Stable - go ahead and release.

Thanks,
Lakmali

On 7 January 2016 at 09:59, Rukshan Premathunga  wrote:

> Hi,
>
> Smoke tested including statistics and throttling. No issues found.
>
> [x]  Stable - go ahead and release.
>
> Thanks and Regards.
>
> On Thu, Jan 7, 2016 at 9:24 AM, Praminda Jayawardana 
> wrote:
>
>> Hi,
>> Tested workflows and workflow clean up with BPS. No issues found.
>>
>> [x] Stable - go ahead and release
>>
>> Thanks,
>> Praminda
>>
>> On Thu, Jan 7, 2016 at 7:59 AM, Sam Sivayogam  wrote:
>>
>>> Tested SSO & JWT Claims in Super Tenant and Tenant mode
>>>
>>>  [x]  Stable - go ahead and release
>>>
>>> On Thu, Jan 7, 2016 at 3:13 AM, Abimaran Kugathasan 
>>> wrote:
>>>
 Tested Following

 1. Default Endpoint
 2. API Subscription/deletion/blocking/unblocking with H2 and MySQL

 [x]  Stable - go ahead and release.

 On Wed, Jan 6, 2016 at 9:02 AM, Roshan Wijesena 
 wrote:

> Hi,
>
> Tested API create/subscribe/invoke flow and map existing auth app with
> pre-generated keys by creating a service provider manually in
> carbon-console.
> No issues found.
>
> [x]  Stable - go ahead and release.
>
> -Roshan
>
> On Wed, Jan 6, 2016 at 10:27 AM, Shani Ranasinghe 
> wrote:
>
>> Tested HTTP redirect in super tenant & tenant mode. No issues found,
>> Tested sample API. No issues found.
>>
>> [x]  Stable - go ahead and release
>>
>> On Wed, Jan 6, 2016 at 9:50 PM, Harsha Kumara 
>> wrote:
>>
>>> Tested the prototype APIs in Tenant and Super Tenant. No issue found.
>>>
>>> [x]  Stable - go ahead and release
>>>
>>> Thanks
>>> Harsha
>>>
>>> On Wed, Jan 6, 2016 at 9:28 PM, Tharindu Dharmarathna <
>>> tharin...@wso2.com> wrote:
>>>
 Tested the IS as a Keymanager and SSO . No issue found.

 [x]  Stable - go ahead and release

 Thanks
 Tharindu


 On Wed, Jan 6, 2016 at 9:22 PM, Bhathiya Jayasekara <
 bhath...@wso2.com> wrote:

> Smoke tested. No issues found.
>
> [x]  Stable - go ahead and release
>
> Thanks,
> Bhathiya
>
> On Wed, Jan 6, 2016 at 6:28 PM, Chamila Adhikarinayake <
> chami...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> This is the fourth release candidate of WSO2 API Manager 1.10.0.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12597
>>
>> Please download, test and vote.
>>
>> Binary distribution files:
>> http://svn.wso2.org/repos/wso2/people/chamilaa/apim-1.10.0-rc4/
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-apim/tree/v1.10.0-rc4
>>
>>
>> [ ]  Stable - go ahead and release
>> [ ]  Broken - do not release (explain why)
>>
>> Thanks and Regards,
>> WSO2 API Manager Team
>>
>> --
>> Regards,
>> Chamila Adhikarinayake
>> Software Engineer
>> WSO2, Inc.
>> Mobile - +94712346437
>> Email  - chami...@wso2.com
>> Blog  -  http://helpfromadhi.blogspot.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Bhathiya Jayasekara*
> *Senior Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <%2B94715478185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax
> *
> *Blog: http://movingaheadblog.blogspot.com
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --

 *Tharindu Dharmarathna*Associate Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: *+94779109091 <%2B94779109091>*

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

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

[Samiyuru Senarathne]

Currently deployable jars have access to the classes in mss bundle. That is
how the deployable jars have access to mss annotations etc. IMO the
deployable jars were expected to have their dependencies inside themselves.
But, If we need to provide access to classes exported by all other bundles
that we cannot assume ahead, I think we will have to add dynamic import to
mss bundle. That way deployable jars will also see all exported classes
since mss bundle gets to see them.

On Wed, Jan 6, 2016 at 11:18 PM, Afkham Azeez  wrote:

> DimuthuL reported that in the case of deployable jar mode, the classes
> coming from OSGi bundles in the enviroment are not visible to the classes
> inside the deployable jar. I think this is a blocker for the release.
>
> On Wed, Jan 6, 2016 at 3:29 PM, Samiyuru Senarathne 
> wrote:
>
>> Hi Devs,
>>
>> This is the 2nd Release Candidate of WSO2 Microservices Server 1.0.0.
>>
>> Please download, test the product and vote.
>>
>> *​Source and binary distribution files:*
>> https://github.com/wso2/product-mss/releases/tag/v1.0.0-RC2
>> 
>>
>> *Maven staging repository:*
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-274
>>
>> *The tag to be voted upon:*
>> *https://github.com/wso2/product-mss/tree/v1.0.0-RC2
>> *
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> Note: Since the artifacts that have to be uploaded to the maven central
>> are not yet uploaded please make sure to first build the project from the
>> source in order to make all artifacts available in the maven local
>> repository.
>>
>> Thank you,
>> Carbon Team
>>
>> --
>> Samiyuru Senarathne
>> *Software Engineer*
>> Mobile : +94 (0) 71 134 6087
>> samiy...@wso2.com
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 
Samiyuru Senarathne
*Software Engineer*
Mobile : +94 (0) 71 134 6087
samiy...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

[Afkham Azeez]

No I totally disagree with you. We have made our POMs less verbose so that
the developers can focus on what is necessary. We put in a lot of thought
before going for this minimized POMs. Instead of copying & pasting a lot of
XML, you focus on only the bits that are relevant to your microservice
bundle or jar. With some basic Maven knowledge, you can figure out from
where the relevant plugins are inherited.

On Thu, Jan 7, 2016 at 10:50 AM, Dimuthu Leelarathne 
wrote:

> Hi,
>
> Additionally I don't think the MSS samples are very developer friendly. I
> think we have gone too far to minimize pom.xmls.
>
> 1 - In deployble-jar sample I was trying to figure out which plugin is
> copying the property "Microservices" to the MANIFEST.MF file. The following
> very important plugin is missing in the immediate pom file and hence the
> sample is not very useful.
>
> 
> org.apache.maven.plugins
> maven-jar-plugin
> 
> 
> 
> $
> {microservice.resourceClasses}
>
> 
> 
> 
> 
> 
>
> 2 - Bunle sample is worse. I had to trace back to following pom to take
> the bundle plugin (with Samiyuru's help).
>
> org.wso2
> wso2
> 2
>
>
> thanks,
>
> Dimuthu
>
>
>
> On Wed, Jan 6, 2016 at 11:18 PM, Afkham Azeez  wrote:
>
>> DimuthuL reported that in the case of deployable jar mode, the classes
>> coming from OSGi bundles in the enviroment are not visible to the classes
>> inside the deployable jar. I think this is a blocker for the release.
>>
>> On Wed, Jan 6, 2016 at 3:29 PM, Samiyuru Senarathne 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 2nd Release Candidate of WSO2 Microservices Server 1.0.0.
>>>
>>> Please download, test the product and vote.
>>>
>>> *​Source and binary distribution files:*
>>> https://github.com/wso2/product-mss/releases/tag/v1.0.0-RC2
>>> 
>>>
>>> *Maven staging repository:*
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-274
>>>
>>> *The tag to be voted upon:*
>>> *https://github.com/wso2/product-mss/tree/v1.0.0-RC2
>>> *
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>> Note: Since the artifacts that have to be uploaded to the maven central
>>> are not yet uploaded please make sure to first build the project from the
>>> source in order to make all artifacts available in the maven local
>>> repository.
>>>
>>> Thank you,
>>> Carbon Team
>>>
>>> --
>>> Samiyuru Senarathne
>>> *Software Engineer*
>>> Mobile : +94 (0) 71 134 6087
>>> samiy...@wso2.com
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> Dimuthu Leelarathne
> Director
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
> Mobile : 0773661935
>
> Lean . Enterprise . Middleware
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

[Afkham Azeez]

OSGi experts, is there a better way to do this rather than add
DynamicImport-Packages: * ?

On Thu, Jan 7, 2016 at 11:09 AM, Samiyuru Senarathne 
wrote:

> Currently deployable jars have access to the classes in mss bundle. That
> is how the deployable jars have access to mss annotations etc. IMO the
> deployable jars were expected to have their dependencies inside themselves.
> But, If we need to provide access to classes exported by all other bundles
> that we cannot assume ahead, I think we will have to add dynamic import to
> mss bundle. That way deployable jars will also see all exported classes
> since mss bundle gets to see them.
>
> On Wed, Jan 6, 2016 at 11:18 PM, Afkham Azeez  wrote:
>
>> DimuthuL reported that in the case of deployable jar mode, the classes
>> coming from OSGi bundles in the enviroment are not visible to the classes
>> inside the deployable jar. I think this is a blocker for the release.
>>
>> On Wed, Jan 6, 2016 at 3:29 PM, Samiyuru Senarathne 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 2nd Release Candidate of WSO2 Microservices Server 1.0.0.
>>>
>>> Please download, test the product and vote.
>>>
>>> *​Source and binary distribution files:*
>>> https://github.com/wso2/product-mss/releases/tag/v1.0.0-RC2
>>> 
>>>
>>> *Maven staging repository:*
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-274
>>>
>>> *The tag to be voted upon:*
>>> *https://github.com/wso2/product-mss/tree/v1.0.0-RC2
>>> *
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>> Note: Since the artifacts that have to be uploaded to the maven central
>>> are not yet uploaded please make sure to first build the project from the
>>> source in order to make all artifacts available in the maven local
>>> repository.
>>>
>>> Thank you,
>>> Carbon Team
>>>
>>> --
>>> Samiyuru Senarathne
>>> *Software Engineer*
>>> Mobile : +94 (0) 71 134 6087
>>> samiy...@wso2.com
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> Samiyuru Senarathne
> *Software Engineer*
> Mobile : +94 (0) 71 134 6087
> samiy...@wso2.com
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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

Re: [Dev] ESB 4.8.1 PassThroughHttpSender issue

[Nariman Abdullayev (TD)]

I continue to test how address endpoint handles timeouts I get new issues, now 
it is  org.apache.synapse.core.axis2.SynapseCallbackReceiver

if we use the same scenario and send, for example 10 requests to the proxy at 
the same time...
Now after I added msgCtx.notifyAll(); all requests are successfully pass by 
PassThroughHttpSender in case of timeouts. However, some of them (like 3 out of 
10) get the following exception:

WARN - SynapseCallbackReceiver Synapse received a response for the request with 
message Id : urn:uuid:e30c5327-c23e-4254-9d3c-d93f02b9979b But a callback is 
not registered (anymore) to process this response

It looks like SynapseCallbackReceiver properly get info that there was a 
connection timeout. However, SynapseCallbackReceiver continue to listen to the 
connection response... I do not understand why it is implemented in this way 
and what is more important how to notify SynapseCallbackReceiver from 
PassThroughHttpSender that it is all, so stop listening for a callback...

can some help me with it?

Reagrds,
Nariman.


On 01/05/2016 03:16 PM, Nariman Abdullayev (TD) wrote:
Hi,


I think that org.apache.synapse.transport.passthru.PassThroughHttpSender which 
is default transport sender for http in wso2esb 4.8.1 (not sure about 4.9.0 
will check it later) does not return borrowed thread to worker pool on 
exception in some cases.

It seems to me that this happens when exception occurs in external sequence 
(not in proxy which is directly accepts incoming request). For example, it 
occurs when you implement store-and-forward pattern with store and message 
processor.

this is my simple WSO2ESB 4.8.1 configuration to reproduce the issue:


http://ws.apache.org/ns/synapse;>
   
  15000
   
   
   
  
 


   



   

 
 
 
  
   
   Test
   
   
  http://localhost/index.php;>
 
10
fault
 
 
-1
0
1.0
0
 
 
-1
 
  
   
   
  
 
 
 
  
  
   
   
  
 
  
  
 
  
  
 
  
   
   
  
 
 http://localhost:9000.*;>

 
  
  
 
  
  The main sequence for the message mediation
   
   
   
  1000
  TestSequence
  1
  true
   




configure endpoint to send request to nowhere and just call TestProxy 20 time 
or more in order to exhaust internal pool of worker threads...

after 20th request is received, new requests will be accepted and stored in 
store but worker pool will be exhausted and messages will not be retried from 
message store.

I think that there must be source code somewhere available for 
PassThroughHttpSender... but it was quicker to decompile 
repository/components/plugins/synapse-nhttp-transport_2.1.2.wso2v4.jar and look 
inside to see the reason of the problem.

we should look inside sendRequestContent method:

synchronized (msgContext)
  {
while 
((!Boolean.TRUE.equals(msgContext.getProperty("WAIT_BUILDER_IN_STREAM_COMPLETE")))
 && (!Boolean.TRUE.equals(msgContext.getProperty("PASSTHRU_CONNECT_ERROR" {
  try
  {
log.info("msgContext before wait");
msgContext.wait();
log.info("msgContext after wait");
  }
  catch (InterruptedException e)
  {
e.printStackTrace();
  }
}



this is where the process stack on error. When exception occurs (in another 
thread) it "forgets" to notify current thread and msgContext waits forever 
(actually till server restart)

so I slightly modify another class in the same package - DeliveryAgent, method 
errorConnecting. this method is used to catch a callback from a thread used to 
connect to a target host... so when we catch a callback we notify msgContext 
and inform it to continue by adding new synchronize block after 
targetErrorHandler...

public void errorConnecting(HttpRoute route, int errorCode, String message)
  {
Queue queue = (Queue)this.waitingMessages.get(route);
if (queue != null)
{
  MessageContext msgCtx = (MessageContext)queue.poll();
  if (msgCtx != null) {
this.targetErrorHandler.handleError(msgCtx, errorCode, "Error 
connecting to the back end", null, ProtocolState.REQUEST_READY);
synchronized (msgCtx)
{
log.info("errorConnecting: notify message context about error");
msgCtx.setProperty("PASSTHRU_CONNECT_ERROR", Boolean.TRUE);
msgCtx.notifyAll();
}
  }
}
else
{
  throw new IllegalStateException("Queue cannot be null for: " + route);
}
  }



I have done some tests and it looks like it fixes the problem of 

Re: [Dev] Issue when installing MB features in products that use carbon.event.core

[Sasikala Kottegoda]

I propose to change the name of 'master-datasources.xml' as well. When we
tried to install MB features in the IoT server, we had to manually add
mb-store configurations into their master-datasources.xml from the code
level.

Thank you

On Wed, Jan 6, 2016 at 3:00 PM, Ramith Jayasinghe  wrote:

> I propose changing the file name at MB side. so the changes are minimal.
> we plan to further optimize this area in upcoming versions.
> @Hemika, shall we do this?
>
> On Wed, Jan 6, 2016 at 2:52 PM, Ruwan Yatawara  wrote:
>
>> Hi All,
>>
>> We ran to in to the above problem when trying to install MB features in
>> the IOTServer. As we discovered when investigating, root cause of the
>> problem was the use of event-broker.xml, which is used for loading
>> configurations in both components.
>>
>> MB uses the andes.event.core component which has now come to replace the
>> event.core from back in the day (event.core is still referred to from
>> governance components and synapse). Since both components refer to the same
>> file, each try to load contradictory (internal) classes that lead to class
>> not found exceptions.
>>
>> As a workaround to overcome this problem, we will have to rename the
>> event-broker.xml file from event.core feature to something like
>> carbon-event-core.xml to ensure the co-existing of both components in
>> harmony. In addition we will also have to remove specific checks for
>> andes/qpid packages inside of the event.core.
>>
>> I have done the changes against the 4.4.8 tag in a separate branch on my
>> personal repository [1]. Can we get a 4.4.9 version released with this
>> change [2] for us to move forward with the milestone?
>>
>> [1] - https://github.com/ruwany/carbon-commons/tree/IoTS-1.0.0-M1
>> [2] -
>> https://github.com/ruwany/carbon-commons/commit/4ea0f1f52b7fa9bc57b856e2271ffcad25eb965a
>>
>> Thanks and Regards,
>>
>> Ruwan Yatawara
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> email : ruw...@wso2.com
>> mobile : +94 77 9110413
>> blog : http://ruwansrants.blogspot.com/
>> www: :http://wso2.com
>>
>>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 777542851
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sasikala Kottegoda
*Software Engineer*
WSO2 Inc., http://wso2.com/
lean. enterprise. middleware
Mobile: +94 774835928/712792401
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC4

[Praminda Jayawardana]

Hi,
Tested workflows and workflow clean up with BPS. No issues found.

[x] Stable - go ahead and release

Thanks,
Praminda

On Thu, Jan 7, 2016 at 7:59 AM, Sam Sivayogam  wrote:

> Tested SSO & JWT Claims in Super Tenant and Tenant mode
>
>  [x]  Stable - go ahead and release
>
> On Thu, Jan 7, 2016 at 3:13 AM, Abimaran Kugathasan 
> wrote:
>
>> Tested Following
>>
>> 1. Default Endpoint
>> 2. API Subscription/deletion/blocking/unblocking with H2 and MySQL
>>
>> [x]  Stable - go ahead and release.
>>
>> On Wed, Jan 6, 2016 at 9:02 AM, Roshan Wijesena  wrote:
>>
>>> Hi,
>>>
>>> Tested API create/subscribe/invoke flow and map existing auth app with
>>> pre-generated keys by creating a service provider manually in
>>> carbon-console.
>>> No issues found.
>>>
>>> [x]  Stable - go ahead and release.
>>>
>>> -Roshan
>>>
>>> On Wed, Jan 6, 2016 at 10:27 AM, Shani Ranasinghe 
>>> wrote:
>>>
 Tested HTTP redirect in super tenant & tenant mode. No issues found,
 Tested sample API. No issues found.

 [x]  Stable - go ahead and release

 On Wed, Jan 6, 2016 at 9:50 PM, Harsha Kumara  wrote:

> Tested the prototype APIs in Tenant and Super Tenant. No issue found.
>
> [x]  Stable - go ahead and release
>
> Thanks
> Harsha
>
> On Wed, Jan 6, 2016 at 9:28 PM, Tharindu Dharmarathna <
> tharin...@wso2.com> wrote:
>
>> Tested the IS as a Keymanager and SSO . No issue found.
>>
>> [x]  Stable - go ahead and release
>>
>> Thanks
>> Tharindu
>>
>>
>> On Wed, Jan 6, 2016 at 9:22 PM, Bhathiya Jayasekara <
>> bhath...@wso2.com> wrote:
>>
>>> Smoke tested. No issues found.
>>>
>>> [x]  Stable - go ahead and release
>>>
>>> Thanks,
>>> Bhathiya
>>>
>>> On Wed, Jan 6, 2016 at 6:28 PM, Chamila Adhikarinayake <
>>> chami...@wso2.com> wrote:
>>>
 Hi Devs,

 This is the fourth release candidate of WSO2 API Manager 1.10.0.

 This release fixes the following issues:
 https://wso2.org/jira/issues/?filter=12597

 Please download, test and vote.

 Binary distribution files:
 http://svn.wso2.org/repos/wso2/people/chamilaa/apim-1.10.0-rc4/

 The tag to be voted upon:
 https://github.com/wso2/product-apim/tree/v1.10.0-rc4


 [ ]  Stable - go ahead and release
 [ ]  Broken - do not release (explain why)

 Thanks and Regards,
 WSO2 API Manager Team

 --
 Regards,
 Chamila Adhikarinayake
 Software Engineer
 WSO2, Inc.
 Mobile - +94712346437
 Email  - chami...@wso2.com
 Blog  -  http://helpfromadhi.blogspot.com/

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


>>>
>>>
>>> --
>>> *Bhathiya Jayasekara*
>>> *Senior Software Engineer,*
>>> *WSO2 inc., http://wso2.com *
>>>
>>> *Phone: +94715478185 <%2B94715478185>*
>>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>>> *
>>> *Twitter: https://twitter.com/bhathiyax
>>> *
>>> *Blog: http://movingaheadblog.blogspot.com
>>> *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Tharindu Dharmarathna*Associate Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94779109091 <%2B94779109091>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618
> Blog:harshcreationz.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Thanks and Regards
 *,Shani Ranasinghe*
 Senior Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 77 2273555
 Blog: http://waysandmeans.blogspot.com/
 linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab

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


>>>
>>>
>>> --
>>> Roshan Wijesena.
>>> Senior Software Engineer-WSO2 Inc.
>>> Mobile: 

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC4

[Rukshan Premathunga]

Hi,

Smoke tested including statistics and throttling. No issues found.

[x]  Stable - go ahead and release.

Thanks and Regards.

On Thu, Jan 7, 2016 at 9:24 AM, Praminda Jayawardana 
wrote:

> Hi,
> Tested workflows and workflow clean up with BPS. No issues found.
>
> [x] Stable - go ahead and release
>
> Thanks,
> Praminda
>
> On Thu, Jan 7, 2016 at 7:59 AM, Sam Sivayogam  wrote:
>
>> Tested SSO & JWT Claims in Super Tenant and Tenant mode
>>
>>  [x]  Stable - go ahead and release
>>
>> On Thu, Jan 7, 2016 at 3:13 AM, Abimaran Kugathasan 
>> wrote:
>>
>>> Tested Following
>>>
>>> 1. Default Endpoint
>>> 2. API Subscription/deletion/blocking/unblocking with H2 and MySQL
>>>
>>> [x]  Stable - go ahead and release.
>>>
>>> On Wed, Jan 6, 2016 at 9:02 AM, Roshan Wijesena  wrote:
>>>
 Hi,

 Tested API create/subscribe/invoke flow and map existing auth app with
 pre-generated keys by creating a service provider manually in
 carbon-console.
 No issues found.

 [x]  Stable - go ahead and release.

 -Roshan

 On Wed, Jan 6, 2016 at 10:27 AM, Shani Ranasinghe 
 wrote:

> Tested HTTP redirect in super tenant & tenant mode. No issues found,
> Tested sample API. No issues found.
>
> [x]  Stable - go ahead and release
>
> On Wed, Jan 6, 2016 at 9:50 PM, Harsha Kumara 
> wrote:
>
>> Tested the prototype APIs in Tenant and Super Tenant. No issue found.
>>
>> [x]  Stable - go ahead and release
>>
>> Thanks
>> Harsha
>>
>> On Wed, Jan 6, 2016 at 9:28 PM, Tharindu Dharmarathna <
>> tharin...@wso2.com> wrote:
>>
>>> Tested the IS as a Keymanager and SSO . No issue found.
>>>
>>> [x]  Stable - go ahead and release
>>>
>>> Thanks
>>> Tharindu
>>>
>>>
>>> On Wed, Jan 6, 2016 at 9:22 PM, Bhathiya Jayasekara <
>>> bhath...@wso2.com> wrote:
>>>
 Smoke tested. No issues found.

 [x]  Stable - go ahead and release

 Thanks,
 Bhathiya

 On Wed, Jan 6, 2016 at 6:28 PM, Chamila Adhikarinayake <
 chami...@wso2.com> wrote:

> Hi Devs,
>
> This is the fourth release candidate of WSO2 API Manager 1.10.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12597
>
> Please download, test and vote.
>
> Binary distribution files:
> http://svn.wso2.org/repos/wso2/people/chamilaa/apim-1.10.0-rc4/
>
> The tag to be voted upon:
> https://github.com/wso2/product-apim/tree/v1.10.0-rc4
>
>
> [ ]  Stable - go ahead and release
> [ ]  Broken - do not release (explain why)
>
> Thanks and Regards,
> WSO2 API Manager Team
>
> --
> Regards,
> Chamila Adhikarinayake
> Software Engineer
> WSO2, Inc.
> Mobile - +94712346437
> Email  - chami...@wso2.com
> Blog  -  http://helpfromadhi.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Bhathiya Jayasekara*
 *Senior Software Engineer,*
 *WSO2 inc., http://wso2.com *

 *Phone: +94715478185 <%2B94715478185>*
 *LinkedIn: http://www.linkedin.com/in/bhathiyaj
 *
 *Twitter: https://twitter.com/bhathiyax
 *
 *Blog: http://movingaheadblog.blogspot.com
 *

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


>>>
>>>
>>> --
>>>
>>> *Tharindu Dharmarathna*Associate Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94779109091 <%2B94779109091>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Harsha Kumara
>> Software Engineer, WSO2 Inc.
>> Mobile: +94775505618
>> Blog:harshcreationz.blogspot.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards
> *,Shani Ranasinghe*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

[Dimuthu Leelarathne]

On Thu, Jan 7, 2016 at 11:51 AM, Dimuthu Leelarathne 
wrote:

>
>
> On Thu, Jan 7, 2016 at 11:18 AM, Afkham Azeez  wrote:
>
>> No I totally disagree with you. We have made our POMs less verbose so
>> that the developers can focus on what is necessary. We put in a lot of
>> thought before going for this minimized POMs. Instead of copying & pasting
>> a lot of XML, you focus on only the bits that are relevant to your
>> microservice bundle or jar. With some basic Maven knowledge, you can figure
>> out from where the relevant plugins are inherited.
>>
>
>
> Yes. One can figure out. But, not developer friendly. IMO, we need to
> include the jar-plugin configuration. That is not making it verbose, but
> rather user friendly.
>

Why do I have to browse the internet looking for a pom file (if I haven't
built the MSS myself)? I believe we need to minimally include the
jar-plugin configuration.


>
>
>
>>
>> On Thu, Jan 7, 2016 at 10:50 AM, Dimuthu Leelarathne 
>> wrote:
>>
>>> Hi,
>>>
>>> Additionally I don't think the MSS samples are very developer friendly.
>>> I think we have gone too far to minimize pom.xmls.
>>>
>>> 1 - In deployble-jar sample I was trying to figure out which plugin is
>>> copying the property "Microservices" to the MANIFEST.MF file. The following
>>> very important plugin is missing in the immediate pom file and hence the
>>> sample is not very useful.
>>>
>>> 
>>> org.apache.maven.plugins
>>> maven-jar-plugin
>>> 
>>> 
>>> 
>>> $
>>> {microservice.resourceClasses}
>>>
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>> 2 - Bunle sample is worse. I had to trace back to following pom to take
>>> the bundle plugin (with Samiyuru's help).
>>>
>>> org.wso2
>>> wso2
>>> 2
>>>
>>>
>>> thanks,
>>>
>>> Dimuthu
>>>
>>>
>>>
>>> On Wed, Jan 6, 2016 at 11:18 PM, Afkham Azeez  wrote:
>>>
 DimuthuL reported that in the case of deployable jar mode, the classes
 coming from OSGi bundles in the enviroment are not visible to the classes
 inside the deployable jar. I think this is a blocker for the release.

 On Wed, Jan 6, 2016 at 3:29 PM, Samiyuru Senarathne 
 wrote:

> Hi Devs,
>
> This is the 2nd Release Candidate of WSO2 Microservices Server 1.0.0.
>
> Please download, test the product and vote.
>
> *​Source and binary distribution files:*
> https://github.com/wso2/product-mss/releases/tag/v1.0.0-RC2
> 
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-274
>
> *The tag to be voted upon:*
> *https://github.com/wso2/product-mss/tree/v1.0.0-RC2
> *
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Note: Since the artifacts that have to be uploaded to the maven
> central are not yet uploaded please make sure to first build the project
> from the source in order to make all artifacts available in the maven
> local repository.
>
> Thank you,
> Carbon Team
>
> --
> Samiyuru Senarathne
> *Software Engineer*
> Mobile : +94 (0) 71 134 6087
> samiy...@wso2.com
>



 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * *
 *email: **az...@wso2.com* 
 * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
 *http://blog.afkham.org* 
 *twitter: **http://twitter.com/afkham_azeez*
 
 *linked-in: **http://lk.linkedin.com/in/afkhamazeez
 *

 *Lean . Enterprise . Middleware*

>>>
>>>
>>>
>>> --
>>> Dimuthu Leelarathne
>>> Director
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: dimut...@wso2.com
>>> Mobile : 0773661935
>>>
>>> Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> Dimuthu Leelarathne
> Director
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
> Mobile : 0773661935
>
> Lean . Enterprise . Middleware
>



-- 
Dimuthu Leelarathne
Director

WSO2, Inc. 

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC2

[Afkham Azeez]

We prefer that people don't copy & paste loads of XML, make mistakes, and
make it difficult for us to make changes in the future, and we prefer to
simply document the relevant properties people need to be aware of to make
their life easy.

On Thu, Jan 7, 2016 at 12:09 PM, Dimuthu Leelarathne 
wrote:

> I prefer not to search internet for a pom/plugin when I have not built MSS.
>
> On Thu, Jan 7, 2016 at 12:02 PM, Afkham Azeez  wrote:
>
>> What you are saying is, you don't like;
>>
>> 
>> 
>> org.wso2.carbon.mss.example.Application
>> 
>>
>>
>> You prefer;
>>
>> 
>> org.apache.maven.plugins
>> maven-shade-plugin
>> 
>> 
>> package
>> 
>> shade
>> 
>> 
>> 
>> 
>> *:*
>> 
>> META-INF/*.SF
>> META-INF/*.DSA
>> META-INF/*.RSA
>> 
>> 
>> 
>> 
>> > 
>> implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
>> ${microservice.mainClass}
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> and you want to copy and paste all this every time.
>>
>>
>>
>> On Thu, Jan 7, 2016 at 11:51 AM, Dimuthu Leelarathne 
>> wrote:
>>
>>>
>>>
>>> On Thu, Jan 7, 2016 at 11:18 AM, Afkham Azeez  wrote:
>>>
 No I totally disagree with you. We have made our POMs less verbose so
 that the developers can focus on what is necessary. We put in a lot of
 thought before going for this minimized POMs. Instead of copying & pasting
 a lot of XML, you focus on only the bits that are relevant to your
 microservice bundle or jar. With some basic Maven knowledge, you can figure
 out from where the relevant plugins are inherited.

>>>
>>>
>>> Yes. One can figure out. But, not developer friendly. IMO, we need to
>>> include the jar-plugin configuration. That is not making it verbose, but
>>> rather user friendly.
>>>
>>>
>>>

 On Thu, Jan 7, 2016 at 10:50 AM, Dimuthu Leelarathne  wrote:

> Hi,
>
> Additionally I don't think the MSS samples are very developer
> friendly. I think we have gone too far to minimize pom.xmls.
>
> 1 - In deployble-jar sample I was trying to figure out which plugin is
> copying the property "Microservices" to the MANIFEST.MF file. The 
> following
> very important plugin is missing in the immediate pom file and hence the
> sample is not very useful.
>
> 
> org.apache.maven.plugins
> maven-jar-plugin
> 
> 
> 
> $
> {microservice.resourceClasses}
>
> 
> 
> 
> 
> 
>
> 2 - Bunle sample is worse. I had to trace back to following pom to
> take the bundle plugin (with Samiyuru's help).
>
> org.wso2
> wso2
> 2
>
>
> thanks,
>
> Dimuthu
>
>
>
> On Wed, Jan 6, 2016 at 11:18 PM, Afkham Azeez  wrote:
>
>> DimuthuL reported that in the case of deployable jar mode, the
>> classes coming from OSGi bundles in the enviroment are not visible to the
>> classes inside the deployable jar. I think this is a blocker for the
>> release.
>>
>> On Wed, Jan 6, 2016 at 3:29 PM, Samiyuru Senarathne <
>> samiy...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 2nd Release Candidate of WSO2 Microservices Server 1.0.0.
>>>
>>> Please download, test the product and vote.
>>>
>>> *​Source and binary distribution files:*
>>> https://github.com/wso2/product-mss/releases/tag/v1.0.0-RC2
>>> 
>>>
>>> *Maven staging repository:*
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-274
>>>
>>> *The tag to be voted upon:*
>>> *https://github.com/wso2/product-mss/tree/v1.0.0-RC2
>>> *
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>> Note: Since the artifacts that have to be uploaded to the maven
>>> central are not yet uploaded please make sure to first build the project
>>> from the source in order to make all artifacts available in the
>>> maven local repository.
>>>
>>> Thank you,
>>> Carbon Team
>>>
>>> --
>>> Samiyuru Senarathne
>>> *Software Engineer*
>>> Mobile : +94 (0) 71 134 6087
>>> samiy...@wso2.com
>>>
>>
>>
>>
>> --
>> 

[Dev] [DAS] Able to update spark scripts published through a capp

[Udara Rathnayake]

Hi,

As per the doc[1], we are restricting users to edit/delete artifacts
published through capp.
But it seems we can update spark scripts(published through a capp) though
management console.

If this is the expected behavior let's update the doc.

[1]
https://docs.wso2.com/display/DAS300/Packaging+Artifacts+as+a+C-App+Archive

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

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC4

[Abimaran Kugathasan]

Tested Following

1. Default Endpoint
2. API Subscription/deletion/blocking/unblocking with H2 and MySQL

[x]  Stable - go ahead and release.

On Wed, Jan 6, 2016 at 9:02 AM, Roshan Wijesena  wrote:

> Hi,
>
> Tested API create/subscribe/invoke flow and map existing auth app with
> pre-generated keys by creating a service provider manually in
> carbon-console.
> No issues found.
>
> [x]  Stable - go ahead and release.
>
> -Roshan
>
> On Wed, Jan 6, 2016 at 10:27 AM, Shani Ranasinghe  wrote:
>
>> Tested HTTP redirect in super tenant & tenant mode. No issues found,
>> Tested sample API. No issues found.
>>
>> [x]  Stable - go ahead and release
>>
>> On Wed, Jan 6, 2016 at 9:50 PM, Harsha Kumara  wrote:
>>
>>> Tested the prototype APIs in Tenant and Super Tenant. No issue found.
>>>
>>> [x]  Stable - go ahead and release
>>>
>>> Thanks
>>> Harsha
>>>
>>> On Wed, Jan 6, 2016 at 9:28 PM, Tharindu Dharmarathna <
>>> tharin...@wso2.com> wrote:
>>>
 Tested the IS as a Keymanager and SSO . No issue found.

 [x]  Stable - go ahead and release

 Thanks
 Tharindu


 On Wed, Jan 6, 2016 at 9:22 PM, Bhathiya Jayasekara 
 wrote:

> Smoke tested. No issues found.
>
> [x]  Stable - go ahead and release
>
> Thanks,
> Bhathiya
>
> On Wed, Jan 6, 2016 at 6:28 PM, Chamila Adhikarinayake <
> chami...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> This is the fourth release candidate of WSO2 API Manager 1.10.0.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12597
>>
>> Please download, test and vote.
>>
>> Binary distribution files:
>> http://svn.wso2.org/repos/wso2/people/chamilaa/apim-1.10.0-rc4/
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-apim/tree/v1.10.0-rc4
>>
>>
>> [ ]  Stable - go ahead and release
>> [ ]  Broken - do not release (explain why)
>>
>> Thanks and Regards,
>> WSO2 API Manager Team
>>
>> --
>> Regards,
>> Chamila Adhikarinayake
>> Software Engineer
>> WSO2, Inc.
>> Mobile - +94712346437
>> Email  - chami...@wso2.com
>> Blog  -  http://helpfromadhi.blogspot.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Bhathiya Jayasekara*
> *Senior Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <%2B94715478185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax
> *
> *Blog: http://movingaheadblog.blogspot.com
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --

 *Tharindu Dharmarathna*Associate Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: *+94779109091 <%2B94779109091>*

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


>>>
>>>
>>> --
>>> Harsha Kumara
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94775505618
>>> Blog:harshcreationz.blogspot.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks and Regards
>> *,Shani Ranasinghe*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 77 2273555
>> Blog: http://waysandmeans.blogspot.com/
>> linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Roshan Wijesena.
> Senior Software Engineer-WSO2 Inc.
> Mobile: *+94719154640 <%2B94719154640>*
> Email: ros...@wso2.com
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks
Abimaran Kugathasan

Software Engineer | WSO2 Inc
Data & APIs Technologies Team
Mobile : +94 773922820


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

Re: [Dev] [DAS] Able to update spark scripts published through a capp

[Inosh Goonewardena]

No it is not the expected behavior. I think you are experiencing the
similar issue reported here [1]. Please use the capp name as Capp artifact
name [2].

[1] - https://wso2.org/jira/browse/DAS-284
[2] -
https://github.com/wso2/product-das/commit/10bba4cd28623fc3fe7b4caec17874ee1bc6c991

On Wed, Jan 6, 2016 at 2:35 PM, Udara Rathnayake  wrote:

> Hi,
>
> As per the doc[1], we are restricting users to edit/delete artifacts
> published through capp.
> But it seems we can update spark scripts(published through a capp) though
> management console.
>
> If this is the expected behavior let's update the doc.
>
> [1]
> https://docs.wso2.com/display/DAS300/Packaging+Artifacts+as+a+C-App+Archive
>
> --
> Regards,
> UdaraR
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

Inosh Goonewardena
Associate Technical Lead- WSO2 Inc.
Mobile: +94779966317
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS] Able to update spark scripts published through a capp

[Udara Rathnayake]

Thanks Inosh.

On Wed, Jan 6, 2016 at 3:53 PM, Inosh Goonewardena  wrote:

> No it is not the expected behavior. I think you are experiencing the
> similar issue reported here [1]. Please use the capp name as Capp artifact
> name [2].
>
> [1] - https://wso2.org/jira/browse/DAS-284
> [2] -
> https://github.com/wso2/product-das/commit/10bba4cd28623fc3fe7b4caec17874ee1bc6c991
>
> On Wed, Jan 6, 2016 at 2:35 PM, Udara Rathnayake  wrote:
>
>> Hi,
>>
>> As per the doc[1], we are restricting users to edit/delete artifacts
>> published through capp.
>> But it seems we can update spark scripts(published through a capp) though
>> management console.
>>
>> If this is the expected behavior let's update the doc.
>>
>> [1]
>> https://docs.wso2.com/display/DAS300/Packaging+Artifacts+as+a+C-App+Archive
>>
>> --
>> Regards,
>> UdaraR
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
>
> Inosh Goonewardena
> Associate Technical Lead- WSO2 Inc.
> Mobile: +94779966317
>



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