[Dev] App Manager 1.1.0 latest build pack - 16-12-2015

[Dinusha Senanayaka]

Hi,

Please find $subject in [1].

[1]
http://builder1.us1.wso2.org/~appm/release-1.1.0/16-12-2015/wso2appm-1.1.0-SNAPSHOT-16-12-2015.zip

Regards,
Dinusha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Carbon Kernel 5.0.0 RC1

[Aruna Karunarathna]

Hi Devs,

This is the 1st Release Candidate of WSO2 Carbon Kernel 5.0.0.

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

Please download and test your products with kernel 5.0.0 RC1
and vote. Vote will be open for 72 hours or as longer as needed.

*​Source and binary distribution files:*
https://github.com/wso2/carbon-kernel/releases/download/v5.0.0-RC1/wso2carbon-kernel-5.0.0-rc1.zip

*Maven staging repository:*
http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-177/

*The tag to be voted upon:*
https://github.com/wso2/carbon-kernel/releases/tag/v5.0.0-RC1


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

Thank you,
Carbon Team
-- 

*Aruna Sujith Karunarathna *| Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 9040362 | Work: +94 112145345
Email: ar...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PPaaS Artifact Migration Tool

[Nishadi Kirielle]

Hi Imesh,

In the mapping between cartridges, there's a conflict between the
Persistence.class of PPaaS 4.0.0 (package
org.apache.stratos.cloud.controller.stub.pojo) and the
PersistenceBean.class of PPaaS 4.1.0 (package
org.apache.stratos.common.beans.cartridge).

PersistenceBean
  -isRequired

Persistence
  -localPersistanceRequired
  -localPersistanceRequiredTracker
  -localVolumesTracker


Out of the above mentioned artifacts of PPaaS 4.1.0, what should be
mapped with isRequired artifact of PPaaS 4.1.0?

Thank you


On Wed, Dec 16, 2015 at 10:04 AM, Nishadi Kirielle  wrote:
> Hi Imesh,
>
> We will send a pull request as soon as possible. The remaining tasks and the
> rough time plan as follows;
>
> 2015/12/16
> 1. Update the bean classes and add dependencies
> 2. Add test cases
> 3. Make the file names configurable via a configuration file
>
> 2015/12/17
> 4. Update errors in exception handling
> 5. Update autoscaling policy mapping using average values
> 6. Add default values to missing artifacts
>
> 2015/12/18
> 7. Use of Apache http client library to write the rest client
> 8. Update deploying scripts
>
> Thanks
>
> On Tue, Dec 15, 2015 at 4:33 PM, Imesh Gunaratne  wrote:
>>
>> Thanks Nishadi, may be you can update the same PR or send a new one with
>> the improvements. Please try to list down the remaining tasks and a rough
>> time plan.
>>
>> Thanks
>>
>> On Tue, Dec 15, 2015 at 1:42 PM, Nishadi Kirielle 
>> wrote:
>>>
>>> Hi,
>>> We have implemented the conversion of cartridge subscription artifacts to
>>> application signups and domain mapping subscriptions. In addition, we were
>>> able to integrate the https connection with the tool.[1] Currently, we are
>>> trying to deploy the artifacts in PPaaS 4.1.0.
>>>
>>> [1]
>>> https://github.com/nishadi/product-private-paas/tree/master/tools/migration/ppaas-artifact-converter
>>>
>>> Thanks
>>>
>>> On Tue, Dec 15, 2015 at 12:55 PM, Imesh Gunaratne  wrote:

 Hi Nishadi,

 Would you mind sharing the latest status of your efforts on this?

 Thanks

 On Wed, Dec 9, 2015 at 3:48 PM, Akila Ravihansa Perera
  wrote:
>
> Hi,
>
> Here are some important improvements that you can do to boost your
> development productivity and stability of the tool.
>
> 1. Develop a set of Unit tests with an embedded web container to mock
> the PPaaS API.
>
>  - I've already done this as a demo for you to take as a reference
> guide at [1]. I've used Jetty web container as an embedded server in my
> JUnit test case to mock the API. I've hosted partition list API in my test
> server and assert whether artifact loader reads the partition list
> correctly.
>
> Advantage of this approach is that when you build your tool, it will
> compile the code, test and validate the functionality and package. You 
> don't
> need to test the tool manually which is very time consuming. You may have 
> to
> refactor/re-organize stuff I've developed to make things clean.
>
> 2. Create a class ArtifactConverterRestClient as a wrapper around
> HttpClient library and use it to fetch resources from Stratos API. You can
> create methods like getPartitionList, getAutoscalePolicyList etc. in this.
> Decouple your conversion logic from data transfer layer much as possible.
> This will make it easy for you to write tests.
>
>
> 3. Always use HTTPS if you are sending/receiving sensitive information.
> In current implementation the tool is passing authentication credentials 
> to
> the server, therefore transport should be secure.
>
> 4. Make user input parameters configurable via configuration files.
> Currently the tool expects username, password, url etc. as user inputs.
> Make it read these values from a properties file and prompt only if those
> values are missing.
>
> [1] https://github.com/nishadi/product-private-paas/pull/1
>
> Thanks.
>
> On Mon, Dec 7, 2015 at 12:19 PM, Nishadi Kirielle 
> wrote:
>>
>> Hi,
>>
>> Thank you for the feedback.
>>
>> @Imesh:
>> I have updated the README file[1] in mark down text format and will
>> start writing the Wiki page.
>>
>> @Gayan:
>> In the initial version, we have used sample json files as templates
>> and used them to be default values. But as it has some conflicts, we have
>> removed the use of template files. The current approach is to fetch the
>> artifacts from the PPaaS 4.0.0 and convert it to PPaaS 4.1.0 without 
>> using
>> any default values. I have updated the READ ME file [1]
>>
>> @Isuru:
>> I will take the approach proposed to handle exceptions in
>> OldArtifactLoader by wrapping them in a custom exception and update it. I
>> will update the log4j properties file to be in the conf directory.
>>
>> [1]
>> https://github.com/nishadi/product-pri

[Dev] Best way to access registry data in java

[Ishara Cooray]

I have a .xml policy file stored in super tenant's registry. I need to read
the file only once at the bundle activation.

I was trying following approaches but none of them give me the resource i
am looking for.

1.







*RegistryService registryService =
ThrottleDataHolder.getRegistryService();Registry registry =
null;try {registry =
registryService.getGovernanceSystemRegistry(Constants.SUPER_TENANT_ID);
} catch (RegistryException e) {log.error("Error while fetching
Governance Registry of Super Tenant");}*

*   String path =
"gov:/apimgt/applicationdata/tenant_tier_policies.xml";*






*try {if (registry.resourceExists(path))
{return registry.get(path);}
} catch (RegistryException e) {log.error("Error while
fetching the resource " + path, e);}*

In this case resourceExists returns false.

2.



*Registry governanceRegistry =
getSuperTenantRegistry();//as abovePolicyManager
policyManager = new PolicyManager(governanceRegistry);
Policy policy = policyManager.getPolicy(Constants.POLICY_KEY); *
In this case policy is null.

3.



















*   String url = "https://192.168.123.100:9443/registry
";String username =
Constants.SUPER_USER_NAME;String password =
Constants.SUPER_USER_PW;
System.setProperty(Constants.CARBON_REPO_WRITE_MODE, "true");
Registry rootRegistry = null;try {rootRegistry
= new RemoteRegistry(new URL(url), username, password);} catch
(RegistryException e) {e.printStackTrace();}
catch (MalformedURLException e) {
e.printStackTrace();}String policyContent =
null;OMElement policyElement = null;try {
PolicyManager policyManager = new
PolicyManager(rootRegistry);Policy policy =
policyManager.getPolicy(Constants.POLICY_KEY);//get the OM
from the policy.policyContent = policy.getPolicyContent();*

In this case it hangs at policyManager.getPolicy(Constants.POLICY_KEY);

Wondering what is the proper way of doing this.
Any help would be appreciated.

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

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Cyril Rognon]

Hi

DB mediator can be handy as you said but it is a bad  practice to query the
DB right from the Esb. It is against the low coupling principles that makes
integration  layer agile and   thin and scalable etc.

DSS is setup in two  minutes and can fulfill your needs   out of the box.

Maybe we should provide a migration tool to turn  DBMediator usage into
Daraservices operation  call.  One could even  generate the dbs Dataservice
definition from the DBMediator.

+1 for deprecating these  mediators.  Setup some tool or complete
documentation to migrate existing usage.

Thanks,
Cyril
Le 9 déc. 2015 13:55, "Malaka Silva"  a écrit :

> In my experience using ​DB mediator we can cover some of the use cases
> using ESB out of the box, which I find very handy.
>
> Also use case of integrating with stored procs can easily covered with
> this.
>
> However there are limits like batch update or getting multiple rows.
>
> ​I guess we can argue both ways. IMO we should keep these mediators since
> it'll become handy for some use cases :)
>
> On Wed, Dec 9, 2015 at 4:58 PM, Kasun Indrasiri  wrote:
>
>>
>>
>> On Wed, Dec 9, 2015 at 3:32 PM, Malaka Silva  wrote:
>>
>>> +1 except  DBReport/DBLookup mediators
>>>
>>> DBReport and DBLookup only offer a very limited set of capabilities.
>> IMO, for any real integration scenario, we can't use them.  :).
>>
>>> On Wed, Dec 9, 2015 at 2:00 PM, Yumani Ranaweera 
>>> wrote:
>>>
 Is it possible to provide sufficient documentation to help the
 customers who would be migrating in future.

 Thanks,
 Yumani


 On Wed, Dec 9, 2015 at 1:45 PM, Chanaka Fernando 
 wrote:

> *- Callout mediator :*
>  All the callout functionality is supported with 'call' mediator with
> blocking=true. Having two similar mediators will be create a bit of a
> confusion.
>
> It will make a lot of confusion when we have more than one mediators
> to do the same thing. Therefore, better to deprecate this mediator.
>
> *- DBReport/DBLookup mediator*
> These mediators offer very limited functionality and we always
> recommend to integrate with databases with the use of DSS (using a 
> separate
> DSS or using DSS features inside ESB)
>
> Even though this mediator has been used by some customers, they are
> using that for very limited functionality and we always suggest them to 
> use
> DSS as Kasun mentioned. If users really want to connect to a database, 
> they
> can easily write a simple class mediator.
>
> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
> development happens on these.
> *- Router* : Same as filter mediator, so no use of having this.
> *- In, Out * : Rarely used and often not required with the new
> call/respond mediator approach.
>
> +1 for deprecating these mediators.
>
> With the new DAS integration, we can deprecate BAM mediator since we
> have the PublishEvent mediator.
>
> On Wed, Dec 9, 2015 at 6:41 AM, Kasun Indrasiri 
> wrote:
>
>> Shall we deprecate following mediators in 4.10 release.
>>
>> *- Callout mediator :*
>>  All the callout functionality is supported with 'call' mediator with
>> blocking=true. Having two similar mediators will be create a bit of a
>> confusion.
>>
>> *- DBReport/DBLookup mediator*
>> These mediators offer very limited functionality and we always
>> recommend to integrate with databases with the use of DSS (using a 
>> separate
>> DSS or using DSS features inside ESB)
>>
>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>> development happens on these.
>> *- Router* : Same as filter mediator, so no use of having this.
>> *- In, Out * : Rarely used and often not required with the new
>> call/respond mediator approach.
>>
>> Any comments  on these or any other features that we should deprecate
>> from 4.10 release?
>>
>> Thanks,
>> Kasun.
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --


 *Yumani Ranaweera* | Technical Lead
 Technical Support- Colombo
 WSO2 Inc. |  http://wso2.com

[Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC1

[Gayan Gunarathne]

 Hi All,

This is the first release candidate of WSO2 Private PaaS 4.1.1.

This release fixes the following issues:
*https://wso2.org/jira/browse/PAAS-305?filter=12582
*

Please download, test and vote. The vote will be open for 72 hours or as
needed.

*​Source and binary distribution files:*
https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.1-rc1/

*Maven staging repository:*
http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-181/

*The tag to be voted upon:*
https://github.com/wso2/product-private-paas/tree/v4.1.1-rc1


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


Thanks,
The WSO2 Private PaaS Team

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Kasun Indrasiri]

@Kathees : Can we verify NTLM use cases with Call mediator + blocking
behavior? I guess it should work out of box as we also reuse the same
blocking sender code?

For DB* mediators, I guess we can clearly mention in the docs that these
mediators can be only used for very limited kind of DB operations but not
for any complex DB integrations we must use DSS. And we won't any such
features to DB* mediators.

POJO/Spring mediators seems to need more attention :) and we should enhance
them with proper use case docs.

WDYT?

On Fri, Dec 11, 2015 at 1:28 AM, Dulitha Wijewantha 
wrote:

>
>
> On Thu, Dec 10, 2015 at 1:26 AM, Vidura Gamini Abhaya 
> wrote:
>
>> Hi Isuru,
>>
>> I've used it in a mediation sequence where I use a POJO to generate a
>> unique customer id given a couple of parameters and there's a checksum
>> added to the end. I already had written this code and it was quite simple
>> and straightforward to reuse it with a POJOCommand mediator. I feel the
>> simplicity of it is a welcome feature, where reading and setting values in
>> MessageContext is automatically handled for me.
>>
>> I don't know whether a single usage case is enough to make the case to
>> keep it. However, if we decide to keep it though, I suggest that we improve
>> the documentation on it. I had to dig around to find out how the what the
>> different actions mean. It wasn't clear to me in the docs (I believe most
>> of the content is carried forward from Syanpse).
>>
>
> +1 for deprecating POJO Mediator. ​The problem I find with the above
> approach is that - there is an alternative way of doing it (using class
> mediators). Not having multiple options (to do the same thing) in a
> configurational language makes it easier for development, maintenance,
> training etc. An example will be - POJOMediator can use expressions where
> Class mediators you can't (making things confusing). It's better to push
> the point home saying - the way to write custom code in the ESB (if you
> have to) is using a class mediator and the message context api.
>
> Apart from that - I believe in the POJO mediator we create multiple
> objects in the heap? Where as in the class mediator we just create once
> instance. Am I correct on this observation?
>
> I am -1 for deprecating Db mediators. Like Malaka said, they are very
> useful in scenarios where people want to connect to databases (also can be
> used in conjunction with cache mediator for performance).
>
>
>>
>> Thanks and Regards,
>>
>> Vidura
>>
>>
>>
>> On 10 December 2015 at 10:57, Isuru Udana  wrote:
>>
>>> Hi Kathees,
>>>
>>> I think we should do a comparison once more to make sure that we have
>>> covered everything before removing Callout. NTLM one which Harshana pointed
>>> out may be due to absence of initClientOptions configuration option.
>>>
>>> Hi Vidura,
>>> Point you raised on the POJOCommand mediator is really interesting. We
>>> haven't seen any usage of that over years. But now we found at least one
>>> user who has found it useful. Thanks for pointing that out. So we should
>>> reconsider how useful it is.
>>>
>>> Thanks.
>>>
>>>
>>>
>>> On Thu, Dec 10, 2015 at 10:39 AM, Kathees Rajendram 
>>> wrote:
>>>
 +1 to deprecate Callout mediator since we have the Callout mediator
 functionalities in Call mediator.

 On Thu, Dec 10, 2015 at 1:18 AM, Vidura Gamini Abhaya 
 wrote:

> I've found DBReport / DBLookup to be quite useful for simple DB
> operations as they are easy to do OOTB. While DB Lookup mediator maybe
> limited in it's ability to only being able to return a single row of data,
> DB Report mediator is still quite useful in writing to a database,
> especially when we use a DB as part of the mediation sequences.
>
> I also feel it is worth continuing with POJOCommand, as it is the most
> simplest way of executing some custom code as part of a sequence. Although
> it is possible to do the same with a Class mediator, one doesn't have to
> worry about adding the proper jars, working with MessageContext etc. with
> the POJOCommand. I think we should retain it for the sake of simplicity of
> use.
>
> I'm +1 to deprecate the rest of the mediators.
>
> Thanks,
>
> Vidura
>
>
>
> On 9 December 2015 at 12:11, Kasun Indrasiri  wrote:
>
>> Shall we deprecate following mediators in 4.10 release.
>>
>> *- Callout mediator :*
>>  All the callout functionality is supported with 'call' mediator with
>> blocking=true. Having two similar mediators will be create a bit of a
>> confusion.
>>
>> *- DBReport/DBLookup mediator*
>> These mediators offer very limited functionality and we always
>> recommend to integrate with databases with the use of DSS (using a 
>> separate
>> DSS or using DSS features inside ESB)
>>
>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>> development happens on these.
>> *-

Re: [Dev] WSO2 Committers += Indunil Upeksha Rathnayake

[Imesh Gunaratne]

Congratulations Indunil!

On Tue, Dec 15, 2015 at 11:07 AM, Johann Nallathamby 
wrote:

> Hi All,
>
> It's my pleasure to announce Indunil Upeksha Rathnayake as a WSO2
> Committer. Indunil has been a valuable contributor for WSO2 Identity
> Server product, and in recognition of her contribution to WSO2, she
> has been voted as a WSO2 Committer.
>
> Indunil, congratulations and keep up the good work!
>
> Thanks & Regards.
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Technical Lead & Product Lead of WSO2 Identity Server
> Governance Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PPaaS Artifact Migration Tool

[Nishadi Kirielle]

Hi Imesh,

We will send a pull request as soon as possible. The remaining tasks and
the rough time plan as follows;

2015/12/16
1. Update the bean classes and add dependencies
2. Add test cases
3. Make the file names configurable via a configuration file

2015/12/17
4. Update errors in exception handling
5. Update autoscaling policy mapping using average values
6. Add default values to missing artifacts

2015/12/18
7. Use of Apache http client library to write the rest client
8. Update deploying scripts

Thanks

On Tue, Dec 15, 2015 at 4:33 PM, Imesh Gunaratne  wrote:

> Thanks Nishadi, may be you can update the same PR or send a new one with
> the improvements. Please try to list down the remaining tasks and a rough
> time plan.
>
> Thanks
>
> On Tue, Dec 15, 2015 at 1:42 PM, Nishadi Kirielle 
> wrote:
>
>> Hi,
>> We have implemented the conversion of cartridge subscription artifacts
>> to application signups and domain mapping subscriptions. In addition, we
>> were able to integrate the https connection with the tool.[1] Currently, we
>> are trying to deploy the artifacts in PPaaS 4.1.0.
>>
>> [1]
>> https://github.com/nishadi/product-private-paas/tree/master/tools/migration/ppaas-artifact-converter
>>
>> Thanks
>>
>> On Tue, Dec 15, 2015 at 12:55 PM, Imesh Gunaratne  wrote:
>>
>>> Hi Nishadi,
>>>
>>> Would you mind sharing the latest status of your efforts on this?
>>>
>>> Thanks
>>>
>>> On Wed, Dec 9, 2015 at 3:48 PM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
 Hi,

 Here are some important improvements that you can do to boost your
 development productivity and stability of the tool.

 1. Develop a set of Unit tests with an embedded web container to mock
 the PPaaS API.

  - I've already done this as a demo for you to take as a reference
 guide at [1]. I've used Jetty web container as an embedded server in my
 JUnit test case to mock the API. I've hosted partition list API in my test
 server and assert whether artifact loader reads the partition list
 correctly.

 Advantage of this approach is that when you build your tool, it will
 compile the code, test and validate the functionality and package. You
 don't need to test the tool manually which is very time consuming. You may
 have to refactor/re-organize stuff I've developed to make things clean.

 2. Create a class ArtifactConverterRestClient as a wrapper around
 HttpClient library and use it to fetch resources from Stratos API. You can
 create methods like getPartitionList, getAutoscalePolicyList etc. in this.
 Decouple your conversion logic from data transfer layer much as possible.
 This will make it easy for you to write tests.


 3. Always use HTTPS if you are sending/receiving sensitive information.
 In current implementation the tool is passing authentication credentials to
 the server, therefore transport should be secure.

 4. Make user input parameters configurable via configuration files.
 Currently the tool expects username, password, url etc. as user inputs.
 Make it read these values from a properties file and prompt only if those
 values are missing.

 [1] https://github.com/nishadi/product-private-paas/pull/1

 Thanks.

 On Mon, Dec 7, 2015 at 12:19 PM, Nishadi Kirielle 
 wrote:

> Hi,
>
> Thank you for the feedback.
>
> @Imesh:
> I have updated the README file[1] in mark down text format and will
> start writing the Wiki page.
>
> @Gayan:
> In the initial version, we have used sample json files as templates
> and used them to be default values. But as it has some conflicts, we have
> removed the use of template files. The current approach is to fetch the
> artifacts from the PPaaS 4.0.0 and convert it to PPaaS 4.1.0 without using
> any default values. I have updated the READ ME file [1]
>
> @Isuru:
> I will take the approach proposed to handle exceptions in
> OldArtifactLoader by wrapping them in a custom exception and update it. I
> will update the log4j properties file to be in the conf directory.
>
> [1]
> https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/README
>
> Thank you,
> Nishadi
>
> On Sun, Dec 6, 2015 at 9:28 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Malmee and Nishadi,
>>
>> Good progress in a short time!
>>
>> Had a glance at the code, couple of things I noticed:
>>
>>1. log4j.properties file is available under conf directory as
>>well as the resources directory. Ideally should be in conf directory.
>>2. In the class OldArtifactLoader [1], the methods are throwing
>>IOException in an error scenario. A better approach would be to wrap 
>> that
>>with a custom exception (ex.: ArtifactLoadingException, etc.) an

Re: [Dev] Need help from DS team to fix Analytics Dashboard issues which are related to DS

[Nipuna Chandradasa]

Hi,

I fixed this  https://wso2.org/jira/browse/DAS-303 jira. I'll put a PR to
the carbon dashboard.

Thank you.

On Tue, Dec 15, 2015 at 11:16 AM, Sachith Withana  wrote:

> Hi all,
>
> I upgraded to the latest version and the issues
> https://wso2.org/jira/browse/DAS-326
> https://wso2.org/jira/browse/DAS-213
>
> seems to be fixed now.
>
> But, https://wso2.org/jira/browse/DAS-303 is still there.
>
>
> On Fri, Dec 11, 2015 at 10:55 AM, Anjana Fernando  wrote:
>
>> Okay, great! ..
>>
>> Cheers,
>> Anjana.
>>
>> On Fri, Dec 11, 2015 at 10:54 AM, Manuranga Perera  wrote:
>>
>>> Old model will still work, so upgrade to latest is the preferred option.
>>> Please try with latest and let us know if anything is broken, we can fix.
>>> On Dec 11, 2015 10:43 AM, "Anjana Fernando"  wrote:
>>>
 Also, these fixes need to be going with DAS 3.0.1, so we somewhat need
 these fixes to be done as a minor release to the earlier DS feature
 versions we used. Because, as I got to know from our last meeting with DS
 team, you guys are working on a modified approach for the gadget generation
 and all, which may not be compatible with our earlier model. @Sachith,
 please follow up on this.

 Cheers,
 Anjana.

 On Fri, Dec 11, 2015 at 3:12 AM, Dunith Dhanushka 
 wrote:

> Hi Manu,
>
> We need the help from DS team to fix following DAS Analytics Dashboard
> issues which are related to DS.
>
> https://wso2.org/jira/browse/DAS-326
> https://wso2.org/jira/browse/DAS-213
> https://wso2.org/jira/browse/DAS-303
>
> I believe most of the issues must have been fixed the latest code
> base. Appreciate if you can verify them from your end.
>
> --
> Regards,
>
> Dunith Dhanushka,
> Senior Software Engineer
> WSO2 Inc,
>
> Mobile - +94 71 8615744
> Blog - dunithd.wordpress.com 
> Twitter - @dunithd 
>



 --
 *Anjana Fernando*
 Senior Technical Lead
 WSO2 Inc. | http://wso2.com
 lean . enterprise . middleware

>>>
>>
>>
>> --
>> *Anjana Fernando*
>> Senior Technical Lead
>> WSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware
>>
>
>
>
> --
> Sachith Withana
> Software Engineer; WSO2 Inc.; http://wso2.com
> E-mail: sachith AT wso2.com
> M: +94715518127
> Linked-In: 
> https://lk.linkedin.com/in/sachithwithana
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nipuna Marcus
*Software Engineer*
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"
Mobile : +94 (0) 713 667906
nipu...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Dev studio errors and feedback

[Awanthika Senarath]

Hi Dulitha,

Find my responses in-line,

1) Can't have the same project name in the workspace. For example - I
create a project called gateway-dev and have gateway-car, gateway-synapse,
gateway-registry. I can't create a project with gateway-staging and have
gateway-car. Is this an eclipse limitation?
This is an eclipse limitation. Eclipse maintains a META file called
.project for each and every project and the name in this .project file
needs to be unique.

2) Can't have the same artifact name in the workspace. This one is bit
annoying. I renamed the project to gateway-dev-synapse and
gateway-staging-synapse. I can't have the api artifact with id.xml inside
dev project and staging project in the same namespace:- the car picking
form gets confused on the two assets. What's more - it will get corrupted
and not have anything at all from synapse to pick. Below is an error that
popped in the error console
Yes, car files import artifacts based on the artifact name and in the
artifact.xml of a car file it will list all the artifacts that needs to be
bundled in that particular car, hence the artifact names needs to be unique
for the car file. The error you have got is due to dev studio crashing
before the file system files are properly refreshed, OR an attempt to
manually edit the file system resources not via eclipse. Ideally this
should be resolved by refreshing the workspace files through eclipse (right
click the file and refresh)

3) Deleting a resource (API) got me below error -
Could you please let us know how to reproduce this? did you attempt to
rename the resource before deleting?

4) Bulk import for resources -
You are correct, this is a current limitation. You can import the
synapse configuration with multiple proxies in it and dev-studio will
generate the proxies for different artifacts in the synapse configuration.
But currently it is not supported to import multiple proxy.xml files
simultaneously.

Regards
Awanthika


Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Wed, Dec 16, 2015 at 6:25 AM, Dulitha Wijewantha 
wrote:

> Hi guys,
> I got some issues today working on the developer studio.
>
> 1) Can't have the same project name in the workspace. For example - I
> create a project called gateway-dev and have gateway-car, gateway-synapse,
> gateway-registry. I can't create a project with gateway-staging and have
> gateway-car. Is this an eclipse limitation?
>
> 2) Can't have the same artifact name in the workspace. This one is bit
> annoying. I renamed the project to gateway-dev-synapse and
> gateway-staging-synapse. I can't have the api artifact with id.xml inside
> dev project and staging project in the same namespace:- the car picking
> form gets confused on the two assets. What's more - it will get corrupted
> and not have anything at all from synapse to pick. Below is an error that
> popped in the error console -
>
> org.eclipse.core.runtime.CoreException: The file is not synchronized with
> the local file system.
> at
> org.eclipse.core.internal.filebuffers.ResourceTextFileBuffer.commitFileBufferContent(ResourceTextFileBuffer.java:338)
> at
> org.eclipse.core.internal.filebuffers.ResourceFileBuffer.commit(ResourceFileBuffer.java:325)
> at
> org.eclipse.ltk.core.refactoring.TextFileChange.commit(TextFileChange.java:233)
> at org.eclipse.ltk.core.refactoring.TextChange.perform(TextChange.java:240)
> at
> org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
> at
> org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
> at
> org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at
> org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306)
> at
> org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92)
> at
> org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at
> org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
> at
> org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
>
>
> org.eclipse.core.runtime.CoreException: The file is not synchronized with
> the local file system.
> at
> org.eclipse.core.internal.filebuffers.ResourceTextFileBuffer.commitFileBufferContent(ResourceTextFileBuffer.java:338)
> at
> org.eclipse.core.internal.filebuffers.ResourceFileBuffer.commit(ResourceFileBuffer.java:325)
> at
> org.eclipse.ltk.core.refactoring.TextFileChange.commit(TextFileChange.java:233)
> at org.eclipse.ltk.core.refactoring.TextChange.perform(TextChange.java:240)
> at
> org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
> at
> org.eclipse.ltk.core.refac

Re: [Dev] MSS-Petstore running in Linux

[Lakmal Warusawithana]

Hi Nanduni,

Will not merge this PR, we need more testing on skydns integration. (it is
not worked as expected) Can you send a PR for update README.md (in
deployment directory) for installation instruction for virtualbox, vagrant
for Linux, which you did.

On Wed, Dec 16, 2015 at 5:46 AM, Nanduni Nimalsiri  wrote:

> Hi,
>
> [1] is the PR for running WSO2 MSS Petstore sample in Linux. Instead of
> using vagrant, kubernetes is run locally via Docker.
>
> [1] https://github.com/wso2/product-mss/pull/80
>
> Could you please review and merge this.
>
> Thank you,
> Nanduni.
>
>
> *Nanduni Nimalsiri*
> Software Engineering Intern, WSO2 Inc. (http://wso2.com)
> email : nand...@wso2.com
> blog : http://nanduni.blogspot.com/
> mobile : +94714114256
>
>


-- 
Lakmal Warusawithana
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Dev studio errors and feedback

[Dulitha Wijewantha]

Hi guys,
I got some issues today working on the developer studio.

1) Can't have the same project name in the workspace. For example - I
create a project called gateway-dev and have gateway-car, gateway-synapse,
gateway-registry. I can't create a project with gateway-staging and have
gateway-car. Is this an eclipse limitation?

2) Can't have the same artifact name in the workspace. This one is bit
annoying. I renamed the project to gateway-dev-synapse and
gateway-staging-synapse. I can't have the api artifact with id.xml inside
dev project and staging project in the same namespace:- the car picking
form gets confused on the two assets. What's more - it will get corrupted
and not have anything at all from synapse to pick. Below is an error that
popped in the error console -

org.eclipse.core.runtime.CoreException: The file is not synchronized with
the local file system.
at
org.eclipse.core.internal.filebuffers.ResourceTextFileBuffer.commitFileBufferContent(ResourceTextFileBuffer.java:338)
at
org.eclipse.core.internal.filebuffers.ResourceFileBuffer.commit(ResourceFileBuffer.java:325)
at
org.eclipse.ltk.core.refactoring.TextFileChange.commit(TextFileChange.java:233)
at org.eclipse.ltk.core.refactoring.TextChange.perform(TextChange.java:240)
at
org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
at
org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
at
org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
at
org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306)
at
org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92)
at
org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
at
org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)


org.eclipse.core.runtime.CoreException: The file is not synchronized with
the local file system.
at
org.eclipse.core.internal.filebuffers.ResourceTextFileBuffer.commitFileBufferContent(ResourceTextFileBuffer.java:338)
at
org.eclipse.core.internal.filebuffers.ResourceFileBuffer.commit(ResourceFileBuffer.java:325)
at
org.eclipse.ltk.core.refactoring.TextFileChange.commit(TextFileChange.java:233)
at org.eclipse.ltk.core.refactoring.TextChange.perform(TextChange.java:240)
at
org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
at
org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
at
org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
at
org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306)
at
org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92)
at
org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
at
org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

3) Deleting a resource (API) got me below error -

 org.eclipse.swt.SWTException: Failed to execute runnable
(java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:4397)
at org.eclipse.swt.SWT.error(SWT.java:4312)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388)
at
org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.run(RefactoringWizardDialog2.java:331)
at
org.eclipse.ltk.ui.refactoring.RefactoringWizard.internalPerformFinish(RefactoringWizard.java:637)
at
org.eclipse.ltk.internal.ui.refactoring.ErrorWizardPage.performFinish(ErrorWizardPage.java:162)
at
org.eclipse.ltk.ui.refactoring.RefactoringWizard.performFinish(RefactoringWizard.java:710)
at
org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.okPressed(RefactoringWizardDialog2.java:468)
at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable

Re: [Dev] String plus compiles to append

[Afkham Azeez]

Yes, this has been the case for sometime where internally append is used.
Try the same with a loop.

On Tue, Dec 15, 2015 at 11:43 PM, Manuranga Perera  wrote:

> I have compiled following class using javac 1.6.0_38
>
> class X{
> public String m(String a, String b, String c){
> return a + b + c;
> }
> }
>
>
> and decoupled using javap
>
>
> class X {
>   X();
> Code:
>0: aload_0
>1: invokespecial #1  // Method
> java/lang/Object."":()V
>4: return
>
>   public java.lang.String m(java.lang.String, java.lang.String,
> java.lang.String);
> Code:
>0: new   #2  // class
> java/lang/StringBuilder
>3: dup
>4: invokespecial #3  // Method
> java/lang/StringBuilder."":()V
>7: aload_1
>8: invokevirtual #4  // Method
> java/lang/StringBuilder.append:(Ljava/lang/String;)Ljava/lang/StringBuilder;
>   11: aload_2
>   12: invokevirtual #4  // Method
> java/lang/StringBuilder.append:(Ljava/lang/String;)Ljava/lang/StringBuilder;
>   15: aload_3
>   16: invokevirtual #4  // Method
> java/lang/StringBuilder.append:(Ljava/lang/String;)Ljava/lang/StringBuilder;
>   19: invokevirtual #5  // Method
> java/lang/StringBuilder.toString:()Ljava/lang/String;
>   22: areturn
> }
>
> As you can see, there are three appends but only one StringBuilder
> objects. Therefor I purpose using plus instead of append in our code.
>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@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

[Dev] MSS-Petstore running in Linux

[Nanduni Nimalsiri]

Hi,

[1] is the PR for running WSO2 MSS Petstore sample in Linux. Instead of
using vagrant, kubernetes is run locally via Docker.

[1] https://github.com/wso2/product-mss/pull/80

Could you please review and merge this.

Thank you,
Nanduni.


*Nanduni Nimalsiri*
Software Engineering Intern, WSO2 Inc. (http://wso2.com)
email : nand...@wso2.com
blog : http://nanduni.blogspot.com/
mobile : +94714114256
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] HTTP event receiver to accept batch of same type events

[Udara Rathnayake]

Hi,

My requirement is to receive a set of events in a single request at DAS
side.
eg:- array of events

is $subject possible else what is the recommended approach other than a
http event receiver?

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

Re: [Dev] [PPaaS] Need to update the Cartridges to support latest Stratos PCA

[Chamila De Alwis]

I've pushed the relevant PCA changes under commits [1] - [5]. This makes it
possible for newer cartridges to work with PPaaS 4.1.0. The PCA will pass
the connected MB_IP to the service starter plugin, which will then be able
to write it to relevant places along with CONFIG_PARAM_MB_PORT.

[1] -
https://github.com/wso2/product-private-paas/commit/8bce7c87105ec0d35c942ba72cca5c17eb593c05
[2] -
https://github.com/wso2/product-private-paas/commit/347cfcb1775fa5db2483af29ec6302e392c6c9d9
[3] -
https://github.com/wso2/product-private-paas/commit/5b355234b788d36325c81836bccfe19998e57455
[4] -
https://github.com/wso2/product-private-paas/commit/c67aea52e7b371c03882e1d0a365ad45b429cd6e
[5] -
https://github.com/wso2/product-private-paas/commit/bd865fd0c4e7081d14fb12b95935917dd01eeebe


Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com



On Tue, Dec 15, 2015 at 11:26 PM, Pubudu Gunatilaka 
wrote:

> Hi,
>
> We can do the following changes to support backward compatibility of PCA.
>
> 1. Update new MB related values such as MB_URLS, MB-USERNAME, etc in
> start-agent.sh
>
> Start-agent script will read the env variables and update the agent.conf
> file in PCA. I have already done the fix for this in [1].
>
> 2. As we have forked the PCA for PPaas, we will be changing that as
> follows.
>
> Users can send MB_URLS or can send both MB_IP and MB_PORT. PCA will give
> the priority for MB_URLS over MB_IP and MB_PORT. PCA will change to handle
> both cases. If MB_URLS are sent, PCA will export one of the successful mb
> ips as MB_IP for the sake of the plugin. In the plugin we need to know any
> of the mb ips for the initialization of the cluster.
>
> With this change there is no need of changing the plugins and template
> modules. If any of the users need to change the default AMQP port, they can
> send that from the cartridge definition. Cartridge definition property
> values will be exported as ENV values and those will be used with the
> configurator when configuring the server.
>
> [1] -
> https://github.com/wso2/private-paas-cartridges/commit/23e6bcdb16d9a032a9f66883f41747469cf45708
>
> Thank you!
>
>
> On Tue, Dec 15, 2015 at 1:01 PM, Chamila De Alwis 
> wrote:
>
>> Hi,
>>
>> I've forked the PCA component and product and started working on the
>> fixes for the config compatibility. After that I will merge the other
>> critical fixes.
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> On Tue, Dec 15, 2015 at 12:59 PM, Imesh Gunaratne  wrote:
>>
>>> Hi All,
>>>
>>> The plan is to fork Apache Stratos python cartridge agent in WSO2
>>> Private PaaS product repository and fix this issue until Stratos community
>>> does another release fixing this. In addition this would add few
>>> performance improvements we did recently in cartridge agent until those are
>>> merged to upstream.
>>>
>>> Thanks
>>>
>>> On Tue, Dec 15, 2015 at 10:04 AM, Gayan Gunarathne 
>>> wrote:
>>>


 On Tue, Dec 15, 2015 at 9:35 AM, Imesh Gunaratne 
 wrote:

> Hi Gayan,
>
> It looks like this modification in cartridge agent is not backward
> compatible [1]. As a result users will need to upgrade all the existing
> cartridges to their latest versions to work with Private PaaS 4.1.1.
>
> IMO we need to fix first.
>
> [1]
> https://github.com/apache/stratos/commit/9c57c7d803f790078963861e553e5b79290d8f2d
>

 Yeah . We need to support MB IP and MB port in the case of that
 configurations are there.

>
> Thanks
>
> On Mon, Dec 14, 2015 at 7:38 PM, Gayan Gunarathne 
> wrote:
>
>> We found that we need to update the Cartridges to support the Stratos
>> Cartridge Agent 4.1.5.We need to update the startup handlers,sample
>> artifact json to support the ActiveMQ HA with WSO2 Cartridges.
>>
>> We will fix those changes and will do the WSO2 PPaaS Cartridges 4.1.3
>> release.
>>
>> [1]
>> https://github.com/wso2/private-paas-cartridges/blob/master/wso2esb/4.9.0/plugins/wso2esb-490-startup-handler.py#L76
>> [2]
>> https://github.com/wso2/private-paas-cartridges/blob/master/wso2esb/4.9.0/samples/kubernetes-clusters/kubernetes-cluster-1.json#L36
>>
>> Thanks,
>> Gayan
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead

[Dev] String plus compiles to append

[Manuranga Perera]

I have compiled following class using javac 1.6.0_38

class X{
public String m(String a, String b, String c){
return a + b + c;
}
}


and decoupled using javap


class X {
  X();
Code:
   0: aload_0
   1: invokespecial #1  // Method
java/lang/Object."":()V
   4: return

  public java.lang.String m(java.lang.String, java.lang.String,
java.lang.String);
Code:
   0: new   #2  // class java/lang/StringBuilder
   3: dup
   4: invokespecial #3  // Method
java/lang/StringBuilder."":()V
   7: aload_1
   8: invokevirtual #4  // Method
java/lang/StringBuilder.append:(Ljava/lang/String;)Ljava/lang/StringBuilder;
  11: aload_2
  12: invokevirtual #4  // Method
java/lang/StringBuilder.append:(Ljava/lang/String;)Ljava/lang/StringBuilder;
  15: aload_3
  16: invokevirtual #4  // Method
java/lang/StringBuilder.append:(Ljava/lang/String;)Ljava/lang/StringBuilder;
  19: invokevirtual #5  // Method
java/lang/StringBuilder.toString:()Ljava/lang/String;
  22: areturn
}

As you can see, there are three appends but only one StringBuilder objects.
Therefor I purpose using plus instead of append in our code.



--
With regards,
*Manu*ranga Perera.

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

[Dev] WSO2 Committers += Nadeeshaan Gunasinghe

[Kasun Indrasiri]

Hi devs,

Its my pleasure to welcome Nadeeshaan Gunasinghe as a WSO2 Committer.
Nadeeshaan, welcome aboard and keep up the good work!

Thanks.

-- 
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Kevin Ratnasekera

[Kasun Indrasiri]

Hi devs,

Its my pleasure to welcome Kevin Ratnasekera as a WSO2 Committer.
Kevin, welcome aboard and keep up the good work!

Thanks.

-- 
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Viraj Senevirathne

[Kasun Indrasiri]

Hi devs,

Its my pleasure to welcome Viraj Senevirathne as a WSO2 Committer.
Viraj, welcome aboard and keep up the good work!

Thanks.

-- 
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PPaaS] Need to update the Cartridges to support latest Stratos PCA

[Pubudu Gunatilaka]

Hi,

We can do the following changes to support backward compatibility of PCA.

1. Update new MB related values such as MB_URLS, MB-USERNAME, etc in
start-agent.sh

Start-agent script will read the env variables and update the agent.conf
file in PCA. I have already done the fix for this in [1].

2. As we have forked the PCA for PPaas, we will be changing that as follows.

Users can send MB_URLS or can send both MB_IP and MB_PORT. PCA will give
the priority for MB_URLS over MB_IP and MB_PORT. PCA will change to handle
both cases. If MB_URLS are sent, PCA will export one of the successful mb
ips as MB_IP for the sake of the plugin. In the plugin we need to know any
of the mb ips for the initialization of the cluster.

With this change there is no need of changing the plugins and template
modules. If any of the users need to change the default AMQP port, they can
send that from the cartridge definition. Cartridge definition property
values will be exported as ENV values and those will be used with the
configurator when configuring the server.

[1] -
https://github.com/wso2/private-paas-cartridges/commit/23e6bcdb16d9a032a9f66883f41747469cf45708

Thank you!


On Tue, Dec 15, 2015 at 1:01 PM, Chamila De Alwis  wrote:

> Hi,
>
> I've forked the PCA component and product and started working on the fixes
> for the config compatibility. After that I will merge the other critical
> fixes.
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Tue, Dec 15, 2015 at 12:59 PM, Imesh Gunaratne  wrote:
>
>> Hi All,
>>
>> The plan is to fork Apache Stratos python cartridge agent in WSO2 Private
>> PaaS product repository and fix this issue until Stratos community does
>> another release fixing this. In addition this would add few performance
>> improvements we did recently in cartridge agent until those are merged to
>> upstream.
>>
>> Thanks
>>
>> On Tue, Dec 15, 2015 at 10:04 AM, Gayan Gunarathne 
>> wrote:
>>
>>>
>>>
>>> On Tue, Dec 15, 2015 at 9:35 AM, Imesh Gunaratne  wrote:
>>>
 Hi Gayan,

 It looks like this modification in cartridge agent is not backward
 compatible [1]. As a result users will need to upgrade all the existing
 cartridges to their latest versions to work with Private PaaS 4.1.1.

 IMO we need to fix first.

 [1]
 https://github.com/apache/stratos/commit/9c57c7d803f790078963861e553e5b79290d8f2d

>>>
>>> Yeah . We need to support MB IP and MB port in the case of that
>>> configurations are there.
>>>

 Thanks

 On Mon, Dec 14, 2015 at 7:38 PM, Gayan Gunarathne 
 wrote:

> We found that we need to update the Cartridges to support the Stratos
> Cartridge Agent 4.1.5.We need to update the startup handlers,sample
> artifact json to support the ActiveMQ HA with WSO2 Cartridges.
>
> We will fix those changes and will do the WSO2 PPaaS Cartridges 4.1.3
> release.
>
> [1]
> https://github.com/wso2/private-paas-cartridges/blob/master/wso2esb/4.9.0/plugins/wso2esb-490-startup-handler.py#L76
> [2]
> https://github.com/wso2/private-paas-cartridges/blob/master/wso2esb/4.9.0/samples/kubernetes-clusters/kubernetes-cluster-1.json#L36
>
> Thanks,
> Gayan
>
> --
>
> Gayan Gunarathne
> Technical Lead, WSO2 Inc. (http://wso2.com)
> Committer & PMC Member, Apache Stratos
> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>
>
>



 --
 *Imesh Gunaratne*
 Senior Technical Lead
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: http://imesh.gunaratne.org
 Lean . Enterprise . Middleware



 --
 *Imesh Gunaratne*
 Senior Technical Lead
 WSO2 Inc: http://wso2.com
 T: +94 11 214 5345 M: +94 77 374 2057
 W: http://imesh.gunaratne.org
 Lean . Enterprise . Middleware



>>>
>>>
>>> --
>>>
>>> Gayan Gunarathne
>>> Technical Lead, WSO2 Inc. (http://wso2.com)
>>> Committer & PMC Member, Apache Stratos
>>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>>
>>>
>>>
>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Senior Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.gunaratne.org
>> Lean . Enterprise . Middleware
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

[Dev] Carbon Feature Plugin 2.0.0 Released!

[Dinusha Boteju]

*WSO2 Carbon Feature plugin 2.0.0 Released!*

We are pleased to inform you that the carbon feature plugin 2.0.0 is now
available to use. Source for this release is available here.


Documentation for WSO2 carbon feature plugin 2.0.0 is now available in WSO2
wiki and can be found from here
.

*Reporting issues*

Please feel free to report bugs you come across, documentation faults and
feature requests through the public issue tracking system
.

Thanks,
WSO2 Carbon Team

-- 
*Dinusha Boteju*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: dinus...@wso2.com 
phone:(+94) 776640275 <%28%2B94%29%2039736>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Indunil Upeksha Rathnayake

[Malithi Edirisinghe]

Congrats :)

On Tue, Dec 15, 2015 at 2:58 AM, Damith Senanayake  wrote:

> Congratulations Indunil... :)
>
> On Tue, Dec 15, 2015 at 11:07 AM, Johann Nallathamby 
> wrote:
>
>> Hi All,
>>
>> It's my pleasure to announce Indunil Upeksha Rathnayake as a WSO2
>> Committer. Indunil has been a valuable contributor for WSO2 Identity
>> Server product, and in recognition of her contribution to WSO2, she
>> has been voted as a WSO2 Committer.
>>
>> Indunil, congratulations and keep up the good work!
>>
>> Thanks & Regards.
>>
>> --
>> Thanks & Regards,
>>
>> *Johann Dilantha Nallathamby*
>> Technical Lead & Product Lead of WSO2 Identity Server
>> Governance Technologies Team
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - *+9476950*
>> Blog - *http://nallaa.wordpress.com *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
>
> *-Damith Senanayake-*+94712205272
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Malithi Edirisinghe*
Senior Software Engineer
WSO2 Inc.

Mobile : +94 (0) 718176807
malit...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.3 RC3

[Hasitha Hiranya]

Hi,

Tested WSO2 MB with Carbon kernel 4.4.3 RC3. All integration tests and
automated cluster tests are passed.
Thus +1 for release.

Thanks

On Tue, Dec 15, 2015 at 3:45 PM, Nipuni Perera  wrote:

> Hi Devs,
>
> Thanks for testing and verifying the Carbon kernel 4.4.3 RC3. We are
> closing this vote now. This vote has passed with 8 +1s and 0 -1s.
> Therefore we will proceed with the Carbon kernel 4.4.3 release.
>
> Carbon Team.
>
> On Tue, Dec 15, 2015 at 1:41 PM, Nipuni Perera  wrote:
>
>> Hi,
>>
>> Tested deployment-synchronizer and Caching in AS-5.3.1-SNAPSHOT cluster
>> (1-manager node, 2- worker nodes with Nginx load balancer). No issues
>> found.
>>
>> Thanks,
>> Nipuni
>>
>> On Mon, Dec 14, 2015 at 4:35 PM, Nipuni Perera  wrote:
>>
>>> Hi,
>>>
>>> Tested AS 5.3.1-SNAPSHOT with kernel 4.4.3-RC3. No issues found.
>>>
>>> [x] Stable - Go ahead and release
>>>
>>> Thanks,
>>> Nipuni
>>>
>>> On Mon, Dec 14, 2015 at 4:07 PM, Damith Senanayake 
>>> wrote:
>>>
 Hi,
 Tested user management and user core functionality. No issues found.

 [x] Stable - Go ahead and release

 thanks

 On Mon, Dec 14, 2015 at 3:05 PM, Sachith Withana 
 wrote:

> Hi all,
>
> Built WSO2 DAS-3.0.1-SNAPSHOT with Kernel 4.4.3-RC3 with tests. No
> issues found.
>
> [x] Stable - Go ahead and release
>
> Cheers,
> Sachith
>
> On Mon, Dec 14, 2015 at 11:39 AM, Milinda Perera 
> wrote:
>
>> Hi,
>>
>> Tested WSO BRS-2.2.0-SNAPSHOT with kernel 4.4.3-RC3, Build with
>> integration test get success and BRS basic functionalities also works 
>> fine.
>>
>> [x] Stable - Go ahead and release
>>
>> Thanks,
>> Milinda
>>
>> On Mon, Dec 14, 2015 at 10:30 AM, Jagath Sisirakumara Ariyarathne <
>> jaga...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Built latest ESB pack with all integration tests. No issues observed.
>>>
>>> [x] Stable - go ahead and release
>>>
>>> Thanks.
>>>
>>> On Mon, Dec 14, 2015 at 10:08 AM, Maheshakya Wijewardena <
>>> mahesha...@wso2.com> wrote:
>>>
 Hi,

 I have built ML 1.1.0 Beta pack including all tests with kernel
 4.4.3 RC3. No issues found.

 [x] Stable - Go ahead and release.

 Best regards.

 On Mon, Dec 14, 2015 at 8:21 AM, Hasitha Aravinda >>> > wrote:

> Hi
>
> I have tested BPS 3.5.1-SNAPSHOT with kernel 4.4.3
> ​ RC3​
> ​
> . No issue found.
>
> [x] Stable - Go ahead and release.
>
> Thanks
> Hasitha.
>
> On Fri, Dec 11, 2015 at 8:15 PM, Nipuni Perera 
> wrote:
>
>>
>> Hi Devs,
>>
>> This is the RC3 release candidate of WSO2 Carbon Kernel 4.4.3.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12540
>>
>> Please download and test your products with kernel 4.4.3 RC3
>> and vote. Vote will be open for 72 hours or as longer as needed.
>>
>> *​Source and binary distribution files:*
>> http://svn.wso2.org/repos/wso2/people/nipuni/4.4.3-rc3/
>>
>> *Maven staging repository:*
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-168
>> /
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.3-RC3
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> Thank you
>> Carbon Team
>>
>> --
>> Nipuni Perera
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> Email: nip...@wso2.com
>> Git hub profile: https://github.com/nipuni
>> Blog : http://nipunipererablog.blogspot.com/
>> Mobile: +94 (71) 5626680
>> 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
> Hasitha Aravinda,
> Senior Software Engineer,
> WSO2 Inc.
> Email: hasi...@wso2.com
> Mobile : +94 718 210 200
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Pruthuvi Maheshakya Wijewardena
 Software Engineer
 WSO2 : http://wso2.com/
 Email: mahesha...@wso2.com
 Mobile: +94711228855



 ___
 Dev mailing list
 Dev@wso2

Re: [Dev] [ML] Got an Error while running sample code of Spark Mllib

[Nirmal Fernando]

You have to set spark master URL. Btw, since this is not related to WSO2 ML
it's better if you can ask these questions in Spark mailing list.

SparkConf sparkConf = new SparkConf();



sparkConf.setMaster("local");

On Tue, Dec 15, 2015 at 5:00 PM, NIFRAS ISMAIL 
wrote:

> Hi,
>
> While running spark mllib code sample to find frequent itemset I have
> received an error, which is not understable to me. Could anyone please
> explain why this happen?
>
> My all code is here : https://github.com/nifrasismail/fpGrowthSparkMllib
>
> I have add all maven dependencies. I am not install any hadoop or spark as
> standalone. I only add spark from dependencies.
>
> Using Spark's default log4j profile:
> org/apache/spark/log4j-defaults.properties
> 15/12/15 16:54:54 INFO SparkContext: Running Spark version 1.5.2
> 15/12/15 16:55:39 WARN NativeCodeLoader: Unable to load native-hadoop
> library for your platform... using builtin-java classes where applicable
> 15/12/15 16:55:39 ERROR SparkContext: Error initializing SparkContext.
> org.apache.spark.SparkException: A master URL must be set in your
> configuration
> at org.apache.spark.SparkContext.(SparkContext.scala:394)
> at
> org.apache.spark.api.java.JavaSparkContext.(JavaSparkContext.scala:61)
> at
> com.mycompany.app.FrequentPatternMiner.main(FrequentPatternMiner.java:17)
> Disconnected from the target VM, address: '127.0.0.1:40024', transport:
> 'socket'
> 15/12/15 16:55:39 INFO SparkContext: Successfully stopped SparkContext
> Exception in thread "main" org.apache.spark.SparkException: A master URL
> must be set in your configuration
> at org.apache.spark.SparkContext.(SparkContext.scala:394)
> at
> org.apache.spark.api.java.JavaSparkContext.(JavaSparkContext.scala:61)
> at
> com.mycompany.app.FrequentPatternMiner.main(FrequentPatternMiner.java:17)
>
>
> Regards.
> *M. Nifras Ismail*
> [image: LinkedIn] 
>
>
>


-- 

Thanks & regards,
Nirmal

Team Lead - WSO2 Machine Learner
Associate Technical Lead - Data Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] Accessing registry resource in java

[Ishara Cooray]

Thanks Thusitha.

Ishara Cooray
Senior Software Engineer
Mobile : +9477 262 9512
WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

On Tue, Dec 15, 2015 at 5:03 PM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi Ishara,
>
> AFAIK it is org.wso2.carbon.registry.core.service.RegistryService
>
> Thanks
>
> On Tue, Dec 15, 2015 at 4:53 PM, Ishara Cooray  wrote:
>
>> Hi,
>> In an osgi bundle, I have to read a .xml file which resides in super
>> tenant's registry at the server startup, when activate() method is invoked.
>>
>> What could be the best approach to do this?
>>
>> I was thinking of wait until registry service is activated by adding a
>> reference to my servicecomponent. If that is the case what could be the
>> reference i should add?
>>
>> Thanks & Regards,.
>> Ishara Cooray
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] Accessing registry resource in java

[Thusitha Thilina Dayaratne]

Hi Ishara,

AFAIK it is org.wso2.carbon.registry.core.service.RegistryService

Thanks

On Tue, Dec 15, 2015 at 4:53 PM, Ishara Cooray  wrote:

> Hi,
> In an osgi bundle, I have to read a .xml file which resides in super
> tenant's registry at the server startup, when activate() method is invoked.
>
> What could be the best approach to do this?
>
> I was thinking of wait until registry service is activated by adding a
> reference to my servicecomponent. If that is the case what could be the
> reference i should add?
>
> Thanks & Regards,.
> Ishara Cooray
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thusitha Dayaratne
Software Engineer
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

Mobile  +94712756809
Blog  alokayasoya.blogspot.com
Abouthttp://about.me/thusithathilina
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Auto Tests] Checking if Carbon server restart is complete

[Gokul Balakrishnan]

That's perfect. thanks Krishantha!

On 15 December 2015 at 16:54, Krishantha Samaraweera 
wrote:

> You can use "*ClientConnectionUtil.waitForPort(port, timeout, true**,
> hostname);"* to wait for port to open after restart.
>
> Thanks,
> Krishantha
>
> On Tue, Dec 15, 2015 at 4:39 PM, Gokul Balakrishnan 
> wrote:
>
>> Hi TA team,
>>
>> Is there a way to do $subject? Basically, my requirement is for the
>> current thread to stay blocked until the initiated server restart is
>> complete.
>>
>> Is there a way to achieve this through the framework itself, rather than
>> use sleep() in the test code? We're currently using TAF 4.4.2 in DAS.
>>
>> Thanks,
>>
>> --
>> Gokul Balakrishnan
>> Senior Software Engineer,
>> WSO2, Inc. http://wso2.com
>> Mob: +94 77 593 5789 | +1 650 272 9927
>>
>
>
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>



-- 
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
Mob: +94 77 593 5789 | +1 650 272 9927
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ML] Got an Error while running sample code of Spark Mllib

[NIFRAS ISMAIL]

Hi,

While running spark mllib code sample to find frequent itemset I have
received an error, which is not understable to me. Could anyone please
explain why this happen?

My all code is here : https://github.com/nifrasismail/fpGrowthSparkMllib

I have add all maven dependencies. I am not install any hadoop or spark as
standalone. I only add spark from dependencies.

Using Spark's default log4j profile:
org/apache/spark/log4j-defaults.properties
15/12/15 16:54:54 INFO SparkContext: Running Spark version 1.5.2
15/12/15 16:55:39 WARN NativeCodeLoader: Unable to load native-hadoop
library for your platform... using builtin-java classes where applicable
15/12/15 16:55:39 ERROR SparkContext: Error initializing SparkContext.
org.apache.spark.SparkException: A master URL must be set in your
configuration
at org.apache.spark.SparkContext.(SparkContext.scala:394)
at
org.apache.spark.api.java.JavaSparkContext.(JavaSparkContext.scala:61)
at com.mycompany.app.FrequentPatternMiner.main(FrequentPatternMiner.java:17)
Disconnected from the target VM, address: '127.0.0.1:40024', transport:
'socket'
15/12/15 16:55:39 INFO SparkContext: Successfully stopped SparkContext
Exception in thread "main" org.apache.spark.SparkException: A master URL
must be set in your configuration
at org.apache.spark.SparkContext.(SparkContext.scala:394)
at
org.apache.spark.api.java.JavaSparkContext.(JavaSparkContext.scala:61)
at com.mycompany.app.FrequentPatternMiner.main(FrequentPatternMiner.java:17)


Regards.
*M. Nifras Ismail*
[image: LinkedIn] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Auto Tests] Checking if Carbon server restart is complete

[Krishantha Samaraweera]

You can use "*ClientConnectionUtil.waitForPort(port, timeout, true**,
hostname);"* to wait for port to open after restart.

Thanks,
Krishantha

On Tue, Dec 15, 2015 at 4:39 PM, Gokul Balakrishnan  wrote:

> Hi TA team,
>
> Is there a way to do $subject? Basically, my requirement is for the
> current thread to stay blocked until the initiated server restart is
> complete.
>
> Is there a way to achieve this through the framework itself, rather than
> use sleep() in the test code? We're currently using TAF 4.4.2 in DAS.
>
> Thanks,
>
> --
> Gokul Balakrishnan
> Senior Software Engineer,
> WSO2, Inc. http://wso2.com
> Mob: +94 77 593 5789 | +1 650 272 9927
>



-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] Accessing registry resource in java

[Ishara Cooray]

Hi,
In an osgi bundle, I have to read a .xml file which resides in super
tenant's registry at the server startup, when activate() method is invoked.

What could be the best approach to do this?

I was thinking of wait until registry service is activated by adding a
reference to my servicecomponent. If that is the case what could be the
reference i should add?

Thanks & Regards,.
Ishara Cooray
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Auto Tests] Checking if Carbon server restart is complete

[Gokul Balakrishnan]

Hi TA team,

Is there a way to do $subject? Basically, my requirement is for the current
thread to stay blocked until the initiated server restart is complete.

Is there a way to achieve this through the framework itself, rather than
use sleep() in the test code? We're currently using TAF 4.4.2 in DAS.

Thanks,

-- 
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
Mob: +94 77 593 5789 | +1 650 272 9927
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PPaaS Artifact Migration Tool

[Imesh Gunaratne]

Thanks Nishadi, may be you can update the same PR or send a new one with
the improvements. Please try to list down the remaining tasks and a rough
time plan.

Thanks

On Tue, Dec 15, 2015 at 1:42 PM, Nishadi Kirielle  wrote:

> Hi,
> We have implemented the conversion of cartridge subscription artifacts to
> application signups and domain mapping subscriptions. In addition, we were
> able to integrate the https connection with the tool.[1] Currently, we are
> trying to deploy the artifacts in PPaaS 4.1.0.
>
> [1]
> https://github.com/nishadi/product-private-paas/tree/master/tools/migration/ppaas-artifact-converter
>
> Thanks
>
> On Tue, Dec 15, 2015 at 12:55 PM, Imesh Gunaratne  wrote:
>
>> Hi Nishadi,
>>
>> Would you mind sharing the latest status of your efforts on this?
>>
>> Thanks
>>
>> On Wed, Dec 9, 2015 at 3:48 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Here are some important improvements that you can do to boost your
>>> development productivity and stability of the tool.
>>>
>>> 1. Develop a set of Unit tests with an embedded web container to mock
>>> the PPaaS API.
>>>
>>>  - I've already done this as a demo for you to take as a reference guide
>>> at [1]. I've used Jetty web container as an embedded server in my JUnit
>>> test case to mock the API. I've hosted partition list API in my test server
>>> and assert whether artifact loader reads the partition list correctly.
>>>
>>> Advantage of this approach is that when you build your tool, it will
>>> compile the code, test and validate the functionality and package. You
>>> don't need to test the tool manually which is very time consuming. You may
>>> have to refactor/re-organize stuff I've developed to make things clean.
>>>
>>> 2. Create a class ArtifactConverterRestClient as a wrapper around
>>> HttpClient library and use it to fetch resources from Stratos API. You can
>>> create methods like getPartitionList, getAutoscalePolicyList etc. in this.
>>> Decouple your conversion logic from data transfer layer much as possible.
>>> This will make it easy for you to write tests.
>>>
>>>
>>> 3. Always use HTTPS if you are sending/receiving sensitive information.
>>> In current implementation the tool is passing authentication credentials to
>>> the server, therefore transport should be secure.
>>>
>>> 4. Make user input parameters configurable via configuration files.
>>> Currently the tool expects username, password, url etc. as user inputs.
>>> Make it read these values from a properties file and prompt only if those
>>> values are missing.
>>>
>>> [1] https://github.com/nishadi/product-private-paas/pull/1
>>>
>>> Thanks.
>>>
>>> On Mon, Dec 7, 2015 at 12:19 PM, Nishadi Kirielle 
>>> wrote:
>>>
 Hi,

 Thank you for the feedback.

 @Imesh:
 I have updated the README file[1] in mark down text format and will
 start writing the Wiki page.

 @Gayan:
 In the initial version, we have used sample json files as templates and
 used them to be default values. But as it has some conflicts, we have
 removed the use of template files. The current approach is to fetch the
 artifacts from the PPaaS 4.0.0 and convert it to PPaaS 4.1.0 without using
 any default values. I have updated the READ ME file [1]

 @Isuru:
 I will take the approach proposed to handle exceptions in
 OldArtifactLoader by wrapping them in a custom exception and update it. I
 will update the log4j properties file to be in the conf directory.

 [1]
 https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/README

 Thank you,
 Nishadi

 On Sun, Dec 6, 2015 at 9:28 AM, Isuru Haththotuwa 
 wrote:

> Hi Malmee and Nishadi,
>
> Good progress in a short time!
>
> Had a glance at the code, couple of things I noticed:
>
>1. log4j.properties file is available under conf directory as well
>as the resources directory. Ideally should be in conf directory.
>2. In the class OldArtifactLoader [1], the methods are throwing
>IOException in an error scenario. A better approach would be to wrap 
> that
>with a custom exception (ex.: ArtifactLoadingException, etc.) and 
> throw it.
>WDYT? In the class Transformation [2], this approach is followed.
>
> [1].
> https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/src/main/java/org/wso2/ppaas/tools/artifactmigration/loader/OldArtifactLoader.java
>
> [2].
> https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/src/main/java/org/wso2/ppaas/tools/artifactmigration/Transformation.java
>
> On Sat, Dec 5, 2015 at 10:25 PM, Gayan Gunarathne 
> wrote:
>
>> Great stuff. This is a really important tool in the case of Private
>> PaaS migration.
>>
>> As per t

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.3 RC3

[Nipuni Perera]

Hi Devs,

Thanks for testing and verifying the Carbon kernel 4.4.3 RC3. We are
closing this vote now. This vote has passed with 8 +1s and 0 -1s. Therefore
we will proceed with the Carbon kernel 4.4.3 release.

Carbon Team.

On Tue, Dec 15, 2015 at 1:41 PM, Nipuni Perera  wrote:

> Hi,
>
> Tested deployment-synchronizer and Caching in AS-5.3.1-SNAPSHOT cluster
> (1-manager node, 2- worker nodes with Nginx load balancer). No issues
> found.
>
> Thanks,
> Nipuni
>
> On Mon, Dec 14, 2015 at 4:35 PM, Nipuni Perera  wrote:
>
>> Hi,
>>
>> Tested AS 5.3.1-SNAPSHOT with kernel 4.4.3-RC3. No issues found.
>>
>> [x] Stable - Go ahead and release
>>
>> Thanks,
>> Nipuni
>>
>> On Mon, Dec 14, 2015 at 4:07 PM, Damith Senanayake 
>> wrote:
>>
>>> Hi,
>>> Tested user management and user core functionality. No issues found.
>>>
>>> [x] Stable - Go ahead and release
>>>
>>> thanks
>>>
>>> On Mon, Dec 14, 2015 at 3:05 PM, Sachith Withana 
>>> wrote:
>>>
 Hi all,

 Built WSO2 DAS-3.0.1-SNAPSHOT with Kernel 4.4.3-RC3 with tests. No
 issues found.

 [x] Stable - Go ahead and release

 Cheers,
 Sachith

 On Mon, Dec 14, 2015 at 11:39 AM, Milinda Perera 
 wrote:

> Hi,
>
> Tested WSO BRS-2.2.0-SNAPSHOT with kernel 4.4.3-RC3, Build with
> integration test get success and BRS basic functionalities also works 
> fine.
>
> [x] Stable - Go ahead and release
>
> Thanks,
> Milinda
>
> On Mon, Dec 14, 2015 at 10:30 AM, Jagath Sisirakumara Ariyarathne <
> jaga...@wso2.com> wrote:
>
>> Hi,
>>
>> Built latest ESB pack with all integration tests. No issues observed.
>>
>> [x] Stable - go ahead and release
>>
>> Thanks.
>>
>> On Mon, Dec 14, 2015 at 10:08 AM, Maheshakya Wijewardena <
>> mahesha...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I have built ML 1.1.0 Beta pack including all tests with kernel
>>> 4.4.3 RC3. No issues found.
>>>
>>> [x] Stable - Go ahead and release.
>>>
>>> Best regards.
>>>
>>> On Mon, Dec 14, 2015 at 8:21 AM, Hasitha Aravinda 
>>> wrote:
>>>
 Hi

 I have tested BPS 3.5.1-SNAPSHOT with kernel 4.4.3
 ​ RC3​
 ​
 . No issue found.

 [x] Stable - Go ahead and release.

 Thanks
 Hasitha.

 On Fri, Dec 11, 2015 at 8:15 PM, Nipuni Perera 
 wrote:

>
> Hi Devs,
>
> This is the RC3 release candidate of WSO2 Carbon Kernel 4.4.3.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12540
>
> Please download and test your products with kernel 4.4.3 RC3
> and vote. Vote will be open for 72 hours or as longer as needed.
>
> *​Source and binary distribution files:*
> http://svn.wso2.org/repos/wso2/people/nipuni/4.4.3-rc3/
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-168
> /
>
> *The tag to be voted upon:*
> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.3-RC3
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Thank you
> Carbon Team
>
> --
> Nipuni Perera
> Software Engineer; WSO2 Inc.; http://wso2.com
> Email: nip...@wso2.com
> Git hub profile: https://github.com/nipuni
> Blog : http://nipunipererablog.blogspot.com/
> Mobile: +94 (71) 5626680
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 --
 Hasitha Aravinda,
 Senior Software Engineer,
 WSO2 Inc.
 Email: hasi...@wso2.com
 Mobile : +94 718 210 200

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


>>>
>>>
>>> --
>>> Pruthuvi Maheshakya Wijewardena
>>> Software Engineer
>>> WSO2 : http://wso2.com/
>>> Email: mahesha...@wso2.com
>>> Mobile: +94711228855
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Jagath Ariyarathne
>> Technical Lead
>> WSO2 Inc.  http://wso2.com/
>> Email: jaga...@wso2.com
>> Mob  : +94 77 386 7048
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/

Re: [Dev] Web Application Statistics Monitoring for Application Server 6.0.0

[Nuwan Pallewela]

[Moving to Architecture group]

On Tue, Dec 15, 2015 at 3:31 PM, Nuwan Pallewela  wrote:

> [Moving thread to Architecture group]
>
> Hi Nathasha,
>
> Is statistics information get update per minute?
> Do we have the capability to update the statistics using a refresh button
> or some other way without waiting for one minute?
>
> It will be great if you could provide a simple diagram which  describes
> the design.
>
> Thanks,
> Nuwan
>
>
> On Tue, Dec 15, 2015 at 11:29 AM, Nathasha Naranpanawa 
> wrote:
>
>> Hi all,
>>
>> I'm currently working on adding web application statistics monitoring
>> feature to the upcoming Application Server 6.0.0. This was done in two
>> iterations as following;
>>
>>- Adding a custom Valve to the tomcat server in order to collect data
>>from the server.
>>- Creating necessary CApp packages in order to define means of
>>publishing data from tomcat server to DAS, receiving and storing the data.
>>
>> The custom tomcat Valve behaves as an Event Publisher and publishes data
>> to DAS through Thrift data agent. For each request from the server, an
>> Event is created including metadata and payload data and is published to
>> the DAS by a DataPublisher.
>>
>> A CApp was created by including the definitions for an Event Stream,
>> Event Receiver and Event Store to receive data from the publisher valve and
>> store them. This is deployed in the
>> wso2das-3.0.0/repository/deployment/server/carbonapps folder.
>>
>> A Spark script is also added to the CApp in order to query the data
>> received by DAS. The script presents a summary of the requests received by
>> DAS per minute. The summary includes the following information;
>>
>>- average request count
>>- average response time
>>- HTTP request success count
>>- HTTP request error count
>>
>> Any suggestions and feedback are highly appreciated.
>>
>> Thanks,
>>
>>
>> --
>> Nathasha Naranpanawa
>> Software Engineering Intern
>> WSO2 Inc.
>>
>> Email: natha...@wso2.com
>> Mobile: +94775496142
>> LinkedIn: https://lk.linkedin.com/in/nathashanaranpanawa
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739 <%2B94719079739>@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Web Application Statistics Monitoring for Application Server 6.0.0

[Nuwan Pallewela]

[Moving thread to Architecture group]

Hi Nathasha,

Is statistics information get update per minute?
Do we have the capability to update the statistics using a refresh button
or some other way without waiting for one minute?

It will be great if you could provide a simple diagram which  describes the
design.

Thanks,
Nuwan


On Tue, Dec 15, 2015 at 11:29 AM, Nathasha Naranpanawa 
wrote:

> Hi all,
>
> I'm currently working on adding web application statistics monitoring
> feature to the upcoming Application Server 6.0.0. This was done in two
> iterations as following;
>
>- Adding a custom Valve to the tomcat server in order to collect data
>from the server.
>- Creating necessary CApp packages in order to define means of
>publishing data from tomcat server to DAS, receiving and storing the data.
>
> The custom tomcat Valve behaves as an Event Publisher and publishes data
> to DAS through Thrift data agent. For each request from the server, an
> Event is created including metadata and payload data and is published to
> the DAS by a DataPublisher.
>
> A CApp was created by including the definitions for an Event Stream, Event
> Receiver and Event Store to receive data from the publisher valve and store
> them. This is deployed in the
> wso2das-3.0.0/repository/deployment/server/carbonapps folder.
>
> A Spark script is also added to the CApp in order to query the data
> received by DAS. The script presents a summary of the requests received by
> DAS per minute. The summary includes the following information;
>
>- average request count
>- average response time
>- HTTP request success count
>- HTTP request error count
>
> Any suggestions and feedback are highly appreciated.
>
> Thanks,
>
>
> --
> Nathasha Naranpanawa
> Software Engineering Intern
> WSO2 Inc.
>
> Email: natha...@wso2.com
> Mobile: +94775496142
> LinkedIn: https://lk.linkedin.com/in/nathashanaranpanawa
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Indunil Upeksha Rathnayake

[Damith Senanayake]

Congratulations Indunil... :)

On Tue, Dec 15, 2015 at 11:07 AM, Johann Nallathamby 
wrote:

> Hi All,
>
> It's my pleasure to announce Indunil Upeksha Rathnayake as a WSO2
> Committer. Indunil has been a valuable contributor for WSO2 Identity
> Server product, and in recognition of her contribution to WSO2, she
> has been voted as a WSO2 Committer.
>
> Indunil, congratulations and keep up the good work!
>
> Thanks & Regards.
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Technical Lead & Product Lead of WSO2 Identity Server
> Governance Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 


*-Damith Senanayake-*+94712205272
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PPaaS Artifact Migration Tool

[Nishadi Kirielle]

Hi,
We have implemented the conversion of cartridge subscription artifacts to
application signups and domain mapping subscriptions. In addition, we were
able to integrate the https connection with the tool.[1] Currently, we are
trying to deploy the artifacts in PPaaS 4.1.0.

[1]
https://github.com/nishadi/product-private-paas/tree/master/tools/migration/ppaas-artifact-converter

Thanks

On Tue, Dec 15, 2015 at 12:55 PM, Imesh Gunaratne  wrote:

> Hi Nishadi,
>
> Would you mind sharing the latest status of your efforts on this?
>
> Thanks
>
> On Wed, Dec 9, 2015 at 3:48 PM, Akila Ravihansa Perera  > wrote:
>
>> Hi,
>>
>> Here are some important improvements that you can do to boost your
>> development productivity and stability of the tool.
>>
>> 1. Develop a set of Unit tests with an embedded web container to mock the
>> PPaaS API.
>>
>>  - I've already done this as a demo for you to take as a reference guide
>> at [1]. I've used Jetty web container as an embedded server in my JUnit
>> test case to mock the API. I've hosted partition list API in my test server
>> and assert whether artifact loader reads the partition list correctly.
>>
>> Advantage of this approach is that when you build your tool, it will
>> compile the code, test and validate the functionality and package. You
>> don't need to test the tool manually which is very time consuming. You may
>> have to refactor/re-organize stuff I've developed to make things clean.
>>
>> 2. Create a class ArtifactConverterRestClient as a wrapper around
>> HttpClient library and use it to fetch resources from Stratos API. You can
>> create methods like getPartitionList, getAutoscalePolicyList etc. in this.
>> Decouple your conversion logic from data transfer layer much as possible.
>> This will make it easy for you to write tests.
>>
>>
>> 3. Always use HTTPS if you are sending/receiving sensitive information.
>> In current implementation the tool is passing authentication credentials to
>> the server, therefore transport should be secure.
>>
>> 4. Make user input parameters configurable via configuration files.
>> Currently the tool expects username, password, url etc. as user inputs.
>> Make it read these values from a properties file and prompt only if those
>> values are missing.
>>
>> [1] https://github.com/nishadi/product-private-paas/pull/1
>>
>> Thanks.
>>
>> On Mon, Dec 7, 2015 at 12:19 PM, Nishadi Kirielle 
>> wrote:
>>
>>> Hi,
>>>
>>> Thank you for the feedback.
>>>
>>> @Imesh:
>>> I have updated the README file[1] in mark down text format and will
>>> start writing the Wiki page.
>>>
>>> @Gayan:
>>> In the initial version, we have used sample json files as templates and
>>> used them to be default values. But as it has some conflicts, we have
>>> removed the use of template files. The current approach is to fetch the
>>> artifacts from the PPaaS 4.0.0 and convert it to PPaaS 4.1.0 without using
>>> any default values. I have updated the READ ME file [1]
>>>
>>> @Isuru:
>>> I will take the approach proposed to handle exceptions in
>>> OldArtifactLoader by wrapping them in a custom exception and update it. I
>>> will update the log4j properties file to be in the conf directory.
>>>
>>> [1]
>>> https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/README
>>>
>>> Thank you,
>>> Nishadi
>>>
>>> On Sun, Dec 6, 2015 at 9:28 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Malmee and Nishadi,

 Good progress in a short time!

 Had a glance at the code, couple of things I noticed:

1. log4j.properties file is available under conf directory as well
as the resources directory. Ideally should be in conf directory.
2. In the class OldArtifactLoader [1], the methods are throwing
IOException in an error scenario. A better approach would be to wrap 
 that
with a custom exception (ex.: ArtifactLoadingException, etc.) and throw 
 it.
WDYT? In the class Transformation [2], this approach is followed.

 [1].
 https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/src/main/java/org/wso2/ppaas/tools/artifactmigration/loader/OldArtifactLoader.java

 [2].
 https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/src/main/java/org/wso2/ppaas/tools/artifactmigration/Transformation.java

 On Sat, Dec 5, 2015 at 10:25 PM, Gayan Gunarathne 
 wrote:

> Great stuff. This is a really important tool in the case of Private
> PaaS migration.
>
> As per the README[1] it mention as "Add the default values to the
> templates folder, if needed".I am not clear on that? Are we packing the
> 4.1.0 artifacts templates with the artifact migration tool? So user need 
> to
> put the default values for those artifacts?
>
> [1]
> https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppa

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.3 RC3

[Nipuni Perera]

Hi,

Tested deployment-synchronizer and Caching in AS-5.3.1-SNAPSHOT cluster
(1-manager node, 2- worker nodes with Nginx load balancer). No issues
found.

Thanks,
Nipuni

On Mon, Dec 14, 2015 at 4:35 PM, Nipuni Perera  wrote:

> Hi,
>
> Tested AS 5.3.1-SNAPSHOT with kernel 4.4.3-RC3. No issues found.
>
> [x] Stable - Go ahead and release
>
> Thanks,
> Nipuni
>
> On Mon, Dec 14, 2015 at 4:07 PM, Damith Senanayake 
> wrote:
>
>> Hi,
>> Tested user management and user core functionality. No issues found.
>>
>> [x] Stable - Go ahead and release
>>
>> thanks
>>
>> On Mon, Dec 14, 2015 at 3:05 PM, Sachith Withana 
>> wrote:
>>
>>> Hi all,
>>>
>>> Built WSO2 DAS-3.0.1-SNAPSHOT with Kernel 4.4.3-RC3 with tests. No
>>> issues found.
>>>
>>> [x] Stable - Go ahead and release
>>>
>>> Cheers,
>>> Sachith
>>>
>>> On Mon, Dec 14, 2015 at 11:39 AM, Milinda Perera 
>>> wrote:
>>>
 Hi,

 Tested WSO BRS-2.2.0-SNAPSHOT with kernel 4.4.3-RC3, Build with
 integration test get success and BRS basic functionalities also works fine.

 [x] Stable - Go ahead and release

 Thanks,
 Milinda

 On Mon, Dec 14, 2015 at 10:30 AM, Jagath Sisirakumara Ariyarathne <
 jaga...@wso2.com> wrote:

> Hi,
>
> Built latest ESB pack with all integration tests. No issues observed.
>
> [x] Stable - go ahead and release
>
> Thanks.
>
> On Mon, Dec 14, 2015 at 10:08 AM, Maheshakya Wijewardena <
> mahesha...@wso2.com> wrote:
>
>> Hi,
>>
>> I have built ML 1.1.0 Beta pack including all tests with kernel 4.4.3
>> RC3. No issues found.
>>
>> [x] Stable - Go ahead and release.
>>
>> Best regards.
>>
>> On Mon, Dec 14, 2015 at 8:21 AM, Hasitha Aravinda 
>> wrote:
>>
>>> Hi
>>>
>>> I have tested BPS 3.5.1-SNAPSHOT with kernel 4.4.3
>>> ​ RC3​
>>> ​
>>> . No issue found.
>>>
>>> [x] Stable - Go ahead and release.
>>>
>>> Thanks
>>> Hasitha.
>>>
>>> On Fri, Dec 11, 2015 at 8:15 PM, Nipuni Perera 
>>> wrote:
>>>

 Hi Devs,

 This is the RC3 release candidate of WSO2 Carbon Kernel 4.4.3.

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

 Please download and test your products with kernel 4.4.3 RC3
 and vote. Vote will be open for 72 hours or as longer as needed.

 *​Source and binary distribution files:*
 http://svn.wso2.org/repos/wso2/people/nipuni/4.4.3-rc3/

 *Maven staging repository:*
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-168/

 *The tag to be voted upon:*
 https://github.com/wso2/carbon-kernel/releases/tag/v4.4.3-RC3


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

 Thank you
 Carbon Team

 --
 Nipuni Perera
 Software Engineer; WSO2 Inc.; http://wso2.com
 Email: nip...@wso2.com
 Git hub profile: https://github.com/nipuni
 Blog : http://nipunipererablog.blogspot.com/
 Mobile: +94 (71) 5626680
 


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


>>>
>>>
>>> --
>>> --
>>> Hasitha Aravinda,
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>> Email: hasi...@wso2.com
>>> Mobile : +94 718 210 200
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Pruthuvi Maheshakya Wijewardena
>> Software Engineer
>> WSO2 : http://wso2.com/
>> Email: mahesha...@wso2.com
>> Mobile: +94711228855
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Jagath Ariyarathne
> Technical Lead
> WSO2 Inc.  http://wso2.com/
> Email: jaga...@wso2.com
> Mob  : +94 77 386 7048
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Milinda Perera
 Software Engineer;
 WSO2 Inc. http://wso2.com ,
 Mobile: (+94) 714 115 032


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


>>>
>>>
>>> --
>>> Sachith Withana
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>> E-mail: sachith AT wso2.com
>>> M: +94715518127
>>> Linked-In: