Re: [Dev] Please review and merge the PR

[Sinthuja Ragendran]

Hi Lalanke,


On Fri, Feb 26, 2016 at 7:56 PM, Lalanke Athauda  wrote:

> Hi,
> Please review and merge the PR [1].
> [1] https://github.com/wso2/jaggery/pull/149
>

Done.

Thanks,
Sinthuja.

>
>
> --
> Lalanke Athauda
> Software Engineer
> WSO2 Inc.
> Mobile: 0772264301
>



-- 
*Sinthuja Rajendran*
Associate Technical Lead
WSO2, Inc.:http://wso2.com

Blog: http://sinthu-rajan.blogspot.com/
Mobile: +94774273955
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Can't we use waitForAPIDeploymentSync() for standalone mode tests?

[Bhathiya Jayasekara]

Thanks a lot for the detailed information Dharshana. I will add and use
this webapp.

Thanks,
Bhathiya

On Fri, Feb 26, 2016 at 9:42 PM, Dharshana Warusavitharana <
dharsha...@wso2.com> wrote:

> Hi Bhatiya,
>
> This uses web app deployed in product to expose set of APIs deployed to
> Synapse context. We originally developed this to monitor dep sync between
> gateway nodes. You can take the web app form [1] and implement until as
> this to check this. There is a web app on APIM repo as well on [2]. But
> latest one is available at [1]. you can merge it to APIM product repo form
> [3].
>
>
> Just deploy this war into product and use following REST calls to take
> status.
>
> Please find webapp details here
> *API status*
>
> All Apis
>
> http://localhost:9763/APIStatusMonitor/apiInformation/api/getApiList
>
> *http://localhost:9763/APIStatusMonitor/apiInformation/api/{tenantDomain}/{tenantId}/getApiList
> *
>
> http://localhost:9763/APIStatusMonitor/apiInformation/api/wso2.org/1/getApiList
>
> Get specific API info
>
>
> *http://localhost:9763/APIStatusMonitor/apiInformation/api/getStatus/{webappName}/{version}
> *
>
> http://localhost:9763/APIStatusMonitor/apiInformation/api/getStatus/adminApi123/1.0.0
> *http://localhost:9763/APIStatusMonitor/apiInformation/api/{tenantDomain}/{tenantId}/{webappName}/{version}
> *
>
> http://localhost:9763/APIStatusMonitor/apiInformation/api/wso2.org/1/testTenantApi/1.0.0
>
> *WebApp status*
>
> All webapps
> http://localhost:9763/APIStatusMonitor/webAppStatus/webappInfo/allApps
>
> *http://localhost:9763/APIStatusMonitor/webAppStatus/webappInfo/
> {tenantDomain}/{tenantId}/allApps*
>
> http://localhost:9763/APIStatusMonitor/webAppStatus/webappInfo/wso2.org/1/allApps
>
> *Webapp Info*
>
>
> http://localhost:9763/APIStatusMonitor/webAppStatus/webappInfo/APIStatusMonitor.war
>
> *http://localhost:9763/APIStatusMonitor/webAppStatus/webappInfo/{tenantDomain}/{tenantId}/{webappName}
> *
>
> http://localhost:9763/APIStatusMonitor/webAppStatus/webappInfo/wso2.org/1/APIStatusMonitor.war
>
>
> *Git repo *
> https://github.com/dkasunw/artifactMonitor.git
>
>
>
> [1]. https://github.com/dkasunw/artifactMonitor.git
> [2].
> https://github.com/wso2/product-apim/tree/master/modules/integration/tests-common/backend-service/monitor-app
> [3].
> https://github.com/krishanthasamaraweera/product-apim/tree/master/modules/integration/tests-common/backend-service/monitor-app
>
> Thank you,
> Dharshana.
>
> On Fri, Feb 26, 2016 at 6:41 PM, Bhathiya Jayasekara 
> wrote:
>
>> Hi TA team,
>>
>> In [1], inside waitForAPIDeploymentSync() method, it checks for
>> ExecutionEnvironment.PLATFORM before proceeding to wait.
>>
>> But even in standalone mode, I have seen API invocations sometimes fail
>> as API is not completely deployed at that time. So, removing above
>> conditional check and getting this functionality for standalone tests as
>> well looks like a solution to me. WDYT? Can you think of any issues that
>> can arise if we do that?
>>
>> [1]
>> https://github.com/wso2/product-apim/blob/master/modules/integration/tests-common/integration-test-utils/src/main/java/org/wso2/am/integration/test/utils/base/APIMIntegrationBaseTest.java#L416
>>
>> Thanks,
>>
>> --
>> *Bhathiya Jayasekara*
>> *Senior Software Engineer,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185 <%2B94715478185>*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>
>
>
> --
>
> Dharshana Warusavitharana
> Senior Software Engineer , Test Automation
> WSO2 Inc. http://wso2.com
> email : dharsha...@wso2.com 
> Tel  : +94 11 214 5345
> Fax :+94 11 2145300
> cell : +94770342233
> blog : http://dharshanaw.blogspot.com
>
> lean . enterprise . middleware
>



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

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

Re: [Dev] Can't we use waitForAPIDeploymentSync() for standalone mode tests?

[Dharshana Warusavitharana]

Hi Bhatiya,

This uses web app deployed in product to expose set of APIs deployed to
Synapse context. We originally developed this to monitor dep sync between
gateway nodes. You can take the web app form [1] and implement until as
this to check this. There is a web app on APIM repo as well on [2]. But
latest one is available at [1]. you can merge it to APIM product repo form
[3].


Just deploy this war into product and use following REST calls to take
status.

Please find webapp details here
*API status*

All Apis

http://localhost:9763/APIStatusMonitor/apiInformation/api/getApiList

*http://localhost:9763/APIStatusMonitor/apiInformation/api/{tenantDomain}/{tenantId}/getApiList
*
http://localhost:9763/APIStatusMonitor/apiInformation/api/wso2.org/1/getApiList

Get specific API info


*http://localhost:9763/APIStatusMonitor/apiInformation/api/getStatus/{webappName}/{version}
*
http://localhost:9763/APIStatusMonitor/apiInformation/api/getStatus/adminApi123/1.0.0
*http://localhost:9763/APIStatusMonitor/apiInformation/api/{tenantDomain}/{tenantId}/{webappName}/{version}
*
http://localhost:9763/APIStatusMonitor/apiInformation/api/wso2.org/1/testTenantApi/1.0.0

*WebApp status*

All webapps
http://localhost:9763/APIStatusMonitor/webAppStatus/webappInfo/allApps

*http://localhost:9763/APIStatusMonitor/webAppStatus/webappInfo/
{tenantDomain}/{tenantId}/allApps*
http://localhost:9763/APIStatusMonitor/webAppStatus/webappInfo/wso2.org/1/allApps

*Webapp Info*

http://localhost:9763/APIStatusMonitor/webAppStatus/webappInfo/APIStatusMonitor.war

*http://localhost:9763/APIStatusMonitor/webAppStatus/webappInfo/{tenantDomain}/{tenantId}/{webappName}
*
http://localhost:9763/APIStatusMonitor/webAppStatus/webappInfo/wso2.org/1/APIStatusMonitor.war


*Git repo *
https://github.com/dkasunw/artifactMonitor.git



[1]. https://github.com/dkasunw/artifactMonitor.git
[2].
https://github.com/wso2/product-apim/tree/master/modules/integration/tests-common/backend-service/monitor-app
[3].
https://github.com/krishanthasamaraweera/product-apim/tree/master/modules/integration/tests-common/backend-service/monitor-app

Thank you,
Dharshana.

On Fri, Feb 26, 2016 at 6:41 PM, Bhathiya Jayasekara 
wrote:

> Hi TA team,
>
> In [1], inside waitForAPIDeploymentSync() method, it checks for
> ExecutionEnvironment.PLATFORM before proceeding to wait.
>
> But even in standalone mode, I have seen API invocations sometimes fail as
> API is not completely deployed at that time. So, removing above conditional
> check and getting this functionality for standalone tests as well looks
> like a solution to me. WDYT? Can you think of any issues that can arise if
> we do that?
>
> [1]
> https://github.com/wso2/product-apim/blob/master/modules/integration/tests-common/integration-test-utils/src/main/java/org/wso2/am/integration/test/utils/base/APIMIntegrationBaseTest.java#L416
>
> Thanks,
>
> --
> *Bhathiya Jayasekara*
> *Senior Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <%2B94715478185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
> *Blog: http://movingaheadblog.blogspot.com
> *
>



-- 

Dharshana Warusavitharana
Senior Software Engineer , Test Automation
WSO2 Inc. http://wso2.com
email : dharsha...@wso2.com 
Tel  : +94 11 214 5345
Fax :+94 11 2145300
cell : +94770342233
blog : http://dharshanaw.blogspot.com

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

[Dev] [ESB][Connector] Salesforce - < salesforce.queryMore > retrieves same data.

[Chanuka Dissanayake]

Hi,

I'm using $subject to retrieve data from Salesforce objects which have more
than 2000 (which exceeds the maximum batch size). I refer [1], it'll
retrieve same data recursively. Following is the proxy service,




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

  



  

  

  

  200

SELECT
AccountId,Action__c,Amount,Best_Case_Amount__c,Breakdown_Type__c,Channel_error__c,CloseDate,Closed_Month__c,Commission_included__c,Competitor_we_Lost_to__c,Confidence__c,Contact_Roles__c,Conversion_Date__c,CreatedDate,Created_Today__c,CurrencyIsoCode,Current_Year_Amount__c,Development_Support_Account_Key__c,Development_Support_Hours__c,Engagement_Code__c,End_Date__c,Expected_Case_Amount__c,First_Account_Sale__c,Fiscal,FiscalQuarter,FiscalYear,Id,If_Lost_Reason_Other_Please_Explain__c,Implied_Exchange_Rate__c,Includes_Consulting__c,Includes_Dev_Support__c,Includes_Production_Support__c,Includes_QuickStart__c,IsClosed,IsDeleted,IsWon,LastActivityDate,LastModifiedDate,Last_Account_Sale__c,LeadSource,Lead_Type__c,Line_Item_Divergence__c,Line_Item_Total_Amount_USD__c,Name,New_Breakdown_Type__c,Opportunity_Term__c,Opp_End_Date__c,Opp_Start_Date__c,OwnerId,Partnership__c,Partner_commission__c,Partner_Lead_Amount__c,Partner_Lead_Close_Date__c,Partner_Registration_Expires__c,Partner_Registration_Status__c,Partner_Sales_Contact_Email__c,Partner_Sales_Contact_Name__c,Prev_Year_Amount__c,Pricebook2Id,Prior_Stage__c,Production_Support_Amount__c,Products_in_use__c,Project_Code__c,Project__c,Reason_Lost__c,RecordTypeId,Referred_to_Partners__c,Registered_by__c,Renewal_Stage__c,RFI_RFQ_RFP_BID__c,Salesforce_Record_Id__c,Services_Amount__c,SFDC__c,StageName,Stage_Change_Date__c,Start_Date__c,Subscription_Activation_Date_del__c,Subscription_Deactivation_Date__c,Test_Formula__c,Type,Type_Code__c,unique_count__c,Worse_Case_Amount__c,Zero_Amount__c
FROM Opportunity WHERE Fiscal '2013 1'

  

  http://wso2.org/salesforce/adaptor;>



  



  200



  



  

  

  

  



  



  UD_DAS

  EventStreamOpportunities_1_0_0_1

  1.0.1

  







  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  

  





  



  



  

  







  




[1]
https://docs.wso2.com/display/ESBCONNECTORS/Working+with+Salesforce+Connector+Operations

Thanks & Regards,
Chanuka.
-- 
Chanuka Dissanayake
*Software Engineer | **WSO2 Inc.*; http://wso2.com

Mobile: +94 71 33 63 596
Email: chan...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please review and merge the PR

[Lalanke Athauda]

Hi,
Please review and merge the PR [1].
[1] https://github.com/wso2/jaggery/pull/149

-- 
Lalanke Athauda
Software Engineer
WSO2 Inc.
Mobile: 0772264301
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Can't we use waitForAPIDeploymentSync() for standalone mode tests?

[Bhathiya Jayasekara]

Hi TA team,

In [1], inside waitForAPIDeploymentSync() method, it checks for
ExecutionEnvironment.PLATFORM before proceeding to wait.

But even in standalone mode, I have seen API invocations sometimes fail as
API is not completely deployed at that time. So, removing above conditional
check and getting this functionality for standalone tests as well looks
like a solution to me. WDYT? Can you think of any issues that can arise if
we do that?

[1]
https://github.com/wso2/product-apim/blob/master/modules/integration/tests-common/integration-test-utils/src/main/java/org/wso2/am/integration/test/utils/base/APIMIntegrationBaseTest.java#L416

Thanks,

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

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

Re: [Dev] [GSoC] [IS] Proposal 20: SCIM 2.0 Support to WSO2 Identity Server.

[Omindu Rathnaweera]

Hi Yasiru,

IMO it's better to improve the Charon library to support SCIM 2.0 since it
already supports SCIM 1.1. We will be able add the library to the list
of SCIM 2.0 implementations in [1].

[1] - http://www.simplecloud.info/

Regards,
Omindu.

On Fri, Feb 26, 2016 at 3:03 PM, Yasiru Kassapa 
wrote:

> Hi All,
> I am currently a third year undergraduate at University of Moratuwa hoping
> to contribute to a GSoc 2016 project at WSO2. I am a bit familiar with WSO2
> Identity Server 5.1.0 and the above project has interested me a lot.
>
> Upon researching on SCIM spec and Identity Server I've come across WSO2
> Charon, would we be developing Charon further to support SCIM 2.0 or using
> an open source SCIM implementation like eSCIMo to add SCIM 2.0 support for
> WSO2 Identity Server?
>
> Thank you & Regards.
> Yasiru Kassapa.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Omindu Rathnaweera
Software Engineer, WSO2 Inc.
Mobile: +94 771 197 211
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] Creating Gadgets for Web Application Statistics Monitoring Dashboard - Application Server 6.0.0

[Tharik Kanaka]

Hi Lochana,

Are you going to use existing analytics API used in DAS? Apart from that
what are the javascript chart libraries are you going to use for these
gadgets?

Regards,

On Fri, Feb 26, 2016 at 3:46 PM, Lochana Ranaweera 
wrote:

>
> Hi KasunG,
>
> The final deliverable of the dashboard will be a set of gadgets that can
> be deployed in the DS separately. It was suggested that ideally with the AS
> build the gadgets could be packed as a car file.
>
> As of now, the gadgets are working along with an API that provides the
> gadgets with properly structured data obtained out of a mysql database. The
> table structure for the tables in the mysql database is to be provided
> using a spark script.
>
> The following will have to be done by a user in order view web application
> statistics by means of a dashboard created using these gadgets
>
> - Publish webapp statistics to the DAS using publisher valve at AS
> - Execute the given Spark script to summarize the event data in to a
> database
> - Configure the datasource definition in Dashboard Server to retrieve data
> from the database
> - Create and publish a dashboard using preferred HTTP monitoring gadgets
> through dashboard server portal
>
> Thanks.
>
> On Fri, Feb 26, 2016 at 2:08 PM, KasunG Gajasinghe 
> wrote:
>
>> +architecture
>>
>> Hi Lochana,
>>
>> Can you describe what is the final deliverable of the dashboard? Also,
>> please explain briefly how the users are going to use these gadgets as well
>> as all other dependencies these need. Based on that, we can figure out how
>> the folder structure should be.
>>
>> Btw, can you explain the overall effort required to port these gadgets?
>> What needs to be done?
>>
>> Thanks.
>>
>> On Fri, Feb 26, 2016 at 12:42 PM, Lochana Ranaweera 
>> wrote:
>>
>>> Hi all,
>>>
>>> This is regarding the HTTP Monitoring Dashboard for AS 6.0.0. It is to
>>> be deployed as a collection of user preferred set of gadgets in the
>>> Dashboard Server.
>>> As of now, I have ported the* basic* HTTP monitoring functionality as
>>> separate gadgets for DS.
>>>
>>> A typical HTTP monitoring gadget has the following structure:
>>>
>>> gadget-name
>>>├── css
>>>├── js
>>>├── fonts
>>>├── images
>>>├── index.xml
>>>└── gadget.json
>>>
>>> What will be the best structure to version control thus created gadgets
>>> in the given branch
>>>  of AS 6.0.0?
>>> Should it be in modules or should it be inside contents directory in the
>>> distribution module?
>>> The directory structure of the build for new AS 6.0.0 is given below:
>>>
>>>
>>> ​
>>> Appreciate your suggestions on this matter.
>>>
>>> Thanks and Regards,
>>> --
>>> Lochana Ranaweera
>>> Intern Software Engineer
>>> WSO2 Inc: http://wso2.com
>>> Blog: https://lochanaranaweera.wordpress.com/
>>> Mobile: +94716487055 
>>>
>>>
>>
>>
>> --
>>
>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
>> email: kasung AT spamfree wso2.com
>> linked-in: http://lk.linkedin.com/in/gajasinghe
>> blog: http://kasunbg.org
>>
>>
>>
>
>
>
> --
> Lochana Ranaweera
> Intern Software Engineer
> WSO2 Inc: http://wso2.com
> Blog: https://lochanaranaweera.wordpress.com/
> Mobile: +94716487055 
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Tharik Kanaka*

WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka

Email: tha...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS] Compressed Event Analytics Relation Provider

[Anjana Fernando]

Merged.

Cheers,
Anjana.

On Fri, Feb 26, 2016 at 4:37 PM, Supun Sethunga  wrote:

> Added the changes as per code review. Please merge [1].
>
> [1] https://github.com/wso2/carbon-analytics/pull/159
>
> Thanks,
> Supun
>
> On Fri, Feb 26, 2016 at 11:30 AM, Anjana Fernando  wrote:
>
>> Please schedule a code review for this.
>>
>> Cheers,
>> Anjana.
>>
>> On Fri, Feb 26, 2016 at 11:03 AM, Supun Sethunga  wrote:
>>
>>> Hi,
>>>
>>> Please find the PR [1] for adding string compression to the event
>>> analytics relational provider.
>>>
>>> [1] https://github.com/wso2/carbon-analytics/pull/159
>>>
>>> Regards,
>>> Supun
>>>
>>> On Wed, Feb 24, 2016 at 3:35 PM, Supun Sethunga  wrote:
>>>
 Thanks!

 Regards,
 Supun

 On Wed, Feb 24, 2016 at 2:20 PM, Anjana Fernando 
 wrote:

> Merged the PR.
>
> Cheers,
> Anjana.
>
> On Wed, Feb 24, 2016 at 1:00 PM, Supun Sethunga 
> wrote:
>
>> Hi,
>>
>> I have done the changes suggested during the code review. Please
>> review and merge [1].
>>
>> Will send a separate PR for Compressing the json string.
>>
>>
>> Thanks,
>> Supun
>>
>> On Fri, Feb 19, 2016 at 3:37 PM, Anjana Fernando 
>> wrote:
>>
>>> Hi Supun,
>>>
>>> Can you please schedule a code review for this.
>>>
>>> Cheers,
>>> Anjana.
>>>
>>> On Tue, Feb 16, 2016 at 4:30 PM, Supun Sethunga 
>>> wrote:
>>>
 Hi,

 Attached [1] is the PR for $subject. Please review and merge.

 [1] https://github.com/wso2/carbon-analytics/pull/156

 Thanks,
 Supun

 --
 *Supun Sethunga*
 Software Engineer
 WSO2, Inc.
 http://wso2.com/
 lean | enterprise | middleware
 Mobile : +94 716546324

>>>
>>>
>>>
>>> --
>>> *Anjana Fernando*
>>> Senior Technical Lead
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>
>>
>>
>> --
>> *Supun Sethunga*
>> Software Engineer
>> WSO2, Inc.
>> http://wso2.com/
>> lean | enterprise | middleware
>> Mobile : +94 716546324
>>
>
>
>
> --
> *Anjana Fernando*
> Senior Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>



 --
 *Supun Sethunga*
 Software Engineer
 WSO2, Inc.
 http://wso2.com/
 lean | enterprise | middleware
 Mobile : +94 716546324

>>>
>>>
>>>
>>> --
>>> *Supun Sethunga*
>>> Software Engineer
>>> WSO2, Inc.
>>> http://wso2.com/
>>> lean | enterprise | middleware
>>> Mobile : +94 716546324
>>>
>>
>>
>>
>> --
>> *Anjana Fernando*
>> Senior Technical Lead
>> WSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware
>>
>
>
>
> --
> *Supun Sethunga*
> Software Engineer
> WSO2, Inc.
> http://wso2.com/
> lean | enterprise | middleware
> Mobile : +94 716546324
>



-- 
*Anjana Fernando*
Senior Technical Lead
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.4 RC1

[Hasitha Aravinda]

Hi Devs,

I have tested BPS pack with kernel 4.4.4 in clustered environment and did
smoke testing. Verified [1] as well.

[x] Stable - go ahead and release.

[1] - https://wso2.org/jira/browse/CARBON-15776

Thanks,
Hasitha.

On Fri, Feb 26, 2016 at 4:34 PM, Amal Gunatilake  wrote:

> Hi all,
>
> We have tested BPS pack against Carbon Kernel 4.4.4. Everything seems to
> be fine.
>
>- Tested core functionalities of BPS.
>- Passed all integration tests
>
> [x] Stable - go ahead and release.
>
> Best regards,
> Amal.
>
> On Wed, Feb 10, 2016 at 11:01 PM, Manuri Amaya Perera 
> wrote:
>
>> Hi Devs,
>>
>> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.4.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12641
>>
>> Please download and test your products with kernel 4.4.4 RC1 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/manurip/carbon-4.4.4/
>>
>> ​*Maven staging repository:*​
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-328/
>>
>> ​*The tag to be voted upon:*​
>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.4-RC1
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> Thank you
>> Carbon Team​
>>
>>
>> --
>>
>> *Manuri Amaya Perera*
>>
>> *Software Engineer*
>>
>> *WSO2 Inc.*
>>
>> *Blog: http://manuriamayaperera.blogspot.com
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Amal Gunatilake*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> ___
> 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

Re: [Dev] [DAS] Compressed Event Analytics Relation Provider

[Supun Sethunga]

Added the changes as per code review. Please merge [1].

[1] https://github.com/wso2/carbon-analytics/pull/159

Thanks,
Supun

On Fri, Feb 26, 2016 at 11:30 AM, Anjana Fernando  wrote:

> Please schedule a code review for this.
>
> Cheers,
> Anjana.
>
> On Fri, Feb 26, 2016 at 11:03 AM, Supun Sethunga  wrote:
>
>> Hi,
>>
>> Please find the PR [1] for adding string compression to the event
>> analytics relational provider.
>>
>> [1] https://github.com/wso2/carbon-analytics/pull/159
>>
>> Regards,
>> Supun
>>
>> On Wed, Feb 24, 2016 at 3:35 PM, Supun Sethunga  wrote:
>>
>>> Thanks!
>>>
>>> Regards,
>>> Supun
>>>
>>> On Wed, Feb 24, 2016 at 2:20 PM, Anjana Fernando 
>>> wrote:
>>>
 Merged the PR.

 Cheers,
 Anjana.

 On Wed, Feb 24, 2016 at 1:00 PM, Supun Sethunga 
 wrote:

> Hi,
>
> I have done the changes suggested during the code review. Please
> review and merge [1].
>
> Will send a separate PR for Compressing the json string.
>
>
> Thanks,
> Supun
>
> On Fri, Feb 19, 2016 at 3:37 PM, Anjana Fernando 
> wrote:
>
>> Hi Supun,
>>
>> Can you please schedule a code review for this.
>>
>> Cheers,
>> Anjana.
>>
>> On Tue, Feb 16, 2016 at 4:30 PM, Supun Sethunga 
>> wrote:
>>
>>> Hi,
>>>
>>> Attached [1] is the PR for $subject. Please review and merge.
>>>
>>> [1] https://github.com/wso2/carbon-analytics/pull/156
>>>
>>> Thanks,
>>> Supun
>>>
>>> --
>>> *Supun Sethunga*
>>> Software Engineer
>>> WSO2, Inc.
>>> http://wso2.com/
>>> lean | enterprise | middleware
>>> Mobile : +94 716546324
>>>
>>
>>
>>
>> --
>> *Anjana Fernando*
>> Senior Technical Lead
>> WSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware
>>
>
>
>
> --
> *Supun Sethunga*
> Software Engineer
> WSO2, Inc.
> http://wso2.com/
> lean | enterprise | middleware
> Mobile : +94 716546324
>



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

>>>
>>>
>>>
>>> --
>>> *Supun Sethunga*
>>> Software Engineer
>>> WSO2, Inc.
>>> http://wso2.com/
>>> lean | enterprise | middleware
>>> Mobile : +94 716546324
>>>
>>
>>
>>
>> --
>> *Supun Sethunga*
>> Software Engineer
>> WSO2, Inc.
>> http://wso2.com/
>> lean | enterprise | middleware
>> Mobile : +94 716546324
>>
>
>
>
> --
> *Anjana Fernando*
> Senior Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>



-- 
*Supun Sethunga*
Software Engineer
WSO2, Inc.
http://wso2.com/
lean | enterprise | middleware
Mobile : +94 716546324
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Complex Event Processor 4.1.0 Released !!

[Damith Wickramasinghe]

Hi All,

The WSO2 CEP team is pleased to announce the release of version 4.1.0 of
Open Source WSO2 Complex Event Processor.

WSO2 Complex Event Processor (CEP) is a lightweight, easy-to-use, open
source Complex Event Processing server (CEP). It identifies the most
meaningful events within the event cloud, analyzes their impact, and acts
on them in real-time. It's built to be extremely high performing with WSO2
Siddhi and massively scalable using Apache Storm.

WSO2 CEP is built up on the award-winning, WSO2 Carbon platform, which is
based on the OSGi framework enabling better modularity for your service
oriented architecture (SOA). WSO2 Carbon framework contains many enhanced
features and optional components to customize the behavior of the server
through simple, point-and-click provisioning. The CEP can be tightly
integrated with WSO2 Data Analytics Server, by adding support for recording
and post processing events with Map-Reduce via Apache Spark, and WSO2
Machine Learner for predictive analytics.

WSO2 Complex Event Processor is released under Apache Software License
Version 2.0, one of the most business-friendly licenses available today.

For more information on WSO2 Complex Event Processor, please visit
http://wso2.com/products/complex-event-processor/. You can also look at our
 online product documentation

.

WSO2 Complex Event Processor 4.1.0 includes following new features,
improvements and bug fixes.

New Feature

   - [CEP-101 ] - Indexing for
   Hazelcast table
   - [CEP-105 ] - Time length window
   implementation for Siddhi
   - [CEP-644 ] - add insertOrUpdate
   to event table
   - [CEP-1365 ] - Add a function to
   extract 'DAY OF WEEK' from time/timestamp
   - [CEP-1423 ] - Support
   outer/left joins in Siddhi
   - [CEP-1439 ] - Map extension
   support
   - [CEP-1440 ] - Geo Closest
   function
   - [CEP-1441 ] - External Batch
   window for siddhi
   - [CEP-1448 ] - Hazelcast Event
   Table for Siddhi
   - [CEP-1457 ] - Minima and Maxima
   detection on Siddhi
   - [CEP-1459 ] - Instrumentation &
   Monitoring support for CEP and Siddhi

Improvement

   - [CEP-1406 ] - Need to have tool
   tips for icons in the Dashboard
   - [CEP-1419 ] - Provide "insert
   or update" functionality to event tables
   - [CEP-1426 ] - When passing
   parameters to function allow the syntax func(*) if all the attributes of
   the inputstream have to be passed
   - [CEP-1445 ] - Improve
   user-friendliness by sorting drop-down lists
   - [CEP-1447 ] - Instrumentation &
   Monitoring support for CEP and Siddhi
   - [CEP-1450 ] - Adding Arbitrary
   Map support for Receiver Components
   - [CEP-1453 ] - Pause, Resume and
   Stop support for Event Simulator
   - [CEP-1458 ] - Support for more
   then 2 nodes in HA deployment
   - [CEP-1467 ] - When deleting a
   gadget need a configurable option to either delete whole layout with block
   or only the block(gadget content))

Fixed Issues

Bug Fixes  

*Known Issues*

All the open issues pertaining to WSO2 Enterprise Service Bus are reported
at the following location:

Known Issues 
Reporting *Issues*
Issues can be reported using the public JIRA available at
https://wso2.org/jira/browse/CEP
Contact usWSO2 Complex Event Processor developers can be contacted via the
mailing lists:

   Developer List : dev@wso2.org | Subscribe
 | Mail Archive


Alternatively, questions can also be raised in the stackoverflow:
*Forum* http://stackoverflow.com/questions/tagged/wso2/

Support

We are committed to ensuring that your enterprise middleware deployment is
completely supported from evaluation to production. Our unique approach
ensures that all support leverages our open development methodology and is
provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please
visit http://wso2.com/support/.

For more information on WSO2 Complex Event Processor, visit the WSO2 CEP
Product Page 

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.4 RC1

[Amal Gunatilake]

Hi all,

We have tested BPS pack against Carbon Kernel 4.4.4. Everything seems to be
fine.

   - Tested core functionalities of BPS.
   - Passed all integration tests

[x] Stable - go ahead and release.

Best regards,
Amal.

On Wed, Feb 10, 2016 at 11:01 PM, Manuri Amaya Perera 
wrote:

> Hi Devs,
>
> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.4.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12641
>
> Please download and test your products with kernel 4.4.4 RC1 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/manurip/carbon-4.4.4/
>
> ​*Maven staging repository:*​
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-328/
>
> ​*The tag to be voted upon:*​
> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.4-RC1
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Thank you
> Carbon Team​
>
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Amal Gunatilake*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Solution requires to remove/reallocate resources assigned to deleted user

[Nuwan Dias]

When a user creates data within an organisation that data doesn't belong to
the user but rather to the organisation. So when the user is deleted (maybe
because he left the organisation) that data should not be deleted but
rather be governed by the organisation.

In the case of APIs in API Manager they are shared with all users having
the required permission. In the case of Applications they too "can be"
shared if the org opts to.

Thanks,
NuwanD.

On Friday, 26 February 2016, Sumedha Rubasinghe  wrote:

> If we introduce a state to user (like what we have done for access tokens)
> this problem can be easily solved at the first level.
>
> Then it's just a matter of deciding what to do with removed users and
> their data later on as a clean up task by infra.
> On Feb 26, 2016 11:30 AM, "Rasika Perera"  > wrote:
>
>> Hi All,
>>
>> My suggestion is that we need to facilitate *both* approaches(soft delete
>> and hard delete).
>>
>> Glad that at least we have some sort of agreed norms for creating,
>> reading and updating users. *But*; W*hat does "delete" mean in the
>> context of this system/application? *this is a sort of a question that
>> we(middleware provider) might not be able to answer when building the
>> EMM/IoT. For some customers this might be completely forgetting that there
>> was a user X, for some others; it might be that there was a user X who is
>> so and so and did these things.
>>
>> I am suggesting a two level approach.
>>
>> Firstly, if we facilitating deleting a user *inside* our application,
>> when it is triggered it should be a *soft* delete. What it would mean is we 
>> delete
>> the user logically. I would recommend this blog Don't Delete, Just Dont!
>> [1] with a simple
>> example in favour of soft delete. Certainly there might be statistical
>> requirements that need to be drilled down into historical data. And
>> deleting a user from the system should not be a gone-gone at least for some
>> grace period.
>>
>> Secondly, there can be requirements such as reclaim disk space,
>> hard-deletion required as per retention/privacy policy. In that case, we
>> need to provide some sort of a workflow that would clear the stuff. There's
>> a possibility that existence of shared resources might cause even far more
>> complex filtering. On the other hand, as Prabath mentioned when
>> user-management is handed by outside of the system, third party products
>> such as LDAPs. Once a user is removed by an outside functionality there is
>> no default way to listen an event or make a workflow to get triggered this
>> into our application. This is why we need to implement *manually* triggered
>> workflow which can be consumed by system administrators.
>>
>> I think we can decide the best approach if we decide whether to maintain
>> historical data on meta data repositories or not?
>>
>> WDYT?
>>
>> Regards,
>> Rasika
>>
>> [1] http://udidahan.com/2009/09/01/dont-delete-just-dont/
>>
>>
>> On Thu, Feb 25, 2016 at 5:41 PM, Prabath Abeysekera > > wrote:
>>
>>> To my understanding, the most commonly practised use-case in many
>>> organizations is that, user management is handled outside third party
>>> products. For instance, in a typical EMM deployment, which utilizes IS as a
>>> key manager, it is highly unlikely that user provisioning/de-provisioning
>>> is done via IS itself, unless IS is what's primarily used for the same.
>>> Most of the people typically prefer to provision/de-provision user
>>> management related resources by directly accessing some in-house
>>> infrastructure that controls access to the underlying LDAPs, etc. In that
>>> sort of a scenario, there's literally no way that you can listen to some
>>> event and make a workflow or some other similar mechanism to get triggered
>>> automatically. Instead, system administrators would have to manually
>>> trigger a workflow or something to clean-up the orphaned resources. So,
>>> there has to be some functionality, IMO, in EMM to support that aspect.
>>>
>>> If all user-mgt tasks are done through IS, however, you have the
>>> opportunity to use the workflow extension feature to clean-up the aforesaid
>>> resources irrespective of the fact that the user is fully removed from the
>>> underlying user-mgt system or made inactive. Note that, in both cases, the
>>> associated resources have to be cleaned up so, the need of triggering a
>>> workflow to detach all stale resources is must.
>>>
>>> Maintaining statistics is a whole different other aspect, IMO. Without
>>> relying on the primary metadata repositories used by the underlying
>>> user-mgt systems for keeping historical data, some appropriate monitoring
>>> infrastructure has to be used, which would analyze and bring us who is
>>> active in the system and who is not, in the form 

Re: [Dev] Creating Gadgets for Web Application Statistics Monitoring Dashboard - Application Server 6.0.0

[Lochana Ranaweera]

Hi KasunG,

The final deliverable of the dashboard will be a set of gadgets that can be
deployed in the DS separately. It was suggested that ideally with the AS
build the gadgets could be packed as a car file.

As of now, the gadgets are working along with an API that provides the
gadgets with properly structured data obtained out of a mysql database. The
table structure for the tables in the mysql database is to be provided
using a spark script.

The following will have to be done by a user in order view web application
statistics by means of a dashboard created using these gadgets

- Publish webapp statistics to the DAS using publisher valve at AS
- Execute the given Spark script to summarize the event data in to a
database
- Configure the datasource definition in Dashboard Server to retrieve data
from the database
- Create and publish a dashboard using preferred HTTP monitoring gadgets
through dashboard server portal

Thanks.

On Fri, Feb 26, 2016 at 2:08 PM, KasunG Gajasinghe  wrote:

> +architecture
>
> Hi Lochana,
>
> Can you describe what is the final deliverable of the dashboard? Also,
> please explain briefly how the users are going to use these gadgets as well
> as all other dependencies these need. Based on that, we can figure out how
> the folder structure should be.
>
> Btw, can you explain the overall effort required to port these gadgets?
> What needs to be done?
>
> Thanks.
>
> On Fri, Feb 26, 2016 at 12:42 PM, Lochana Ranaweera 
> wrote:
>
>> Hi all,
>>
>> This is regarding the HTTP Monitoring Dashboard for AS 6.0.0. It is to be
>> deployed as a collection of user preferred set of gadgets in the Dashboard
>> Server.
>> As of now, I have ported the* basic* HTTP monitoring functionality as
>> separate gadgets for DS.
>>
>> A typical HTTP monitoring gadget has the following structure:
>>
>> gadget-name
>>├── css
>>├── js
>>├── fonts
>>├── images
>>├── index.xml
>>└── gadget.json
>>
>> What will be the best structure to version control thus created gadgets
>> in the given branch
>>  of AS 6.0.0?
>> Should it be in modules or should it be inside contents directory in the
>> distribution module?
>> The directory structure of the build for new AS 6.0.0 is given below:
>>
>>
>> ​
>> Appreciate your suggestions on this matter.
>>
>> Thanks and Regards,
>> --
>> Lochana Ranaweera
>> Intern Software Engineer
>> WSO2 Inc: http://wso2.com
>> Blog: https://lochanaranaweera.wordpress.com/
>> Mobile: +94716487055 
>>
>>
>
>
> --
>
> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
> email: kasung AT spamfree wso2.com
> linked-in: http://lk.linkedin.com/in/gajasinghe
> blog: http://kasunbg.org
>
>
>



-- 
Lochana Ranaweera
Intern Software Engineer
WSO2 Inc: http://wso2.com
Blog: https://lochanaranaweera.wordpress.com/
Mobile: +94716487055 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC] [IS] Proposal 20: SCIM 2.0 Support to WSO2 Identity Server.

[Yasiru Kassapa]

Hi All,
I am currently a third year undergraduate at University of Moratuwa hoping
to contribute to a GSoc 2016 project at WSO2. I am a bit familiar with WSO2
Identity Server 5.1.0 and the above project has interested me a lot.

Upon researching on SCIM spec and Identity Server I've come across WSO2
Charon, would we be developing Charon further to support SCIM 2.0 or using
an open source SCIM implementation like eSCIMo to add SCIM 2.0 support for
WSO2 Identity Server?

Thank you & Regards.
Yasiru Kassapa.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to enable SMS based OTPs in Identity Server

[Tharindu Edirisinghe]

Hi Thilini,

Normally for Identity Management notification flows, if any customization
is needed, what we do is that use the
*Identity.Mgt.Notification.Sending.Module.1
*extension point in identity-mgt.properties file and plug our own custom
implementation.

For the custom implementation, either we can extend
*org.wso2.carbon.identity.mgt.mail.DefaultEmailSendingModule* class or
implement the *org.wso2.carbon.identity.mgt.mail.AbstractEmailSendingModule
*class. There we can write our logic overriding the *sendEmail() *method.

However inside the sendEmail() method, we are unaware of the user who
should get this notification. For that, we can identify the user by adding
some placeholders like {user-name}, {userstore-domain} and {tenant-domain}
in the email template of OTP [1].

However in OTP notification flow, the {userstore-domain} and
{tenant-domain} placeholders will not be resolved to the particular values
of the user which is a limitation in IS currently. This is raised in the
JIRA [2].

Therefore we cannot write a custom implementation for the OTP notification
flow using the Identity Management extension point.

However since the SMSOTP is already there, you can use it instead of a
custom implementation.


[1]
http://tharindue.blogspot.com/2015/10/a-step-by-step-guide-to-setup-one-time.html
[2] https://wso2.org/jira/browse/IDENTITY-4372

Thanks,
TharinduE

On Fri, Feb 26, 2016 at 12:14 PM, Elilmatha Sivanesan 
wrote:

> Hi Thilini,
>
> You can find the source code at [1], and download the authenticator from
> store [2].
>
> [1] https://github.com/wso2-extensions/identity-outbound-auth-sms-otp
>
> [2]
> https://store.wso2.com/store/assets/isconnector/bfbe6b6a-c694-4890-b6b4-5a3098bf98f4
>
> Thanks.
>
> On Fri, Feb 26, 2016 at 12:05 PM, Lakshani Gamage 
> wrote:
>
>> Hi Thilini,
>>
>> [2]  will be a help.
>>
>> [2] 
>> *https://docs.wso2.com/display/ISCONNECTORS/Configuring+SMSOTP+Authenticator
>> *
>>
>> Thanks,
>> Lakshani.
>>
>> On Fri, Feb 26, 2016 at 11:01 AM, Thilini Cooray 
>> wrote:
>>
>>> Hi,
>>>
>>> I want to use SMS based OTPs for user registration in WSO2 Identity
>>> Server.
>>> My identity server version is 5.0.0 with SP1.
>>>
>>> [1] has mentioned that we can achieve this via extending 
>>> IdentityMgtEvenListener
>>> or writing custom listener. Can you please point me to any available
>>> resources which I can look into ?
>>>
>>> [1] [Dev] WSO2 Identity Server OTP SMS
>>>
>>> Thanks.
>>>
>>> --
>>> Best Regards,
>>>
>>> *Thilini Cooray*
>>> Software Engineer
>>> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
>>> E-mail : thili...@wso2.com
>>>
>>> WSO2 Inc. www.wso2.com
>>> lean.enterprise.middleware
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Lakshani Gamage
>>
>> *Software Engineer*
>> Mobile : +94 (0) 71 5478184 <%2B94%20%280%29%20773%20451194>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *S.Elilmatha*
> Associate  Software Engineer,
>
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> Mobile 0779842221.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Platform Security Team
Blog : tharindue.blogspot.com
mobile : +94 775181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Creating Gadgets for Web Application Statistics Monitoring Dashboard - Application Server 6.0.0

[KasunG Gajasinghe]

+architecture

Hi Lochana,

Can you describe what is the final deliverable of the dashboard? Also,
please explain briefly how the users are going to use these gadgets as well
as all other dependencies these need. Based on that, we can figure out how
the folder structure should be.

Btw, can you explain the overall effort required to port these gadgets?
What needs to be done?

Thanks.

On Fri, Feb 26, 2016 at 12:42 PM, Lochana Ranaweera 
wrote:

> Hi all,
>
> This is regarding the HTTP Monitoring Dashboard for AS 6.0.0. It is to be
> deployed as a collection of user preferred set of gadgets in the Dashboard
> Server.
> As of now, I have ported the* basic* HTTP monitoring functionality as
> separate gadgets for DS.
>
> A typical HTTP monitoring gadget has the following structure:
>
> gadget-name
>├── css
>├── js
>├── fonts
>├── images
>├── index.xml
>└── gadget.json
>
> What will be the best structure to version control thus created gadgets in
> the given branch 
> of AS 6.0.0?
> Should it be in modules or should it be inside contents directory in the
> distribution module?
> The directory structure of the build for new AS 6.0.0 is given below:
>
>
> ​
> Appreciate your suggestions on this matter.
>
> Thanks and Regards,
> --
> Lochana Ranaweera
> Intern Software Engineer
> WSO2 Inc: http://wso2.com
> Blog: https://lochanaranaweera.wordpress.com/
> Mobile: +94716487055 
>
>


-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2016: Proposal 7

[Nadeeshaan Gunasinghe]

Hi Dinanjana,

First let's try to build WSO2 ESB from source and then dig in deep to the
source. In order to do so you will need build the following repositories in
the order.

[1] https://github.com/wso2/wso2-synapse
[2] https://github.com/wso2/carbon-mediation
[3] https://github.com/wso2/product-esb

Thanks,

*Nadeeshaan Gunasinghe*
Software Engineer, WSO2 Inc. http://wso2.com
+94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe <#>

  

Get a signature like this: Click here!


On Thu, Feb 25, 2016 at 6:24 AM, Dinanjana Gunaratne <
dinanjanagunara...@gmail.com> wrote:

> Dear Isuru,
>
> Can you send me a link of api documentation of management package of ESB ?
>
> On Sun, Feb 21, 2016 at 2:34 PM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Dear Isuru,
>>
>> Sorry for bothering you again. I created a sample module with some of the
>> requirements you mentioned in gsoc project page. Those requirements are
>> creating thread dumps when resources usage increased unexpectedly. Now I
>> like to know how to integrate this in to ESB and test the functionality. I
>> couldn't find the location of ESB source.
>> On Feb 20, 2016 9:33 AM, "Dinanjana Gunaratne" <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Dear Isuru,
>>>
>>> Are we looking at an implementation like this ?
>>> "Dashboard is a remote monitoring system which was developed to monitor
>>> the status(server's aliveness and management details) of software deployed
>>> remotely. This monitoring system is highly scalable and does not depend on
>>> any component which is being monitored. With Dashboard comes a Java library
>>> called "HeartBeat".HeartBeat is a client which was developed by us for
>>> connects to Dashboard and share information. So any component wish to
>>> register with Dashboard monitoring system must implement that Java
>>> library."
>>>
>>> I did this during my internship. I think we are looking at an
>>> implementation within esb for debugging and monitoring. am i correct ? :)
>>>
>>>
>>> On Sat, Feb 20, 2016 at 9:12 AM, Isuru Udana  wrote:
>>>
 Great...!

 btw, don't call me "Sir" :)

 On Sat, Feb 20, 2016 at 8:58 AM, Dinanjana Gunaratne <
 dinanjanagunara...@gmail.com> wrote:

> Dear Isuru,
> Found the solution :)
>
> On Sat, Feb 20, 2016 at 8:49 AM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Dear Isuru,
>> Sorry for bothering you. Found the solution for earlier problem from
>> here [1
>> ].
>> Now i am facing a new problem. axis2 server looking for axis2.xml on 
>> wrong
>> directory. below is the stack trace
>>
>> [2016-02-20 08:41:21,491] FATAL
>> {samples.util.SampleAxis2ServerManager} -  [SimpleAxisServer] Shutti
>> ng down. Error starting SimpleAxisServer
>> org.apache.axis2.AxisFault: System can not find the given axis2.xml
>> E:\Project\wso2esb-4.9.0\samples
>> \axis2Serverrepository\conf\axis2.xml
>> at
>> org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigu
>> rator.java:118)
>> at
>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(Configura
>> tionContextFactory.java:64)
>> at
>> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSy
>> stem(ConfigurationContextFactory.java:210)
>> at
>> samples.util.SampleAxis2ServerManager.start(SampleAxis2ServerManager.java:93)
>> at
>> samples.util.SampleAxis2Server.startServer(SampleAxis2Server.java:61)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:483)
>> at samples.util.Bootstrap.main(Bootstrap.java:132)
>>
>> I have defined AXIS2_HOME correctly
>>
>> [1]
>> http://stackoverflow.com/questions/32866263/axis2server-packed-with-esb-4-9-0-doesnt-start-while-it-works-fine-4-8-0
>>
>> On Sat, Feb 20, 2016 at 7:55 AM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Dear sir,
>>>
>>> When i tried to