Re: [Dev] Datamapper - OutNode icon need to be filled inside with white color

[Susinda Perera]

Hi Sharon

Thanks alot for the quick response.
FYI - I have created a RM (https://redmine.wso2.com/issues/5075)for this
for tracking purpose.

Thanks
Susinda

On Fri, Apr 8, 2016 at 11:13 AM, Sharon David  wrote:

> HI Susinda,
>
> Please find attached Icon with the requested modifications
>
> On Thu, Apr 7, 2016 at 3:25 PM, Susinda Perera  wrote:
>
>> Hi Sharon
>>
>> Can we have the white filled one with black border arround it.
>>
>> Thanks
>> Susinda
>>
>> On Thu, Apr 7, 2016 at 2:39 PM, Sharon David  wrote:
>>
>>> Hi Susinda,
>>>
>>> Please find attached Icons as requested
>>>
>>> On Thu, Apr 7, 2016 at 2:18 PM, Susinda Perera  wrote:
>>>
 Hi Sharon

 $subject to solve the https://wso2.org/jira/browse/DEVTOOLESB-149.
 Could you help on this.

 Thanks
 Susinda


 --
 *Susinda Perera*
 Software Engineer
 B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
 Mobile:(+94)716049075
 Blog: susinda.blogspot.com
 WSO2 Inc. http://wso2.com/
 Tel : 94 11 214 5345 Fax :94 11 2145300


>>>
>>>
>>> --
>>> Sharon David
>>> Software Engineer - UI/UX  |   WSO2 Inc
>>>
>>> +94 777 668 411  |  shar...@wso2.com  |   http://wso2.com
>>>
>>
>>
>>
>> --
>> *Susinda Perera*
>> Software Engineer
>> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
>> Mobile:(+94)716049075
>> Blog: susinda.blogspot.com
>> WSO2 Inc. http://wso2.com/
>> Tel : 94 11 214 5345 Fax :94 11 2145300
>>
>>
>
>
> --
> Sharon David
> Software Engineer - UI/UX  |   WSO2 Inc
>
> +94 777 668 411  |  shar...@wso2.com  |   http://wso2.com
>



-- 
*Susinda Perera*
Software Engineer
B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
Mobile:(+94)716049075
Blog: susinda.blogspot.com
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Datamapper - OutNode icon need to be filled inside with white color

[Sharon David]

HI Susinda,

Please find attached Icon with the requested modifications

On Thu, Apr 7, 2016 at 3:25 PM, Susinda Perera  wrote:

> Hi Sharon
>
> Can we have the white filled one with black border arround it.
>
> Thanks
> Susinda
>
> On Thu, Apr 7, 2016 at 2:39 PM, Sharon David  wrote:
>
>> Hi Susinda,
>>
>> Please find attached Icons as requested
>>
>> On Thu, Apr 7, 2016 at 2:18 PM, Susinda Perera  wrote:
>>
>>> Hi Sharon
>>>
>>> $subject to solve the https://wso2.org/jira/browse/DEVTOOLESB-149.
>>> Could you help on this.
>>>
>>> Thanks
>>> Susinda
>>>
>>>
>>> --
>>> *Susinda Perera*
>>> Software Engineer
>>> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
>>> Mobile:(+94)716049075
>>> Blog: susinda.blogspot.com
>>> WSO2 Inc. http://wso2.com/
>>> Tel : 94 11 214 5345 Fax :94 11 2145300
>>>
>>>
>>
>>
>> --
>> Sharon David
>> Software Engineer - UI/UX  |   WSO2 Inc
>>
>> +94 777 668 411  |  shar...@wso2.com  |   http://wso2.com
>>
>
>
>
> --
> *Susinda Perera*
> Software Engineer
> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
> Mobile:(+94)716049075
> Blog: susinda.blogspot.com
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>


-- 
Sharon David
Software Engineer - UI/UX  |   WSO2 Inc

+94 777 668 411  |  shar...@wso2.com  |   http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] [Passive STS] Error while Invoking Passive STS in Identity Server

[Malithi Edirisinghe]

Hi Chamila,

In the orbit bundle I think we have missed to include the 'schemas'
directory of 'opensaml1-1.1' artifact.

If you see the pom.xml of the orbit you will see that we have included the
resources of opensaml1 as below.

*@opensaml1-${opensaml1.version}.jar!/schema/**.xsd*

It should be
*@opensaml1-${opensaml1.version}.jar!/schemas/**.xsd *instead.

So as it seems we need to release the orbit again fixing all these issues.

Thanks,
Malithi

On Fri, Apr 8, 2016 at 2:37 AM, Chamila Wijayarathna 
wrote:

> Hi all,
>
> Currently passive STS in Identity Server is not workong, but after
> applying following changes in orbit and identity-inbound-auth-sts I could
> successfully run passive sts scenarios using PassiveSTSSampleApp.
>
> *Orbit*
>
> *diff --git a/opensaml/2.6.4.wso2v1/pom.xml
> b/opensaml/2.6.4.wso2v1/pom.xml*
> *index 06b4d26..e10c16f 100644*
> *--- a/opensaml/2.6.4.wso2v1/pom.xml*
> *+++ b/opensaml/2.6.4.wso2v1/pom.xml*
> *@@ -259,6 +259,7 @@*
> *
>  
> net.jcip.annotations.*;version="${net.jcip.annotations.version}";resolution:=optional,*
> *
>  
> org.apache.commons.httpclient.*;version="${org.apache.commons.httpclient.version}";resolution:=optional,*
> *
>  
> org.apache.commons.ssl.*;version="${org.apache.commons.ssl.version}";resolution:=optional,*
> *+
>  org.apache.commons.codec.binary;version="[1.4,2)",*
> * org.apache.velocity.*;resolution:=optional,*
> *
>  
> org.apache.xml.security.*;version="${org.apache.xml.security.version}";resolution:=optional,*
> *
>  
> org.bouncycastle.*;version="${org.bouncycastle.version}";resolution:=optional,*
> *@@ -279,6 +280,7 @@*
> *
>  org.apache.commons.fileupload.*;resolution:=optional,*
> * org.apache.log4j.*;resolution:=optional,*
> *
>  org.owasp.validator.html;resolution:=optional,*
> *+
>  org.apache.axiom.om.impl.dom.jaxp;version="${axiom.osgi.version.range}"*
> * *
> *
>  
> esapi;scope=compile|runtime;inline=false*
> * *
> *@@ -321,6 +323,7 @@*
> * [1.6.0,1.8.0)*
> * 0.0.0*
> * 0.0.0*
> *+[1.2.11,
> 2.0.0)*
> * *
>
> * *
>
>
> *identity-inbound-auth-sts*
>
> *diff --git a/components/org.wso2.carbon.identity.sts.passive/pom.xml
> b/components/org.wso2.carbon.identity.sts.passive/pom.xml*
> *index f391798..2d927ae 100644*
> *--- a/components/org.wso2.carbon.identity.sts.passive/pom.xml*
> *+++ b/components/org.wso2.carbon.identity.sts.passive/pom.xml*
> *@@ -97,7 +97,8 @@*
> * javax.xml.stream;
> version="${equinox.osgi.stax-api.imp.pkg.version.range}",*
> * javax.servlet.http;
> version="${imp.pkg.version.javax.servlet}",*
>
> *-org.apache.axiom.*;
> version="${axiom.osgi.version.range}",*
> *+org.apache.axiom.om
> ; version="${axiom.osgi.version.range}",*
> *+org.apache.axiom.soap;
> version="${axiom.osgi.version.range}",*
> * org.apache.axis2.*;
> version="${axis2.osgi.version.range}",*
> * org.apache.rahas.*;
> version="${rampart.wso2.osgi.version.range}",*
> * org.apache.ws.secpolicy;
> version="${rampart.wso2.osgi.version.range}",*
> *@@ -128,11 +129,13 @@*
> *
>  version="${carbon.identity.package.import.version.range}",*
> * org.wso2.carbon.identity.core.*;*
> *
>  version="${carbon.identity.package.import.version.range}",*
> *+
>  org.opensaml;version="${opensaml2.wso2.osgi.version.range}"*
> * *
> * *
> *
>  !org.wso2.carbon.identity.sts.passive.internal,*
> * org.wso2.carbon.identity.sts.passive.*;
> version="${carbon.identity.package.export.version}",*
> * *
> *+**
> * *
> * *
> * *
>
> But now I am observing following error at back end.
>
> *[2016-04-08 02:05:08,960] ERROR {org.opensaml.XML} -  Unable to parse
> SAML 1.0 Schemas: org.xml.sax.SAXParseException; schema_reference.4: Failed
> to read schema document 'xml.xsd', because 1) could not find the document;
> 2) the document could not be read; 3) the root element of the document is
> not .*
> *[2016-04-08 02:05:08,962] ERROR {org.opensaml.XML} -  Unable to parse
> SAML 1.1 Schemas: org.xml.sax.SAXParseException; schema_reference.4: Failed
> to read schema document 'xml.xsd', because 1) could not find the document;
> 2) the document could not be read; 3) the root element of the document is
> not .*
>
> Any idea about what is the reason for this?
>
> Thanks!
> --
> *Chamila Dilshan Wijayarathna,*
> Software Engineer
> Mobile:(+94)788193620
> WSO2 Inc., http://wso2.com/
>



-- 

*Malithi Edirisinghe*
Senior Software Engineer
WSO2 Inc.

Mobile : +94 (0) 718176807

Re: [Dev] WSO2 Process Center

[Chathura Ekanayake]

Hi Lakshitha,

Currently, BPEL processes are not supported by process center. Only BPMN
models (i.e .bpmn files) can be associated with processes in PC.

Regards,
Chathura

On Wed, Apr 6, 2016 at 10:14 AM, Lakshitha Warnakulasuriya <
lakshitha...@gmail.com> wrote:

> Hi All,
>
> Is there any way to add BPEL process to Process Center. Can we upload BPEL
> process using add processess inside add category in Management Console. Any
> help can be really appreciated.
>
> Thanx and Regards,
> Lakshitha.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fwd: [EMM 2.1.0] [Device Analytics] Obtaining 'No-Passcode' & 'No-Encryption' states via Device Info

[Hasunie Adikari]

Hi Dilan,

Passcode state and encryption state can be retrieved from windows device
also.We have already taken those information while applying passcode
related policies to the device.

On Thu, Apr 7, 2016 at 6:31 PM, Kasun Dananjaya Delgolla 
wrote:

> Hi Dilan,
>
> It's possible on android. We can simply check it via device policy manager
> and attach it to device info payload. Also it should be possible on iOS.
> But we will have to check on Windows. @Hasunie - Any input on this?
>
> Thanks
> On Apr 7, 2016 6:27 PM, "Dilan Udara Ariyaratne"  wrote:
>
>> Adding KasunD, Milan, InoshP, Dilshan and Hasunie to the thread...
>>
>> *Dilan U. Ariyaratne*
>> Software Engineer
>> WSO2 Inc. 
>> Mobile: +94766405580 <%2B94766405580>
>> lean . enterprise . middleware
>>
>>
>> -- Forwarded message --
>> From: Dilan Udara Ariyaratne 
>> Date: Thu, Apr 7, 2016 at 6:23 PM
>> Subject: [Dev] [EMM 2.1.0] [Device Analytics] Obtaining 'No-Passcode' &
>> 'No-Encryption' states via Device Info
>> To: WSO2 Developers' List 
>>
>>
>> Hi Folks,
>>
>> Is there currently any possibility of retrieving the following states
>> via device-info capturing task of EMM for all mobile platforms, i.e.
>> Android, iOS and Windows ?
>>
>> [1] No-Passcode state - This could carry the value of either true or
>> false and express whether the device is currently having a passcode or not
>> [2] No-Encryption state - This could also carry the value of either true
>> or false and express whether the device data is currently encrypted or not
>>
>> If we can obtain these data, there lies the possibility of showing
>> related analytics (See Following Figure) on Device Dashboard page for EMM
>> administrators
>> which is currently considered as a useful requirement.
>>
>>
>>
>>
>> Thanks.
>>
>> *Dilan U. Ariyaratne*
>> Software Engineer
>> WSO2 Inc. 
>> Mobile: +94766405580 <%2B94766405580>
>> lean . enterprise . middleware
>>
>>
>>


-- 
*Hasunie Adikari*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
blog http://hasuniea.blogspot.com
Mobile:+94715139495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [C5] Must Inject CarbonServerInfo when writing OSGi Test Cases

[Aruna Karunarathna]

On Fri, Apr 8, 2016 at 7:07 AM, Sameera Jayasoma  wrote:

>
>
> On Fri, Apr 8, 2016 at 12:13 AM, Imesh Gunaratne  wrote:
>
>> Hi Aruna,
>>
>> On Thu, Apr 7, 2016 at 6:21 PM, Aruna Karunarathna 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> When writing OSGi Test Cases, Please Inject the CarbonServerInfo service
>>> [1]. Otherwise the container wont start properly and the test cases will
>>> fail.
>>>
>>> After injecting the service it will guarantee that the server will fully
>>> start, before running the test cases. e.g. [2]
>>>
>>
>> Would you mind mentioning what CarbonServerInfo does and why containers
>> would not start without it?
>>
>
Hi Imesh,

Sorry If I have confused you, as Sameera mentioned I was talking about the
PAX Exam test cases for OSGi runtimes. :)

@Kishanthan
Sure will do the necessary to get it added to the documentation.

>
> Aruna is talking about Pax Exam test containers (OSGi runtimes) :)
>
>>
>> Thanks
>>
>> --
>> *Imesh Gunaratne*
>> Senior Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.io
>> Lean . Enterprise . Middleware
>>
>>
>
>
> --
> Sameera Jayasoma,
> Software Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://blog.sameera.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
> Lean . Enterprise . Middleware
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

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

Re: [Dev] [DAS] Spark clustering and DAS analytics cluster tuning

[Rukshani Weerasinha]

Hello Niranda,

Now I have added the Spark Performance Tuning section to [1] in DAS 3.0.0,
3.0.1, and DAS 3.1.0.

I will work with Sam to add the clustering related sections to the
Clustering guide.

[1] https://docs.wso2.com/display/DAS300/Performance+Tuning

Best Regards,
Rukshani.

On Thu, Apr 7, 2016 at 7:07 PM, Niranda Perera  wrote:

> Hi Rukshani,
>
> This has still not been done. Is it possible for us get this done soon?
>
> On Fri, Mar 4, 2016 at 11:36 AM, Rukshani Weerasinha 
> wrote:
>
>> Hi Niranda,
>>
>> Not yet. I will add this content soon and let you know once it is done.
>>
>> Best Regards,
>> Rukshani.
>>
>> On Fri, Mar 4, 2016 at 11:33 AM, Niranda Perera  wrote:
>>
>>> Hi Rukshani and Sam,
>>>
>>> were we able to publish these content?
>>>
>>> best
>>>
>>> On Tue, Jan 26, 2016 at 8:20 AM, Rukshani Weerasinha 
>>> wrote:
>>>
 Hello Niranda,

 Thank you for providing this content. We will start working on this.

 Best Regards,
 Rukshani.

 On Tue, Jan 26, 2016 at 3:34 AM, Niranda Perera 
 wrote:

> Hi,
>
> I added 2 blog posts explaining how Spark clustering works [1] and how
> to manage the resources in a DAS analytics cluster [2].
>
> @Rukshani, some of the content should go to this doc [3]. Can we work
> on that?
>
> Best
>
> [1]
> https://pythagoreanscript.wordpress.com/2016/01/23/the-dynamics-of-a-spark-cluster-wrt-wso2-das/
> [2]
> https://pythagoreanscript.wordpress.com/2016/01/25/wso2-das-spark-cluster-tuning/
> [3] https://docs.wso2.com/display/DAS301/Performance+Tuning
>
> --
> *Niranda Perera*
> Software Engineer, WSO2 Inc.
> Mobile: +94-71-554-8430
> Twitter: @n1r44 
> https://pythagoreanscript.wordpress.com/
>



 --
 Rukshani Weerasinha

 WSO2 Inc.
 Web:http://wso2.com
 Mobile: 0777 683 738


>>>
>>>
>>> --
>>> *Niranda Perera*
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94-71-554-8430
>>> Twitter: @n1r44 
>>> https://pythagoreanscript.wordpress.com/
>>>
>>
>>
>>
>> --
>> Rukshani Weerasinha
>>
>> WSO2 Inc.
>> Web:http://wso2.com
>> Mobile: 0777 683 738
>>
>>
>
>
> --
> *Niranda Perera*
> Software Engineer, WSO2 Inc.
> Mobile: +94-71-554-8430
> Twitter: @n1r44 
> https://pythagoreanscript.wordpress.com/
>



-- 
Rukshani Weerasinha

WSO2 Inc.
Web:http://wso2.com
Mobile: 0777 683 738
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] HumanTask Plugin Build failure

[Hasitha Aravinda]

Hi Heshitha,

I am getting following build failure when I try to build
https://github.com/wso2/devstudio-tooling-bps/pull/1. Could you please have
a look ?


[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 2:23.177s
[INFO] Finished at: Thu Apr 07 17:06:47 IST 2016
[INFO] Final Memory: 200M/1051M
[INFO]

[ERROR] Failed to execute goal
org.eclipse.tycho:tycho-compiler-plugin:0.23.0:compile (default-compile) on
project org.wso2.developerstudio.bpel.humantask.model: Compilation failure:
Compilation failure:
[ERROR]
/home/hasi/git/hasithaa/devstudio-tooling-bps/plugins/org.wso2.developerstudio.bpel.humantask.model/src/org/wso2/developerstudio/bpel/humantask/model/impl/PeopleActivityRNImpl.java:[31]
[ERROR] import
org.eclipse.smila.processing.designer.model.processor.util.DOMUtils;
[ERROR] ^
[ERROR] The import org.eclipse.smila cannot be resolved
[ERROR]
/home/hasi/git/hasithaa/devstudio-tooling-bps/plugins/org.wso2.developerstudio.bpel.humantask.model/src/org/wso2/developerstudio/bpel/humantask/model/impl/PeopleActivityRNImpl.java:[230]
[ERROR] DOMUtils.appendIndented(element,
getRemoteNotification().fixElement(document));
[ERROR] 
[ERROR] DOMUtils cannot be resolved
[ERROR]
/home/hasi/git/hasithaa/devstudio-tooling-bps/plugins/org.wso2.developerstudio.bpel.humantask.model/src/org/wso2/developerstudio/bpel/humantask/model/impl/PeopleActivityRTImpl.java:[37]
[ERROR] import
org.eclipse.smila.processing.designer.model.processor.util.DOMUtils;
[ERROR] ^
[ERROR] The import org.eclipse.smila cannot be resolved
[ERROR]
/home/hasi/git/hasithaa/devstudio-tooling-bps/plugins/org.wso2.developerstudio.bpel.humantask.model/src/org/wso2/developerstudio/bpel/humantask/model/impl/PeopleActivityRTImpl.java:[354]
[ERROR] DOMUtils.appendIndented(element,
getRemoteTask().fixElement(document));
[ERROR] 
[ERROR] DOMUtils cannot be resolved
[ERROR]
/home/hasi/git/hasithaa/devstudio-tooling-bps/plugins/org.wso2.developerstudio.bpel.humantask.model/src/org/wso2/developerstudio/bpel/humantask/model/util/HTDeserializer.java:[43]
[ERROR] import
org.eclipse.smila.processing.designer.model.processor.util.DOMUtils;
[ERROR] ^
[ERROR] The import org.eclipse.smila cannot be resolved
[ERROR]
/home/hasi/git/hasithaa/devstudio-tooling-bps/plugins/org.wso2.developerstudio.bpel.humantask.model/src/org/wso2/developerstudio/bpel/humantask/model/util/HTDeserializer.java:[90]
[ERROR] Element rtElement  = DOMUtils.getChildElement(paElement,
ModelPackage.eINSTANCE.getNsURI(), HTConstants.ND_REMOTE_TASK);
[ERROR] 
[ERROR] DOMUtils cannot be resolved
[ERROR]
/home/hasi/git/hasithaa/devstudio-tooling-bps/plugins/org.wso2.developerstudio.bpel.humantask.model/src/org/wso2/developerstudio/bpel/humantask/model/util/HTDeserializer.java:[194]
[ERROR] Element rnElement  = DOMUtils.getChildElement(paElement,
ModelPackage.eINSTANCE.getNsURI(), HTConstants.ND_REMOTE_NOTIFICATION);
[ERROR] 
[ERROR] DOMUtils cannot be resolved
[ERROR] 7 problems (7 errors)
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :org.wso2.developerstudio.bpel.humantask.model


Thanks,
Hasitha.

-- 
--
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] [APPM] Mobile application binary file upload REST API

[Ruwan Abeykoon]

Hi All,
Off topic: Just another idea on file upload in UI side, can we do something
like [1] with this API?

[1] http://www.sitepoint.com/html5-javascript-file-upload-progress-bar/

Cheers,

On Fri, Apr 8, 2016 at 9:38 AM, Ruwan Abeykoon  wrote:

> Hi All,
> How about
> URL :  http://localhost:9763/api/appm/publisher/v1.0/apps
> */static-contents*
>
> Which says it is not just Images. We can upload PDF, Movie etc.
> I think GET has no meaning. This API should return a URI (without
> host:port/context) once the file is uploaded.
>
>
> Cheers,
> Ruwan
>
> On Fri, Apr 8, 2016 at 9:25 AM, Thilini Shanika  wrote:
>
>> If we are introducing a dedicated API for images, I would like to suggest
>> below API design for that.
>>
>> URL :  http://localhost:9763/api/appm/publisher/v1.0/apps*/images*
>> HTTP Methods : POST, GET
>> Content-Type : multipart/form-data
>>
>>
>> On Fri, Apr 8, 2016 at 7:42 AM, Rushmin Fernando 
>> wrote:
>>
>>> I agree with RuwanA. When Thilini says, "the flows of the different
>>> upload types are different", it means that the only common aspect between
>>> these upload types is, that they use the file system for storage.
>>>
>>> So -1 for the option 1. But we, of course should re-use the file upload
>>> code in different upload types :-)
>>>
>>> Thanks
>>> Rushmin
>>>
>>> On Fri, Apr 8, 2016 at 7:16 AM, Ruwan Abeykoon  wrote:
>>>
 Hi Dinusha,
 I think option (1) poses few complications in both REST API user
 perspective and the implementation perspective.
 1. Application binaries need to be placed in secured location and allow
 GET access based on various security policies(This is not available yet,
 but is a necessary feature in future.). few examples are,
 1.a) Reviewer need to have access, but any other person should not
 until published, even he has the URL,
 1.b) Implementing One time/ time based download link
 Images, PDF, etc, does not have this restriction, they can be
 accessible by public with known URL

 2. Application binary need to be analyzed for number of details
 including package name, version, any meta information, malware code, etc.
 However for images we need only to verify if the file type and size fits,
 if ever. Also the result of the REST call is different fro App binary to
 any other static content.

 Hence I think option (2) is intuitive and clear.

 Cheers,
 Ruwan

 On Thu, Apr 7, 2016 at 9:55 PM, Dinusha Senanayaka 
 wrote:

>
>
> On Thu, Apr 7, 2016 at 11:44 AM, Thilini Shanika 
> wrote:
>
>> Hi all,
>>
>> We have a concern regarding the design of mobile application
>> binary/image upload API. As per the discussions we had on the new design 
>> of
>> the API model, we decided to use a separate API to upload mobile binary
>> files(.apk, .ipa) including the images. Thus, in order to create a mobile
>> app,  we have to initially upload relevant application binary and image
>> files of app thumbnail, banner and screenshots and later the application
>> should be created with the references to uploaded binaries.
>> We have already implemented the REST API for application binary
>> upload. But we have few concerns regarding the image file upload. We have
>> two options in implementing image upload scenario.
>>
>>
>>1. Reusing the binary upload API for image upload also. But in
>>this case, we need to change the API design in order to distinguish 
>> the
>>uploading file type (Whether is it is an app binary or an image for
>>screenshots, thumbnails etc) since we have separate flows of 
>> processing the
>>files.
>>2. Implementing a dedicated API for image upload only. In this
>>case, we can implement this API in order to be reused in webapp image
>>upload also.
>>
>>  I'm +1 for option 1. Keep the API as
> http://localhost:9763/api/appm/publisher/v1.0/apps/binaries and
> handle all binary uploads(apks, images, documents) for web/mobile from 
> this
> API, instead introducing API per each binary type.
>
> Regards,
> Dinusha.
>
>>
>> As per the offline discussion I had with RuwanA, another concern was
>> raised regarding the URL for binary upload API. The current URL is '
>> http://localhost:9763/api/appm/publisher/v1.0/apps/mobile/
>> binaries'. But
>> this particular URL is mobile application specific. In that case, we 
>> cannot
>> reuse this API in future, for any other application binary upload, other
>> that mobile binary upload. Our suggestion here is to rename the API as
>> http://localhost:9763/api/appm/publisher/v1.0/apps/application/
>> 

Re: [Dev] [APPM] Mobile application binary file upload REST API

[Thilini Shanika]

URL :  http://localhost:9763/api/appm/publisher/v1.0/apps*/static-contents*
*+1. *In that case, we can reuse this in Document upload etc also.

On Fri, Apr 8, 2016 at 9:38 AM, Ruwan Abeykoon  wrote:

> Hi All,
> How about
> URL :  http://localhost:9763/api/appm/publisher/v1.0/apps
> */static-contents*
>
> Which says it is not just Images. We can upload PDF, Movie etc.
> I think GET has no meaning. This API should return a URI (without
> host:port/context) once the file is uploaded.
>
>
> Cheers,
> Ruwan
>
> On Fri, Apr 8, 2016 at 9:25 AM, Thilini Shanika  wrote:
>
>> If we are introducing a dedicated API for images, I would like to suggest
>> below API design for that.
>>
>> URL :  http://localhost:9763/api/appm/publisher/v1.0/apps*/images*
>> HTTP Methods : POST, GET
>> Content-Type : multipart/form-data
>>
>>
>> On Fri, Apr 8, 2016 at 7:42 AM, Rushmin Fernando 
>> wrote:
>>
>>> I agree with RuwanA. When Thilini says, "the flows of the different
>>> upload types are different", it means that the only common aspect between
>>> these upload types is, that they use the file system for storage.
>>>
>>> So -1 for the option 1. But we, of course should re-use the file upload
>>> code in different upload types :-)
>>>
>>> Thanks
>>> Rushmin
>>>
>>> On Fri, Apr 8, 2016 at 7:16 AM, Ruwan Abeykoon  wrote:
>>>
 Hi Dinusha,
 I think option (1) poses few complications in both REST API user
 perspective and the implementation perspective.
 1. Application binaries need to be placed in secured location and allow
 GET access based on various security policies(This is not available yet,
 but is a necessary feature in future.). few examples are,
 1.a) Reviewer need to have access, but any other person should not
 until published, even he has the URL,
 1.b) Implementing One time/ time based download link
 Images, PDF, etc, does not have this restriction, they can be
 accessible by public with known URL

 2. Application binary need to be analyzed for number of details
 including package name, version, any meta information, malware code, etc.
 However for images we need only to verify if the file type and size fits,
 if ever. Also the result of the REST call is different fro App binary to
 any other static content.

 Hence I think option (2) is intuitive and clear.

 Cheers,
 Ruwan

 On Thu, Apr 7, 2016 at 9:55 PM, Dinusha Senanayaka 
 wrote:

>
>
> On Thu, Apr 7, 2016 at 11:44 AM, Thilini Shanika 
> wrote:
>
>> Hi all,
>>
>> We have a concern regarding the design of mobile application
>> binary/image upload API. As per the discussions we had on the new design 
>> of
>> the API model, we decided to use a separate API to upload mobile binary
>> files(.apk, .ipa) including the images. Thus, in order to create a mobile
>> app,  we have to initially upload relevant application binary and image
>> files of app thumbnail, banner and screenshots and later the application
>> should be created with the references to uploaded binaries.
>> We have already implemented the REST API for application binary
>> upload. But we have few concerns regarding the image file upload. We have
>> two options in implementing image upload scenario.
>>
>>
>>1. Reusing the binary upload API for image upload also. But in
>>this case, we need to change the API design in order to distinguish 
>> the
>>uploading file type (Whether is it is an app binary or an image for
>>screenshots, thumbnails etc) since we have separate flows of 
>> processing the
>>files.
>>2. Implementing a dedicated API for image upload only. In this
>>case, we can implement this API in order to be reused in webapp image
>>upload also.
>>
>>  I'm +1 for option 1. Keep the API as
> http://localhost:9763/api/appm/publisher/v1.0/apps/binaries and
> handle all binary uploads(apks, images, documents) for web/mobile from 
> this
> API, instead introducing API per each binary type.
>
> Regards,
> Dinusha.
>
>>
>> As per the offline discussion I had with RuwanA, another concern was
>> raised regarding the URL for binary upload API. The current URL is '
>> http://localhost:9763/api/appm/publisher/v1.0/apps/mobile/
>> binaries'. But
>> this particular URL is mobile application specific. In that case, we 
>> cannot
>> reuse this API in future, for any other application binary upload, other
>> that mobile binary upload. Our suggestion here is to rename the API as
>> http://localhost:9763/api/appm/publisher/v1.0/apps/application/
>> binaries and
>> 

Re: [Dev] [APPM] Mobile application binary file upload REST API

[Ruwan Abeykoon]

Hi All,
How about
URL :  http://localhost:9763/api/appm/publisher/v1.0/apps*/static-contents*

Which says it is not just Images. We can upload PDF, Movie etc.
I think GET has no meaning. This API should return a URI (without
host:port/context) once the file is uploaded.


Cheers,
Ruwan

On Fri, Apr 8, 2016 at 9:25 AM, Thilini Shanika  wrote:

> If we are introducing a dedicated API for images, I would like to suggest
> below API design for that.
>
> URL :  http://localhost:9763/api/appm/publisher/v1.0/apps*/images*
> HTTP Methods : POST, GET
> Content-Type : multipart/form-data
>
>
> On Fri, Apr 8, 2016 at 7:42 AM, Rushmin Fernando  wrote:
>
>> I agree with RuwanA. When Thilini says, "the flows of the different
>> upload types are different", it means that the only common aspect between
>> these upload types is, that they use the file system for storage.
>>
>> So -1 for the option 1. But we, of course should re-use the file upload
>> code in different upload types :-)
>>
>> Thanks
>> Rushmin
>>
>> On Fri, Apr 8, 2016 at 7:16 AM, Ruwan Abeykoon  wrote:
>>
>>> Hi Dinusha,
>>> I think option (1) poses few complications in both REST API user
>>> perspective and the implementation perspective.
>>> 1. Application binaries need to be placed in secured location and allow
>>> GET access based on various security policies(This is not available yet,
>>> but is a necessary feature in future.). few examples are,
>>> 1.a) Reviewer need to have access, but any other person should not until
>>> published, even he has the URL,
>>> 1.b) Implementing One time/ time based download link
>>> Images, PDF, etc, does not have this restriction, they can be accessible
>>> by public with known URL
>>>
>>> 2. Application binary need to be analyzed for number of details
>>> including package name, version, any meta information, malware code, etc.
>>> However for images we need only to verify if the file type and size fits,
>>> if ever. Also the result of the REST call is different fro App binary to
>>> any other static content.
>>>
>>> Hence I think option (2) is intuitive and clear.
>>>
>>> Cheers,
>>> Ruwan
>>>
>>> On Thu, Apr 7, 2016 at 9:55 PM, Dinusha Senanayaka 
>>> wrote:
>>>


 On Thu, Apr 7, 2016 at 11:44 AM, Thilini Shanika 
 wrote:

> Hi all,
>
> We have a concern regarding the design of mobile application
> binary/image upload API. As per the discussions we had on the new design 
> of
> the API model, we decided to use a separate API to upload mobile binary
> files(.apk, .ipa) including the images. Thus, in order to create a mobile
> app,  we have to initially upload relevant application binary and image
> files of app thumbnail, banner and screenshots and later the application
> should be created with the references to uploaded binaries.
> We have already implemented the REST API for application binary
> upload. But we have few concerns regarding the image file upload. We have
> two options in implementing image upload scenario.
>
>
>1. Reusing the binary upload API for image upload also. But in
>this case, we need to change the API design in order to distinguish the
>uploading file type (Whether is it is an app binary or an image for
>screenshots, thumbnails etc) since we have separate flows of 
> processing the
>files.
>2. Implementing a dedicated API for image upload only. In this
>case, we can implement this API in order to be reused in webapp image
>upload also.
>
>  I'm +1 for option 1. Keep the API as
 http://localhost:9763/api/appm/publisher/v1.0/apps/binaries and handle
 all binary uploads(apks, images, documents) for web/mobile from this API,
 instead introducing API per each binary type.

 Regards,
 Dinusha.

>
> As per the offline discussion I had with RuwanA, another concern was
> raised regarding the URL for binary upload API. The current URL is '
> http://localhost:9763/api/appm/publisher/v1.0/apps/mobile/
> binaries'. But
> this particular URL is mobile application specific. In that case, we 
> cannot
> reuse this API in future, for any other application binary upload, other
> that mobile binary upload. Our suggestion here is to rename the API as
> http://localhost:9763/api/appm/publisher/v1.0/apps/application/
> binaries and
> making the API more generic.
>
> Your suggestions are highly appreciated.
>
> [1] -
> https://docs.google.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit
>
>
> Thanks,
> Thilini
>
> --
> Thilini Shanika
> Software Engineer
> WSO2, Inc.; http://wso2.com
> 20, Palmgrove Avenue, Colombo 

Re: [Dev] [APPM] Mobile application binary file upload REST API

[Thilini Shanika]

If we are introducing a dedicated API for images, I would like to suggest
below API design for that.

URL :  http://localhost:9763/api/appm/publisher/v1.0/apps*/images*
HTTP Methods : POST, GET
Content-Type : multipart/form-data


On Fri, Apr 8, 2016 at 7:42 AM, Rushmin Fernando  wrote:

> I agree with RuwanA. When Thilini says, "the flows of the different upload
> types are different", it means that the only common aspect between these
> upload types is, that they use the file system for storage.
>
> So -1 for the option 1. But we, of course should re-use the file upload
> code in different upload types :-)
>
> Thanks
> Rushmin
>
> On Fri, Apr 8, 2016 at 7:16 AM, Ruwan Abeykoon  wrote:
>
>> Hi Dinusha,
>> I think option (1) poses few complications in both REST API user
>> perspective and the implementation perspective.
>> 1. Application binaries need to be placed in secured location and allow
>> GET access based on various security policies(This is not available yet,
>> but is a necessary feature in future.). few examples are,
>> 1.a) Reviewer need to have access, but any other person should not until
>> published, even he has the URL,
>> 1.b) Implementing One time/ time based download link
>> Images, PDF, etc, does not have this restriction, they can be accessible
>> by public with known URL
>>
>> 2. Application binary need to be analyzed for number of details including
>> package name, version, any meta information, malware code, etc. However for
>> images we need only to verify if the file type and size fits, if ever. Also
>> the result of the REST call is different fro App binary to any other static
>> content.
>>
>> Hence I think option (2) is intuitive and clear.
>>
>> Cheers,
>> Ruwan
>>
>> On Thu, Apr 7, 2016 at 9:55 PM, Dinusha Senanayaka 
>> wrote:
>>
>>>
>>>
>>> On Thu, Apr 7, 2016 at 11:44 AM, Thilini Shanika 
>>> wrote:
>>>
 Hi all,

 We have a concern regarding the design of mobile application
 binary/image upload API. As per the discussions we had on the new design of
 the API model, we decided to use a separate API to upload mobile binary
 files(.apk, .ipa) including the images. Thus, in order to create a mobile
 app,  we have to initially upload relevant application binary and image
 files of app thumbnail, banner and screenshots and later the application
 should be created with the references to uploaded binaries.
 We have already implemented the REST API for application binary upload.
 But we have few concerns regarding the image file upload. We have two
 options in implementing image upload scenario.


1. Reusing the binary upload API for image upload also. But in this
case, we need to change the API design in order to distinguish the
uploading file type (Whether is it is an app binary or an image for
screenshots, thumbnails etc) since we have separate flows of processing 
 the
files.
2. Implementing a dedicated API for image upload only. In this
case, we can implement this API in order to be reused in webapp image
upload also.

  I'm +1 for option 1. Keep the API as
>>> http://localhost:9763/api/appm/publisher/v1.0/apps/binaries and handle
>>> all binary uploads(apks, images, documents) for web/mobile from this API,
>>> instead introducing API per each binary type.
>>>
>>> Regards,
>>> Dinusha.
>>>

 As per the offline discussion I had with RuwanA, another concern was
 raised regarding the URL for binary upload API. The current URL is '
 http://localhost:9763/api/appm/publisher/v1.0/apps/mobile/
 binaries'. But
 this particular URL is mobile application specific. In that case, we cannot
 reuse this API in future, for any other application binary upload, other
 that mobile binary upload. Our suggestion here is to rename the API as
 http://localhost:9763/api/appm/publisher/v1.0/apps/application/
 binaries and
 making the API more generic.

 Your suggestions are highly appreciated.

 [1] -
 https://docs.google.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit


 Thanks,
 Thilini

 --
 Thilini Shanika
 Software Engineer
 WSO2, Inc.; http://wso2.com
 20, Palmgrove Avenue, Colombo 3

 E-mail: tgtshan...@gmail.com


>>>
>>>
>>> --
>>> Dinusha Dilrukshi
>>> Associate Technical Lead
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94725255071
>>> Blog: http://dinushasblog.blogspot.com/
>>>
>>
>>
>>
>> --
>>
>> *Ruwan Abeykoon*
>> *Architect,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: ruw...@wso2.com
>>
>
>
>
> --
> *Rushmin Fernando*
> *Technical Lead*
>
> WSO2 Inc.  - Lean . 

Re: [Dev] [APPM] Mobile application binary file upload REST API

[Rushmin Fernando]

I agree with RuwanA. When Thilini says, "the flows of the different upload
types are different", it means that the only common aspect between these
upload types is, that they use the file system for storage.

So -1 for the option 1. But we, of course should re-use the file upload
code in different upload types :-)

Thanks
Rushmin

On Fri, Apr 8, 2016 at 7:16 AM, Ruwan Abeykoon  wrote:

> Hi Dinusha,
> I think option (1) poses few complications in both REST API user
> perspective and the implementation perspective.
> 1. Application binaries need to be placed in secured location and allow
> GET access based on various security policies(This is not available yet,
> but is a necessary feature in future.). few examples are,
> 1.a) Reviewer need to have access, but any other person should not until
> published, even he has the URL,
> 1.b) Implementing One time/ time based download link
> Images, PDF, etc, does not have this restriction, they can be accessible
> by public with known URL
>
> 2. Application binary need to be analyzed for number of details including
> package name, version, any meta information, malware code, etc. However for
> images we need only to verify if the file type and size fits, if ever. Also
> the result of the REST call is different fro App binary to any other static
> content.
>
> Hence I think option (2) is intuitive and clear.
>
> Cheers,
> Ruwan
>
> On Thu, Apr 7, 2016 at 9:55 PM, Dinusha Senanayaka 
> wrote:
>
>>
>>
>> On Thu, Apr 7, 2016 at 11:44 AM, Thilini Shanika 
>> wrote:
>>
>>> Hi all,
>>>
>>> We have a concern regarding the design of mobile application
>>> binary/image upload API. As per the discussions we had on the new design of
>>> the API model, we decided to use a separate API to upload mobile binary
>>> files(.apk, .ipa) including the images. Thus, in order to create a mobile
>>> app,  we have to initially upload relevant application binary and image
>>> files of app thumbnail, banner and screenshots and later the application
>>> should be created with the references to uploaded binaries.
>>> We have already implemented the REST API for application binary upload.
>>> But we have few concerns regarding the image file upload. We have two
>>> options in implementing image upload scenario.
>>>
>>>
>>>1. Reusing the binary upload API for image upload also. But in this
>>>case, we need to change the API design in order to distinguish the
>>>uploading file type (Whether is it is an app binary or an image for
>>>screenshots, thumbnails etc) since we have separate flows of processing 
>>> the
>>>files.
>>>2. Implementing a dedicated API for image upload only. In this case,
>>>we can implement this API in order to be reused in webapp image upload
>>>also.
>>>
>>>  I'm +1 for option 1. Keep the API as
>> http://localhost:9763/api/appm/publisher/v1.0/apps/binaries and handle
>> all binary uploads(apks, images, documents) for web/mobile from this API,
>> instead introducing API per each binary type.
>>
>> Regards,
>> Dinusha.
>>
>>>
>>> As per the offline discussion I had with RuwanA, another concern was
>>> raised regarding the URL for binary upload API. The current URL is '
>>> http://localhost:9763/api/appm/publisher/v1.0/apps/mobile/
>>> binaries'. But
>>> this particular URL is mobile application specific. In that case, we cannot
>>> reuse this API in future, for any other application binary upload, other
>>> that mobile binary upload. Our suggestion here is to rename the API as
>>> http://localhost:9763/api/appm/publisher/v1.0/apps/application/
>>> binaries and
>>> making the API more generic.
>>>
>>> Your suggestions are highly appreciated.
>>>
>>> [1] -
>>> https://docs.google.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit
>>>
>>>
>>> Thanks,
>>> Thilini
>>>
>>> --
>>> Thilini Shanika
>>> Software Engineer
>>> WSO2, Inc.; http://wso2.com
>>> 20, Palmgrove Avenue, Colombo 3
>>>
>>> E-mail: tgtshan...@gmail.com
>>>
>>>
>>
>>
>> --
>> Dinusha Dilrukshi
>> Associate Technical Lead
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94725255071
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
>
> --
>
> *Ruwan Abeykoon*
> *Architect,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ruw...@wso2.com
>



-- 
*Rushmin Fernando*
*Technical Lead*

WSO2 Inc.  - Lean . Enterprise . Middleware

email : rush...@wso2.com
mobile : +94772310855
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APPM] Mobile application binary file upload REST API

[Ruwan Abeykoon]

Hi Dinusha,
I think option (1) poses few complications in both REST API user
perspective and the implementation perspective.
1. Application binaries need to be placed in secured location and allow GET
access based on various security policies(This is not available yet, but is
a necessary feature in future.). few examples are,
1.a) Reviewer need to have access, but any other person should not until
published, even he has the URL,
1.b) Implementing One time/ time based download link
Images, PDF, etc, does not have this restriction, they can be accessible by
public with known URL

2. Application binary need to be analyzed for number of details including
package name, version, any meta information, malware code, etc. However for
images we need only to verify if the file type and size fits, if ever. Also
the result of the REST call is different fro App binary to any other static
content.

Hence I think option (2) is intuitive and clear.

Cheers,
Ruwan

On Thu, Apr 7, 2016 at 9:55 PM, Dinusha Senanayaka  wrote:

>
>
> On Thu, Apr 7, 2016 at 11:44 AM, Thilini Shanika 
> wrote:
>
>> Hi all,
>>
>> We have a concern regarding the design of mobile application binary/image
>> upload API. As per the discussions we had on the new design of the API
>> model, we decided to use a separate API to upload mobile binary files(.apk,
>> .ipa) including the images. Thus, in order to create a mobile app,  we have
>> to initially upload relevant application binary and image files of app
>> thumbnail, banner and screenshots and later the application should be
>> created with the references to uploaded binaries.
>> We have already implemented the REST API for application binary upload.
>> But we have few concerns regarding the image file upload. We have two
>> options in implementing image upload scenario.
>>
>>
>>1. Reusing the binary upload API for image upload also. But in this
>>case, we need to change the API design in order to distinguish the
>>uploading file type (Whether is it is an app binary or an image for
>>screenshots, thumbnails etc) since we have separate flows of processing 
>> the
>>files.
>>2. Implementing a dedicated API for image upload only. In this case,
>>we can implement this API in order to be reused in webapp image upload
>>also.
>>
>>  I'm +1 for option 1. Keep the API as
> http://localhost:9763/api/appm/publisher/v1.0/apps/binaries and handle
> all binary uploads(apks, images, documents) for web/mobile from this API,
> instead introducing API per each binary type.
>
> Regards,
> Dinusha.
>
>>
>> As per the offline discussion I had with RuwanA, another concern was
>> raised regarding the URL for binary upload API. The current URL is '
>> http://localhost:9763/api/appm/publisher/v1.0/apps/mobile/
>> binaries'. But
>> this particular URL is mobile application specific. In that case, we cannot
>> reuse this API in future, for any other application binary upload, other
>> that mobile binary upload. Our suggestion here is to rename the API as
>> http://localhost:9763/api/appm/publisher/v1.0/apps/application/
>> binaries and
>> making the API more generic.
>>
>> Your suggestions are highly appreciated.
>>
>> [1] -
>> https://docs.google.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit
>>
>>
>> Thanks,
>> Thilini
>>
>> --
>> Thilini Shanika
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>> 20, Palmgrove Avenue, Colombo 3
>>
>> E-mail: tgtshan...@gmail.com
>>
>>
>
>
> --
> Dinusha Dilrukshi
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 

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

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

Re: [Dev] [Architecture] [C5] Must Inject CarbonServerInfo when writing OSGi Test Cases

[Sameera Jayasoma]

On Fri, Apr 8, 2016 at 12:13 AM, Imesh Gunaratne  wrote:

> Hi Aruna,
>
> On Thu, Apr 7, 2016 at 6:21 PM, Aruna Karunarathna  wrote:
>
>> Hi Devs,
>>
>> When writing OSGi Test Cases, Please Inject the CarbonServerInfo service
>> [1]. Otherwise the container wont start properly and the test cases will
>> fail.
>>
>> After injecting the service it will guarantee that the server will fully
>> start, before running the test cases. e.g. [2]
>>
>
> Would you mind mentioning what CarbonServerInfo does and why containers
> would not start without it?
>

Aruna is talking about Pax Exam test containers (OSGi runtimes) :)

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


-- 
Sameera Jayasoma,
Software Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://blog.sameera.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456

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

[Dev] [IS] [Passive STS] Error while Invoking Passive STS in Identity Server

[Chamila Wijayarathna]

Hi all,

Currently passive STS in Identity Server is not workong, but after applying
following changes in orbit and identity-inbound-auth-sts I could
successfully run passive sts scenarios using PassiveSTSSampleApp.

*Orbit*

*diff --git a/opensaml/2.6.4.wso2v1/pom.xml b/opensaml/2.6.4.wso2v1/pom.xml*
*index 06b4d26..e10c16f 100644*
*--- a/opensaml/2.6.4.wso2v1/pom.xml*
*+++ b/opensaml/2.6.4.wso2v1/pom.xml*
*@@ -259,6 +259,7 @@*
*
 
net.jcip.annotations.*;version="${net.jcip.annotations.version}";resolution:=optional,*
*
 
org.apache.commons.httpclient.*;version="${org.apache.commons.httpclient.version}";resolution:=optional,*
*
 
org.apache.commons.ssl.*;version="${org.apache.commons.ssl.version}";resolution:=optional,*
*+
 org.apache.commons.codec.binary;version="[1.4,2)",*
* org.apache.velocity.*;resolution:=optional,*
*
 
org.apache.xml.security.*;version="${org.apache.xml.security.version}";resolution:=optional,*
*
 org.bouncycastle.*;version="${org.bouncycastle.version}";resolution:=optional,*
*@@ -279,6 +280,7 @@*
*
 org.apache.commons.fileupload.*;resolution:=optional,*
* org.apache.log4j.*;resolution:=optional,*
*
 org.owasp.validator.html;resolution:=optional,*
*+
 org.apache.axiom.om.impl.dom.jaxp;version="${axiom.osgi.version.range}"*
* *
*
 esapi;scope=compile|runtime;inline=false*
* *
*@@ -321,6 +323,7 @@*
* [1.6.0,1.8.0)*
* 0.0.0*
* 0.0.0*
*+[1.2.11,
2.0.0)*
* *

* *


*identity-inbound-auth-sts*

*diff --git a/components/org.wso2.carbon.identity.sts.passive/pom.xml
b/components/org.wso2.carbon.identity.sts.passive/pom.xml*
*index f391798..2d927ae 100644*
*--- a/components/org.wso2.carbon.identity.sts.passive/pom.xml*
*+++ b/components/org.wso2.carbon.identity.sts.passive/pom.xml*
*@@ -97,7 +97,8 @@*
* javax.xml.stream;
version="${equinox.osgi.stax-api.imp.pkg.version.range}",*
* javax.servlet.http;
version="${imp.pkg.version.javax.servlet}",*

*-org.apache.axiom.*;
version="${axiom.osgi.version.range}",*
*+org.apache.axiom.om
; version="${axiom.osgi.version.range}",*
*+org.apache.axiom.soap;
version="${axiom.osgi.version.range}",*
* org.apache.axis2.*;
version="${axis2.osgi.version.range}",*
* org.apache.rahas.*;
version="${rampart.wso2.osgi.version.range}",*
* org.apache.ws.secpolicy;
version="${rampart.wso2.osgi.version.range}",*
*@@ -128,11 +129,13 @@*
*
 version="${carbon.identity.package.import.version.range}",*
* org.wso2.carbon.identity.core.*;*
*
 version="${carbon.identity.package.import.version.range}",*
*+
 org.opensaml;version="${opensaml2.wso2.osgi.version.range}"*
* *
* *
*
 !org.wso2.carbon.identity.sts.passive.internal,*
* org.wso2.carbon.identity.sts.passive.*;
version="${carbon.identity.package.export.version}",*
* *
*+**
* *
* *
* *

But now I am observing following error at back end.

*[2016-04-08 02:05:08,960] ERROR {org.opensaml.XML} -  Unable to parse SAML
1.0 Schemas: org.xml.sax.SAXParseException; schema_reference.4: Failed to
read schema document 'xml.xsd', because 1) could not find the document; 2)
the document could not be read; 3) the root element of the document is not
.*
*[2016-04-08 02:05:08,962] ERROR {org.opensaml.XML} -  Unable to parse SAML
1.1 Schemas: org.xml.sax.SAXParseException; schema_reference.4: Failed to
read schema document 'xml.xsd', because 1) could not find the document; 2)
the document could not be read; 3) the root element of the document is not
.*

Any idea about what is the reason for this?

Thanks!
-- 
*Chamila Dilshan Wijayarathna,*
Software Engineer
Mobile:(+94)788193620
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [C5] Must Inject CarbonServerInfo when writing OSGi Test Cases

[Imesh Gunaratne]

Hi Aruna,

On Thu, Apr 7, 2016 at 6:21 PM, Aruna Karunarathna  wrote:

> Hi Devs,
>
> When writing OSGi Test Cases, Please Inject the CarbonServerInfo service
> [1]. Otherwise the container wont start properly and the test cases will
> fail.
>
> After injecting the service it will guarantee that the server will fully
> start, before running the test cases. e.g. [2]
>

Would you mind mentioning what CarbonServerInfo does and why containers
would not start without it?

Thanks

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

Re: [Dev] Error while implementing the Integration test for salesforce(SOAP API) connector

[Hariprasath Thanarajah]

Hi Malaka,

No In this I set the blocking as false and also test it with ESB 5.0.0-M1.

On Thu, Apr 7, 2016 at 9:08 PM, Malaka Silva  wrote:

> Hariprasath seems like this is related to [1]. Are you using call mediator
> in blocking mode? If so avoid it for integration tests with esb 490.
>
> [1] https://wso2.org/jira/browse/ESBJAVA-4388
>
> On Thu, Apr 7, 2016 at 3:59 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi All,
>>
>> I am working on to create integration test for salesforce connector. When
>> I create the testcase for a particular method(getUserInfo) I got the
>> response via the ESB call but after that I get the following error in [1].
>>
>> I have added the proxy[2] and soap request[3] as well.
>>
>> Can anyone suggest me what could be the reason for this follwing error.
>>
>> [1]
>> FAILED: testGetUserInfoWithMandatoryParameters
>> Salesforce {getUserInfo} integration test with mandatory
>> parameters.
>> java.lang.NullPointerException
>> at
>> org.apache.axis2.transport.http.AbstractHTTPSender.processCookieHeaders(AbstractHTTPSender.java:213)
>> at
>> org.apache.axis2.transport.http.AbstractHTTPSender.obtainHTTPHeaderInformation(AbstractHTTPSender.java:170)
>> at
>> org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:224)
>> at
>> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:294)
>> at
>> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
>> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
>> at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
>> at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>> at
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>> at
>> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendSOAPRequest(ConnectorIntegrationTestBase.java:616)
>> at
>> org.wso2.carbon.connector.integration.test.salesforce.SalesforceConnectorIntegrationTest.testGetUserInfoWithMandatoryParameters(SalesforceConnectorIntegrationTest.java:60)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
>> at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
>> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
>> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
>> at
>> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
>> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
>> at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
>> at org.testng.TestRunner.privateRun(TestRunner.java:757)
>> at org.testng.TestRunner.run(TestRunner.java:608)
>> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
>> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
>> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
>> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
>> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
>> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
>> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
>> at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
>> at org.testng.TestNG.run(TestNG.java:999)
>> at
>> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
>> at
>> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
>> at
>> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>> at
>> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>> at
>> 

Re: [Dev] [C5] Must Inject CarbonServerInfo when writing OSGi Test Cases

[Kishanthan Thangarajah]

Can we also add this to the kernel osgi test framework documentation as a
best practice guideline?

On Thu, Apr 7, 2016 at 6:21 PM, Aruna Karunarathna  wrote:

> Hi Devs,
>
> When writing OSGi Test Cases, Please Inject the CarbonServerInfo service
> [1]. Otherwise the container wont start properly and the test cases will
> fail.
>
> After injecting the service it will guarantee that the server will fully
> start, before running the test cases. e.g. [2]
>
>
> [1].
> https://github.com/wso2/carbon-kernel/blob/master/core/src/main/java/org/wso2/carbon/kernel/utils/CarbonServerInfo.java
> [2].
> https://github.com/wso2/carbon-kernel/blob/master/tests/osgi-tests/src/test/java/org/wso2/carbon/osgi/startupresolver/SampleStartupOrderResolverOSGiTest.java#L71
>
> Regards,
> Aruna
> --
>
> *Aruna Sujith Karunarathna *
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>



-- 
*Kishanthan Thangarajah*
Associate Technical Lead,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Secure vault for C5 ?

[Firzhan Naqash]

We can have kube secret variables to read password [1]

[1] [1] http://kubernetes.io/docs/user-guide/secrets/

Regards,
Firzhan


-- 
*Firzhan Naqash*
Senior Software Engineer - Integration Platform Team
WSO2 Inc. http://wso2.com

email: firz...@wso2.com
mobile: (+94) 77 9785674 <%28%2B94%29%2071%205247551>*|
blog: http://firzhanblogger.blogspot.com/
  *
*twitter: https://twitter.com/firzhan007  |
linked-in: **https://www.linkedin.com/in/firzhan
*

On Thu, Apr 7, 2016 at 11:29 AM, Manuranga Perera  wrote:

>
> On Thu, Apr 7, 2016 at 9:59 PM, Manuranga Perera  wrote:
>
>> be may be bit too complex to implement though
>
>
> It may be bit too complex to implement though
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Configuring load balancing in app cloud with HA Proxy

[Imesh Gunaratne]

On Wed, Mar 16, 2016 at 10:49 AM, Nishadi Kirielle  wrote:
>
>
> In the current deployment, we have tested a service with a single port
> exposed. This is because the service identifies whether this is exposed to
> http or https through the service annotation which is common to all exposed
> ports in the service. If we are going with that approach, in order to
> support http traffic and https traffic, we need several services. Thus,
> currently I'm attempting to deploy a service with several exposed ports.
>

AFAIU this is not a restriction enforced by K8S services rather a
limitation in the service load balancer (the way it uses service
annotations) [3]. K8S services allow to define any number of annotations
with any key/value pair. We can change the service load balancer to use an
annotation per port to handle this.

>
> In addition, another concern is how the HAProxy load balancer itself is
> exposed to external traffic. Currently it is done through host ports. If we
> use node ports for this, it will expose the particular port in all the
> nodes. But the use of host port will only expose the particular port in the
> specified node.
>

Why do we use host ports instead of node ports? I believe traffic get
delegated to HAProxy via an AWS load balancer. If so what would happen if
the above host becomes unavailable?

[3]
https://github.com/nishadi/contrib/blob/master/service-loadbalancer/service_loadbalancer.go#L468

Thanks


>
> Appreciate your feedback on the approach taken.
>
> Thanks
>
> [1].
> https://github.com/nishadi/contrib/commit/f169044546dc8a84a359d889bb186aef83d9c422
> [2].
> https://github.com/nishadi/contrib/blob/master/service-loadbalancer/rc.yaml#L52
>
> On Mon, Mar 14, 2016 at 10:39 AM, Nishadi Kirielle 
> wrote:
>
>> Hi all,
>> +1 for going with SSL pass through approach. Once the testing with
>> staging is done, I will focus on this approach.
>>
>> Thanks
>>
>> On Mon, Mar 14, 2016 at 10:29 AM, Manjula Rathnayake 
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> On Mon, Mar 14, 2016 at 10:20 AM, Imesh Gunaratne 
>>> wrote:
>>>
 Hi Manjula,

 On Mon, Mar 14, 2016 at 10:06 AM, Manjula Rathnayake  wrote:

> Hi Imesh,
>
> On Mon, Mar 14, 2016 at 9:56 AM, Imesh Gunaratne 
> wrote:
>
>>
>> On Sun, Mar 13, 2016 at 11:36 PM, Nishadi Kirielle 
>> wrote:
>>
>>> Hi all,
>>> Currently I'm working on configuring HAProxy load balancing support
>>> for app cloud.
>>> In checking the session affinity functionality in kuberenetes, I
>>> have verified the load balancing of http traffic with HAProxy. It could 
>>> be
>>> done using kubernetes contribution repo, 'service loadbalancer' [1].
>>>
>>> In order to check the load balancing with https traffic the taken
>>> approach is SSL termination.In the scenario of app cloud, kubernetes
>>> cluster is not directly exposed and the load balancer exists within the
>>> cluster. Thus the communication between the application servers and the
>>> load balancer happens internally. Although SSL termination ends the 
>>> secure
>>> connection at the load balancer, due to the above mentioned reasons, SSL
>>> termination seems to be a better solution. The reason for the use of SSL
>>> termination over SSL pass through is because of the complexity of 
>>> handling
>>> a separate SSL certificate for each server behind the load balancer in 
>>> the
>>> case of SSL pass through.
>>>
>>> -1 for this approach, IMO this has a major security risk.
>>
>> Let me explain the problem. If we offload SSL at the service load
>> balancer, all traffic beyond the load balancer will use HTTP and the
>> message content will be visible to anyone on network inside K8S. Which
>> means someone can simply start a container in K8S and trace all HTTP
>> traffic going through.
>>
>

> Below is from HA Proxy documentation[1]. AFAIU, HA Proxy to backend
> server communication happens with HTTPS enabled but not validating the
> server certificate.
>


> verify
> 
> [none|required]
>
> This setting is only available when support for OpenSSL was built in. If 
> set
> to 'none', server certificate is not verified. In the other case, The
> certificate provided by the server is verified using CAs from 'ca-file'
> and optional CRLs from 'crl-file'. If 'ssl_server_verify' is not specified
> in global  section, this is the default. On verify failure the handshake
> is aborted. It is critically important to verify server certificates when
> using SSL to connect to servers, otherwise the communication is prone to
> trivial man-in-the-middle attacks rendering SSL totally 

Re: [Dev] [APPM][UX] Responsive left menu with submenus

[Dinusha Senanayaka]

Hi Jerad,

On Thu, Apr 7, 2016 at 12:39 PM, Jerad Rutnam  wrote:

> Hi Jenananthan,
>
> Yes, Its ok to use it. But we have not finalized the markup etc ... yet.
> But we can update you about the changes once it's finalized.
>

This is something critical for AppM new UI. Please let us know  once this
is updated.

Regards,
Dinusha.

>
> Regards,
> Jerad
>
>
> On Wed, Apr 6, 2016 at 10:56 AM, Jenananthan Yogendran <
> jenanant...@wso2.com> wrote:
>
>> Hi UX Team,
>>
>> In APP Manager we need to have sub menu(my subscription) under left
>> column menus(asset types).
>> With current markup [1] this is not supported.In the markup of API
>> Manager[2]  sub menu support is available. Is this markup  completed ? Can
>> we use the same markup for left menus ?
>>
>> 1. https://github.com/wso2-dev-ux/product-appm
>> 2. https://github.com/wso2-dev-ux/product-apim
>>
>> Thanks
>> --
>> Jenananthan Yogendran
>> *Software Engineer,*
>> *WSO2 inc., http://wso2.com *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Jerad Rutnam*
> *Software Engineer*
>
> WSO2 Inc.
> lean | enterprise | middleware
> M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com
>



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

Re: [Dev] Secure vault for C5 ?

[Manuranga Perera]

On Thu, Apr 7, 2016 at 9:59 PM, Manuranga Perera  wrote:

> be may be bit too complex to implement though


It may be bit too complex to implement though


-- 
With regards,
*Manu*ranga Perera.

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

Re: [Dev] Secure vault for C5 ?

[Manuranga Perera]

One improvement we can do is take the decrypting entity out and give it
some rules such as
1) Check requester's network address
2) Check if it has real requirement to scale out, eg: high traffic

(a) container ---{secret}Kb,Ka-rand--> (b) central
decrypting service out side Docker

(a) container <---{secret}Ka-rand---  (b) central
decrypting service out side Docker


I'll be may be bit too complex to implement though


On Wed, Mar 30, 2016 at 12:44 PM, Thilina Piyasundara 
wrote:

> IMO we need to have the solution within WSO2 products. Like its talking to
> OC in the bootup process.
>
> Reason is, when we talk about securevault we need to assume that the evil
> person have full access to the host VM and containers.
>
> Thanks and regards,
>
> Thilina Piyasundara
> Systems Engineer
> ​
> ​
> Blog: thilina.piyasundara.org
> Linkedin: linkedin.com/in/thilinapiyasundara
>
> WSO2, Inc.
> ​
> ​ 
> lean . enterprise . middleware
> https://cloud.wso2.com
>
> On Wed, Mar 30, 2016 at 12:37 PM, Aruna Karunarathna 
> wrote:
>
>>
>>
>> On Wed, Mar 30, 2016 at 12:26 PM, Afkham Azeez  wrote:
>>
>>> What if we modify secvault to be able to read the password from an env
>>> var?
>>>
>>>
>> Env variables for passwords in docker is not a good approach I believe.
>>
>> Can't we use something like [1], for docker containers?
>>
>> [1]. https://github.com/ehazlett/docker-volume-libsecret
>>
>>
>>> On Wed, Mar 30, 2016 at 12:19 PM, Thilina Piyasundara >> > wrote:
>>>
 Yes we can't use C4 approach.
 We try to do it in docker environments but somehow we need to send the
 password-tmp in to the dokcer (via puppet or environment variables).

 If we us docker volumes or if we store the password-tmp in the image
 there is a possibility that anyone can get that root/main password if they
 have access to the containers. Isn't it ?

 Thanks and regards,

 Thilina Piyasundara
 Systems Engineer
 ​
 ​
 Blog: thilina.piyasundara.org
 Linkedin: linkedin.com/in/thilinapiyasundara

 WSO2, Inc.
 ​
 ​ 
 lean . enterprise . middleware
 https://cloud.wso2.com

 On Wed, Mar 30, 2016 at 12:12 PM, Afkham Azeez  wrote:

> In the container world, the sec vault files will get packed into the
> containers, and if there are changes to those files, you will need to
> create a new version of the container image. This is true for the rest of
> the configuration files as well. This goes with the concept of immutable
> servers.
>
> Azeez
>
> On Wed, Mar 30, 2016 at 11:54 AM, Sameera Jayasoma 
> wrote:
>
>> I believe we cannot apply the same thing we had in C4. We have to
>> think about how we can apply this for containers as well. Lets have a 
>> quick
>> chat on this.
>>
>> Thanks,
>> Sameera.
>>
>> On Wed, Mar 30, 2016 at 11:51 AM, Hasitha Aravinda 
>> wrote:
>>
>>> I think we have to target this for Hamming platform ? Because we
>>> have some configuration files like (*-datasource.xml) with passwords.
>>>
>>> Apart from securing passwords in configuration files, I think we
>>> will need secure vault support for runtime as well. In products like GW,
>>> ESB and BPS do secure services invocations, (i.e BasicAuth) and we will
>>> need a central place to store encrypted credentials.
>>>
>>> Thanks,
>>> Hasitha.
>>>
>>> On Wed, Mar 30, 2016 at 11:33 AM, Afkham Azeez 
>>> wrote:
>>>
 Simply porting the existing sec vault to work with C5 should be
 sufficient.

 On Wed, Mar 30, 2016 at 11:03 AM, Hasitha Aravinda <
 hasi...@wso2.com> wrote:

> Hi team,
>
> How are we going to use $Subject in C5. Can we use existing secure
> vault implementation for this.
>
> Thanks,
> Hasitha.
>
> --
> --
> Hasitha Aravinda,
> Senior Software Engineer,
> WSO2 Inc.
> Email: hasi...@wso2.com
> Mobile : +94 718 210 200
>



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

 *Lean . Enterprise . 

Re: [Dev] [APPM] Mobile application binary file upload REST API

[Dinusha Senanayaka]

On Thu, Apr 7, 2016 at 11:44 AM, Thilini Shanika  wrote:

> Hi all,
>
> We have a concern regarding the design of mobile application binary/image
> upload API. As per the discussions we had on the new design of the API
> model, we decided to use a separate API to upload mobile binary files(.apk,
> .ipa) including the images. Thus, in order to create a mobile app,  we have
> to initially upload relevant application binary and image files of app
> thumbnail, banner and screenshots and later the application should be
> created with the references to uploaded binaries.
> We have already implemented the REST API for application binary upload.
> But we have few concerns regarding the image file upload. We have two
> options in implementing image upload scenario.
>
>
>1. Reusing the binary upload API for image upload also. But in this
>case, we need to change the API design in order to distinguish the
>uploading file type (Whether is it is an app binary or an image for
>screenshots, thumbnails etc) since we have separate flows of processing the
>files.
>2. Implementing a dedicated API for image upload only. In this case,
>we can implement this API in order to be reused in webapp image upload
>also.
>
>  I'm +1 for option 1. Keep the API as
http://localhost:9763/api/appm/publisher/v1.0/apps/binaries and handle all
binary uploads(apks, images, documents) for web/mobile from this API,
instead introducing API per each binary type.

Regards,
Dinusha.

>
> As per the offline discussion I had with RuwanA, another concern was
> raised regarding the URL for binary upload API. The current URL is '
> http://localhost:9763/api/appm/publisher/v1.0/apps/mobile/
> binaries'. But this
> particular URL is mobile application specific. In that case, we cannot
> reuse this API in future, for any other application binary upload, other
> that mobile binary upload. Our suggestion here is to rename the API as
> http://localhost:9763/api/appm/publisher/v1.0/apps/application/
> binaries and making
> the API more generic.
>
> Your suggestions are highly appreciated.
>
> [1] -
> https://docs.google.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit
>
>
> Thanks,
> Thilini
>
> --
> Thilini Shanika
> Software Engineer
> WSO2, Inc.; http://wso2.com
> 20, Palmgrove Avenue, Colombo 3
>
> E-mail: tgtshan...@gmail.com
>
>


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

Re: [Dev] Error while implementing the Integration test for salesforce(SOAP API) connector

[Malaka Silva]

Hariprasath seems like this is related to [1]. Are you using call mediator
in blocking mode? If so avoid it for integration tests with esb 490.

[1] https://wso2.org/jira/browse/ESBJAVA-4388

On Thu, Apr 7, 2016 at 3:59 PM, Hariprasath Thanarajah  wrote:

> Hi All,
>
> I am working on to create integration test for salesforce connector. When
> I create the testcase for a particular method(getUserInfo) I got the
> response via the ESB call but after that I get the following error in [1].
>
> I have added the proxy[2] and soap request[3] as well.
>
> Can anyone suggest me what could be the reason for this follwing error.
>
> [1]
> FAILED: testGetUserInfoWithMandatoryParameters
> Salesforce {getUserInfo} integration test with mandatory
> parameters.
> java.lang.NullPointerException
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.processCookieHeaders(AbstractHTTPSender.java:213)
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.obtainHTTPHeaderInformation(AbstractHTTPSender.java:170)
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:224)
> at
> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:294)
> at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendSOAPRequest(ConnectorIntegrationTestBase.java:616)
> at
> org.wso2.carbon.connector.integration.test.salesforce.SalesforceConnectorIntegrationTest.testGetUserInfoWithMandatoryParameters(SalesforceConnectorIntegrationTest.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
> at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
> at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
> at org.testng.TestRunner.privateRun(TestRunner.java:757)
> at org.testng.TestRunner.run(TestRunner.java:608)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
> at org.testng.TestNG.run(TestNG.java:999)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
> at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
>
> [2]
> 

Re: [Dev] [DAS] Spark clustering and DAS analytics cluster tuning

[Niranda Perera]

Hi Rukshani,

This has still not been done. Is it possible for us get this done soon?

On Fri, Mar 4, 2016 at 11:36 AM, Rukshani Weerasinha 
wrote:

> Hi Niranda,
>
> Not yet. I will add this content soon and let you know once it is done.
>
> Best Regards,
> Rukshani.
>
> On Fri, Mar 4, 2016 at 11:33 AM, Niranda Perera  wrote:
>
>> Hi Rukshani and Sam,
>>
>> were we able to publish these content?
>>
>> best
>>
>> On Tue, Jan 26, 2016 at 8:20 AM, Rukshani Weerasinha 
>> wrote:
>>
>>> Hello Niranda,
>>>
>>> Thank you for providing this content. We will start working on this.
>>>
>>> Best Regards,
>>> Rukshani.
>>>
>>> On Tue, Jan 26, 2016 at 3:34 AM, Niranda Perera 
>>> wrote:
>>>
 Hi,

 I added 2 blog posts explaining how Spark clustering works [1] and how
 to manage the resources in a DAS analytics cluster [2].

 @Rukshani, some of the content should go to this doc [3]. Can we work
 on that?

 Best

 [1]
 https://pythagoreanscript.wordpress.com/2016/01/23/the-dynamics-of-a-spark-cluster-wrt-wso2-das/
 [2]
 https://pythagoreanscript.wordpress.com/2016/01/25/wso2-das-spark-cluster-tuning/
 [3] https://docs.wso2.com/display/DAS301/Performance+Tuning

 --
 *Niranda Perera*
 Software Engineer, WSO2 Inc.
 Mobile: +94-71-554-8430
 Twitter: @n1r44 
 https://pythagoreanscript.wordpress.com/

>>>
>>>
>>>
>>> --
>>> Rukshani Weerasinha
>>>
>>> WSO2 Inc.
>>> Web:http://wso2.com
>>> Mobile: 0777 683 738
>>>
>>>
>>
>>
>> --
>> *Niranda Perera*
>> Software Engineer, WSO2 Inc.
>> Mobile: +94-71-554-8430
>> Twitter: @n1r44 
>> https://pythagoreanscript.wordpress.com/
>>
>
>
>
> --
> Rukshani Weerasinha
>
> WSO2 Inc.
> Web:http://wso2.com
> Mobile: 0777 683 738
>
>


-- 
*Niranda Perera*
Software Engineer, WSO2 Inc.
Mobile: +94-71-554-8430
Twitter: @n1r44 
https://pythagoreanscript.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] product-mss hangs after deploying a (faulty) service

[Rasika Perera]

Hi Himasha,

This usually happens when MSF4J is waiting for its required capabilities.
MSF4J has cardinality of AT_LEAST_ONE as required capabilities for the Carbon
Transport. Which means server is waiting on the startup for at least one
OSGi service implementing CarbonTransport.class interface[1]. As Aruna
mentioned can you verify whether you are packing carbon transport.

However one issue found on your pom file.


org.wso2.carbon.bpmn.rest.**,*
version=${carbon.business-process.exp.pkg.version},


should be corrected as;


org.wso2.carbon.bpmn.rest.**;*
version=${carbon.business-process.exp.pkg.version},


[1]
https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/MicroservicesServerSC.java#L74

Thanks
~Rasika


On Thu, Apr 7, 2016 at 2:47 PM, Aruna Karunarathna  wrote:

> Have you guys added the carbon-transport-mgt?
>
> On Thu, Apr 7, 2016 at 1:57 PM, Hasitha Aravinda  wrote:
>
>> Hi Manu,
>>
>> were you able to solve this issue, I am getting the same error.
>>
>> Thanks,
>> Hasitha.
>>
>> On Wed, Feb 10, 2016 at 1:42 PM, Manuranga Perera  wrote:
>>
>>> MSS product hangs when I deploy my service, but fat-jar mode works.
>>>
>>> prints
>>> Waiting on pending capability registration. Capability:
>>> org.wso2.msf4j.Interceptor
>>>
>>> how to proceed debugging?
>>> --
>>> With regards,
>>> *Manu*ranga Perera.
>>>
>>> phone : 071 7 70 20 50
>>> mail : m...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> --
>> 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
>>
>>
>
>
> --
>
> *Aruna Sujith Karunarathna *
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
With Regards,

*Rasika Perera*
Software Engineer
M: +94 71 680 9060 E: rasi...@wso2.com
LinkedIn: http://lk.linkedin.com/in/rasika90

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

Re: [Dev] [EMM][AppM] Why APPM platform specific implementations are in mdm-admin JAX-RS?

[Ruwan Abeykoon]

Hi Kasun,
Yes, I think this needs to be refactored to expose generic "Operation" in
REST/OSGI API integration. Following are the things which can be improved
IMO,
1. The operation info-set can be made extensible, so that we can add
different application types without changing the API
2. Remove these Util classes as this seems tied up to existing device
types, and seems they are not Utilities at all.
3. Re-factory will cause further decoupling AppM (or any client side) from
EMM internal details.

>> Correct way of implementing this would be, having these platform
specific REST APIs in respective platform JAX-RS services and AppM should
invoke those APIs according to the device platform.
+1

Cheers,
Ruwan

On Thu, Apr 7, 2016 at 12:42 PM, Kasun Dananjaya Delgolla 
wrote:

> Hi All,
>
> While restructuring mdm-admin jax-rs to be in the core layer, I found out
> that several platform specific implementations are residing in mdm-admin
> jax-rs. All such implementations are related to AppM functionality
> (ex: MDMAndroidOperationUtil and MDMIOSOperationUtil classes).
>
> We know that AppM is invoking mdm-admin REST APIs to get its functionality
> done, but ideally mdm-admin should have only generic functionalities. If we
> want to enable these features via mdm-admin, we should make it generic
> without having any platform specific code within mdm-admin IMO.
>
> Correct way of implementing this would be, having these platform specific
> REST APIs in respective platform JAX-RS services and AppM should invoke
> those APIs according to the device platform.
>
> Is there any specific reason why we implemented it like that?
>
> Thanks
>
> --
> Kasun Dananjaya Delgolla
>
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
> Tel:  +94 11 214 5345
> Fax: +94 11 2145300
> Mob: + 94 771 771 015
> Blog: http://kddcodingparadise.blogspot.com
> Linkedin: *http://lk.linkedin.com/in/kasundananjaya
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

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

Re: [Dev] Fwd: [EMM 2.1.0] [Device Analytics] Obtaining 'No-Passcode' & 'No-Encryption' states via Device Info

[Kasun Dananjaya Delgolla]

Hi Dilan,

It's possible on android. We can simply check it via device policy manager
and attach it to device info payload. Also it should be possible on iOS.
But we will have to check on Windows. @Hasunie - Any input on this?

Thanks
On Apr 7, 2016 6:27 PM, "Dilan Udara Ariyaratne"  wrote:

> Adding KasunD, Milan, InoshP, Dilshan and Hasunie to the thread...
>
> *Dilan U. Ariyaratne*
> Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> -- Forwarded message --
> From: Dilan Udara Ariyaratne 
> Date: Thu, Apr 7, 2016 at 6:23 PM
> Subject: [Dev] [EMM 2.1.0] [Device Analytics] Obtaining 'No-Passcode' &
> 'No-Encryption' states via Device Info
> To: WSO2 Developers' List 
>
>
> Hi Folks,
>
> Is there currently any possibility of retrieving the following states
> via device-info capturing task of EMM for all mobile platforms, i.e.
> Android, iOS and Windows ?
>
> [1] No-Passcode state - This could carry the value of either true or false
> and express whether the device is currently having a passcode or not
> [2] No-Encryption state - This could also carry the value of either true
> or false and express whether the device data is currently encrypted or not
>
> If we can obtain these data, there lies the possibility of showing related
> analytics (See Following Figure) on Device Dashboard page for EMM
> administrators
> which is currently considered as a useful requirement.
>
>
>
>
> Thanks.
>
> *Dilan U. Ariyaratne*
> Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [EMM 2.1.0] [Device Analytics] Obtaining 'No-Passcode' & 'No-Encryption' states via Device Info

[Dilan Udara Ariyaratne]

Hi Folks,

Is there currently any possibility of retrieving the following states
via device-info capturing task of EMM for all mobile platforms, i.e.
Android, iOS and Windows ?

[1] No-Passcode state - This could carry the value of either true or false
and express whether the device is currently having a passcode or not
[2] No-Encryption state - This could also carry the value of either true or
false and express whether the device data is currently encrypted or not

If we can obtain these data, there lies the possibility of showing related
analytics (See Following Figure) on Device Dashboard page for EMM
administrators
which is currently considered as a useful requirement.




Thanks.

*Dilan U. Ariyaratne*
Software Engineer
WSO2 Inc. 
Mobile: +94766405580 <%2B94766405580>
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [C5] Must Inject CarbonServerInfo when writing OSGi Test Cases

[Aruna Karunarathna]

Hi Devs,

When writing OSGi Test Cases, Please Inject the CarbonServerInfo service
[1]. Otherwise the container wont start properly and the test cases will
fail.

After injecting the service it will guarantee that the server will fully
start, before running the test cases. e.g. [2]


[1].
https://github.com/wso2/carbon-kernel/blob/master/core/src/main/java/org/wso2/carbon/kernel/utils/CarbonServerInfo.java
[2].
https://github.com/wso2/carbon-kernel/blob/master/tests/osgi-tests/src/test/java/org/wso2/carbon/osgi/startupresolver/SampleStartupOrderResolverOSGiTest.java#L71

Regards,
Aruna
-- 

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

[Dev] Opaque mouse cursor in datamapper editor (eclipse mars)

[Susinda Perera]

Hi Viraj

I have created a JIRA[1] to track this. Further investigate to see who is
drawing this cursor but could not find any extension points to override
that. hence raised the same in eclipse forum[2]. Does anyone have any clue
on this?

[1] https://wso2.org/jira/browse/DEVTOOLESB-153
[2] https://www.eclipse.org/forums/index.php/m/1728797/#msg_1728797

-- 
*Susinda Perera*
Software Engineer
B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
Mobile:(+94)716049075
Blog: susinda.blogspot.com
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to create database tables with -Dsetup in Carbon 5?

[Isuru Perera]

Hi Carbon team,

When will this feature be implemented in Carbon? As I understand, most of
the products need this feature.

Thanks!

On Tue, Mar 29, 2016 at 11:51 AM, Asitha Nanayakkara 
wrote:

> +1 for having this as a common feature. MB will also be using this feature
> to create the database schema based on the database vendor.
>
> On Tue, Mar 29, 2016 at 11:09 AM, Isuru Perera  wrote:
>
>> Hi Aruna,
>>
>> I think this feature will be important for other products as most of the
>> products will eventually need to create the database schema based on the
>> database vendor.
>>
>> I hope MB team will also need this feature soon and it would be good if
>> this feature can be supported in next platform release.
>>
>> Thanks!
>>
>> On Fri, Mar 25, 2016 at 2:03 PM, Aruna Karunarathna 
>> wrote:
>>
>>>
>>>
>>> On Fri, Mar 25, 2016 at 1:45 PM, Isuru Perera  wrote:
>>>
 Hi,

 In Carbon 4.x.x, we extend [1]
 org.wso2.carbon.utils.dbcreator.DatabaseCreator [2]. How can we do the same
 in Carbon 5?

>>>
>>> Hi Isuru,
>>>
>>> There is no such feature planned or available ATM for hamming platform
>>> release.
>>> Regards,
>>> Aruna
>>>

 Thanks!

 [1]
 https://github.com/search?l==DatabaseCreator++user%3Awso2=advsearch=Code=%E2%9C%93
 [2]
 https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/dbcreator/DatabaseCreator.java

 --
 Isuru Perera
 Associate Technical Lead | WSO2, Inc. | http://wso2.com/
 Lean . Enterprise . Middleware

 about.me/chrishantha
 Contact: +IsuruPereraWSO2
 

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


>>>
>>>
>>> --
>>>
>>> *Aruna Sujith Karunarathna *
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 9040362 | Work: +94 112145345
>>> Email: ar...@wso2.com | Web: www.wso2.com
>>>
>>>
>>
>>
>>
>> --
>> Isuru Perera
>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>> Contact: +IsuruPereraWSO2 
>>
>
>
>
> --
> *Asitha Nanayakkara*
> Software Engineer
> WSO2, Inc. http://wso2.com/
> Mob: +94 77 853 0682
>
>


-- 
Isuru Perera
Associate Technical Lead | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
Contact: +IsuruPereraWSO2 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Configuring load balancing in app cloud with HA Proxy

[Nishadi Kirielle]

Hi all,
Please find the below blogpost as a guide to deploy a HAProxy pod in
Kubernetes cluster. [1]

Regards
Nishadi

[1].
http://nishadikirielle.blogspot.com/2016/04/configuring-haproxy-load-balancer-for.html

On Thu, Mar 17, 2016 at 12:25 PM, Nishadi Kirielle  wrote:

> Hi,
> The IP addresses have been used to generate certs only for the development
> purposes. We'll update these with proper certs when it is going for
> production.
> Thanks
>
> On Thu, Mar 17, 2016 at 12:03 PM, Udara Liyanage  wrote:
>
>>
>>
>> On Wed, Mar 16, 2016 at 10:49 AM, Nishadi Kirielle 
>> wrote:
>>
>>> Hi all,
>>> I have configured load balancing in AppCloud staging with HAProxy.
>>> In the configuration I have done few changes in the kubernetes service
>>> loadbalancer. [1]
>>>
>>> Do we create certificates for IP addresses? Though it is not invalid,
>> general approach is to create certificate for hot names.
>> If we create certificate for Ip addresses, when ip addresses change or
>> add a new node, we need to again create certificate.
>>
>> In order to run the haproxy load balancer in kubernetes and provide
>>> support for https traffic, we need to add the SSL certificate specific to
>>> the node public IP to each node. In this deployment I have manually added
>>> the certificate file inside the container. It should be added to the
>>> location specified in the replication controller definition. [2] If we are
>>> adding a ca certificate as well, we can define it in the replication
>>> controller definition as an arg as follows
>>>  - --ssl-ca-cert=/ssl/ca.crt
>>>
>>> In the current deployment, we have tested a service with a single port
>>> exposed. This is because the service identifies whether this is exposed to
>>> http or https through the service annotation which is common to all exposed
>>> ports in the service. If we are going with that approach, in order to
>>> support http traffic and https traffic, we need several services. Thus,
>>> currently I'm attempting to deploy a service with several exposed ports.
>>>
>>> In addition, another concern is how the HAProxy load balancer itself is
>>> exposed to external traffic. Currently it is done through host ports. If we
>>> use node ports for this, it will expose the particular port in all the
>>> nodes. But the use of host port will only expose the particular port in the
>>> specified node.
>>>
>>> Appreciate your feedback on the approach taken.
>>>
>>> Thanks
>>>
>>> [1].
>>> https://github.com/nishadi/contrib/commit/f169044546dc8a84a359d889bb186aef83d9c422
>>> [2].
>>> https://github.com/nishadi/contrib/blob/master/service-loadbalancer/rc.yaml#L52
>>>
>>> On Mon, Mar 14, 2016 at 10:39 AM, Nishadi Kirielle 
>>> wrote:
>>>
 Hi all,
 +1 for going with SSL pass through approach. Once the testing with
 staging is done, I will focus on this approach.

 Thanks

 On Mon, Mar 14, 2016 at 10:29 AM, Manjula Rathnayake  wrote:

> Hi Imesh,
>
> On Mon, Mar 14, 2016 at 10:20 AM, Imesh Gunaratne 
> wrote:
>
>> Hi Manjula,
>>
>> On Mon, Mar 14, 2016 at 10:06 AM, Manjula Rathnayake <
>> manju...@wso2.com> wrote:
>>
>>> Hi Imesh,
>>>
>>> On Mon, Mar 14, 2016 at 9:56 AM, Imesh Gunaratne 
>>> wrote:
>>>

 On Sun, Mar 13, 2016 at 11:36 PM, Nishadi Kirielle <
 nish...@wso2.com> wrote:

> Hi all,
> Currently I'm working on configuring HAProxy load balancing
> support for app cloud.
> In checking the session affinity functionality in kuberenetes, I
> have verified the load balancing of http traffic with HAProxy. It 
> could be
> done using kubernetes contribution repo, 'service loadbalancer' [1].
>
> In order to check the load balancing with https traffic the taken
> approach is SSL termination.In the scenario of app cloud, kubernetes
> cluster is not directly exposed and the load balancer exists within 
> the
> cluster. Thus the communication between the application servers and 
> the
> load balancer happens internally. Although SSL termination ends the 
> secure
> connection at the load balancer, due to the above mentioned reasons, 
> SSL
> termination seems to be a better solution. The reason for the use of 
> SSL
> termination over SSL pass through is because of the complexity of 
> handling
> a separate SSL certificate for each server behind the load balancer 
> in the
> case of SSL pass through.
>
> -1 for this approach, IMO this has a major security risk.

 Let me explain the problem. If we offload SSL at the service load
 balancer, all traffic beyond the load balancer will use HTTP and the

Re: [Dev] GoogleAuth library for TOTP authenticator

[Johann Nallathamby]

Hi Keerthika,

First of all you should always copy such mails to dev.

Why do you need to fork the entire code? If its the POM that you are
modifying can't we do it like a orbit bundle without forking the entire
code? I think that should be the way to do it.

Regards,
Johann.

On Thu, Apr 7, 2016 at 6:14 AM, Keerthika Mahendralingam  wrote:

> Hi All,
> For TOTP authenticator I have done some changes in GoogleAuth library pom
> file so that it can be added into the dropins folder(Otherwise it is not
> getting deployed). So I have added modified GoggleAuth library inside the
> TOTP component[1].
>
> Any concern on this?
>
> [1]. https://github.com/keerthu/identity-outbound-auth-totp
>
> Thanks,
> --
> 
> Keerthika Mahendralingam
> Associate Software Engineer
> Mobile :+94 (0) 776 121144
> keerth...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>



-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Governance Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error while implementing the Integration test for salesforce(SOAP API) connector

[Hariprasath Thanarajah]

Hi All,

I have attached the wire log here.

On Thu, Apr 7, 2016 at 3:59 PM, Hariprasath Thanarajah  wrote:

> Hi All,
>
> I am working on to create integration test for salesforce connector. When
> I create the testcase for a particular method(getUserInfo) I got the
> response via the ESB call but after that I get the following error in [1].
>
> I have added the proxy[2] and soap request[3] as well.
>
> Can anyone suggest me what could be the reason for this follwing error.
>
> [1]
> FAILED: testGetUserInfoWithMandatoryParameters
> Salesforce {getUserInfo} integration test with mandatory
> parameters.
> java.lang.NullPointerException
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.processCookieHeaders(AbstractHTTPSender.java:213)
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.obtainHTTPHeaderInformation(AbstractHTTPSender.java:170)
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:224)
> at
> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:294)
> at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendSOAPRequest(ConnectorIntegrationTestBase.java:616)
> at
> org.wso2.carbon.connector.integration.test.salesforce.SalesforceConnectorIntegrationTest.testGetUserInfoWithMandatoryParameters(SalesforceConnectorIntegrationTest.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
> at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
> at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
> at org.testng.TestRunner.privateRun(TestRunner.java:757)
> at org.testng.TestRunner.run(TestRunner.java:608)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
> at org.testng.TestNG.run(TestNG.java:999)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
> at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
>
> [2]
> http://ws.apache.org/ns/synapse;
>name="salesforce"
>transports="https http"
>startOnLoad="true"
>trace="disable">
> 
>

[Dev] Error while implementing the Integration test for salesforce(SOAP API) connector

[Hariprasath Thanarajah]

Hi All,

I am working on to create integration test for salesforce connector. When I
create the testcase for a particular method(getUserInfo) I got the response
via the ESB call but after that I get the following error in [1].

I have added the proxy[2] and soap request[3] as well.

Can anyone suggest me what could be the reason for this follwing error.

[1]
FAILED: testGetUserInfoWithMandatoryParameters
Salesforce {getUserInfo} integration test with mandatory parameters.
java.lang.NullPointerException
at
org.apache.axis2.transport.http.AbstractHTTPSender.processCookieHeaders(AbstractHTTPSender.java:213)
at
org.apache.axis2.transport.http.AbstractHTTPSender.obtainHTTPHeaderInformation(AbstractHTTPSender.java:170)
at
org.apache.axis2.transport.http.AbstractHTTPSender.processResponse(AbstractHTTPSender.java:224)
at
org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:294)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.wso2.connector.integration.test.base.ConnectorIntegrationTestBase.sendSOAPRequest(ConnectorIntegrationTestBase.java:616)
at
org.wso2.carbon.connector.integration.test.salesforce.SalesforceConnectorIntegrationTest.testGetUserInfoWithMandatoryParameters(SalesforceConnectorIntegrationTest.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:673)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:842)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1166)
at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
at org.testng.TestRunner.runWorkers(TestRunner.java:1178)
at org.testng.TestRunner.privateRun(TestRunner.java:757)
at org.testng.TestRunner.run(TestRunner.java:608)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)

[2]
http://ws.apache.org/ns/synapse;
   name="salesforce"
   transports="https http"
   startOnLoad="true"
   trace="disable">








{$ctx:loginUrl}
{$ctx:username}
{$ctx:password}










 

Re: [Dev] Datamapper - OutNode icon need to be filled inside with white color

[Susinda Perera]

Hi Sharon

Can we have the white filled one with black border arround it.

Thanks
Susinda

On Thu, Apr 7, 2016 at 2:39 PM, Sharon David  wrote:

> Hi Susinda,
>
> Please find attached Icons as requested
>
> On Thu, Apr 7, 2016 at 2:18 PM, Susinda Perera  wrote:
>
>> Hi Sharon
>>
>> $subject to solve the https://wso2.org/jira/browse/DEVTOOLESB-149. Could
>> you help on this.
>>
>> Thanks
>> Susinda
>>
>>
>> --
>> *Susinda Perera*
>> Software Engineer
>> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
>> Mobile:(+94)716049075
>> Blog: susinda.blogspot.com
>> WSO2 Inc. http://wso2.com/
>> Tel : 94 11 214 5345 Fax :94 11 2145300
>>
>>
>
>
> --
> Sharon David
> Software Engineer - UI/UX  |   WSO2 Inc
>
> +94 777 668 411  |  shar...@wso2.com  |   http://wso2.com
>



-- 
*Susinda Perera*
Software Engineer
B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
Mobile:(+94)716049075
Blog: susinda.blogspot.com
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shall we use latest APPM in EMM?

[Lakshman Udayakantha]

Hi Sajith,

Added some comments and fixes in code. can you have a look?

Thanks

On Wed, Apr 6, 2016 at 8:45 PM, Sajith Abeywardhana 
wrote:

> Hi Lakshman,
>
> I reviewed some files in PR https://github.com/wso2/carbon-appmgt/pull/250 and
> add some comments. Please have a look.
>
> Thanks,
> Sajith.
>
> On Wed, Apr 6, 2016 at 7:33 PM, Lakshman Udayakantha 
> wrote:
>
>> Hi APPM Team, EMM Team,
>>
>> I have created following pull requests [1], [2] and [3] for latest APPM
>> and EMM integration. Could you review and merge them?
>>
>> [1] https://github.com/wso2/carbon-appmgt/pull/250
>> [2] https://github.com/wso2/product-emm/pull/203
>> [3] https://github.com/wso2/carbon-device-mgt/pull/208/
>>
>> Thanks
>>
>> On Wed, Mar 23, 2016 at 6:02 PM, Lakshman Udayakantha > > wrote:
>>
>>> Hi All,
>>>
>>> After I have merged the APPM latest version and configuration changes
>>> from APPM to EMM and after the above code changes, publisher and store can
>>> be browsed and publish apps without any issue. But app installing on
>>> devices failed because the code which handles that part are moved to an
>>> APPM old branch(which is currently using in EMM) from EMM. So I
>>> cherry-picked those specific commits from that old branch to master branch
>>> in APPM. After that app installing on devices worked without any issue. But
>>> product app manager P2 profile generation failed with below error messages.
>>>
>>>  Software being installed: WSO2 Carbon - App Manager WSO2 MDM Feature
>>> 1.1.3.SNAPSHOT (org.wso2.carbon.appmgt.mdm.wso2mdm.feature.group
>>> 1.1.3.SNAPSHOT)
>>>  Missing requirement: org.wso2.carbon.appmgt.mdm.wso2mdm 1.1.3.SNAPSHOT
>>> (org.wso2.carbon.appmgt.mdm.wso2mdm 1.1.3.SNAPSHOT) requires 'package
>>> org.wso2.carbon.device.mgt.core.app.mgt 0.0.0' but it could not be found
>>>
>>> According to the error, It seems like we have to bundle carbon device
>>> features and lot of other features which depend on it with APPM product
>>> which is not actually used in APPM.
>>>
>>> According to the offline discussion with PrabathA, DinushaS, RuwanA, It
>>> was proposed to keep the code handled which handled app installing on
>>> devices in APPM as a separate independent feature, but not bundled with
>>> APPM product rather it bundled with EMM product.
>>>
>>> Thanks
>>>
>>>
>>> On Mon, Mar 21, 2016 at 4:59 PM, Dinusha Senanayaka 
>>> wrote:
>>>


 On Mon, Mar 21, 2016 at 4:42 PM, Lakshman Udayakantha <
 lakshm...@wso2.com> wrote:

> Hi Dinusha,
>
> Updated the pull with your suggestions.
>
 Thanks. Merged.

>
> Thanks
>
> On Mon, Mar 21, 2016 at 2:57 PM, Dinusha Senanayaka 
> wrote:
>
>> Hi Lakshman,
>>
>> Thanks for fixing this. Added few comments to PR. Please update.
>>
>> Regards,
>> Dinusha.
>>
>> On Mon, Mar 21, 2016 at 2:40 PM, Lakshman Udayakantha <
>> lakshm...@wso2.com> wrote:
>>
>>> Hi Dinusha,
>>>
>>> I have moved subscriber persisting code [1] to subscription creation
>>> moment from login moment. Could you review and merge it.
>>>
>>> [1] https://github.com/wso2/carbon-appmgt/pull/245/files
>>>
>>> Thanks
>>>
>>>
>>> On Fri, Mar 18, 2016 at 9:30 PM, Dinusha Senanayaka <
>>> dinu...@wso2.com> wrote:
>>>
 Hi All,

 This is something we got from the APIM code and we need to refactor
 it. In their case, users login to store can create oauth app and 
 subscribe
 to APIs. App creation also should be done by a subscriber and that's 
 why
 user is added to SUBSCRIBER table at the login. Then SUBSCRIPTION 
 table is
 populate when the actual subscription happen to API.

 Anyway, AppM do not have this app creation concept in the store.
 Hence we could move this SUBSCRIBER, SUBSCRIPTION both table inserts to
 where actual subscription happens.

 Regards,
 Dinusha.

 On Fri, Mar 18, 2016 at 8:33 PM, Lahiru Cooray 
 wrote:

> +1 for Ruwan's suggestion.
> Further in current model, Subscriptions(APM_SUBSCRIPTION) are
> mapped to a Application(APM_APPLICATION) and Application is bound to a
> subscriber (APM_SUBSCRIBER)
>
> Subscriber should ideally contain the users who are subscribed to
> an App.
> But currently APM_SUBSCRIBER table getting updated when an user
> log in to the store (which is not ideal)
> This operation should be moved to just before user get subscribed
> to an App.
>
>
> On Fri, Mar 18, 2016 at 5:12 PM, Ruwan Abeykoon 
> wrote:
>
>> Hi All,
>> I think APM_SUBSCRIBER is used to check subscription on 

Re: [Dev] product-mss hangs after deploying a (faulty) service

[Aruna Karunarathna]

Have you guys added the carbon-transport-mgt?

On Thu, Apr 7, 2016 at 1:57 PM, Hasitha Aravinda  wrote:

> Hi Manu,
>
> were you able to solve this issue, I am getting the same error.
>
> Thanks,
> Hasitha.
>
> On Wed, Feb 10, 2016 at 1:42 PM, Manuranga Perera  wrote:
>
>> MSS product hangs when I deploy my service, but fat-jar mode works.
>>
>> prints
>> Waiting on pending capability registration. Capability:
>> org.wso2.msf4j.Interceptor
>>
>> how to proceed debugging?
>> --
>> With regards,
>> *Manu*ranga Perera.
>>
>> phone : 071 7 70 20 50
>> mail : m...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
> 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
>
>


-- 

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

Re: [Dev] product-mss hangs after deploying a (faulty) service

[Himasha Guruge]

Hi Rasika,

Please find the attached  pom.xml that is in place.

Regards,
Himasha

On Thu, Apr 7, 2016 at 2:07 PM, Manuranga Perera  wrote:

> Rasika is the one who actually fixed it. I think it was some OSGi thing
> being not imported or exported properly.
> Rasika can you please mention the steps.
>
> On Thu, Apr 7, 2016 at 1:57 PM, Hasitha Aravinda  wrote:
>
>> Hi Manu,
>>
>> were you able to solve this issue, I am getting the same error.
>>
>> Thanks,
>> Hasitha.
>>
>> On Wed, Feb 10, 2016 at 1:42 PM, Manuranga Perera  wrote:
>>
>>> MSS product hangs when I deploy my service, but fat-jar mode works.
>>>
>>> prints
>>> Waiting on pending capability registration. Capability:
>>> org.wso2.msf4j.Interceptor
>>>
>>> how to proceed debugging?
>>> --
>>> With regards,
>>> *Manu*ranga Perera.
>>>
>>> phone : 071 7 70 20 50
>>> mail : m...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> --
>> Hasitha Aravinda,
>> Senior Software Engineer,
>> WSO2 Inc.
>> Email: hasi...@wso2.com
>> Mobile : +94 718 210 200
>>
>
>
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Himasha Guruge
*Software Engineer*
WS*O2* *Inc.*
Mobile: +94 777459299
himas...@wso2.com


http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;>


org.wso2.carbon.business-process
bpmn
5.0.0-SNAPSHOT
../pom.xml



4.0.0
org.wso2.carbon.bpmn.rest
bpmn rest api
bundle
WSO2 Carbon - BPMN Rest Component
http://wso2.org




org.codehaus.mojo
findbugs-maven-plugin

false










org.wso2.carbon.business-process
org.wso2.carbon.bpmn




org.wso2.orbit.org.activiti
activiti-all


org.wso2.orbit.com.fasterxml.jackson.core
jackson-core


org.wso2.orbit.com.fasterxml.jackson.core
jackson-annotations


org.wso2.orbit.com.fasterxml.jackson.core
jackson-databind


org.wso2.orbit.com.fasterxml.jackson.module
jackson-module-jaxb-annotations


joda-time
joda-time




org.wso2.msf4j
msf4j-core


org.eclipse.osgi
org.eclipse.osgi





commons-httpclient
commons-httpclient
3.1
provided


commons-logging
commons-logging
provided


org.apache.commons
commons-lang3


org.eclipse.equinox
javax.servlet




true

org.wso2.carbon.bpmn.rest.*,
version=${carbon.business-process.exp.pkg.version},


org.osgi.framework; version="[1.8.0, 2.0.0)",
org.wso2.msf4j.*;version="${carbon.msf4j.version}",
org.slf4j; version="[1.7.7, 2.0.0)",
javax.ws.rs.*,

*


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

Re: [Dev] Datamapper - OutNode icon need to be filled inside with white color

[Sharon David]

Hi Susinda,

Please find attached Icons as requested

On Thu, Apr 7, 2016 at 2:18 PM, Susinda Perera  wrote:

> Hi Sharon
>
> $subject to solve the https://wso2.org/jira/browse/DEVTOOLESB-149. Could
> you help on this.
>
> Thanks
> Susinda
>
>
> --
> *Susinda Perera*
> Software Engineer
> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
> Mobile:(+94)716049075
> Blog: susinda.blogspot.com
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>


-- 
Sharon David
Software Engineer - UI/UX  |   WSO2 Inc

+94 777 668 411  |  shar...@wso2.com  |   http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Eclipse Mars(4.5) system.setproperty javax.net.ssh.truststore not working anymore

[Jasintha Dasanayake]

I already tried out but it didn't work for me :(

Thanks
/Jasintha

On Thu, Apr 7, 2016 at 2:33 PM, Harshana Eranga Martin  wrote:

> Hi Jasintha,
>
> Import the SSL Cert from the remote server to your trust store. It should
> solve this issue.
>
>
> On Thursday, 7 April 2016, Jasintha Dasanayake  wrote:
>
>> Hi Devs
>>
>>  trying to connect to a remote server using SSL connection through an
>> eclipse plugin and making use of the following code to set the trust store
>> path :
>>
>> System.setProperty("javax.net.ssl.trustStore", path);
>>
>>
>>
>>  System.setProperty("javax.net.ssl.trustStorePassword",
>> "trustorepassword");
>>
>>
>>
>>  System.setProperty("javax.net.ssl.trustStoreType","JKS");
>>
>>
>> I am getting the following exception
>>
>>
>> *javax.net.ssl.SSLHandshakeException: 
>> sun.security.validator.ValidatorException: PKIX path building failed:
>> sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
>> valid certification path to requested target.*
>>
>>
>> Furthermore this plugin worked in eclipse Luna (4.4) without any issue ,
>> so  any thought please ?
>>
>> --
>>
>> *Jasintha Dasanayake*
>>
>> *Senior Software EngineerWSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware*
>>
>>
>> *mobile :- 0711368118 <0711368118>*
>>
>
>
> --
> Sent from Gmail Mobile for IPhone
>



-- 

*Jasintha Dasanayake*

*Senior Software EngineerWSO2 Inc. | http://wso2.com lean
. enterprise . middleware*


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

Re: [Dev] Eclipse Mars(4.5) system.setproperty javax.net.ssh.truststore not working anymore

[Harshana Eranga Martin]

Hi Jasintha,

Import the SSL Cert from the remote server to your trust store. It should
solve this issue.

On Thursday, 7 April 2016, Jasintha Dasanayake  wrote:

> Hi Devs
>
>  trying to connect to a remote server using SSL connection through an
> eclipse plugin and making use of the following code to set the trust store
> path :
>
> System.setProperty("javax.net.ssl.trustStore", path);
>
>
>
>  System.setProperty("javax.net.ssl.trustStorePassword",
> "trustorepassword");
>
>
>
>  System.setProperty("javax.net.ssl.trustStoreType","JKS");
>
>
> I am getting the following exception
>
>
> *javax.net.ssl.SSLHandshakeException: 
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
> valid certification path to requested target.*
>
>
> Furthermore this plugin worked in eclipse Luna (4.4) without any issue ,
> so  any thought please ?
>
> --
>
> *Jasintha Dasanayake*
>
> *Senior Software EngineerWSO2 Inc. | http://wso2.com
> lean . enterprise . middleware*
>
>
> *mobile :- 0711368118*
>


-- 
Sent from Gmail Mobile for IPhone
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Why we maintain different kind of device identifiers in device management core

[Milan Perera]

Hi Lakshman,

+1 for removing deviceIdentifier and type Strings, and add device
identifier object [1] instead.

[1]
https://github.com/wso2/carbon-device-mgt/blob/master/components/device-mgt/org.wso2.carbon.device.mgt.common/src/main/java/org/wso2/carbon/device/mgt/common/DeviceIdentifier.java

Regards,

On Thu, Apr 7, 2016 at 1:05 PM, Lakshman Udayakantha 
wrote:

> Hi,
>
> We have DeviceIdentifier[1] object and deviceIdentifier String field[2] in
> Device class. IMO we should stick to one Identifier. WDYT?
>
> [1]
> https://github.com/wso2/carbon-device-mgt/blob/master/components/device-mgt/org.wso2.carbon.device.mgt.common/src/main/java/org/wso2/carbon/device/mgt/common/DeviceIdentifier.java
> [2]
> https://github.com/wso2/carbon-device-mgt/blob/master/components/device-mgt/org.wso2.carbon.device.mgt.common/src/main/java/org/wso2/carbon/device/mgt/common/Device.java
>
>
> Thanks
> --
> Lakshman Udayakantha
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
> Mobile: *0714388124*
>
>


-- 
*Milan Perera *| Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 77 309 7088 | Work: +94 11 214 5345
Email: mi...@wso2.com  | Web: www.wso2.com

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

[Dev] Datamapper - OutNode icon need to be filled inside with white color

[Susinda Perera]

Hi Sharon

$subject to solve the https://wso2.org/jira/browse/DEVTOOLESB-149. Could
you help on this.

Thanks
Susinda


-- 
*Susinda Perera*
Software Engineer
B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
Mobile:(+94)716049075
Blog: susinda.blogspot.com
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] product-mss hangs after deploying a (faulty) service

[Manuranga Perera]

Rasika is the one who actually fixed it. I think it was some OSGi thing
being not imported or exported properly.
Rasika can you please mention the steps.

On Thu, Apr 7, 2016 at 1:57 PM, Hasitha Aravinda  wrote:

> Hi Manu,
>
> were you able to solve this issue, I am getting the same error.
>
> Thanks,
> Hasitha.
>
> On Wed, Feb 10, 2016 at 1:42 PM, Manuranga Perera  wrote:
>
>> MSS product hangs when I deploy my service, but fat-jar mode works.
>>
>> prints
>> Waiting on pending capability registration. Capability:
>> org.wso2.msf4j.Interceptor
>>
>> how to proceed debugging?
>> --
>> With regards,
>> *Manu*ranga Perera.
>>
>> phone : 071 7 70 20 50
>> mail : m...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
> Hasitha Aravinda,
> Senior Software Engineer,
> WSO2 Inc.
> Email: hasi...@wso2.com
> Mobile : +94 718 210 200
>



-- 
With regards,
*Manu*ranga Perera.

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

Re: [Dev] product-mss hangs after deploying a (faulty) service

[Hasitha Aravinda]

Hi Manu,

were you able to solve this issue, I am getting the same error.

Thanks,
Hasitha.

On Wed, Feb 10, 2016 at 1:42 PM, Manuranga Perera  wrote:

> MSS product hangs when I deploy my service, but fat-jar mode works.
>
> prints
> Waiting on pending capability registration. Capability:
> org.wso2.msf4j.Interceptor
>
> how to proceed debugging?
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--
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

[Dev] Why we maintain different kind of device identifiers in device management core

[Lakshman Udayakantha]

Hi,

We have DeviceIdentifier[1] object and deviceIdentifier String field[2] in
Device class. IMO we should stick to one Identifier. WDYT?

[1]
https://github.com/wso2/carbon-device-mgt/blob/master/components/device-mgt/org.wso2.carbon.device.mgt.common/src/main/java/org/wso2/carbon/device/mgt/common/DeviceIdentifier.java
[2]
https://github.com/wso2/carbon-device-mgt/blob/master/components/device-mgt/org.wso2.carbon.device.mgt.common/src/main/java/org/wso2/carbon/device/mgt/common/Device.java


Thanks
-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0714388124*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APPM] Mobile application binary file upload REST API

[Thilini Shanika]

Hi Sajith,

Here .../apps/application/... part seems redundant. I like to propose  "
http://localhost:9763/api/appm/publisher/v1.0/apps/binaries;.

+1

On Thu, Apr 7, 2016 at 12:57 PM, SajithAR Ariyarathna 
wrote:

> Hi Ruwan,
>
> Images can be quite big right.. > 1MB (if we haven't prescribed a limit
>> e.g. < 400kb) wouldn't thilini's approach be better?
>
> That is actually a valid point. So +1 for an image upload API.
>
> 2. Implementing a dedicated API for image upload only. In this case, we
>> can implement this API in order to be reused in webapp image upload also.
>>
> +1
>
> Thanks.
>
> On Thu, Apr 7, 2016 at 12:34 PM, Ruwan Yatawara  wrote:
>
>> Hi Sajith,
>>
>> Images can be quite big right.. > 1MB (if we haven't prescribed a limit
>> e.g. < 400kb) wouldn't thilini's approach be better?
>>
>> Thanks and Regards,
>>
>> Ruwan Yatawara
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> email : ruw...@wso2.com
>> mobile : +94 77 9110413
>> blog : http://ruwansrants.blogspot.com/
>> www: :http://wso2.com
>>
>>
>> On Thu, Apr 7, 2016 at 12:23 PM, SajithAR Ariyarathna 
>> wrote:
>>
>>> Hi Thilini,
>>>
>>> ... in order to create a mobile app,  we have to initially upload
 relevant application binary and image files of app thumbnail, banner and
 screenshots ...

>>> What is the reason behind this? As I remember in the current AppM, both
>>> text data (app name, version , description etc.) and images (banner,
>>> screenshots) are submitted via a single POST request when creating a new
>>> app. Why we are separating image upload?
>>>
>>> Our suggestion here is to rename the API as
 http://localhost:9763/api/appm/publisher/v1.0/apps/application/
 binaries and
 making the API more generic.
>>>
>>> Here .../apps/application/... part seems redundant. I like to propose  "
>>> http://localhost:9763/api/appm/publisher/v1.0/apps/binaries;.
>>>
>>> Thanks.
>>>
>>> On Thu, Apr 7, 2016 at 11:44 AM, Thilini Shanika 
>>> wrote:
>>>
 Hi all,

 We have a concern regarding the design of mobile application
 binary/image upload API. As per the discussions we had on the new design of
 the API model, we decided to use a separate API to upload mobile binary
 files(.apk, .ipa) including the images. Thus, in order to create a mobile
 app,  we have to initially upload relevant application binary and image
 files of app thumbnail, banner and screenshots and later the application
 should be created with the references to uploaded binaries.
 We have already implemented the REST API for application binary upload.
 But we have few concerns regarding the image file upload. We have two
 options in implementing image upload scenario.


1. Reusing the binary upload API for image upload also. But in this
case, we need to change the API design in order to distinguish the
uploading file type (Whether is it is an app binary or an image for
screenshots, thumbnails etc) since we have separate flows of processing 
 the
files.
2. Implementing a dedicated API for image upload only. In this
case, we can implement this API in order to be reused in webapp image
upload also.


 As per the offline discussion I had with RuwanA, another concern was
 raised regarding the URL for binary upload API. The current URL is '
 http://localhost:9763/api/appm/publisher/v1.0/apps/mobile/
 binaries'. But
 this particular URL is mobile application specific. In that case, we cannot
 reuse this API in future, for any other application binary upload, other
 that mobile binary upload. Our suggestion here is to rename the API as
 http://localhost:9763/api/appm/publisher/v1.0/apps/application/
 binaries and
 making the API more generic.

 Your suggestions are highly appreciated.

 [1] -
 https://docs.google.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit


 Thanks,
 Thilini

 --
 Thilini Shanika
 Software Engineer
 WSO2, Inc.; http://wso2.com
 20, Palmgrove Avenue, Colombo 3

 E-mail: tgtshan...@gmail.com


>>>
>>>
>>> --
>>> Sajith Janaprasad Ariyarathna
>>> Software Engineer; WSO2, Inc.;  http://wso2.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Software Engineer; WSO2, Inc.;  http://wso2.com/
>



-- 
Thilini Shanika
Software Engineer
WSO2, Inc.; http://wso2.com
20, Palmgrove Avenue, Colombo 3

E-mail: tgtshan...@gmail.com
___
Dev mailing list
Dev@wso2.org

Re: [Dev] [APPM] Mobile application binary file upload REST API

[SajithAR Ariyarathna]

Hi Ruwan,

Images can be quite big right.. > 1MB (if we haven't prescribed a limit
> e.g. < 400kb) wouldn't thilini's approach be better?

That is actually a valid point. So +1 for an image upload API.

2. Implementing a dedicated API for image upload only. In this case, we can
> implement this API in order to be reused in webapp image upload also.
>
+1

Thanks.

On Thu, Apr 7, 2016 at 12:34 PM, Ruwan Yatawara  wrote:

> Hi Sajith,
>
> Images can be quite big right.. > 1MB (if we haven't prescribed a limit
> e.g. < 400kb) wouldn't thilini's approach be better?
>
> Thanks and Regards,
>
> Ruwan Yatawara
>
> Senior Software Engineer,
> WSO2 Inc.
>
> email : ruw...@wso2.com
> mobile : +94 77 9110413
> blog : http://ruwansrants.blogspot.com/
> www: :http://wso2.com
>
>
> On Thu, Apr 7, 2016 at 12:23 PM, SajithAR Ariyarathna 
> wrote:
>
>> Hi Thilini,
>>
>> ... in order to create a mobile app,  we have to initially upload
>>> relevant application binary and image files of app thumbnail, banner and
>>> screenshots ...
>>>
>> What is the reason behind this? As I remember in the current AppM, both
>> text data (app name, version , description etc.) and images (banner,
>> screenshots) are submitted via a single POST request when creating a new
>> app. Why we are separating image upload?
>>
>> Our suggestion here is to rename the API as
>>> http://localhost:9763/api/appm/publisher/v1.0/apps/application/
>>> binaries and
>>> making the API more generic.
>>
>> Here .../apps/application/... part seems redundant. I like to propose  "
>> http://localhost:9763/api/appm/publisher/v1.0/apps/binaries;.
>>
>> Thanks.
>>
>> On Thu, Apr 7, 2016 at 11:44 AM, Thilini Shanika 
>> wrote:
>>
>>> Hi all,
>>>
>>> We have a concern regarding the design of mobile application
>>> binary/image upload API. As per the discussions we had on the new design of
>>> the API model, we decided to use a separate API to upload mobile binary
>>> files(.apk, .ipa) including the images. Thus, in order to create a mobile
>>> app,  we have to initially upload relevant application binary and image
>>> files of app thumbnail, banner and screenshots and later the application
>>> should be created with the references to uploaded binaries.
>>> We have already implemented the REST API for application binary upload.
>>> But we have few concerns regarding the image file upload. We have two
>>> options in implementing image upload scenario.
>>>
>>>
>>>1. Reusing the binary upload API for image upload also. But in this
>>>case, we need to change the API design in order to distinguish the
>>>uploading file type (Whether is it is an app binary or an image for
>>>screenshots, thumbnails etc) since we have separate flows of processing 
>>> the
>>>files.
>>>2. Implementing a dedicated API for image upload only. In this case,
>>>we can implement this API in order to be reused in webapp image upload
>>>also.
>>>
>>>
>>> As per the offline discussion I had with RuwanA, another concern was
>>> raised regarding the URL for binary upload API. The current URL is '
>>> http://localhost:9763/api/appm/publisher/v1.0/apps/mobile/
>>> binaries'. But
>>> this particular URL is mobile application specific. In that case, we cannot
>>> reuse this API in future, for any other application binary upload, other
>>> that mobile binary upload. Our suggestion here is to rename the API as
>>> http://localhost:9763/api/appm/publisher/v1.0/apps/application/
>>> binaries and
>>> making the API more generic.
>>>
>>> Your suggestions are highly appreciated.
>>>
>>> [1] -
>>> https://docs.google.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit
>>>
>>>
>>> Thanks,
>>> Thilini
>>>
>>> --
>>> Thilini Shanika
>>> Software Engineer
>>> WSO2, Inc.; http://wso2.com
>>> 20, Palmgrove Avenue, Colombo 3
>>>
>>> E-mail: tgtshan...@gmail.com
>>>
>>>
>>
>>
>> --
>> Sajith Janaprasad Ariyarathna
>> Software Engineer; WSO2, Inc.;  http://wso2.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Sajith Janaprasad Ariyarathna
Software Engineer; WSO2, Inc.;  http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [EMM][AppM] Why APPM platform specific implementations are in mdm-admin JAX-RS?

[Kasun Dananjaya Delgolla]

Hi All,

While restructuring mdm-admin jax-rs to be in the core layer, I found out
that several platform specific implementations are residing in mdm-admin
jax-rs. All such implementations are related to AppM functionality
(ex: MDMAndroidOperationUtil and MDMIOSOperationUtil classes).

We know that AppM is invoking mdm-admin REST APIs to get its functionality
done, but ideally mdm-admin should have only generic functionalities. If we
want to enable these features via mdm-admin, we should make it generic
without having any platform specific code within mdm-admin IMO.

Correct way of implementing this would be, having these platform specific
REST APIs in respective platform JAX-RS services and AppM should invoke
those APIs according to the device platform.

Is there any specific reason why we implemented it like that?

Thanks

-- 
Kasun Dananjaya Delgolla

Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
Tel:  +94 11 214 5345
Fax: +94 11 2145300
Mob: + 94 771 771 015
Blog: http://kddcodingparadise.blogspot.com
Linkedin: *http://lk.linkedin.com/in/kasundananjaya
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APPM][UX] Responsive left menu with submenus

[Jerad Rutnam]

Hi Jenananthan,

Yes, Its ok to use it. But we have not finalized the markup etc ... yet.
But we can update you about the changes once it's finalized.

Regards,
Jerad


On Wed, Apr 6, 2016 at 10:56 AM, Jenananthan Yogendran  wrote:

> Hi UX Team,
>
> In APP Manager we need to have sub menu(my subscription) under left column
> menus(asset types).
> With current markup [1] this is not supported.In the markup of API
> Manager[2]  sub menu support is available. Is this markup  completed ? Can
> we use the same markup for left menus ?
>
> 1. https://github.com/wso2-dev-ux/product-appm
> 2. https://github.com/wso2-dev-ux/product-apim
>
> Thanks
> --
> Jenananthan Yogendran
> *Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Jerad Rutnam*
*Software Engineer*

WSO2 Inc.
lean | enterprise | middleware
M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APPM] Mobile application binary file upload REST API

[Ruwan Yatawara]

Hi Sajith,

Images can be quite big right.. > 1MB (if we haven't prescribed a limit
e.g. < 400kb) wouldn't thilini's approach be better?

Thanks and Regards,

Ruwan Yatawara

Senior Software Engineer,
WSO2 Inc.

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


On Thu, Apr 7, 2016 at 12:23 PM, SajithAR Ariyarathna 
wrote:

> Hi Thilini,
>
> ... in order to create a mobile app,  we have to initially upload relevant
>> application binary and image files of app thumbnail, banner and screenshots
>> ...
>>
> What is the reason behind this? As I remember in the current AppM, both
> text data (app name, version , description etc.) and images (banner,
> screenshots) are submitted via a single POST request when creating a new
> app. Why we are separating image upload?
>
> Our suggestion here is to rename the API as
>> http://localhost:9763/api/appm/publisher/v1.0/apps/application/
>> binaries and
>> making the API more generic.
>
> Here .../apps/application/... part seems redundant. I like to propose  "
> http://localhost:9763/api/appm/publisher/v1.0/apps/binaries;.
>
> Thanks.
>
> On Thu, Apr 7, 2016 at 11:44 AM, Thilini Shanika 
> wrote:
>
>> Hi all,
>>
>> We have a concern regarding the design of mobile application binary/image
>> upload API. As per the discussions we had on the new design of the API
>> model, we decided to use a separate API to upload mobile binary files(.apk,
>> .ipa) including the images. Thus, in order to create a mobile app,  we have
>> to initially upload relevant application binary and image files of app
>> thumbnail, banner and screenshots and later the application should be
>> created with the references to uploaded binaries.
>> We have already implemented the REST API for application binary upload.
>> But we have few concerns regarding the image file upload. We have two
>> options in implementing image upload scenario.
>>
>>
>>1. Reusing the binary upload API for image upload also. But in this
>>case, we need to change the API design in order to distinguish the
>>uploading file type (Whether is it is an app binary or an image for
>>screenshots, thumbnails etc) since we have separate flows of processing 
>> the
>>files.
>>2. Implementing a dedicated API for image upload only. In this case,
>>we can implement this API in order to be reused in webapp image upload
>>also.
>>
>>
>> As per the offline discussion I had with RuwanA, another concern was
>> raised regarding the URL for binary upload API. The current URL is '
>> http://localhost:9763/api/appm/publisher/v1.0/apps/mobile/
>> binaries'. But
>> this particular URL is mobile application specific. In that case, we cannot
>> reuse this API in future, for any other application binary upload, other
>> that mobile binary upload. Our suggestion here is to rename the API as
>> http://localhost:9763/api/appm/publisher/v1.0/apps/application/
>> binaries and
>> making the API more generic.
>>
>> Your suggestions are highly appreciated.
>>
>> [1] -
>> https://docs.google.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit
>>
>>
>> Thanks,
>> Thilini
>>
>> --
>> Thilini Shanika
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>> 20, Palmgrove Avenue, Colombo 3
>>
>> E-mail: tgtshan...@gmail.com
>>
>>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Software Engineer; WSO2, Inc.;  http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APPM] Mobile application binary file upload REST API

[SajithAR Ariyarathna]

Hi Thilini,

... in order to create a mobile app,  we have to initially upload relevant
> application binary and image files of app thumbnail, banner and screenshots
> ...
>
What is the reason behind this? As I remember in the current AppM, both
text data (app name, version , description etc.) and images (banner,
screenshots) are submitted via a single POST request when creating a new
app. Why we are separating image upload?

Our suggestion here is to rename the API as
> http://localhost:9763/api/appm/publisher/v1.0/apps/application/
> binaries and making
> the API more generic.

Here .../apps/application/... part seems redundant. I like to propose  "
http://localhost:9763/api/appm/publisher/v1.0/apps/binaries;.

Thanks.

On Thu, Apr 7, 2016 at 11:44 AM, Thilini Shanika  wrote:

> Hi all,
>
> We have a concern regarding the design of mobile application binary/image
> upload API. As per the discussions we had on the new design of the API
> model, we decided to use a separate API to upload mobile binary files(.apk,
> .ipa) including the images. Thus, in order to create a mobile app,  we have
> to initially upload relevant application binary and image files of app
> thumbnail, banner and screenshots and later the application should be
> created with the references to uploaded binaries.
> We have already implemented the REST API for application binary upload.
> But we have few concerns regarding the image file upload. We have two
> options in implementing image upload scenario.
>
>
>1. Reusing the binary upload API for image upload also. But in this
>case, we need to change the API design in order to distinguish the
>uploading file type (Whether is it is an app binary or an image for
>screenshots, thumbnails etc) since we have separate flows of processing the
>files.
>2. Implementing a dedicated API for image upload only. In this case,
>we can implement this API in order to be reused in webapp image upload
>also.
>
>
> As per the offline discussion I had with RuwanA, another concern was
> raised regarding the URL for binary upload API. The current URL is '
> http://localhost:9763/api/appm/publisher/v1.0/apps/mobile/
> binaries'. But this
> particular URL is mobile application specific. In that case, we cannot
> reuse this API in future, for any other application binary upload, other
> that mobile binary upload. Our suggestion here is to rename the API as
> http://localhost:9763/api/appm/publisher/v1.0/apps/application/
> binaries and making
> the API more generic.
>
> Your suggestions are highly appreciated.
>
> [1] -
> https://docs.google.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit
>
>
> Thanks,
> Thilini
>
> --
> Thilini Shanika
> Software Engineer
> WSO2, Inc.; http://wso2.com
> 20, Palmgrove Avenue, Colombo 3
>
> E-mail: tgtshan...@gmail.com
>
>


-- 
Sajith Janaprasad Ariyarathna
Software Engineer; WSO2, Inc.;  http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] WSO2 Enterprise Store 2.1.0 Alpha 1 Released!

[Elilmatha Sivanesan]

Hi ES Team ,

The issue reported in jira[1] is blocker to us to the migration of  WSO2
Store. Can we get this fixed in beta.

[1] https://wso2.org/jira/browse/STORE-1216

Thanks.

On Tue, Apr 5, 2016 at 3:05 PM, Sameera Medagammaddegedara <
samee...@wso2.com> wrote:

>
> Hi Everyone,
>
> This is the alpha-1 of the WSO2 Enterprise Store version 2.1.0, which will
> create a marketplace for your enterprise assets. You can download the alpha
> at [1]. The alpha-1 specifically contains the following features, tasks,
> improvements and bug fixes.
>
> New Feature
>
>- [STORE-1229 ] - CLONE -
>Store search text box should maintain a list of last five searches 
> performed
>
> Task
>
>- [STORE-1199 ] - remove All
>Rights Reserved string from footer
>
> Improvement
>
>- [STORE-1008 ] - Http Status
>code displayed for Trying to update asset fields that are readonly via REST
>API is 202. Expecting to see an Error Status Code
>- [STORE-1122 ] - Add Cancel
>buttons in appropriate places
>- [STORE-1131 ] - Adding
>category and tag based filtering
>- [STORE-1139 ] - [G-REG]
>Store landing page does not show any of the added assets when not logged in
>- [STORE-1148 ] - Publisher
>REST API regex validation for fields
>- [STORE-1154 ] - Redirect
>user to login page after successful registration
>- [STORE-1157 ] - Make store
>search box display what asset type is searched
>- [STORE-1200 ] - All the
>URLs should be clickable
>- [STORE-1201 ] - User must
>be made aware of check list item auto save
>- [STORE-1202 ] - Need to
>change the size of the History label and a separator in the lifecycle view
>- [STORE-1207 ] - Remove
>Duplicate Lifecycle details in Lifecycle view
>
> Bug
>
>- [STORE-998 ] - Assets can be
>created without having values for Required Fields from REST API
>- [STORE-1013 ] - Assets
>cannot be created when Special Characters are added to Asset "Name"
>- [STORE-1033 ] - Provide tag
>cloud support for ES
>- [STORE-1041 ] - It loads
>only single row of assets at a time
>- [STORE-1048 ] - [STORE]
>When scrolling it shows the loading asset info multiple times on top
>- [STORE-1051 ] - [SERVER] On
>Asset delete successful message there is delete button
>- [STORE-1053 ] - When
>creating assets, it allow to upload non image formats as images .
>- [STORE-1054 ] - [Publisher]
>Can't say No to delete rest service
>- [STORE-1068 ] - [STORE]
>Re-Login failed for store within the same session window
>- [STORE-1071 ] - When adding
>a asset for teneant ,Backend print an error log
>- [STORE-1082 ] - Tenant
>Store - Clicking Signout from asset detail page throws http 500 error page
>- [STORE-1089 ] - Username as
>email - User with Publisher Role can publish assets without reviewer
>reviewing them
>- [STORE-1105 ] - Values
>filled in URL field of a newly added RXT does not show at the Governance
>publisher
>- [STORE-1106 ] - Custom drop
>down is not populating in Greg Publisher
>- [STORE- ] - [publisher]
>Remove artifact name from Add button
>- [STORE-1115 ] - UI don't
>let you delete asset if you enable more then one
>meta.lifecycle.deletableStates
>- [STORE-1120 ] - Publisher
>create asset page should load default value from RXT definition
>- [STORE-1125 ] - Multiple
>lifecycle UI breaks when you click the select option in publisher in G-Reg
>- [STORE-1127 ] - Sanitize
>get parameters in store/publisher and sso apps
>- [STORE-1136 

Re: [Dev] [CDMF][IOTs] Merging UI changes

[Kasun Dananjaya Delgolla]

Hi All,

I have merged and committed styling changes (CSS) + device detailed view
core level UIs. Currently, the only remaining bit is plugin level UI
changes (ex: android device detailed view etc).

Thanks

On Thu, Mar 10, 2016 at 9:09 PM, Kasun Dananjaya Delgolla 
wrote:

> Hi All,
>
> I have merged and committed policy listing, policy priority views and all
> the units under
> carbon-devicemgt-plugin/device-mgt-mdm/org.wso2.carbon.device.mgt.mobile.ui.
> Now the remaining units are device listing + view and policy wizard.
>
> Thank you
>
> On Wed, Mar 9, 2016 at 12:26 PM, Charitha Goonetilleke  > wrote:
>
>> Hi Kasun,
>>
>> Actually we can have operations bar for device listing view. I removed
>> that earlier for IoTS since we didn't had such operation bar to display for
>> IoT devices. But as far as we are listing both EMM and IoT devices, and
>> also have dynamic operations related to IoT devices, we can use same
>> operation-bar unit which we are using in device details page. However we
>> might need to have specific logic to select relevant operation bar for
>> specific device type as we are doing in device details page.
>>
>> On Tue, Mar 8, 2016 at 10:58 PM, Kasun Dananjaya Delgolla <
>> kas...@wso2.com> wrote:
>>
>>> HI All,
>>>
>>> $subject is in progress from EMM 2.0.1 branch to IOTs IoTS-1.0.0-M4
>>> branch. Reason is, IOTs jaggery app UI is still in the state where EMM was
>>> in its alpha. We need to carefully merge the changes to all the jaggery
>>> units + modules and pages to get all the latest bug fixes and feature
>>> additions of EMM.
>>>
>>> Currently, I was able to merge and test all the units related to user
>>> and role management, therefore committed them to the IoTS-1.0.0-M4 branch
>>> of CDMF core. I faced some issues while merging device view + listing views
>>> because of newly added pagination and operation module changes. Will
>>> carefully test all possible use cases and fix the issues encountered.
>>>
>>> I found out that operation bar has been removed from the device listing
>>> view of IOTs (operation bar which appears on select of a platform via
>>> search filter). Is there any specific reason for that?
>>>
>>> Thanks
>>>
>>> --
>>> Kasun Dananjaya Delgolla
>>>
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>> Tel:  +94 11 214 5345
>>> Fax: +94 11 2145300
>>> Mob: + 94 771 771 015
>>> Blog: http://kddcodingparadise.blogspot.com
>>> Linkedin: *http://lk.linkedin.com/in/kasundananjaya
>>> *
>>>
>>
>>
>>
>> --
>> *Charitha Goonetilleke*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 77 751 3669 <%2B94777513669>
>> Twitter:@CharithaWs , fb: charithag
>> , linkedin: charithag
>> 
>>
>
>
>
> --
> Kasun Dananjaya Delgolla
>
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
> Tel:  +94 11 214 5345
> Fax: +94 11 2145300
> Mob: + 94 771 771 015
> Blog: http://kddcodingparadise.blogspot.com
> Linkedin: *http://lk.linkedin.com/in/kasundananjaya
> *
>



-- 
Kasun Dananjaya Delgolla

Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
Tel:  +94 11 214 5345
Fax: +94 11 2145300
Mob: + 94 771 771 015
Blog: http://kddcodingparadise.blogspot.com
Linkedin: *http://lk.linkedin.com/in/kasundananjaya
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APPM] Mobile application binary file upload REST API

[Thilini Shanika]

Hi all,

We have a concern regarding the design of mobile application binary/image
upload API. As per the discussions we had on the new design of the API
model, we decided to use a separate API to upload mobile binary files(.apk,
.ipa) including the images. Thus, in order to create a mobile app,  we have
to initially upload relevant application binary and image files of app
thumbnail, banner and screenshots and later the application should be
created with the references to uploaded binaries.
We have already implemented the REST API for application binary upload. But
we have few concerns regarding the image file upload. We have two options
in implementing image upload scenario.


   1. Reusing the binary upload API for image upload also. But in this
   case, we need to change the API design in order to distinguish the
   uploading file type (Whether is it is an app binary or an image for
   screenshots, thumbnails etc) since we have separate flows of processing the
   files.
   2. Implementing a dedicated API for image upload only. In this case, we
   can implement this API in order to be reused in webapp image upload also.


As per the offline discussion I had with RuwanA, another concern was raised
regarding the URL for binary upload API. The current URL is '
http://localhost:9763/api/appm/publisher/v1.0/apps/mobile/
binaries'. But this
particular URL is mobile application specific. In that case, we cannot
reuse this API in future, for any other application binary upload, other
that mobile binary upload. Our suggestion here is to rename the API as
http://localhost:9763/api/appm/publisher/v1.0/apps/application/
binaries and making
the API more generic.

Your suggestions are highly appreciated.

[1] -
https://docs.google.com/document/d/1UE7SgZGsGnOgo6CokXClc6LVtI3N0tcGeXClFOT7jIA/edit


Thanks,
Thilini

-- 
Thilini Shanika
Software Engineer
WSO2, Inc.; http://wso2.com
20, Palmgrove Avenue, Colombo 3

E-mail: tgtshan...@gmail.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev