[Dev] [ESB-Connector] Google Spreadsheet Connector Documentation not Changed

[Rajjaz Mohammed]

Hi All,
Please Note $Subject . Authentication method changed to OAuth 2.0 so init
method should be oAuth2init . but its still not updated in Documentation.

-- 
Thank you
Best Regards

*Rajjaz HM*
Associate Software Engineer
WSO2 Inc. 
lean | enterprise | middleware
Mobile : +94752833834
Email  :raj...@wso2.com
LinkedIn | Blogger | WSO2 Profile

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

Re: [Dev] at_hash hash size

[Johann Nallathamby]

Thanks Udara for reporting this. Fixed it with PRs [1] and [2].

[1] https://github.com/wso2/carbon-identity/pull/814
[2] https://github.com/wso2/carbon-identity/pull/815

On Tue, Aug 11, 2015 at 2:55 PM, Udara Liyanage  wrote:

>
> Hi,
>
> The fixing PR of [3] (Access Token hash value is calculated incorrectly)
> pick the first 16 bytes as the left most half of the digest. Just for my
> curiosity, can we guarantee it is always
> 16 bytes, or otherwise digest is always 32 bytes. Does n't it vary
> depending on the algorithm use(alg header).
>
> byte[] leftmost = new byte[16];
> +for (int i = 0; i < 16; i++){
> +leftmost[i]=digest[i];
> +}
>
>
> at_hash
>   OPTIONAL.  Access Token hash value.  Its value is the base64url
>   encoding of the left-most half of the hash of the octets of the
>   ASCII representation of the "access_token" value, where the hash
>   algorithm used is the hash algorithm used in the "alg" parameter
>   of the State Token's JWS [JWS] header. * For instance, if the "alg"*
> *  is "RS256"*, hash the "access_token" value with SHA-256, then take
>   the left-most 128 bits and base64url encode them.  The "at_hash"
>
>
> [1]
> https://github.com/wso2/carbon-identity/commit/1756178b9ad62295eb5274a47b06775de13eab95
> [2] https://tools.ietf.org/html/draft-bradley-oauth-jwt-encoded-state-01
> [3] https://wso2.org/jira/browse/IDENTITY-3385
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Integration 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

Re: [Dev] [ML] Error when deserializing model summary

[Madawa Soysa]

Yes I was able to resolve the issue by removing RDD fields from the
SummaryModel object as @Mano pointed out. Still I have the same exception
when retrieving the model. Trying to fix that issue.

On 14 August 2015 at 10:43, Nirmal Fernando  wrote:

> Thanks Niranda, this doc is useful.
>
> On Fri, Aug 14, 2015 at 10:36 AM, Niranda Perera  wrote:
>
>> From what I know, OneToOneDependancy come into play when spark tries to
>> create the RDD dependency tree.
>>
>> Just thought of sharing that. this would be a good resource [1] :-)
>>
>> [1]
>> https://databricks-training.s3.amazonaws.com/slides/advanced-spark-training.pdf
>>
>> On Thu, Aug 13, 2015 at 12:09 AM, Nirmal Fernando 
>> wrote:
>>
>>> What is *org.apache.spark.OneToOneDependency ? Is it something you use?*
>>>
>>> On Wed, Aug 12, 2015 at 11:30 PM, Madawa Soysa 
>>> wrote:
>>>
 Hi,

 I created a model summary in order to show the model data in the
 analysis.jag page.
 But when refreshing the page after building the model I get the
 following error.

 org.wso2.carbon.ml.core.exceptions.MLAnalysisHandlerException:  An
 error has occurred while extracting all the models of analysis id: 13
 at
 org.wso2.carbon.ml.core.impl.MLAnalysisHandler.getAllModelsOfAnalysis(MLAnalysisHandler.java:245)
 at
 org.wso2.carbon.ml.rest.api.AnalysisApiV10.getAllModelsOfAnalysis(AnalysisApiV10.java:517)
 Caused by:
 org.wso2.carbon.ml.database.exceptions.DatabaseHandlerException:  An error
 has occurred while extracting all the models of analysis id: 13
 at
 org.wso2.carbon.ml.database.internal.MLDatabaseService.getAllModels(MLDatabaseService.java:1797)
 at
 org.wso2.carbon.ml.core.impl.MLAnalysisHandler.getAllModelsOfAnalysis(MLAnalysisHandler.java:243)
 ... 52 more

 *Caused by: java.lang.ClassNotFoundException:
 org.apache.spark.OneToOneDependency cannot be found by
 org.scala-lang.scala-library_2.10.4.v20140209-180020-VFINAL-b66a3965*
 at
 org.wso2.carbon.ml.database.util.MLDBUtil.getModelSummaryFromInputStream(MLDBUtil.java:54)
 at
 org.wso2.carbon.ml.database.internal.MLDatabaseService.getAllModels(MLDatabaseService.java:1790)
 ... 53 more

 I guess there is an error in persistence of the model summary object,
 what should be the cause for this error? [1]
 
  contains
 the commit which I introduced the model summary.

 [1] -
 https://github.com/madawas/carbon-ml/commit/987c799231dad2bab6f4046df7acc672d0564f22

 --

 *_**Madawa Soysa*

 Undergraduate,

 Department of Computer Science and Engineering,

 University of Moratuwa.


 Mobile: +94 71 461 6050 <%2B94%2075%20812%200726> | Email:
 madawa...@cse.mrt.ac.lk
 LinkedIn  | Twitter
  | Tumblr 

>>>
>>>
>>>
>>> --
>>>
>>> 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
>>>
>>>
>>
>>
>> --
>> *Niranda Perera*
>> Software Engineer, WSO2 Inc.
>> Mobile: +94-71-554-8430
>> Twitter: @n1r44 
>> https://pythagoreanscript.wordpress.com/
>>
>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>


-- 

*_**Madawa Soysa*

Undergraduate,

Department of Computer Science and Engineering,

University of Moratuwa.


Mobile: +94 71 461 6050 <%2B94%2075%20812%200726> | Email:
madawa...@cse.mrt.ac.lk
LinkedIn  | Twitter
 | Tumblr 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [CARBON-15265][IDENTITY-3423][MB-1128] is reproducible in kernal 4.4.1

[Johann Nallathamby]

I have resolved CARBON-15265/IDENTITY-3511 as it seems to be related but
different. The current issue will be tracked in IDENTITY-3423.

On Fri, Aug 14, 2015 at 4:07 PM, Indika Sampath  wrote:

> Hi Tharindu,
>
> Please find the attach files which contains stack trace separately.
>
> Cheers!
>
> On Fri, Aug 14, 2015 at 3:55 PM, Tharindu Edirisinghe 
> wrote:
>
>> Hi Indika,
>>
>> We are looking to identify the issue. Can you also send us the stack
>> trace of the two scenarios separately.
>>
>> Thanks,
>> TharinduE
>>
>> On Fri, Aug 14, 2015 at 3:50 PM, Indika Sampath  wrote:
>>
>>> Hi Tharindu,
>>>
>>> Above deadlock occurred when we remove topic subscription.
>>>
>>> DELETE FROM UM_HYBRID_ROLE WHERE UM_ROLE_NAME =
>>> 'Q_tmp_192_168_1_21_41372_1' AND UM_TENANT_ID=-1234
>>>
>>> We are getting another deadlock when we adding topic subscription also.
>>>
>>> INSERT INTO UM_HYBRID_USER_ROLE (UM_USER_NAME, UM_ROLE_ID, UM_TENANT_ID,
>>> UM_DOMAIN_ID) VALUES ('admin',(SELECT UM_ID FROM UM_HYBRID_ROLE WHERE
>>> UM_ROLE_NAME='Q_tmp_192_168_1_21_58252_1' AND UM_TENANT_ID=-1234), -1234,
>>> (SELECT UM_DOMAIN_ID FROM UM_DOMAIN WHERE UM_TENANT_ID=-1234 AND
>>> UM_DOMAIN_NAME='PRIMARY'))
>>>
>>> Please find the attached text file which contains output of SHOW ENGINE
>>> INNODB STATUS;
>>>
>>> Cheers!
>>>
>>> On Fri, Aug 14, 2015 at 3:40 PM, Indika Sampath 
>>> wrote:
>>>
 Hi Tharindu,

 Please find the attach text file which contains output of above command.

 Cheers!

 On Fri, Aug 14, 2015 at 1:03 PM, Tharindu Edirisinghe <
 tharin...@wso2.com> wrote:

> Hi Ramith,
>
> It seems this is not the exact same issue reported in [1]. For
> investigating further can you connect to mysql database from 
> terminal/mysql
> client and run the following command and share the output with us. We
> should be able to see the database level errors caused from the output of
> this command [2].
>
> *SHOW ENGINE INNODB STATUS;*
>
> [1] https://wso2.org/jira/browse/CARBON-15265
> [2] https://dev.mysql.com/doc/refman/5.5/en/show-engine.html
>
> Thanks,
> TharinduE
>
> On Fri, Aug 14, 2015 at 12:44 PM, Ramith Jayasinghe 
> wrote:
>
>> $subject. Could we have a look?
>>
>> --
>> Ramith Jayasinghe
>> Technical Lead
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> E: ram...@wso2.com
>> P: +94 777542851
>>
>>
>
>
> --
>
> Tharindu Edirisinghe
> Software Engineer | WSO2 Inc
> Identity Server Team
> Blog : tharindue.blogspot.com
> mobile : +94 775 181586
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Indika Sampath
 Senior Software Engineer
 WSO2 Inc.
 http://wso2.com

 Phone: +94 716 424 744
 Blog: http://indikasampath.blogspot.com/


>>>
>>>
>>> --
>>> Indika Sampath
>>> Senior Software Engineer
>>> WSO2 Inc.
>>> http://wso2.com
>>>
>>> Phone: +94 716 424 744
>>> Blog: http://indikasampath.blogspot.com/
>>>
>>>
>>
>>
>> --
>>
>> Tharindu Edirisinghe
>> Software Engineer | WSO2 Inc
>> Identity Server Team
>> Blog : tharindue.blogspot.com
>> mobile : +94 775 181586
>>
>>
>>
>
>
> --
> Indika Sampath
> Senior Software Engineer
> WSO2 Inc.
> http://wso2.com
>
> Phone: +94 716 424 744
> Blog: http://indikasampath.blogspot.com/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Integration 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

[Dev] Please review and merge PR for IDENTITY-3423

[Indunil Upeksha Rathnayake]

Hi,

Please review and merge the PR [1] as the fix for the public JIRA [2] that
relates to [3].

[1] https://github.com/wso2/carbon4-kernel/pull/386
[2] https://wso2.org/jira/browse/IDENTITY-3423
[3] https://wso2.org/jira/browse/MB-1128

Thanks and Regards
-- 
Indunil Upeksha Rathnayake
Software Engineer | WSO2 Inc
Emailindu...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ML] Progress with Deeplearning Integration

[Thushan Ganegedara]

Hi all,

Below is a progress report on the Deeplearning integration

The previous two weeks I mainly dedicated for testing what is already
implemented for errors and potential enhancements.

*Getting the deeplearning component to work*
After rigorously testing the deeplearning component, it seems to be working
well with all the datasets tested so far. There were few bugs in the
implementation (i.e. onExBarrierCompletion error, conversion to enum) which
have been resolved with the help of WSO2 team and H-2-O team.

*​Testing the deeplearning component*
So far DL component has been tested against 4 datasets. They are,

*Iris​, MNIST, Leaf, Action Recognition*

Deeplearning has shown remarkable performance with all the datasets except
for the leaf dataset. (The performance for the leaf dataset does not exceed
the Linear Reg - L-BFGS by a lot) I speculate this could be due to a
linearity in data (so the model is too complicated). For all the other
datasets, DL reaches 95%+ without much effort

*Fixing minor bugs and Enhancements*
Few minor bugs were fixed such as,

Input sanitization error for Stacked Autoencoders
​Code formatting and changes suggested in the review​


​Enhancements include,

Introducing ​activation function selection




-- 
Regards,

Thushan Ganegedara
School of IT
University of Sydney, Australia
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] What is the best approach to version webapps?

[Joseph Fonseka]

Hi Nirmal

IMO we should have version number in war since we will be shipping fixes
which means a new war. And changing the context is also not good because
then client has to changed. So I think the third option is the best if it
works.


Thanks
Jo

On Sat, Aug 15, 2015 at 9:16 PM, Thilini Cooray  wrote:

> Hi Nirmal,
>
> Thanks for the suggestion. We are looking in to the most suitable approach
> to version the API. As you have mentioned, it would be a better approach if
> we can direct the requests to the latest API version. I will look into it.
>
> On Sat, Aug 15, 2015 at 11:16 AM, Nirmal Fernando  wrote:
>
>> Any particular reason for having a war file per version? Much better
>> approach would be to version the API classes. That way you could get all
>> traffic without an explicit version on to the latest available REST API.
>> You need to embed version info into API classes.
>>
>> https://developer.github.com/v3/ Github api is a good reference to
>> check.
>>
>> On Sat, Aug 15, 2015 at 10:17 AM, Sanjeewa Malalgoda 
>> wrote:
>>
>>> +1 for option 02.
>>> On Aug 15, 2015 10:01 AM, "Thilini Cooray"  wrote:
>>>
 Hi,

 We need to version a  webapp which contains RESTful APIs.
 This webapp will be deployed in WSO2 Api Manager.

 Following are 3 approaches I found for the purpose :

1. Make war name as ${project.artifactId}-${pom.version}>>>warName> which will output webappName-version.war

Its endpoint address is http://HostName:port
 /webappName-version/
Ex : https://localhost:9443/api-import-export-1.0.0/

2.  Make war name as 
 ${project.artifactId}#${pom.version} which will output
 webappName#version.war

 This will allow Tomcat server to identify versions of the
 web app.
 Its endpoint address is http://HostName:port/
 webappName/version/
 Ex : https://localhost:9443/api-import-export/1.0.0/
 

 WSO2 Application Server follows this approach [1].

3.  Apache tomcat consists of another approach using "##" for
 context naming [2].
 That approach needs to make war name as 
 ${project.artifactId}##${pom.version} which will output
 webappName##version.war

Its endpoint address is http://HostName:port/webappName/
This will use the latest version.
Ex : https://localhost:9443/api-import-export/
 
However this naming convention cannot be deployed in WSO2
 Api Manager. It returns AbstractWebappDeployer Unsupported file path
 format.

 What is the best approach to follow when versioning the webapp ?

 [1] https://docs.wso2.com/display/AS521/Webapp+Versioning
 [2] http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Naming

 Thanks,
 ThiliniC.

 --
 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
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Team Lead - WSO2 Machine Learner
>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>
>
> --
> 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
>
>


-- 

-- 
*Joseph Fonseka*
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 772 512 430
skype: jpfonseka

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

[Dev] [PR] API Changes for Zoho Recruit connector

[Kesavan Yogarajah]

Hi Malaka,

Please find the pull request[1] for Zoho Recruit connector.

Thanks

[1] - https://github.com/wso2/esb-connectors/pull/271

Kesavan Yogarajah
Associate Software Engineer
Mobile :+94 (0) 779 758021
kesav...@wso2.com
WSO2, Inc.
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] What is the best approach to version webapps?

[Nuwan Dias]

Yes, the objective is to be able to release newer versions of webapps
without depending on product releases so we can iteratively do improvements
to those. Ex: An app with API Analytics.

Thanks,
NuwanD.

On Mon, Aug 17, 2015 at 8:49 AM, Joseph Fonseka  wrote:

> Hi Nirmal
>
> IMO we should have version number in war since we will be shipping fixes
> which means a new war. And changing the context is also not good because
> then client has to changed. So I think the third option is the best if it
> works.
>
>
> Thanks
> Jo
>
> On Sat, Aug 15, 2015 at 9:16 PM, Thilini Cooray  wrote:
>
>> Hi Nirmal,
>>
>> Thanks for the suggestion. We are looking in to the most suitable
>> approach to version the API. As you have mentioned, it would be a better
>> approach if we can direct the requests to the latest API version. I will
>> look into it.
>>
>> On Sat, Aug 15, 2015 at 11:16 AM, Nirmal Fernando 
>> wrote:
>>
>>> Any particular reason for having a war file per version? Much better
>>> approach would be to version the API classes. That way you could get all
>>> traffic without an explicit version on to the latest available REST API.
>>> You need to embed version info into API classes.
>>>
>>> https://developer.github.com/v3/ Github api is a good reference to
>>> check.
>>>
>>> On Sat, Aug 15, 2015 at 10:17 AM, Sanjeewa Malalgoda 
>>> wrote:
>>>
 +1 for option 02.
 On Aug 15, 2015 10:01 AM, "Thilini Cooray"  wrote:

> Hi,
>
> We need to version a  webapp which contains RESTful APIs.
> This webapp will be deployed in WSO2 Api Manager.
>
> Following are 3 approaches I found for the purpose :
>
>1. Make war name as ${project.artifactId}-${pom.version}warName> which will output webappName-version.war
>
>Its endpoint address is http://HostName:port
> /webappName-version/
>Ex : https://localhost:9443/api-import-export-1.0.0/
>
>2.  Make war name as 
> ${project.artifactId}#${pom.version} which will output
> webappName#version.war
>
> This will allow Tomcat server to identify versions of the
> web app.
> Its endpoint address is http://HostName:port/
> webappName/version/
> Ex : https://localhost:9443/api-import-export/1.0.0/
> 
>
> WSO2 Application Server follows this approach [1].
>
>3.  Apache tomcat consists of another approach using "##" for
> context naming [2].
> That approach needs to make war name as 
> ${project.artifactId}##${pom.version} which will output
> webappName##version.war
>
>Its endpoint address is http://HostName:port/webappName/
>This will use the latest version.
>Ex : https://localhost:9443/api-import-export/
> 
>However this naming convention cannot be deployed in WSO2
> Api Manager. It returns AbstractWebappDeployer Unsupported file path
> format.
>
> What is the best approach to follow when versioning the webapp ?
>
> [1] https://docs.wso2.com/display/AS521/Webapp+Versioning
> [2] http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Naming
>
> Thanks,
> ThiliniC.
>
> --
> 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


>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Team Lead - WSO2 Machine Learner
>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>
>>
>> --
>> 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
>>
>>
>
>
> --
>
> --
> *Joseph Fonseka*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 772 512 430
> skype: jpfonseka
>
> * *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nuwan Dias

Technical Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PR] API Changes for Zoho Recruit connector

[Malaka Silva]

Merged please re upload the connector

On Mon, Aug 17, 2015 at 8:51 AM, Kesavan Yogarajah 
wrote:

> Hi Malaka,
>
> Please find the pull request[1] for Zoho Recruit connector.
>
> Thanks
>
> [1] - https://github.com/wso2/esb-connectors/pull/271
>
> Kesavan Yogarajah
> Associate Software Engineer
> Mobile :+94 (0) 779 758021
> kesav...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>



-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/


Save a tree -Conserve nature & Save the world for your future. Print this
email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][EMM] Android enrollment production readiness

[Inosh Perera]

Hi Milan/Kasun,

During the EMM registration[1], Step 3 and 4 where the user has to enter
the IP/domain;
 should be designed in a way where in a production scenario, this step can
be bypassed. In other words, the IP can be hard coded and the step can be
hidden from the user, since in production the user is not expected to know
about the backend IPs/Domains. Same can be applicable to step 5 Ownership
type selection. Once option would be to maintain these in a configuration
file.

[1].
https://docs.wso2.com/display/EMM200/End-user+Registering+an+Android+Device

Regards,
Inosh

-- 
Inosh Perera
Software Engineer, WSO2 Inc.
Tel: 0785293686
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB-Connector] Google Spreadsheet Connector Documentation not Changed

[Nirdesha Munasinghe]

Copying Nisrin...

On Sun, Aug 16, 2015 at 2:58 PM, Rajjaz Mohammed  wrote:

> Hi All,
> Please Note $Subject . Authentication method changed to OAuth 2.0 so init
> method should be oAuth2init . but its still not updated in Documentation.
>
> --
> Thank you
> Best Regards
>
> *Rajjaz HM*
> Associate Software Engineer
> WSO2 Inc. 
> lean | enterprise | middleware
> Mobile : +94752833834
> Email  :raj...@wso2.com
> LinkedIn | Blogger | WSO2 Profile
> 
>
> --
> You received this message because you are subscribed to the Google Groups
> "WSO2 Documentation Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to documentation+unsubscr...@wso2.com.
> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>



-- 

Thanks,

Nirdesha Munasinghe,
WSO2 Inc.
Web:http://wso2.com

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

Re: [Dev] [DEV][EMM] Android enrollment production readiness

[Dilshan Edirisuriya]

Hi,

Better make the IP configurable so that it can be hidden anytime specially
when it comes to a production environment. When it comes to domain also
same thing is applicable since for most of the deployment it will only need
just one tenant.

Regards,

Dilshan

On Mon, Aug 17, 2015 at 10:07 AM, Inosh Perera  wrote:

> Hi Milan/Kasun,
>
> During the EMM registration[1], Step 3 and 4 where the user has to enter
> the IP/domain;
>  should be designed in a way where in a production scenario, this step can
> be bypassed. In other words, the IP can be hard coded and the step can be
> hidden from the user, since in production the user is not expected to know
> about the backend IPs/Domains. Same can be applicable to step 5 Ownership
> type selection. Once option would be to maintain these in a configuration
> file.
>
> [1].
> https://docs.wso2.com/display/EMM200/End-user+Registering+an+Android+Device
>
> Regards,
> Inosh
>
> --
> Inosh Perera
> Software Engineer, WSO2 Inc.
> Tel: 0785293686
>



-- 
Dilshan Edirisuriya
Senior Software Engineer - WSO2
Mob: + 94 777878905
http://wso2.com/
https://www.linkedin.com/profile/view?id=50486426
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS][Doc] Configuring a Hbase datasource doc is not correct

[Anjana Fernando]

Hi,

@Gokul, we will have to put at least a sample configuration of how a
possible proper clustered setup and a pseudo-distributed would be like. So
an user can create a setup quickly. And of course, we do not have to put
all the possible configuration properties of HBase, for that, pointing to
the official HBase documentation is fine. But still, our docs should
contain enough information for an user to start with a typical setup. Thank
you Nirmal for the comments.

Cheers,
Anjana.

On Sun, Aug 16, 2015 at 10:20 AM, Nirmal Fernando  wrote:

> Also, hbase.master, didn't work of course, that's why I had to read.
>
> On Sun, Aug 16, 2015 at 10:19 AM, Nirmal Fernando  wrote:
>
>> Hi Gokul,
>>
>> I'm sorry, I have to disagree. Here I am talking about a DAS config file,
>> not a HBase config file, hence the documentation should be precise and
>> clear.
>>
>> More over, I think you need to test this again. As I read from the
>> Internet, hbase.master property is deprecated and clients should use
>> Zookeeper quorum IP and Zookeeper client port to retrieve the master
>> IP/port, as master ports are allocated dynamically (my setup is a
>> pseudo-distributed one).
>>
>> IMO in our documentation, we should properly guide our users, so they
>> don't need to learn it hard-way like I did.
>>
>> On Sat, Aug 15, 2015 at 11:41 PM, Gokul Balakrishnan 
>> wrote:
>>
>>> Hi Nirmal,
>>>
>>> The doc that you've pointed merely shows how the datasource should be
>>> configured (i.e. the format), and does not necessarily represent a complete
>>> configuration, which would naturally depend on the environment. But I agree
>>> the wording "add the following configuration" is incorrect and misleading.
>>> @Praneesha could you please correct it accordingly?
>>>
>>> The hbase.master property is used for identifying the HBase master node,
>>> through which all schema-related operations would go. So unless the HBase
>>> node is in the same machine as the DAS node, that property is required.
>>>
>>> Thanks,
>>> Gokul.
>>>
>>>
>>> On Saturday, 15 August 2015, Nirmal Fernando  wrote:
>>>

 https://docs.wso2.com/display/DAS300/Configuring+a+HBase+Datasource

 hbase.master doesn't work, what works is following;

 

 WSO2_ANALYTICS_EVENT_STORE_DB_HBASE

 The datasource used for analytics file
 system

 

 jdbc/WSO2HBaseDB

 

 

 

 **

 *hbase.zookeeper.quorum*

 *192.168.x.x*

 **

 

 fs.hdfs.impl


 org.apache.hadoop.hdfs.DistributedFileSystem

 

 

 fs.file.impl


 org.apache.hadoop.fs.LocalFileSystem

 

 

 

 

 --

 Thanks & regards,
 Nirmal

 Team Lead - WSO2 Machine Learner
 Associate Technical Lead - Data Technologies Team, WSO2 Inc.
 Mobile: +94715779733
 Blog: http://nirmalfdo.blogspot.com/



>>>
>>> --
>>> Gokul Balakrishnan
>>> Senior Software Engineer,
>>> WSO2, Inc. http://wso2.com
>>> Mob: +94 77 593 5789 | +1 650 272 9927
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Team Lead - WSO2 Machine Learner
>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>


-- 
*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] [DEV][EMM] Android enrollment production readiness

[Dulitha Wijewantha]

Hi Inosh,
+1 for the property file. We also can trigger the build from Gradle for
environments right? [1]. We can pass in an environment parameter to build
an artifact.

[1] -
http://tobiasbayer.com/blog/2011/04/16/building-for-different-environments-with-gradle/
Cheers~

On Mon, Aug 17, 2015 at 3:08 PM, Dilshan Edirisuriya 
wrote:

> Hi,
>
> Better make the IP configurable so that it can be hidden anytime specially
> when it comes to a production environment. When it comes to domain also
> same thing is applicable since for most of the deployment it will only need
> just one tenant.
>
> Regards,
>
> Dilshan
>
> On Mon, Aug 17, 2015 at 10:07 AM, Inosh Perera  wrote:
>
>> Hi Milan/Kasun,
>>
>> During the EMM registration[1], Step 3 and 4 where the user has to enter
>> the IP/domain;
>>  should be designed in a way where in a production scenario, this step
>> can be bypassed. In other words, the IP can be hard coded and the step can
>> be hidden from the user, since in production the user is not expected to
>> know about the backend IPs/Domains. Same can be applicable to step
>> 5 Ownership type selection. Once option would be to maintain these in a
>> configuration file.
>>
>> [1].
>> https://docs.wso2.com/display/EMM200/End-user+Registering+an+Android+Device
>>
>> Regards,
>> Inosh
>>
>> --
>> Inosh Perera
>> Software Engineer, WSO2 Inc.
>> Tel: 0785293686
>>
>
>
>
> --
> Dilshan Edirisuriya
> Senior Software Engineer - WSO2
> Mob: + 94 777878905
> http://wso2.com/
> https://www.linkedin.com/profile/view?id=50486426
>



-- 
Dulitha Wijewantha (Chan)
Software Engineer - Mobile Development
WSO2 Inc
Lean.Enterprise.Middleware
 * ~Email   duli...@wso2.com *
*  ~Mobile +94712112165*
*  ~Website   dulitha.me *
*  ~Twitter @dulitharw *
  *~Github @dulichan *
  *~SO @chan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please Review and Merge

[Chamin Dias]

Hi,

This is the Fix [1] for JIRA issue [2].

Please review and merge.

[1] https://github.com/wso2/carbon-apimgt/pull/907
[2] https://wso2.org/jira/browse/APIMANAGER-3963

Thanks.

-- 
Chamin Dias
*Software Engineer*
Mobile : +94 (0) 716 097455 <%2B94%20%280%29%20773%20451194>
Email : cham...@wso2.com
Blog : https://chamindias.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UI / UX] [BPS] Calender date picker is not shown in Firefox for 'Date' input type

[Sharon David]

Hi Milinda,

As per the offline chat I had with you, incorporate [
bootstrap-daterangepicker
], this will help
solve the issue.
We have user bootstrap-daterangepicker on some of our other product.
Let me know if you have an issue with the same.

[1] https://github.com/dangrossman/bootstrap-daterangepicker
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Madusanka Premaratne

[Roshan Wijesena]

Congratulations!

On Sat, Aug 15, 2015 at 10:15 AM, Nuwan Dias  wrote:

> Hi,
>
> It is with great pleasure we welcome Madusanka Premaratne as a
> WSO2 Committer. @Madusanka, congratulations and keep up the good work!
>
> Thanks,
> NuwanD.
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

[Dev] PR for RabbitMQ Inbound sample.

[Kesavan Yogarajah]

Hi Malaka,

Please review and merge the PR [1] for RabbitMQ Inbound sample.

[1] - https://github.com/wso2/product-esb/pull/289

Thanks

Kesavan Yogarajah
Associate Software Engineer
Mobile :+94 (0) 779 758021
kesav...@wso2.com
WSO2, Inc.
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] Carbon Spark JDBC connector

[Iranga Muthuthanthri]

Would it be possible to use the connector as a datasource in the  dashboard
for creating gadgets?

On Sat, Aug 15, 2015 at 9:47 AM, Inosh Goonewardena  wrote:

> Hi,
>
>>
>>1. Adding new spark dialects related for various dbs (WIP)
>>
>> I have added new spark JDBC dialects for following DBs.
>
>- mysql
>- mssql
>- oracle
>- postgres
>- db2
>
>
> No. Not incremental data processing. My question regarding the deleting
>> entire summery table records and re-insert again. IMO, doing upsert will be
>> more efficient than your above approach. Again, if there is no other
>> option, above re-insert is done as a batch operation or are you insert
>> record one by one?
>>
>
> Yes. We had this implementation in Hive JDBC Handler. It is possible to
> follow the similar  approach here, i.e., if upsert queries are supported by
> the DB(most DBs support merge queries) we can let the user to specify the
> upsert query to be used in the spark script and if the upsert query is not
> provided we can check the records exist in the table by using primary key
> and update or insert the records accordingly. But, IMO, since we support
> update operations in our data layer(when the CarbonAnalytics is used), we
> shouldn't worry that much about supporting it in Carbon Spark JDBC
> connector. On the other hand if that is how Spark supports insert
> into/overwrite by default, we should follow the same approach.
>
> On Thu, Aug 13, 2015 at 8:18 AM, Gihan Anuruddha  wrote:
>
>> Hi Niranda,
>>
>> No. Not incremental data processing. My question regarding the deleting
>> entire summery table records and re-insert again. IMO, doing upsert will be
>> more efficient than your above approach. Again, if there is no other
>> option, above re-insert is done as a batch operation or are you insert
>> record one by one?
>>
>> Regards,
>> Gihan
>>
>> On Wed, Aug 12, 2015 at 11:40 AM, Niranda Perera 
>> wrote:
>>
>>> Hi Gihan,
>>>
>>> are we talking about incremental processing here? insert into/overwrite
>>> queries will normally be used to push analyzed data into summary tables.
>>>
>>> in the spark jargon, insert overwrite table means, completely deleting
>>> the table and recreating it. I'm a confused with the meaning of 'overwrite'
>>> with respect to the previous 2.5.0 Hive scripts, are doing an update there?
>>>
>>> rgds
>>>
>>> On Tue, Aug 11, 2015 at 7:58 PM, Gihan Anuruddha  wrote:
>>>
 Hi Niranda,

 Are we going to solve those limitations before the GA? Specially
 limitation no.2. Over time we can have stat table with thousands of
 records, so are we going to remove all the records and reinsert every time
 that spark script runs?

 Regards,
 Gihan

 On Tue, Aug 11, 2015 at 7:13 AM, Niranda Perera 
 wrote:

> Hi all,
>
> we have implemented a custom Spark JDBC connector to be used in the
> Carbon environment.
>
> this enables the following
>
>1. Now, temporary tables can be created in the Spark environment
>by specifying an analytics datasource (configured by the
>analytics-datasources.xml) and a table
>2. Spark uses "SELECT 1 FROM $table LIMIT 1" query to check the
>existence of a table and the LIMIT query is not provided by all dbs. 
> With
>the new connector, this query can be provided with as a config. (this
>config is still WIP)
>3. Adding new spark dialects related for various dbs (WIP)
>
> the idea is to test this for the following dbs
>
>- mysql
>- h2
>- mssql
>- oracle
>- postgres
>- db2
>
> I have loosely tested the connector with MySQL, and I would like the
> APIM team to use it with the API usage stats use-case, and provide us some
> feedback.
>
> this connector can be accessed as follows. (docs are still not
> updated. I will do that ASAP)
>
> create temporary table  using CarbonJDBC options
> (dataSource "", tableName "");
>
> select * from 
>
> insert into/overwrite table  
>
> known limitations
>
>1.  when creating a temp table, it should already be created in
>the underlying datasource
>2. "insert overwrite table" deletes the existing table and creates
>it again
>
>
> would be very grateful if you could use this connector in your current
> JDBC use cases and provide us with feedback.
>
> best
> --
> *Niranda Perera*
> Software Engineer, WSO2 Inc.
> Mobile: +94-71-554-8430
> Twitter: @n1r44 
> https://pythagoreanscript.wordpress.com/
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


 --
 W.G. Gihan Anuruddha
 Senior Software Engineer | WSO2, Inc.
 M: +94

Re: [Dev] Build failed in Jenkins: product-private-paas #247

[Imesh Gunaratne]

Hi Maheshika,

I investigated the above issue and found that Private PaaS now needs JDK
1.7 to be compiled. Can you please update Jenkins accordingly?

Thanks

On Wed, Aug 12, 2015 at 10:57 PM, Imesh Gunaratne  wrote:

> No it does not need JDK 1.7. Will check this and get back to you.
> Temporarily I have removed the above component from the build.
>
> Thanks
>
> On Wed, Aug 12, 2015 at 10:46 PM, Maheshika Goonetilleke <
> mahesh...@wso2.com> wrote:
>
>> Hi Lasindu
>>
>> product-private-pass build is configured to jdk1.6. Do you require moving
>> it to 1.7?
>>
>> On Wed, Aug 12, 2015 at 10:33 PM, Lasindu Charith 
>> wrote:
>>
>>> Hi All,
>>>
>>> I was able to build the repo with jdk 7. What is the builder JDK version?
>>> @Imesh : Fior the carbon extension, do we need JDK 7?
>>>
>>> On Wed, Aug 12, 2015 at 10:16 PM,  wrote:
>>>
 See 

 Changes:

 [Imesh Gunaratne] Adding the packaging model to generate a zip for
 private paas membership scheme

 [lasinducharith] Setting CARBON_HOME as APPLICATION_PATH in
 start-agent.sh

 --
 [...truncated 988 lines...]
 [INFO]
 [INFO] --- maven-surefire-plugin:2.18:test (default-test) @ wso2ppaas
 ---
 [JENKINS] Recording test results
 [INFO]
 [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ wso2ppaas ---
 [INFO] Building jar: <
 https://wso2.org/jenkins/job/product-private-paas/ws/products/ppaas/modules/distribution/target/wso2ppaas-4.1.0-SNAPSHOT.jar
 >
 [INFO]
 [INFO] --- maven-dependency-plugin:2.10:unpack (2-unpack-wso2carbon) @
 wso2ppaas ---
 [INFO] Configured Artifact: org.wso2.carbon:wso2carbon-core:4.2.0:zip
 [INFO] Unpacking <
 https://wso2.org/jenkins/job/product-private-paas/ws/.repository/org/wso2/carbon/wso2carbon-core/4.2.0/wso2carbon-core-4.2.0.zip>
 to <
 https://wso2.org/jenkins/job/product-private-paas/ws/products/ppaas/modules/distribution/target>
 with includes "" and excludes ""
 [INFO]
 [INFO] --- maven-antrun-plugin:1.7:run (1-run-ant) @ wso2ppaas ---
 [WARNING] Parameter tasks is deprecated, use target instead
 [INFO] Executing tasks

 main:
  [copy] Copying 16 files to <
 https://wso2.org/jenkins/job/product-private-paas/ws/products/ppaas/modules/distribution/target/wso2carbon-core-4.2.0/dbscripts/identity
 >
  [echo] ### Adding identity , identity/application-mgt
 tables to WSO2Carbon DB ##
   [sql] Executing resource: <
 https://wso2.org/jenkins/job/product-private-paas/ws/products/ppaas/modules/distribution/target/wso2carbon-core-4.2.0/dbscripts/identity/application-mgt/h2.sql
 >
   [sql] 29 of 29 SQL statements executed successfully
   [sql] Executing resource: <
 https://wso2.org/jenkins/job/product-private-paas/ws/products/ppaas/modules/distribution/target/wso2carbon-core-4.2.0/dbscripts/identity/h2.sql
 >
   [sql] 20 of 20 SQL statements executed successfully
 [INFO] Executed tasks
 [INFO]
 [INFO] --- maven-assembly-plugin:2.4:attached (4-dist) @ wso2ppaas ---
 [INFO] Reading assembly descriptor: <
 https://wso2.org/jenkins/job/product-private-paas/ws/products/ppaas/modules/distribution/src/assembly/bin.xml
 >
 [INFO] Building zip: <
 https://wso2.org/jenkins/job/product-private-paas/ws/products/ppaas/modules/distribution/target/wso2ppaas-4.1.0-SNAPSHOT.zip
 >
 [INFO]
 [INFO] --- maven-install-plugin:2.5.2:install (default-install) @
 wso2ppaas ---
 [INFO] Installing <
 https://wso2.org/jenkins/job/product-private-paas/ws/products/ppaas/modules/distribution/target/wso2ppaas-4.1.0-SNAPSHOT.jar>
 to <
 https://wso2.org/jenkins/job/product-private-paas/ws/.repository/org/wso2/ppaas/wso2ppaas/4.1.0-SNAPSHOT/wso2ppaas-4.1.0-SNAPSHOT.jar
 >
 [INFO] Installing <
 https://wso2.org/jenkins/job/product-private-paas/ws/products/ppaas/modules/distribution/pom.xml>
 to <
 https://wso2.org/jenkins/job/product-private-paas/ws/.repository/org/wso2/ppaas/wso2ppaas/4.1.0-SNAPSHOT/wso2ppaas-4.1.0-SNAPSHOT.pom
 >
 [INFO] Installing <
 https://wso2.org/jenkins/job/product-private-paas/ws/products/ppaas/modules/distribution/target/wso2ppaas-4.1.0-SNAPSHOT.zip>
 to <
 https://wso2.org/jenkins/job/product-private-paas/ws/.repository/org/wso2/ppaas/wso2ppaas/4.1.0-SNAPSHOT/wso2ppaas-4.1.0-SNAPSHOT.zip
 >
 [INFO]
 [INFO] --- maven-antrun-plugin:1.7:run (clean_target) @ wso2ppaas ---
 [WARNING] Parameter tasks is deprecated, use target instead
 [INFO] Executing tasks

 main:
[delete] Deleting directory <
 https://wso2.org/jenkins/job/product-private-paas/ws/products/ppaas/modules/distribution/target/archive-tmp
 >
[delete] Deleting directory <
 https://wso2.org/jenkin

Re: [Dev] [DEV][EMM] Android enrollment production readiness

[Milan Perera]

Hi Dulitha,

+1 for building from Gradle.

On Mon, Aug 17, 2015 at 11:20 AM, Dulitha Wijewantha 
wrote:

> Hi Inosh,
> +1 for the property file. We also can trigger the build from Gradle for
> environments right? [1]. We can pass in an environment parameter to build
> an artifact.
>
> [1] -
> http://tobiasbayer.com/blog/2011/04/16/building-for-different-environments-with-gradle/
> Cheers~
>
> On Mon, Aug 17, 2015 at 3:08 PM, Dilshan Edirisuriya 
> wrote:
>
>> Hi,
>>
>> Better make the IP configurable so that it can be hidden anytime
>> specially when it comes to a production environment. When it comes to
>> domain also same thing is applicable since for most of the deployment it
>> will only need just one tenant.
>>
>> Regards,
>>
>> Dilshan
>>
>> On Mon, Aug 17, 2015 at 10:07 AM, Inosh Perera  wrote:
>>
>>> Hi Milan/Kasun,
>>>
>>> During the EMM registration[1], Step 3 and 4 where the user has to enter
>>> the IP/domain;
>>>  should be designed in a way where in a production scenario, this step
>>> can be bypassed. In other words, the IP can be hard coded and the step can
>>> be hidden from the user, since in production the user is not expected to
>>> know about the backend IPs/Domains. Same can be applicable to step
>>> 5 Ownership type selection. Once option would be to maintain these in a
>>> configuration file.
>>>
>>> [1].
>>> https://docs.wso2.com/display/EMM200/End-user+Registering+an+Android+Device
>>>
>>> Regards,
>>> Inosh
>>>
>>> --
>>> Inosh Perera
>>> Software Engineer, WSO2 Inc.
>>> Tel: 0785293686
>>>
>>
>>
>>
>> --
>> Dilshan Edirisuriya
>> Senior Software Engineer - WSO2
>> Mob: + 94 777878905
>> http://wso2.com/
>> https://www.linkedin.com/profile/view?id=50486426
>>
>
>
>
> --
> Dulitha Wijewantha (Chan)
> Software Engineer - Mobile Development
> WSO2 Inc
> Lean.Enterprise.Middleware
>  * ~Email   duli...@wso2.com *
> *  ~Mobile +94712112165 <%2B94712112165>*
> *  ~Website   dulitha.me *
> *  ~Twitter @dulitharw *
>   *~Github @dulichan *
>   *~SO @chan *
>



-- 
Milan Harindu Perera
Software Engineer
*WSO2, Inc*
(+94) 77 309 7088
lean . enterprise . middleware

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