[Dev] [Build] Compilation fails with CNF

[Dumidu Handakumbura]

Hi Devs,

DSS 3.5.0(master) build fails for with[1]. I have close to an empty .m2
repo on my machine. How can I get this built?

[1] - [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
project org.wso2.dataservices.styles: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.18:test failed: Unable to
load the mojo 'test' in the plugin
'org.apache.maven.plugins:maven-surefire-plugin:2.18'. A required class is
missing: org/apache/maven/plugin/surefire/SurefireReportParameters

[WARNING] Error injecting: org.apache.maven.plugin.surefire.SurefirePlugin
java.lang.TypeNotPresentException: Type
org.apache.maven.plugin.surefire.SurefirePlugin not present
at
org.eclipse.sisu.space.URLClassSpace.loadClass(URLClassSpace.java:115)
at org.eclipse.sisu.space.NamedClass.load(NamedClass.java:46)
at
org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
at
com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86)
at
com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:55)
at
com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70)

...
...
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
at
org.eclipse.sisu.space.URLClassSpace.loadClass(URLClassSpace.java:107)
... 41 more
Caused by: java.lang.ClassNotFoundException:
org.apache.maven.plugin.surefire.SurefireReportParameters
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
... 56 more
...
...

Thank,

-- 
*Dumidu Handakumbura*
Software Engineer - QA
WSO2 Inc; http://www.wso2.com/.
Mobile;
*+9406740 *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Running WSO2 Products on Cloud Foundry

[Nanduni Nimalsiri]

*@Lakmal*
Thank you for the information. I will try using that.

*@Chamila*
Thank you for the details.
It seems that the choice of buildpacks or containers depends on the
application developer, operator, environment, requirements etc. If we
really want to get something really fast, Cloud Foundry recommends to build
a docker container and push it, so that we can use that container for local
testing as well. But the drawback that lies here is that the developers
have to know about Docker and other operations. (eg: how to write a
Dockerfile). They say that if the developer needs to set up the environment
instead of the operator, this approach would be perfect.

Cloud Foundry suggests that buildpacks are suitable if we don't want to use
Ubuntu, Red Hat, Fedora, CentOS or different java versions that need to be
patched differently or else if we don't want to use different custom things
etc. Hence the developer can focus more on application logic and business
logic rather than running Dockerfiles. Any way, the buildpack approach also
ends up in a container(droplet) eventually.

I suppose that low maintenance cost can be achieved with buildpacks because
this approach does not end up with very heterogenic container cluster where
every container is really different, then we have to come up with different
ways when we need to patch something. But with buildpacks, we can patch up
one buildpack so that we can deploy all applications and go ahead. I
suppose this might be a reason for mentioning it as low maintenance cost. I
have no deep thought on this.

In case of port based health checks which I have mentioned, if the Docker
images we are pushing don't declare ports to expose, or the processes they
run don't listen for TCP connections on the ports they expose, then they
will fail the default 'port' health check when pushed as a CF app. If we
turn that port-based health-check off by changing it to 'none', though, the
image may run successfully.

Hope this had been useful.

Best regards,
Nanduni.


*Nanduni Nimalsiri*
Software Engineering Intern, WSO2 Inc. (http://wso2.com)
email : nand...@wso2.com
blog : http://nanduni.blogspot.com/
mobile : +94714114256


On Tue, Feb 16, 2016 at 7:20 AM, Lakmal Warusawithana 
wrote:

> PS: Still private docker registry UI not configured. Currently this only
> work in docker client, using docker registry APIs. Which is docker
> login/push/pull
>
> On Tue, Feb 16, 2016 at 7:16 AM, Lakmal Warusawithana 
> wrote:
>
>> Awesome! great progress Nanduni.
>>
>> If you want to test with private docker registry, I have setup internal
>> private docker registry [1], you can use it for push/pull docker images. It
>> required authentication ( your WSO2 credentials - username : email,
>> Password: email password ). You need to do docker login first to pull/push
>> docker images. (please note currently this is only work inside the WSO2
>> network)
>>
>> Lets try CF locally.
>>
>>
>> [1] https://dockerhub.private.wso2.com
>>
>>
>> On Mon, Feb 15, 2016 at 11:25 PM, Nanduni Nimalsiri 
>> wrote:
>>
>>> Hi,
>>>
>>> I was able to deploy Docker images in Cloud Foundry with Diego. Here I
>>> am going to clear several facts regarding that.
>>>
>>> There are several approaches of integrating Docker with Cloud Foundry.
>>> If I summarize them, they are are follows. Each of them possesses different
>>> limitations.
>>>
>>>
>>> *Integrating Docker with Cloud Foundry*
>>>
>>> *1. Docker Buildpack - *Provides framework and runtime support for the
>>> applications. When we push an application, Cloud Foundry automatically
>>> detects which buildpack is required and installs it on the Droplet
>>> Execution Agent (DEA) where the application needs to run.
>>>
>>> *2. Docker Service Provider - * A service provider to expose Docker
>>> containers as services.
>>>
>>> *3. Cloud Rocker *- A project carried out by a company called 'Cloud
>>> Credo' which builds docker images using Cloud Foundry buildpacks. If you
>>> don't want to use Cloud Foundry but you want to use its buildpack system,
>>> this is the best choice.
>>>
>>> *4. Diego - *Rewrite of DEA. In a Cloud Foundry deployment without
>>> Diego, the Cloud Controller schedules and manages applications on the DEA
>>> nodes. Diego replaces the DEAs and the Health Manager, and assumes
>>> application scheduling and management responsibility from the Cloud
>>> Controller. Diego is special because it provides built-in-support for
>>> Docker containers.
>>>
>>> *5. Lattice - *Lattice is a standalone scheduler extracted from Diego
>>> for Docker images. If Cloud Foundry is too much, Lattice might be a
>>> suitable project. Lattice tries to be little simpler and easier to set up
>>> with less features around it. The nice thing about this Lattice system is
>>> that it is super light weight.
>>>
>>> Out of the aforementioned approaches, I used 4th option - Diego in Cloud
>>> Foundry. As mentiond above, Diego builds out the 

[Dev] [Calling Admin Services- DAS] Issue in deploying an Event Receiver to DAS via Admin Services

[Samitha Chathuranga]

Hi,

I am trying to deploy an event receiver in DAS, via calling Admin Services,
but getting an *IllegalArgumentException*. By the way I succeeded in
creating an Event Stream in DAS by "EventStreamAdminService" Admin Service,
and I followed the same basic procedure to call DAS's
"EventReceiverAdminService", in order to deploy an Event Receiver.

I set EventReceiverName, StreamNameWithVersion, EventAdapterType (to
"wso2event") and a BasicInputAdapterPropertyDto property
"events.duplicated.in.cluster" as key and "false" as its value for the
DeployTextEventReceiverConfiguration. Does anybody has an idea on the issue?
Am I missing something here?

Stack trace is mentioned below.

Thanks & Regards,
Samitha

TID: [-1234] [] [2016-02-16 11:43:11,125]  INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
'admin@carbon.super [-1234]' logged in at [2016-02-16 11:43:11,124+0530]
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
TID: [-1234] [] [2016-02-16 11:43:11,215] ERROR
{org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
{org.apache.axis2.rpc.receivers.RPCMessageReceiver}
java.lang.IllegalArgumentException
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.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
at
org.wso2.carbon.event.receiver.core.internal.tenantmgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:48)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
at

Re: [Dev] Integrating WSO2 IS with Kubernetes

[Nishadi Kirielle]

Hi,

As of now, it seems LDAP integration of Kuberenetes with IS has two basic
approaches.

First approach is to directly integrate LDAP with Kubernetes. It requires
the authentication and authorization process to go through a LDAP
connector. Although Kismatic has a LDAP/AD integration, it does not seem to
be a complete implementation. [1]

Alternatively, we can do user provisioning through a client. The client can
retrieve users from LDAP server and create contexts per user in K8s. A
context includes a namespace that is specific to a user group, a user and
the cluster that the user needs to access. Users can be given access to the
context with tokens / username password credentials or through authorizing
certificates. This configuration can be done via kube config file. [2] But
this approach replicates user data in K8s.

Suggestions are highly appreciated.

[1]. https://github.com/kismatic/kubernetes-ldap
[2]. http://kubernetes.io/v1.1/docs/user-guide/kubeconfig-file.html

On Tue, Feb 9, 2016 at 11:40 AM, Nishadi Kirielle  wrote:

> @Imesh : This configuration has to be done in kube api server. It provides
> options to set the authorization mode in 'always allow', 'always deny' or
> 'ABAC' modes. In using ABAC mode, it provides an option 
> --authorization-policy-file
>   to set the user configured authorization policy. [1]
>
> kube-apiserver --authorization-mode=""
> kube-apiserver --authorization-policy-file=""
>
> @Chamila:
> +1 for OpenLDAP.
>
> [1].
> https://github.com/kubernetes/kubernetes/blob/master/pkg/auth/authorizer/abac/example_policy_file.jsonl
>
>
> On Tue, Feb 9, 2016 at 7:00 AM, Chamila De Alwis 
> wrote:
>
>> Hi Nishadi,
>>
>>
>> On Mon, Feb 8, 2016 at 11:11 PM, Nishadi Kirielle 
>> wrote:
>>
>>> My initial plan is to connect a LDAP implementation like OpenDS or
>>> ApacheDS with Kubernetes.
>>>
>>
>> Is OpenLDAP[1] not an option? It has a long track record and is the case
>> when most user scenarios are considered.
>>
>>
>> [1] - http://www.openldap.org/
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>
>
> --
> *Nishadi Kirielle*
> *Software Engineering Intern*
> Mobile : +94 (0) 714722148
> Blog : http://nishadikirielle.blogspot.com/
> nish...@wso2.com
>



-- 
*Nishadi Kirielle*
*Software Engineering Intern*
Mobile : +94 (0) 714722148
Blog : http://nishadikirielle.blogspot.com/
nish...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Microservices Framework for Java (WSO2 MSF4J) 1.0.0 Released!

[Samiyuru Senarathne]

WSO2 Microservices Framework for Java (WSO2 MSF4J) 1.0.0 Released!

We are pleased to announce the release of WSO2 Microservices Framework for
Java (WSO2 MSF4J) 1.0.0. The distribution, source and tag location for this
release is available here
.

WSO2 MSF4J provides a lightweight, high performance microservices runtime
in addition to a very simple programming model for developing Java based
microservices.

This release of WSO2 MSF4J includes the following key features. For further
details please see the documentation
 and WSO2 MSF4J product page
.

Key Features

   -

   Annotation based definition of microservices
   -

   High performance Netty based transport
   -

   WSO2 Developer Studio based tooling for microservices development
   starting from a Swagger API definition
   -

   HTTP request and response streaming
   -

   Custom interceptors
   -

   Support for metrics and visualization of metrics using WSO2 Data
   Analytics Server (WSO2 DAS) dashboards
   -

   Support for securing microservices
   -

   Integration with Mustache rendering engine
   -

   Comprehensive samples demonstrating how to develop microservices based
   solutions


How you can contribute

You can find instructions on how to contribute at our documentation
 site.

If you have any suggestions or are interested in WSO2 MSF4J 1.0.0
discussions, please join the dev@wso2.org or architect...@wso2.org mailing
lists.

Reporting Issues

We encourage you to report issues and documentation errors regarding WSO2
MSF4J 1.0.0 through the public issue tracking system
.

Thanks,
WSO2 MSF4J Team

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

Re: [Dev] Including Data Mapper Mediator in ESB 5.0 Release

[Jasintha Dasanayake]

IMO , Both data mapper editor and the engine are a cross platform
components which can be used /ship with other product as well , Only the
ESB graphical mediator and synapse mediators should be added into exiting
ESB product and ESB tool repos ,

Also I feel that it requires more frequent release in data mapper editor to
make it rock-solid also more new feature should be introduced to improve
the user experience ,therefore this editor should be able to release on its
own.

WDYT ?

Thanks and Regards
/Jasintha


On Tue, Feb 16, 2016 at 10:11 AM, Chanaka Fernando 
wrote:

> Hi Nuwan,
>
> +1 for keeping the Data mapper engine in a separate repo. That will make
> it easy to maintain and reuse by other components if there is a requirement
> in the future.
>
>
> On Tue, Feb 16, 2016 at 10:06 AM, Susinda Perera  wrote:
>
>>
>>
>> On Tue, Feb 16, 2016 at 10:01 AM, Nuwan Pallewela 
>> wrote:
>>
>>>
>>> Hi All,
>>>
>>> Data Mapper feature is planned to release with ESB 5.0 and initially it
>>> was done by team developer studio as a POC.
>>>
>>> There are three components in data mapper implementation. They are
>>>
>>>1. Data Mapper Tool
>>>2. Data Mapper Mediator
>>>3. Data Mapper Engine
>>>
>>> Data Mapper Tool should be with the Developer Studio ESB Tooling.
>>>
>> This can also be place outside as this is a separate plugin. But ESB
>> plugin has a dependency to datamapper plugin.
>>
>>> Data Mapper Mediator should be move to Carbon Mediation.
>>>
>>> Ideally we should maintain a separate repository for the Data Mapper
>>> Engine. So where we should keep the Data Mapper Engine and how to proceed?
>>>
>> +1 for place this in a separate place,  At the moment  'Data Mapper
>> Engine' is needed by datamapper-mediator, but datamapper-tool will also use
>> the engine (if we are giving some dry-run/emulator feature)
>>
>> Susinda
>>
>>> Thanks,
>>>
>>> Nuwan
>>> --
>>> --
>>>
>>> *Nuwan Chamara Pallewela*
>>>
>>>
>>> *Software Engineer*
>>>
>>> *WSO2, Inc. *http://wso2.com
>>> *lean . enterprise . middleware*
>>>
>>> Email   *nuw...@wso2.com *
>>> Mobile  *+94719079739 <%2B94719079739>@*
>>>
>>>
>>>
>>
>>
>> --
>> *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
>>
>>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>


-- 

*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] [G-Reg] Visibility of policy artifacts

[Rajith Roshan]

Hi Pubudu,

Currently the getting started sample does not set anonymous view permission
to the policies. You can give the anonymous view permission to the asset
using management console. Select one of the policies and inside the detail
view of the policy , expand the Permission Tab, and add "
system/wso2.anonymous.role" role with read permission to that asset. Then
that asset will be visible at the store when user is not logged in.

Thanks!
Rajith

On Tue, Feb 16, 2016 at 10:50 AM, Pubudu Priyashan  wrote:

>
> Hello G-Reg team,
>
> I have a question regarding how to set up the visibility of a certain
> artifact type in Store section for logged in and logged out users. The
> reason I'm asking is, if you run "Getting Started" sample and the access
> the store while being logged out, there are no policy artifacts displayed.
> If you do the same while being logged in, you can see there are policy
> artifacts available. I would like to know from where we can set up this
> visibility for different artifact types. Thanks.
>
>
> Cheers,
> Pubudu D.P
> Senior Software Engineer - QA Team | WSO2 inc.
> Mobile : +94775464547
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: +94-72-642-8350 <%2B94-71-554-8430>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM][Analytics] Calculatiing percentile in Spark

[Sachini Jayasekara]

Hi Suho,

What the duration are we looking at ? If its like an hour then we can use
> CEP.
>
Initial plan was to do the calculations daily.

> Can you look at whether we can implement percentile in CEP in a scalable
> manner ?
>
  Will look into this and update the thread.

Thanks,
Sachini

> Suho
>
> On Mon, Feb 15, 2016 at 4:39 PM, Sachini Jayasekara 
> wrote:
>
>> Hi all,
>>
>> I am working on following two alert generation scenarios,
>>
>> 1. Abnormal response time/ backend time - If an API response time or the
>> backend time lies outside the Xth percentile.
>>
>> 2. Abnormal request counts - Count the number of requests during last
>> minute and check if it lies outside the Xth percentile.
>>
>> Initially, we thought of having a summarization job to calculate the
>> percentile values daily. However, in DAS, spark doesn't have OOB support to
>> calculate percentile even though hive has that as a built-in aggregate
>> function.
>>
>> With DAS 3.0.1 we can define UDFs (User Defined Functions), but the
>> function 'percentile'  is a user-defined aggregation function (UDAF).
>> Hence, we cannot use that approach as well.
>>
>> Is there an alternative way in DAS to define custom aggregation function?
>>
>>
>> Thanks,
>> Sachini
>>
>> --
>>
>>
>>
>> *Thanks & Regards,Sachini JayasekaraSoftware Engineer; **WSO2 Inc. *
>>
>> *lean . enterprise . middleware |  http://wso2.com  *
>>
>> Mobile : +94712371165
>>
>
>
>
> --
>
> *S. Suhothayan*
> Technical Lead & Team Lead of WSO2 Complex Event Processor
> *WSO2 Inc. *http://wso2.com
> * *
> lean . enterprise . middleware
>
>
> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
> http://suhothayan.blogspot.com/ twitter:
> http://twitter.com/suhothayan  | linked-in:
> http://lk.linkedin.com/in/suhothayan *
>



-- 



*Thanks & Regards,Sachini JayasekaraSoftware Engineer; **WSO2 Inc. *

*lean . enterprise . middleware |  http://wso2.com  *

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

[Dev] [G-Reg] Visibility of policy artifacts

[Pubudu Priyashan]

Hello G-Reg team,

I have a question regarding how to set up the visibility of a certain
artifact type in Store section for logged in and logged out users. The
reason I'm asking is, if you run "Getting Started" sample and the access
the store while being logged out, there are no policy artifacts displayed.
If you do the same while being logged in, you can see there are policy
artifacts available. I would like to know from where we can set up this
visibility for different artifact types. Thanks.


Cheers,
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Fixes of ESB and DSS in the product plugins to be released

[Sohani Weerasinghe]

Hi Jasintha,

We have issued patches for Dev Studio 380,  patch0007, patch0009 and
patch0012 for ESB and patch0008, patch0010 and patch0011 for DSS separately.

As we haven't released the product plugins yet, shall we have two separate
Git repositories for ESB tooling and DSS tooling ( for ESB this has been
suggested already at [1] ) including these fixes. i.e not giving these
fixes as updates but include these fixes in the release.

AFAIU including these fixes would be better and then each product team can
continue the proposed patching model as discussed in [2] for the future
fixes


[1] Git Repository for ESB Tooling in wso2
[2] Proposed patching model for Developer Studio 4.0.0

Thanks,
Sohani
Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com

Mobile  : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter  : https://twitter.com/sohanichristine
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][UI/UX] Data Table Extended Prompt An Alert When Filtering Data

[Jerad Rutnam]

Hi Kamidu,

This is the method which is given by the DataTable examples [1]. And yes if
it's published back-end API call, it will be not a best practice. So yes
you can overwrite it and customize to match your requirement.

[1] - https://datatables.net/examples/api/multi_filter_select.html

Regards,
Jerad


On Tue, Feb 16, 2016 at 10:23 AM, Kamidu Punchihewa 
wrote:

> Hi Jerad,
>
> Since we are using the data table extended library and its filtering
> option where backend ajax option is enabled.We don't have the access to
> perform the suggestion you have provided.
> Which is "if this is causing any issue for back-end processing. We should
> handle it from the back-end or* before we make the back-end cal*l".
>
> Handling the css selectors which is appended from one particular UI
> library from a published backend API is not the best practise to follow.
> Sending css selectors to a backend api via the library is not the
> advisable either.
>
> We should  address this and enable the backend filtering without the "^",
> "$" or any css and frontend related characters/selectors from the  data
> table extended library.
>
> Thanks and Regards.
>
> Kamidu Sachith Punchihewa
> *Software Engineer*
> WSO2, Inc.
> lean . enterprise . middleware
> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
> On Tue, Feb 16, 2016 at 8:22 AM, Jerad Rutnam  wrote:
>
>> Hi Kamidu,
>>
>> This is to fix *exact *match filtering in front-end level. "^" for
>> starts and "$" for ends with, for more details check html selectors [1].
>>
>> e.g. This will fix the issue where it shows "in*active*" queries when we
>> filter for "*active*".
>>
>> And if this is causing any issue for back-end processing. We should
>> handle it from the back-end or before we make the back-end call.
>>
>> [1] - http://www.w3schools.com/cssref/css_selectors.asp
>>
>> Cheers!
>> Jerad
>>
>>
>> On Mon, Feb 15, 2016 at 9:05 PM, Kamidu Punchihewa 
>> wrote:
>>
>>> Hi UI/UX Team,
>>>
>>> I have faced $subject when fitting data using the ajax method.
>>> An "IllegalArgumentException" was thoun in the back end, and a datatable
>>> error alert was prompt from the front end when a filtering was triggered.
>>>
>>> There was a mismatch in the expected uri format and the current uri
>>> format given by the data table extended library.When comparing expected
>>> backend call [1] with current backend call [2] there were two extra
>>> characters included to the current uri.
>>>
>>> This causes due to the latest change which is listed below.
>>>
>>> Older version :
>>>
>>> column

 .search(val ? val : '', true, false)

 .draw();


>>> New version :
>>>
>>> column
 .search(val ? '^' + val + '$' : '', true, false)
 .draw();
>>>
>>>
>>>
>>> Any reason for this latest change ?
>>>
>>> [1].  'endpoint?draw=2=0=16*=data'*
>>> [2].  'endpoint?draw=2=0=16*=^data$'*
>>>
>>> Thanks and Regards.
>>> Kamidu Sachith Punchihewa
>>> *Software Engineer*
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>>
>>>
>>> Disclaimer: This communication may contain privileged or other
>>> confidential information and is intended exclusively for the addressee/s.
>>> If you are not the intended recipient/s, or believe that you may have
>>> received this communication in error, please reply to the sender indicating
>>> that fact and delete the copy you received and in addition, you should not
>>> print, copy, retransmit, disseminate, or otherwise use the information
>>> contained in this communication. Internet communications cannot be
>>> guaranteed to be timely, secure, error or virus-free. The sender does not
>>> accept liability for any errors or omissions.
>>>
>>> ___
>>> 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
>>
>
>


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

Re: [Dev] [DEV][UI/UX] Data Table Extended Prompt An Alert When Filtering Data

[Kamidu Punchihewa]

Hi Jerad,

Since we are using the data table extended library and its filtering option
where backend ajax option is enabled.We don't have the access to perform
the suggestion you have provided.
Which is "if this is causing any issue for back-end processing. We should
handle it from the back-end or* before we make the back-end cal*l".

Handling the css selectors which is appended from one particular UI library
from a published backend API is not the best practise to follow.
Sending css selectors to a backend api via the library is not the advisable
either.

We should  address this and enable the backend filtering without the "^",
"$" or any css and frontend related characters/selectors from the  data
table extended library.

Thanks and Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.

On Tue, Feb 16, 2016 at 8:22 AM, Jerad Rutnam  wrote:

> Hi Kamidu,
>
> This is to fix *exact *match filtering in front-end level. "^" for starts
> and "$" for ends with, for more details check html selectors [1].
>
> e.g. This will fix the issue where it shows "in*active*" queries when we
> filter for "*active*".
>
> And if this is causing any issue for back-end processing. We should handle
> it from the back-end or before we make the back-end call.
>
> [1] - http://www.w3schools.com/cssref/css_selectors.asp
>
> Cheers!
> Jerad
>
>
> On Mon, Feb 15, 2016 at 9:05 PM, Kamidu Punchihewa 
> wrote:
>
>> Hi UI/UX Team,
>>
>> I have faced $subject when fitting data using the ajax method.
>> An "IllegalArgumentException" was thoun in the back end, and a datatable
>> error alert was prompt from the front end when a filtering was triggered.
>>
>> There was a mismatch in the expected uri format and the current uri
>> format given by the data table extended library.When comparing expected
>> backend call [1] with current backend call [2] there were two extra
>> characters included to the current uri.
>>
>> This causes due to the latest change which is listed below.
>>
>> Older version :
>>
>> column
>>>
>>> .search(val ? val : '', true, false)
>>>
>>> .draw();
>>>
>>>
>> New version :
>>
>> column
>>> .search(val ? '^' + val + '$' : '', true, false)
>>> .draw();
>>
>>
>>
>> Any reason for this latest change ?
>>
>> [1].  'endpoint?draw=2=0=16*=data'*
>> [2].  'endpoint?draw=2=0=16*=^data$'*
>>
>> Thanks and Regards.
>> Kamidu Sachith Punchihewa
>> *Software Engineer*
>> WSO2, Inc.
>> lean . enterprise . middleware
>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, retransmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>> ___
>> 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] Including Data Mapper Mediator in ESB 5.0 Release

[Chanaka Fernando]

Hi Nuwan,

+1 for keeping the Data mapper engine in a separate repo. That will make it
easy to maintain and reuse by other components if there is a requirement in
the future.


On Tue, Feb 16, 2016 at 10:06 AM, Susinda Perera  wrote:

>
>
> On Tue, Feb 16, 2016 at 10:01 AM, Nuwan Pallewela  wrote:
>
>>
>> Hi All,
>>
>> Data Mapper feature is planned to release with ESB 5.0 and initially it
>> was done by team developer studio as a POC.
>>
>> There are three components in data mapper implementation. They are
>>
>>1. Data Mapper Tool
>>2. Data Mapper Mediator
>>3. Data Mapper Engine
>>
>> Data Mapper Tool should be with the Developer Studio ESB Tooling.
>>
> This can also be place outside as this is a separate plugin. But ESB
> plugin has a dependency to datamapper plugin.
>
>> Data Mapper Mediator should be move to Carbon Mediation.
>>
>> Ideally we should maintain a separate repository for the Data Mapper
>> Engine. So where we should keep the Data Mapper Engine and how to proceed?
>>
> +1 for place this in a separate place,  At the moment  'Data Mapper
> Engine' is needed by datamapper-mediator, but datamapper-tool will also use
> the engine (if we are giving some dry-run/emulator feature)
>
> Susinda
>
>> Thanks,
>>
>> Nuwan
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>@*
>>
>>
>>
>
>
> --
> *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
>
>


-- 
Thank you and Best Regards,
Chanaka Fernando
Senior Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Including Data Mapper Mediator in ESB 5.0 Release

[Susinda Perera]

On Tue, Feb 16, 2016 at 10:01 AM, Nuwan Pallewela  wrote:

>
> Hi All,
>
> Data Mapper feature is planned to release with ESB 5.0 and initially it
> was done by team developer studio as a POC.
>
> There are three components in data mapper implementation. They are
>
>1. Data Mapper Tool
>2. Data Mapper Mediator
>3. Data Mapper Engine
>
> Data Mapper Tool should be with the Developer Studio ESB Tooling.
>
This can also be place outside as this is a separate plugin. But ESB plugin
has a dependency to datamapper plugin.

> Data Mapper Mediator should be move to Carbon Mediation.
>
> Ideally we should maintain a separate repository for the Data Mapper
> Engine. So where we should keep the Data Mapper Engine and how to proceed?
>
+1 for place this in a separate place,  At the moment  'Data Mapper Engine'
is needed by datamapper-mediator, but datamapper-tool will also use the
engine (if we are giving some dry-run/emulator feature)

Susinda

> Thanks,
>
> Nuwan
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>


-- 
*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] SMS OTP Authenticator

[Elilmatha Sivanesan]

Hi Darshana,

Thanks for your suggestion , I'l consider them for the improvement.

Thanks.


On Mon, Feb 15, 2016 at 7:11 PM, Malaka Silva  wrote:

> +Elilmatha
>
> On Mon, Feb 15, 2016 at 6:56 PM, Darshana Gunawardana 
> wrote:
>
>> Hi Devs,
>>
>> Tried $subject and its really cool, easy to set up and get working. Kudos
>> to everyone to get that out...!!
>>
>> I have checked the source and there are couple of things we can improve
>>
>>1. Avoid using instance variables in the authentication to store any
>>data since the authentication is a single. There are different context
>>objects have different scopes, pick the correct context to store relevant
>>data.
>>2. Having smsprovider.properties file to configure any additional
>>data is correct. But if there is a need of such property file should be in
>>the /repository/resources/ folder
>>3. It should have configurable the SMS text from the UI, rather from
>>the property file.
>>4. We could comeup with a provisioning connector which do the number
>>registering automatically, so it won't need to do manual update from
>>external sms provider.
>>
>> Hope these suggestions improve the usability and functionality of the
>> authenticator much more.
>>
>> Thanks,
>>
>> --
>> Regards,
>>
>>
>> *Darshana Gunawardana*Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>>
>> *E-mail: darsh...@wso2.com *
>> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>>
>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> 
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
*S.Elilmatha*
Associate  Software Engineer,

WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

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

[Dev] Including Data Mapper Mediator in ESB 5.0 Release

[Nuwan Pallewela]

Hi All,

Data Mapper feature is planned to release with ESB 5.0 and initially it was
done by team developer studio as a POC.

There are three components in data mapper implementation. They are

   1. Data Mapper Tool
   2. Data Mapper Mediator
   3. Data Mapper Engine

Data Mapper Tool should be with the Developer Studio ESB Tooling.

Data Mapper Mediator should be move to Carbon Mediation.

Ideally we should maintain a separate repository for the Data Mapper
Engine. So where we should keep the Data Mapper Engine and how to proceed?

Thanks,

Nuwan
-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

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

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

Re: [Dev] [Architecture] WSO2 ESB 5.0.0 - Milestone 2 Released!

[Susinda Perera]

On Tue, Feb 16, 2016 at 8:13 AM, Dushan Abeyruwan  wrote:

> Hi
>  Have seen mediation debugging feature in docs (others audience: please
> note, doc are still at a draft stage so not visible to public)  anyway, is
> there correspondent DevS version available?
>
Yes we are inline with releasing DevStudio with debugger feature.

Thanks
Susinda

>
>
> On Mon, Feb 15, 2016 at 4:09 AM, Vijitha Ekanayake 
> wrote:
>
>> *WSO2 ESB 5.0.0-Milestone 2 Released*
>>
>> ESB Team is pleased to announce the WSO2 ESB 5.0.0 - Milestone 2 Release.
>> It contains following improvement and bug fixes.
>>
>> Bug
>>
>>- [ESBJAVA-4416 ] - ESB
>>Management console shows Invalid product version.
>>- [ESBJAVA-4417 ] - ESB
>>server terminal shows Invalid product version.
>>
>> Improvement
>>
>>- [ESBJAVA-4415 ] - SSL
>>support for MQTT inbound.
>>
>>
>>
>> The distribution is available to download at [1].
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/scratch/ESB/packs/5.0.0-Releases/5.0.0-M2/
>>
>> - WSO2 ESB Team -
>>
>> --
>> Vijitha Ekanayake
>> Software Engineer*, *WSO2, Inc.; http://wso2.com/
>> Mobile : +94 777 24 73 39 | +94 718 74 44 08
>> lean.enterprise.middleware
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Dushan Abeyruwan | Technical Lead
>
> PMC Member Apache Synpase
> WSO2 Inc. http://wso2.com/
> Blog:*http://www.dushantech.com/ *
> Mobile:(001)408-791-9312
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*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] [DEV][UI/UX] Data Table Extended Prompt An Alert When Filtering Data

[Jerad Rutnam]

Hi Kamidu,

This is to fix *exact *match filtering in front-end level. "^" for starts
and "$" for ends with, for more details check html selectors [1].

e.g. This will fix the issue where it shows "in*active*" queries when we
filter for "*active*".

And if this is causing any issue for back-end processing. We should handle
it from the back-end or before we make the back-end call.

[1] - http://www.w3schools.com/cssref/css_selectors.asp

Cheers!
Jerad


On Mon, Feb 15, 2016 at 9:05 PM, Kamidu Punchihewa 
wrote:

> Hi UI/UX Team,
>
> I have faced $subject when fitting data using the ajax method.
> An "IllegalArgumentException" was thoun in the back end, and a datatable
> error alert was prompt from the front end when a filtering was triggered.
>
> There was a mismatch in the expected uri format and the current uri format
> given by the data table extended library.When comparing expected backend
> call [1] with current backend call [2] there were two extra characters
> included to the current uri.
>
> This causes due to the latest change which is listed below.
>
> Older version :
>
> column
>>
>> .search(val ? val : '', true, false)
>>
>> .draw();
>>
>>
> New version :
>
> column
>> .search(val ? '^' + val + '$' : '', true, false)
>> .draw();
>
>
>
> Any reason for this latest change ?
>
> [1].  'endpoint?draw=2=0=16*=data'*
> [2].  'endpoint?draw=2=0=16*=^data$'*
>
> Thanks and Regards.
> Kamidu Sachith Punchihewa
> *Software Engineer*
> WSO2, Inc.
> lean . enterprise . middleware
> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
> ___
> 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] [Architecture] WSO2 ESB 5.0.0 - Milestone 2 Released!

[Dushan Abeyruwan]

Hi
 Have seen mediation debugging feature in docs (others audience: please
note, doc are still at a draft stage so not visible to public)  anyway, is
there correspondent DevS version available?


On Mon, Feb 15, 2016 at 4:09 AM, Vijitha Ekanayake 
wrote:

> *WSO2 ESB 5.0.0-Milestone 2 Released*
>
> ESB Team is pleased to announce the WSO2 ESB 5.0.0 - Milestone 2 Release.
> It contains following improvement and bug fixes.
>
> Bug
>
>- [ESBJAVA-4416 ] - ESB
>Management console shows Invalid product version.
>- [ESBJAVA-4417 ] - ESB
>server terminal shows Invalid product version.
>
> Improvement
>
>- [ESBJAVA-4415 ] - SSL
>support for MQTT inbound.
>
>
>
> The distribution is available to download at [1].
>
> [1]
> https://svn.wso2.org/repos/wso2/scratch/ESB/packs/5.0.0-Releases/5.0.0-M2/
>
> - WSO2 ESB Team -
>
> --
> Vijitha Ekanayake
> Software Engineer*, *WSO2, Inc.; http://wso2.com/
> Mobile : +94 777 24 73 39 | +94 718 74 44 08
> lean.enterprise.middleware
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Dushan Abeyruwan | Technical Lead

PMC Member Apache Synpase
WSO2 Inc. http://wso2.com/
Blog:*http://www.dushantech.com/ *
Mobile:(001)408-791-9312
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Running WSO2 Products on Cloud Foundry

[Lakmal Warusawithana]

PS: Still private docker registry UI not configured. Currently this only
work in docker client, using docker registry APIs. Which is docker
login/push/pull

On Tue, Feb 16, 2016 at 7:16 AM, Lakmal Warusawithana 
wrote:

> Awesome! great progress Nanduni.
>
> If you want to test with private docker registry, I have setup internal
> private docker registry [1], you can use it for push/pull docker images. It
> required authentication ( your WSO2 credentials - username : email,
> Password: email password ). You need to do docker login first to pull/push
> docker images. (please note currently this is only work inside the WSO2
> network)
>
> Lets try CF locally.
>
>
> [1] https://dockerhub.private.wso2.com
>
>
> On Mon, Feb 15, 2016 at 11:25 PM, Nanduni Nimalsiri 
> wrote:
>
>> Hi,
>>
>> I was able to deploy Docker images in Cloud Foundry with Diego. Here I am
>> going to clear several facts regarding that.
>>
>> There are several approaches of integrating Docker with Cloud Foundry. If
>> I summarize them, they are are follows. Each of them possesses different
>> limitations.
>>
>>
>> *Integrating Docker with Cloud Foundry*
>>
>> *1. Docker Buildpack - *Provides framework and runtime support for the
>> applications. When we push an application, Cloud Foundry automatically
>> detects which buildpack is required and installs it on the Droplet
>> Execution Agent (DEA) where the application needs to run.
>>
>> *2. Docker Service Provider - * A service provider to expose Docker
>> containers as services.
>>
>> *3. Cloud Rocker *- A project carried out by a company called 'Cloud
>> Credo' which builds docker images using Cloud Foundry buildpacks. If you
>> don't want to use Cloud Foundry but you want to use its buildpack system,
>> this is the best choice.
>>
>> *4. Diego - *Rewrite of DEA. In a Cloud Foundry deployment without
>> Diego, the Cloud Controller schedules and manages applications on the DEA
>> nodes. Diego replaces the DEAs and the Health Manager, and assumes
>> application scheduling and management responsibility from the Cloud
>> Controller. Diego is special because it provides built-in-support for
>> Docker containers.
>>
>> *5. Lattice - *Lattice is a standalone scheduler extracted from Diego
>> for Docker images. If Cloud Foundry is too much, Lattice might be a
>> suitable project. Lattice tries to be little simpler and easier to set up
>> with less features around it. The nice thing about this Lattice system is
>> that it is super light weight.
>>
>> Out of the aforementioned approaches, I used 4th option - Diego in Cloud
>> Foundry. As mentiond above, Diego builds out the new runtime architecture
>> for Cloud Foundry, replacing the DEAs and Health Manager. In fact, *Cloud
>> Foundry now encourages the use of Diego.*
>>
>> *Using Diego with Cloud Foundry*
>>
>> First I tried to use Diego with PWS (Pivotal Web Services). Then it gave
>> me errors in enabling Diego feature due to conflicts in administrator
>> privileges. In that case, I have been running the 60 days trial version of
>> Pivotal.io and that's why I had no administrator control because PWS is a
>> shared platform.
>>
>> So the next option was to run Diego locally in my machine so that I can
>> then get admin control and do whatever I want with the system. So I used* 
>> Cloud
>> Foundry Diego [BOSH release] *in [1] for that. With several
>> modifications, I managed to deploy Docker containers eventually. Here are
>> the steps I followed.
>>
>> 1. Uploaded the latest version of the Warden BOSH-Lite stemcell directly
>> to BOSH-Lite
>> 2. Used two releases to generate two manifests basically. They are
>> cf-relaese and diego-release.
>> 3. Generated CF manifest and Diego manifest.
>> 4. Created, uploaded, and deployed the CF release.
>> 5. Uploaded the latest garden-linux-release.
>> 6. Uploaded the latest etcd-release.
>> 7. Created, uploaded, and deployed the Diego release
>> 8. Logged in to CF and enabled Docker support.
>> 9. Deployed cloudfoundry/lattice-app docker image.
>> 10. Scaled the number of instances and so on...
>>
>> [1] https://github.com/cloudfoundry-incubator/diego-release
>>
>>
>> *Containers vs Buildpacks*
>>
>> If I move to the Docker buildpacks, I could not find any buildpack
>> compatible for deploying Docker images yet. I am trying on it, but the
>> problem seems that they require some external Docker host which I have no
>> idea on how to set up.
>>
>> Meanwhile, I found several pros and cons with these two approaches:
>> Buildpack mechanism and Container mechanism. I have summarized them as
>> below.
>>
>> *Containers are better when*,
>> - Developers require more control
>> - Developers know Operations/Docker
>> - Time to market is important
>>
>> *Buildpacks are better when*,
>> - Operations require more control
>> - Developers focus on application
>>   

Re: [Dev] Running WSO2 Products on Cloud Foundry

[Lakmal Warusawithana]

Awesome! great progress Nanduni.

If you want to test with private docker registry, I have setup internal
private docker registry [1], you can use it for push/pull docker images. It
required authentication ( your WSO2 credentials - username : email,
Password: email password ). You need to do docker login first to pull/push
docker images. (please note currently this is only work inside the WSO2
network)

Lets try CF locally.


[1] https://dockerhub.private.wso2.com

On Mon, Feb 15, 2016 at 11:25 PM, Nanduni Nimalsiri 
wrote:

> Hi,
>
> I was able to deploy Docker images in Cloud Foundry with Diego. Here I am
> going to clear several facts regarding that.
>
> There are several approaches of integrating Docker with Cloud Foundry. If
> I summarize them, they are are follows. Each of them possesses different
> limitations.
>
>
> *Integrating Docker with Cloud Foundry*
>
> *1. Docker Buildpack - *Provides framework and runtime support for the
> applications. When we push an application, Cloud Foundry automatically
> detects which buildpack is required and installs it on the Droplet
> Execution Agent (DEA) where the application needs to run.
>
> *2. Docker Service Provider - * A service provider to expose Docker
> containers as services.
>
> *3. Cloud Rocker *- A project carried out by a company called 'Cloud
> Credo' which builds docker images using Cloud Foundry buildpacks. If you
> don't want to use Cloud Foundry but you want to use its buildpack system,
> this is the best choice.
>
> *4. Diego - *Rewrite of DEA. In a Cloud Foundry deployment without Diego,
> the Cloud Controller schedules and manages applications on the DEA nodes.
> Diego replaces the DEAs and the Health Manager, and assumes application
> scheduling and management responsibility from the Cloud Controller. Diego
> is special because it provides built-in-support for Docker containers.
>
> *5. Lattice - *Lattice is a standalone scheduler extracted from Diego for
> Docker images. If Cloud Foundry is too much, Lattice might be a suitable
> project. Lattice tries to be little simpler and easier to set up with less
> features around it. The nice thing about this Lattice system is that it is
> super light weight.
>
> Out of the aforementioned approaches, I used 4th option - Diego in Cloud
> Foundry. As mentiond above, Diego builds out the new runtime architecture
> for Cloud Foundry, replacing the DEAs and Health Manager. In fact, *Cloud
> Foundry now encourages the use of Diego.*
>
> *Using Diego with Cloud Foundry*
>
> First I tried to use Diego with PWS (Pivotal Web Services). Then it gave
> me errors in enabling Diego feature due to conflicts in administrator
> privileges. In that case, I have been running the 60 days trial version of
> Pivotal.io and that's why I had no administrator control because PWS is a
> shared platform.
>
> So the next option was to run Diego locally in my machine so that I can
> then get admin control and do whatever I want with the system. So I used* 
> Cloud
> Foundry Diego [BOSH release] *in [1] for that. With several
> modifications, I managed to deploy Docker containers eventually. Here are
> the steps I followed.
>
> 1. Uploaded the latest version of the Warden BOSH-Lite stemcell directly
> to BOSH-Lite
> 2. Used two releases to generate two manifests basically. They are
> cf-relaese and diego-release.
> 3. Generated CF manifest and Diego manifest.
> 4. Created, uploaded, and deployed the CF release.
> 5. Uploaded the latest garden-linux-release.
> 6. Uploaded the latest etcd-release.
> 7. Created, uploaded, and deployed the Diego release
> 8. Logged in to CF and enabled Docker support.
> 9. Deployed cloudfoundry/lattice-app docker image.
> 10. Scaled the number of instances and so on...
>
> [1] https://github.com/cloudfoundry-incubator/diego-release
>
>
> *Containers vs Buildpacks*
>
> If I move to the Docker buildpacks, I could not find any buildpack
> compatible for deploying Docker images yet. I am trying on it, but the
> problem seems that they require some external Docker host which I have no
> idea on how to set up.
>
> Meanwhile, I found several pros and cons with these two approaches:
> Buildpack mechanism and Container mechanism. I have summarized them as
> below.
>
> *Containers are better when*,
> - Developers require more control
> - Developers know Operations/Docker
> - Time to market is important
>
> *Buildpacks are better when*,
> - Operations require more control
> - Developers focus on application
> - Low maintenance cost is important
>
> Since we already have Docker images for WSO2 products (k8s artifacts) , I
> suggest that we can use Diego for deploying WSO2 products in Cloud Foundry.
> But the problem seems that they are private images and still I have no idea
> on how we should proceed with docker images that are not available in
> 

Re: [Dev] Running WSO2 Products on Cloud Foundry

[Chamila De Alwis]

Hi Nanduni,

I suppose the need for an external Docker host is for the build-pack to
build the Docker images somehow, although it would be better to mention the
source of this information. Can you elaborate more why build-packs give
more control to ops and have low maintenance cost?

The Docker images for WSO2 products in Kubernetes Artifacts repository are
not private images. Rather, the repository contains the Dockerfiles that
can be used to build the images locally [1] and then uploaded to Docker Hub
or a private Docker registry. I guess a good option will be to build these
images and upload them to a personal Docker Hub account, for test purposes,
as it is better to verify open Docker registry work flow, before figuring
out the details on private Docker registry, as Lakmal mentions above.

Can you further elaborate how health checks happen in Diego and why some
Docker images cannot be run because of it?

Great work so far! :)

[1] -
http://code.chamiladealwis.com/blog/2016/02/09/running-wso2-products-on-kubernetes/



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



On Mon, Feb 15, 2016 at 11:25 PM, Nanduni Nimalsiri 
wrote:

> Hi,
>
> I was able to deploy Docker images in Cloud Foundry with Diego. Here I am
> going to clear several facts regarding that.
>
> There are several approaches of integrating Docker with Cloud Foundry. If
> I summarize them, they are are follows. Each of them possesses different
> limitations.
>
>
> *Integrating Docker with Cloud Foundry*
>
> *1. Docker Buildpack - *Provides framework and runtime support for the
> applications. When we push an application, Cloud Foundry automatically
> detects which buildpack is required and installs it on the Droplet
> Execution Agent (DEA) where the application needs to run.
>
> *2. Docker Service Provider - * A service provider to expose Docker
> containers as services.
>
> *3. Cloud Rocker *- A project carried out by a company called 'Cloud
> Credo' which builds docker images using Cloud Foundry buildpacks. If you
> don't want to use Cloud Foundry but you want to use its buildpack system,
> this is the best choice.
>
> *4. Diego - *Rewrite of DEA. In a Cloud Foundry deployment without Diego,
> the Cloud Controller schedules and manages applications on the DEA nodes.
> Diego replaces the DEAs and the Health Manager, and assumes application
> scheduling and management responsibility from the Cloud Controller. Diego
> is special because it provides built-in-support for Docker containers.
>
> *5. Lattice - *Lattice is a standalone scheduler extracted from Diego for
> Docker images. If Cloud Foundry is too much, Lattice might be a suitable
> project. Lattice tries to be little simpler and easier to set up with less
> features around it. The nice thing about this Lattice system is that it is
> super light weight.
>
> Out of the aforementioned approaches, I used 4th option - Diego in Cloud
> Foundry. As mentiond above, Diego builds out the new runtime architecture
> for Cloud Foundry, replacing the DEAs and Health Manager. In fact, *Cloud
> Foundry now encourages the use of Diego.*
>
> *Using Diego with Cloud Foundry*
>
> First I tried to use Diego with PWS (Pivotal Web Services). Then it gave
> me errors in enabling Diego feature due to conflicts in administrator
> privileges. In that case, I have been running the 60 days trial version of
> Pivotal.io and that's why I had no administrator control because PWS is a
> shared platform.
>
> So the next option was to run Diego locally in my machine so that I can
> then get admin control and do whatever I want with the system. So I used* 
> Cloud
> Foundry Diego [BOSH release] *in [1] for that. With several
> modifications, I managed to deploy Docker containers eventually. Here are
> the steps I followed.
>
> 1. Uploaded the latest version of the Warden BOSH-Lite stemcell directly
> to BOSH-Lite
> 2. Used two releases to generate two manifests basically. They are
> cf-relaese and diego-release.
> 3. Generated CF manifest and Diego manifest.
> 4. Created, uploaded, and deployed the CF release.
> 5. Uploaded the latest garden-linux-release.
> 6. Uploaded the latest etcd-release.
> 7. Created, uploaded, and deployed the Diego release
> 8. Logged in to CF and enabled Docker support.
> 9. Deployed cloudfoundry/lattice-app docker image.
> 10. Scaled the number of instances and so on...
>
> [1] https://github.com/cloudfoundry-incubator/diego-release
>
>
> *Containers vs Buildpacks*
>
> If I move to the Docker buildpacks, I could not find any buildpack
> compatible for deploying Docker images yet. I am trying on it, but the
> problem seems that they require some external Docker host which I have no
> idea on how to set up.
>
> Meanwhile, I found several pros and cons with these two approaches:
> Buildpack mechanism and Container mechanism. I have summarized them as
> below.
>
> *Containers are better 

Re: [Dev] Running WSO2 Products on Cloud Foundry

[Nanduni Nimalsiri]

Hi,

I was able to deploy Docker images in Cloud Foundry with Diego. Here I am
going to clear several facts regarding that.

There are several approaches of integrating Docker with Cloud Foundry. If I
summarize them, they are are follows. Each of them possesses different
limitations.


*Integrating Docker with Cloud Foundry*

*1. Docker Buildpack - *Provides framework and runtime support for the
applications. When we push an application, Cloud Foundry automatically
detects which buildpack is required and installs it on the Droplet
Execution Agent (DEA) where the application needs to run.

*2. Docker Service Provider - * A service provider to expose Docker
containers as services.

*3. Cloud Rocker *- A project carried out by a company called 'Cloud Credo'
which builds docker images using Cloud Foundry buildpacks. If you don't
want to use Cloud Foundry but you want to use its buildpack system, this is
the best choice.

*4. Diego - *Rewrite of DEA. In a Cloud Foundry deployment without Diego,
the Cloud Controller schedules and manages applications on the DEA nodes.
Diego replaces the DEAs and the Health Manager, and assumes application
scheduling and management responsibility from the Cloud Controller. Diego
is special because it provides built-in-support for Docker containers.

*5. Lattice - *Lattice is a standalone scheduler extracted from Diego for
Docker images. If Cloud Foundry is too much, Lattice might be a suitable
project. Lattice tries to be little simpler and easier to set up with less
features around it. The nice thing about this Lattice system is that it is
super light weight.

Out of the aforementioned approaches, I used 4th option - Diego in Cloud
Foundry. As mentiond above, Diego builds out the new runtime architecture
for Cloud Foundry, replacing the DEAs and Health Manager. In fact, *Cloud
Foundry now encourages the use of Diego.*

*Using Diego with Cloud Foundry*

First I tried to use Diego with PWS (Pivotal Web Services). Then it gave me
errors in enabling Diego feature due to conflicts in administrator
privileges. In that case, I have been running the 60 days trial version of
Pivotal.io and that's why I had no administrator control because PWS is a
shared platform.

So the next option was to run Diego locally in my machine so that I can
then get admin control and do whatever I want with the system. So I used* Cloud
Foundry Diego [BOSH release] *in [1] for that. With several modifications,
I managed to deploy Docker containers eventually. Here are the steps I
followed.

1. Uploaded the latest version of the Warden BOSH-Lite stemcell directly to
BOSH-Lite
2. Used two releases to generate two manifests basically. They are
cf-relaese and diego-release.
3. Generated CF manifest and Diego manifest.
4. Created, uploaded, and deployed the CF release.
5. Uploaded the latest garden-linux-release.
6. Uploaded the latest etcd-release.
7. Created, uploaded, and deployed the Diego release
8. Logged in to CF and enabled Docker support.
9. Deployed cloudfoundry/lattice-app docker image.
10. Scaled the number of instances and so on...

[1] https://github.com/cloudfoundry-incubator/diego-release


*Containers vs Buildpacks*

If I move to the Docker buildpacks, I could not find any buildpack
compatible for deploying Docker images yet. I am trying on it, but the
problem seems that they require some external Docker host which I have no
idea on how to set up.

Meanwhile, I found several pros and cons with these two approaches:
Buildpack mechanism and Container mechanism. I have summarized them as
below.

*Containers are better when*,
- Developers require more control
- Developers know Operations/Docker
- Time to market is important

*Buildpacks are better when*,
- Operations require more control
- Developers focus on application
- Low maintenance cost is important

Since we already have Docker images for WSO2 products (k8s artifacts) , I
suggest that we can use Diego for deploying WSO2 products in Cloud Foundry.
But the problem seems that they are private images and still I have no idea
on how we should proceed with docker images that are not available in
Docker Hub. I suppose that there is some mechanism with 'Private Docker
Registry' in Diego. Meanwhile there are some other limitations of this
approach such as port based health check etc. which blocks deploying some
Docker images.

Please add your comments on this.

Best regards,
Nanduni.

*Nanduni Nimalsiri*
Software Engineering Intern, WSO2 Inc. (http://wso2.com)
email : nand...@wso2.com
blog : http://nanduni.blogspot.com/
mobile : +94714114256


*Nanduni Nimalsiri*
Software Engineering Intern, WSO2 Inc. (http://wso2.com)
email : nand...@wso2.com
blog : http://nanduni.blogspot.com/
mobile : +94714114256


On Tue, Feb 9, 2016 at 12:51 PM, Lakmal Warusawithana 
wrote:

> Initial stage, don't worry 

[Dev] Fwd: GSOC 2016: Proposal 7

[Dinanjana Gunaratne]

From: Dinanjana Gunaratne 
Date: Mon, Feb 15, 2016 at 9:27 PM
Subject: [Dev]GSOC 2016: Proposal 7


Dear Sir,

I m a 3rd year Computer Engineering undergraduate at University of
Peradeniya. I would like to contribute to open source community by taking
part in GSOC 2016.

Recently i developed a remote monitoring system for an organization which
had some of those mentioned features. Such as alerting when resources are
over used and alerting when server stop responding. The monitoring system
developed in such a manner that the implementation of monitoring system
does not depend on components that are been monitored. The solution is
built using Java and Spring framework.

So i wold like to know how to proceed on this project.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][UI/UX] Data Table Extended Prompt An Alert When Filtering Data

[Kamidu Punchihewa]

Hi UI/UX Team,

I have faced $subject when fitting data using the ajax method.
An "IllegalArgumentException" was thoun in the back end, and a datatable
error alert was prompt from the front end when a filtering was triggered.

There was a mismatch in the expected uri format and the current uri format
given by the data table extended library.When comparing expected backend
call [1] with current backend call [2] there were two extra characters
included to the current uri.

This causes due to the latest change which is listed below.

Older version :

column
>
> .search(val ? val : '', true, false)
>
> .draw();
>
>
New version :

column
> .search(val ? '^' + val + '$' : '', true, false)
> .draw();



Any reason for this latest change ?

[1].  'endpoint?draw=2=0=16*=data'*
[2].  'endpoint?draw=2=0=16*=^data$'*

Thanks and Regards.
Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM][Analytics] Calculatiing percentile in Spark

[Sriskandarajah Suhothayan]

What the duration are we looking at ? If its like an hour then we can use
CEP.
Can you look at whether we can implement percentile in CEP in a scalable
manner ?

Suho

On Mon, Feb 15, 2016 at 4:39 PM, Sachini Jayasekara 
wrote:

> Hi all,
>
> I am working on following two alert generation scenarios,
>
> 1. Abnormal response time/ backend time - If an API response time or the
> backend time lies outside the Xth percentile.
>
> 2. Abnormal request counts - Count the number of requests during last
> minute and check if it lies outside the Xth percentile.
>
> Initially, we thought of having a summarization job to calculate the
> percentile values daily. However, in DAS, spark doesn't have OOB support to
> calculate percentile even though hive has that as a built-in aggregate
> function.
>
> With DAS 3.0.1 we can define UDFs (User Defined Functions), but the
> function 'percentile'  is a user-defined aggregation function (UDAF).
> Hence, we cannot use that approach as well.
>
> Is there an alternative way in DAS to define custom aggregation function?
>
>
> Thanks,
> Sachini
>
> --
>
>
>
> *Thanks & Regards,Sachini JayasekaraSoftware Engineer; **WSO2 Inc. *
>
> *lean . enterprise . middleware |  http://wso2.com  *
>
> Mobile : +94712371165
>



-- 

*S. Suhothayan*
Technical Lead & Team Lead of WSO2 Complex Event Processor
*WSO2 Inc. *http://wso2.com
* *
lean . enterprise . middleware


*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: http://twitter.com/suhothayan
 | linked-in:
http://lk.linkedin.com/in/suhothayan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SMS OTP Authenticator

[Malaka Silva]

+Elilmatha

On Mon, Feb 15, 2016 at 6:56 PM, Darshana Gunawardana 
wrote:

> Hi Devs,
>
> Tried $subject and its really cool, easy to set up and get working. Kudos
> to everyone to get that out...!!
>
> I have checked the source and there are couple of things we can improve
>
>1. Avoid using instance variables in the authentication to store any
>data since the authentication is a single. There are different context
>objects have different scopes, pick the correct context to store relevant
>data.
>2. Having smsprovider.properties file to configure any additional data
>is correct. But if there is a need of such property file should be in the
>/repository/resources/ folder
>3. It should have configurable the SMS text from the UI, rather from
>the property file.
>4. We could comeup with a provisioning connector which do the number
>registering automatically, so it won't need to do manual update from
>external sms provider.
>
> Hope these suggestions improve the usability and functionality of the
> authenticator much more.
>
> Thanks,
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Senior Software Engineer
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>



-- 

Best Regards,

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

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

https://store.wso2.com/store/

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

[Dev] SMS OTP Authenticator

[Darshana Gunawardana]

Hi Devs,

Tried $subject and its really cool, easy to set up and get working. Kudos
to everyone to get that out...!!

I have checked the source and there are couple of things we can improve

   1. Avoid using instance variables in the authentication to store any
   data since the authentication is a single. There are different context
   objects have different scopes, pick the correct context to store relevant
   data.
   2. Having smsprovider.properties file to configure any additional data
   is correct. But if there is a need of such property file should be in the
   /repository/resources/ folder
   3. It should have configurable the SMS text from the UI, rather from the
   property file.
   4. We could comeup with a provisioning connector which do the number
   registering automatically, so it won't need to do manual update from
   external sms provider.

Hope these suggestions improve the usability and functionality of the
authenticator much more.

Thanks,

-- 
Regards,


*Darshana Gunawardana*Senior Software Engineer
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com *
*Mobile: +94718566859*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Test Automation Framework] Compilation Error while building

[Irham Iqbal]

Hi Yashothara,

Did you try to build the latest version from git ?. Please share the full
stack trace.

Thanks,
iqbal

On Mon, Feb 15, 2016 at 3:57 AM, Yashothara Shanmugarajah <
yashoth...@wso2.com> wrote:

> Hi,
> I have already build carbon kernel 4.2.0 in JDK 1.6 and maven 3.0.4.
> After that I went  to *Platform* and build the modules listed below
> accordingly:parent, dependencies, service-stubs and components.
>
> Even though I could not build Test Automation Frame work. It is giving
> error in Test API. The following error came when I try to build it.
>
> [ERROR]Could not resolve dependencies for project
> org.wso2.carbon.automation:org.wso2.carbon.automation.api:jar:4.2.0-SNAPSHOT:
>
> Like that it says most of the jar files could not be resolved.
>
> Best Regards,
> Yashothara.S
>
> Software Engineer
> WSO2
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Irham Iqbal
Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 777888452
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Google summer of code 2016

[Jayamine A.]

I'm a third year computer engineering student at University of Peradeniya.
I'm interested at the project "support xml, cvs, json, execl and web
services formats in data mapper".

I read some stuffs about wso2 data mapper. But i would like to know more
about data mapper and the related product .Because i'm trying to understand
why you are using avro in data mapper and the functionalities of data
mapper.

please suggest me if there are any references about data mapper and the
related products.

Thanks :-)

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

Re: [Dev] [APIM] APIM Integration test classes aren't being resolved in testng.xml

[Erandi Ganepola]

Hi Iqbal,

I was able to solve it. Thank you very much.

Regards,
Erandi.



Erandi Ganepola
Software Engineering Intern
+94710695692


On Mon, Feb 15, 2016 at 3:53 PM, Irham Iqbal  wrote:

> Hi Erandi,
>
> In which pom you added that dependency ?. Also you don't need to copy
> anything manually while using maven to build.
>
> Thanks,
> Iqbal
>
> On Sat, Feb 13, 2016 at 5:59 PM, Erandi Ganepola  wrote:
>
>> Hi All,
>>
>> I'm currently trying to automate the APIM Integration test cases in cloud
>> Heartbeat system. I have added the below dependency to pom.
>>
>> 
>> org.wso2.am
>>
>> org.wso2.carbon.am.integration.backend.test
>> 1.10.1-SNAPSHOT
>>  
>>
>> Then built the pom and added those resulting jar files to libraries.
>> Still it doesn't resolve the classes in testng.xml. But inside those
>> packages, those classes are already there.
>>
>> Can someone please explain what is the issue?
>>
>> Thanks and regards,
>>
>> Erandi Ganepola
>> Software Engineering Intern
>> +94710695692
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Irham Iqbal
> Software Engineer - Test Automation
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
> phone: +94 777888452
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] WSO2 IoT Server 1.0.0 M3 Released

[Shavantha Weerasinghe]

Hi Sumedha

Thanks will go through these

regards,shavantha

Shavantha Weerasinghe
Senior Software Engineer QA
WSO2, Inc.
lean.enterprise.middleware.
http://wso2.com
http://wso2.org
Tel : 94 11 214 5345
Fax :94 11 2145300


On Mon, Feb 15, 2016 at 5:26 PM, Sumedha Rubasinghe 
wrote:

> Shavantha,
> Can you go through the documentation and getting started guide?
>
>
> https://docs.wso2.com/display/IoTS100/Getting+Started+with+WSO2+IoT+Server
> https://docs.wso2.com/display/IoTS100/Quick+Start+Guide
>
>
>
>
> On Mon, Feb 15, 2016 at 5:13 PM, Ruwan Yatawara  wrote:
>
>> Sure Shavantha,
>>
>> We are a bit busy these days as we are doing some work for WSO2Con, how
>> about we have a session on Friday?
>>
>> 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 Mon, Feb 15, 2016 at 4:54 PM, Shavantha Weerasinghe <
>> shavan...@wso2.com> wrote:
>>
>>> Hi Ruwan
>>>
>>> My self and jason have been assigned to the QA cycles, can we arrange
>>> for a KT session
>>>
>>> regards,shavantha
>>>
>>> Shavantha Weerasinghe
>>> Senior Software Engineer QA
>>> WSO2, Inc.
>>> lean.enterprise.middleware.
>>> http://wso2.com
>>> http://wso2.org
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>>
>>>
>>> On Mon, Feb 8, 2016 at 7:17 PM, Ruwan Yatawara  wrote:
>>>
 *WSO2 IoT Server 1.0.0 M3 Released*
 Please find below, download link of the third Milestone of WSO2
 IoTServer 1.0.0.


 https://github.com/wso2-incubator/product-iot-server/releases/tag/IoTS-1.0.0-M3


 The list of new features & Bug fixes are as follows.

 Features

- Merging with CDMF/CDMF-Plugins Master Branch
- New Device Type Implemented (Water Dispenser)


 Bug Fixes

 - [IOTS-30 ] - QR Code is not
 shown when user is added
 - [IOTS-32 ] - Doesn't allow to
 edit a user without adding PW value
 - [IOTS-40 ] - Incorrect
 information sequence on the Drone Analyzer device UI page
 - [IOTS-41 ] - Missing
 wso2Agent.sh file for the Digital Display agent
 - [IOTS-42 ] - Page not
 navigated to success page after adding new user

 Sub-task

- Enhanced packaging structure of device types




 Thanks and Regards,

 *~ EMM / IOT Team ~*



 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


 ___
 Architecture mailing list
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] WSO2 IoT Server 1.0.0 M3 Released

[Shavantha Weerasinghe]

Hi Ruwan

+1 lets have it for 19 th Friday in the mean time we will go through the
documentation and get started.

regards,shavantha

Shavantha Weerasinghe
Senior Software Engineer QA
WSO2, Inc.
lean.enterprise.middleware.
http://wso2.com
http://wso2.org
Tel : 94 11 214 5345
Fax :94 11 2145300


On Mon, Feb 15, 2016 at 5:13 PM, Ruwan Yatawara  wrote:

> Sure Shavantha,
>
> We are a bit busy these days as we are doing some work for WSO2Con, how
> about we have a session on Friday?
>
> 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 Mon, Feb 15, 2016 at 4:54 PM, Shavantha Weerasinghe  > wrote:
>
>> Hi Ruwan
>>
>> My self and jason have been assigned to the QA cycles, can we arrange for
>> a KT session
>>
>> regards,shavantha
>>
>> Shavantha Weerasinghe
>> Senior Software Engineer QA
>> WSO2, Inc.
>> lean.enterprise.middleware.
>> http://wso2.com
>> http://wso2.org
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>>
>>
>> On Mon, Feb 8, 2016 at 7:17 PM, Ruwan Yatawara  wrote:
>>
>>> *WSO2 IoT Server 1.0.0 M3 Released*
>>> Please find below, download link of the third Milestone of WSO2
>>> IoTServer 1.0.0.
>>>
>>>
>>> https://github.com/wso2-incubator/product-iot-server/releases/tag/IoTS-1.0.0-M3
>>>
>>>
>>> The list of new features & Bug fixes are as follows.
>>>
>>> Features
>>>
>>>- Merging with CDMF/CDMF-Plugins Master Branch
>>>- New Device Type Implemented (Water Dispenser)
>>>
>>>
>>> Bug Fixes
>>>
>>> - [IOTS-30 ] - QR Code is not
>>> shown when user is added
>>> - [IOTS-32 ] - Doesn't allow to
>>> edit a user without adding PW value
>>> - [IOTS-40 ] - Incorrect
>>> information sequence on the Drone Analyzer device UI page
>>> - [IOTS-41 ] - Missing
>>> wso2Agent.sh file for the Digital Display agent
>>> - [IOTS-42 ] - Page not navigated
>>> to success page after adding new user
>>>
>>> Sub-task
>>>
>>>- Enhanced packaging structure of device types
>>>
>>>
>>>
>>>
>>> Thanks and Regards,
>>>
>>> *~ EMM / IOT Team ~*
>>>
>>>
>>>
>>> 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
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 ESB 5.0.0 - Milestone 2 Released!

[Vijitha Ekanayake]

*WSO2 ESB 5.0.0-Milestone 2 Released*

ESB Team is pleased to announce the WSO2 ESB 5.0.0 - Milestone 2 Release.
It contains following improvement and bug fixes.

Bug

   - [ESBJAVA-4416 ] - ESB
   Management console shows Invalid product version.
   - [ESBJAVA-4417 ] - ESB
   server terminal shows Invalid product version.

Improvement

   - [ESBJAVA-4415 ] - SSL
   support for MQTT inbound.



The distribution is available to download at [1].

[1]
https://svn.wso2.org/repos/wso2/scratch/ESB/packs/5.0.0-Releases/5.0.0-M2/

- WSO2 ESB Team -

-- 
Vijitha Ekanayake
Software Engineer*, *WSO2, Inc.; http://wso2.com/
Mobile : +94 777 24 73 39 | +94 718 74 44 08
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] WSO2 IoT Server 1.0.0 M3 Released

[Sumedha Rubasinghe]

Shavantha,
Can you go through the documentation and getting started guide?


https://docs.wso2.com/display/IoTS100/Getting+Started+with+WSO2+IoT+Server
https://docs.wso2.com/display/IoTS100/Quick+Start+Guide




On Mon, Feb 15, 2016 at 5:13 PM, Ruwan Yatawara  wrote:

> Sure Shavantha,
>
> We are a bit busy these days as we are doing some work for WSO2Con, how
> about we have a session on Friday?
>
> 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 Mon, Feb 15, 2016 at 4:54 PM, Shavantha Weerasinghe  > wrote:
>
>> Hi Ruwan
>>
>> My self and jason have been assigned to the QA cycles, can we arrange for
>> a KT session
>>
>> regards,shavantha
>>
>> Shavantha Weerasinghe
>> Senior Software Engineer QA
>> WSO2, Inc.
>> lean.enterprise.middleware.
>> http://wso2.com
>> http://wso2.org
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>>
>>
>> On Mon, Feb 8, 2016 at 7:17 PM, Ruwan Yatawara  wrote:
>>
>>> *WSO2 IoT Server 1.0.0 M3 Released*
>>> Please find below, download link of the third Milestone of WSO2
>>> IoTServer 1.0.0.
>>>
>>>
>>> https://github.com/wso2-incubator/product-iot-server/releases/tag/IoTS-1.0.0-M3
>>>
>>>
>>> The list of new features & Bug fixes are as follows.
>>>
>>> Features
>>>
>>>- Merging with CDMF/CDMF-Plugins Master Branch
>>>- New Device Type Implemented (Water Dispenser)
>>>
>>>
>>> Bug Fixes
>>>
>>> - [IOTS-30 ] - QR Code is not
>>> shown when user is added
>>> - [IOTS-32 ] - Doesn't allow to
>>> edit a user without adding PW value
>>> - [IOTS-40 ] - Incorrect
>>> information sequence on the Drone Analyzer device UI page
>>> - [IOTS-41 ] - Missing
>>> wso2Agent.sh file for the Digital Display agent
>>> - [IOTS-42 ] - Page not navigated
>>> to success page after adding new user
>>>
>>> Sub-task
>>>
>>>- Enhanced packaging structure of device types
>>>
>>>
>>>
>>>
>>> Thanks and Regards,
>>>
>>> *~ EMM / IOT Team ~*
>>>
>>>
>>>
>>> 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
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] WSO2 IoT Server 1.0.0 M3 Released

[Ruwan Yatawara]

Sure Shavantha,

We are a bit busy these days as we are doing some work for WSO2Con, how
about we have a session on Friday?

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 Mon, Feb 15, 2016 at 4:54 PM, Shavantha Weerasinghe 
wrote:

> Hi Ruwan
>
> My self and jason have been assigned to the QA cycles, can we arrange for
> a KT session
>
> regards,shavantha
>
> Shavantha Weerasinghe
> Senior Software Engineer QA
> WSO2, Inc.
> lean.enterprise.middleware.
> http://wso2.com
> http://wso2.org
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
>
> On Mon, Feb 8, 2016 at 7:17 PM, Ruwan Yatawara  wrote:
>
>> *WSO2 IoT Server 1.0.0 M3 Released*
>> Please find below, download link of the third Milestone of WSO2 IoTServer
>> 1.0.0.
>>
>>
>> https://github.com/wso2-incubator/product-iot-server/releases/tag/IoTS-1.0.0-M3
>>
>>
>> The list of new features & Bug fixes are as follows.
>>
>> Features
>>
>>- Merging with CDMF/CDMF-Plugins Master Branch
>>- New Device Type Implemented (Water Dispenser)
>>
>>
>> Bug Fixes
>>
>> - [IOTS-30 ] - QR Code is not
>> shown when user is added
>> - [IOTS-32 ] - Doesn't allow to
>> edit a user without adding PW value
>> - [IOTS-40 ] - Incorrect
>> information sequence on the Drone Analyzer device UI page
>> - [IOTS-41 ] - Missing
>> wso2Agent.sh file for the Digital Display agent
>> - [IOTS-42 ] - Page not navigated
>> to success page after adding new user
>>
>> Sub-task
>>
>>- Enhanced packaging structure of device types
>>
>>
>>
>>
>> Thanks and Regards,
>>
>> *~ EMM / IOT Team ~*
>>
>>
>>
>> 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
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 MSF4J 1.0.0 RC6

[Samiyuru Senarathne]

Thank you all.

We are closing this vote and this vote passes with 5 +1 and 0 -1 votes. We
will proceed with publishing the maven artifacts.

On Mon, Feb 15, 2016 at 5:02 PM, Samiyuru Senarathne 
wrote:

> Tested following:
>
>- MSF4J templating
>- Fatjar mode
>- Bundle mode
>
> [X ] Stable - go ahead and release
>
> On Sun, Feb 14, 2016 at 12:31 AM, Sumedha Rubasinghe 
> wrote:
>
>>
>>
>> On Sun, Feb 14, 2016 at 12:11 AM, Sumedha Rubasinghe 
>> wrote:
>>
>>> Tested following:
>>> 1. Developed a service using archetype
>>> 2. Deployed and tested
>>> 3. Tested @QueryParam, @PathParam and @DefaultValue
>>> 4. Load tested GET with 100 concurrency for 10mins
>>>
>>> [x] Stable - go ahead and release - subjected to following documentation
>>> fixes.
>>>
>>>
>>> Following section should be changed:
>>>
>>> Sorry. Following section need not be changed.
>> I created the project using archetype and used testing instructions in
>> getting started page. :)
>>
>> Code and instructions on getting started page are matching.
>>
>>
>>
>>> Run the following command or simply go to
>>> http://localhost:8080/hello/wso2 from your browser.
>>> curl http://localhost:8080/hello/wso2
>>> You should see a response that prints "Hello wso2"
>>>
>>> To:
>>> Run the following command or simply go to *http://localhost:8080/service
>>> * from your browser.
>>> curl *http://localhost:8080/service *
>>> You should see a response that prints "*Hello from WSO2 MSF4J*"
>>>
>>> Also archetype generates a file called 'dependency-reduced-pom.xml'.
>>> License is missing there.
>>>
>>>
>>>
>>> On Fri, Feb 12, 2016 at 8:24 PM, Samiyuru Senarathne 
>>> wrote:
>>>
 Hi Devs,

 This is the 6th Release Candidate of WSO2 Microservices Framework for
 Java 1.0.0.

 Please download, test the framework and vote.
 Refer to github readmes for guides.

 *​Source and binary distribution files:*
 *https://github.com/wso2/msf4j/releases/tag/v1.0.0-RC6
 *

 *Maven staging repository:*
 *http://maven.wso2.org/nexus/content/repositories/orgwso2-333/
 *

 *The tag to be voted upon:*
 *https://github.com/wso2/msf4j/tree/v1.0.0-RC6
 *

 *Note*
 When developing MSF4J applications, we need to use several poms
 provided by MSF4J. Since they are not yet uploaded to the maven
 central, we have to add the MSF4J maven repo url to the project to
 resolve them. For that, the following segment should be added to the
 project pom before building.

 
> 
> wso2-nexus
> 
> *http://maven.wso2.org/nexus/content/repositories/orgwso2-333/
> *
> 
> 



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

 Thank you,
 Carbon Team

 --
 Samiyuru Senarathne
 *Software Engineer*
 Mobile : +94 (0) 71 134 6087
 samiy...@wso2.com

>>>
>>>
>>>
>>> --
>>> /sumedha
>>> m: +94 773017743
>>> b :  bit.ly/sumedha
>>>
>>
>>
>>
>> --
>> /sumedha
>> m: +94 773017743
>> b :  bit.ly/sumedha
>>
>
>
>
> --
> Samiyuru Senarathne
> *Software Engineer*
> Mobile : +94 (0) 71 134 6087
> samiy...@wso2.com
>



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

[Dev] Android Client Parent version incorrect for tag 2.0.0

[Niranjan Karunanandham]

Hi EMM Team,

Is it possible to build the Android agent using maven? I tried to build the
android client and got the following exception[1]. When I checked the
pom.xml, it is referring to version 2.0.0-SNAPSHOT in the parent tag.
Please note that I have change my branch to the tags/v2.0.0 [2].

[1] -
mvn clean install
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project org.wso2.mdm:mdm-android-mobile-agent:2.0.0-SNAPSHOT
(/home/nira/wso2/git/product-mdm/modules/mobile-agents/android/client/pom.xml)
has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact
org.wso2.mdm:wso2mdm-product-mobileservices:pom:2.0.0-SNAPSHOT and
'parent.relativePath' points at wrong local POM @ line 23, column 13 ->
[Help 2]
[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/ProjectBuildingException
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

[2] -
https://github.com/wso2/product-mdm/blob/v2.0.0/modules/mobile-agents/android/client/pom.xml#L26

Regards,
Nira
-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 MSF4J 1.0.0 RC6

[Afkham Azeez]

Everything looks good. Let's release 1.0 today.

On Fri, Feb 12, 2016 at 8:24 PM, Samiyuru Senarathne 
wrote:

> Hi Devs,
>
> This is the 6th Release Candidate of WSO2 Microservices Framework for
> Java 1.0.0.
>
> Please download, test the framework and vote.
> Refer to github readmes for guides.
>
> *​Source and binary distribution files:*
> *https://github.com/wso2/msf4j/releases/tag/v1.0.0-RC6
> *
>
> *Maven staging repository:*
> *http://maven.wso2.org/nexus/content/repositories/orgwso2-333/
> *
>
> *The tag to be voted upon:*
> *https://github.com/wso2/msf4j/tree/v1.0.0-RC6
> *
>
> *Note*
> When developing MSF4J applications, we need to use several poms provided
> by MSF4J. Since they are not yet uploaded to the maven central, we have
> to add the MSF4J maven repo url to the project to resolve them. For that,
> the following segment should be added to the project pom before building.
>
> 
>> 
>> wso2-nexus
>> *http://maven.wso2.org/nexus/content/repositories/orgwso2-333/
>> *
>> 
>> 
>
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Thank you,
> Carbon Team
>
> --
> Samiyuru Senarathne
> *Software Engineer*
> Mobile : +94 (0) 71 134 6087
> samiy...@wso2.com
>



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

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

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

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

Re: [Dev] [VOTE] Release WSO2 MSF4J 1.0.0 RC6

[Samiyuru Senarathne]

Tested following:

   - MSF4J templating
   - Fatjar mode
   - Bundle mode

[X ] Stable - go ahead and release

On Sun, Feb 14, 2016 at 12:31 AM, Sumedha Rubasinghe 
wrote:

>
>
> On Sun, Feb 14, 2016 at 12:11 AM, Sumedha Rubasinghe 
> wrote:
>
>> Tested following:
>> 1. Developed a service using archetype
>> 2. Deployed and tested
>> 3. Tested @QueryParam, @PathParam and @DefaultValue
>> 4. Load tested GET with 100 concurrency for 10mins
>>
>> [x] Stable - go ahead and release - subjected to following documentation
>> fixes.
>>
>>
>> Following section should be changed:
>>
>> Sorry. Following section need not be changed.
> I created the project using archetype and used testing instructions in
> getting started page. :)
>
> Code and instructions on getting started page are matching.
>
>
>
>> Run the following command or simply go to
>> http://localhost:8080/hello/wso2 from your browser.
>> curl http://localhost:8080/hello/wso2
>> You should see a response that prints "Hello wso2"
>>
>> To:
>> Run the following command or simply go to *http://localhost:8080/service
>> * from your browser.
>> curl *http://localhost:8080/service *
>> You should see a response that prints "*Hello from WSO2 MSF4J*"
>>
>> Also archetype generates a file called 'dependency-reduced-pom.xml'.
>> License is missing there.
>>
>>
>>
>> On Fri, Feb 12, 2016 at 8:24 PM, Samiyuru Senarathne 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 6th Release Candidate of WSO2 Microservices Framework for
>>> Java 1.0.0.
>>>
>>> Please download, test the framework and vote.
>>> Refer to github readmes for guides.
>>>
>>> *​Source and binary distribution files:*
>>> *https://github.com/wso2/msf4j/releases/tag/v1.0.0-RC6
>>> *
>>>
>>> *Maven staging repository:*
>>> *http://maven.wso2.org/nexus/content/repositories/orgwso2-333/
>>> *
>>>
>>> *The tag to be voted upon:*
>>> *https://github.com/wso2/msf4j/tree/v1.0.0-RC6
>>> *
>>>
>>> *Note*
>>> When developing MSF4J applications, we need to use several poms
>>> provided by MSF4J. Since they are not yet uploaded to the maven
>>> central, we have to add the MSF4J maven repo url to the project to
>>> resolve them. For that, the following segment should be added to the
>>> project pom before building.
>>>
>>> 
 
 wso2-nexus
 *http://maven.wso2.org/nexus/content/repositories/orgwso2-333/
 *
 
 
>>>
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>> Thank you,
>>> Carbon Team
>>>
>>> --
>>> Samiyuru Senarathne
>>> *Software Engineer*
>>> Mobile : +94 (0) 71 134 6087
>>> samiy...@wso2.com
>>>
>>
>>
>>
>> --
>> /sumedha
>> m: +94 773017743
>> b :  bit.ly/sumedha
>>
>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>



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

Re: [Dev] [Architecture] WSO2 IoT Server 1.0.0 M3 Released

[Shavantha Weerasinghe]

Hi Ruwan

My self and jason have been assigned to the QA cycles, can we arrange for a
KT session

regards,shavantha

Shavantha Weerasinghe
Senior Software Engineer QA
WSO2, Inc.
lean.enterprise.middleware.
http://wso2.com
http://wso2.org
Tel : 94 11 214 5345
Fax :94 11 2145300


On Mon, Feb 8, 2016 at 7:17 PM, Ruwan Yatawara  wrote:

> *WSO2 IoT Server 1.0.0 M3 Released*
> Please find below, download link of the third Milestone of WSO2 IoTServer
> 1.0.0.
>
>
> https://github.com/wso2-incubator/product-iot-server/releases/tag/IoTS-1.0.0-M3
>
>
> The list of new features & Bug fixes are as follows.
>
> Features
>
>- Merging with CDMF/CDMF-Plugins Master Branch
>- New Device Type Implemented (Water Dispenser)
>
>
> Bug Fixes
>
> - [IOTS-30 ] - QR Code is not shown
> when user is added
> - [IOTS-32 ] - Doesn't allow to
> edit a user without adding PW value
> - [IOTS-40 ] - Incorrect
> information sequence on the Drone Analyzer device UI page
> - [IOTS-41 ] - Missing wso2Agent.sh
> file for the Digital Display agent
> - [IOTS-42 ] - Page not navigated
> to success page after adding new user
>
> Sub-task
>
>- Enhanced packaging structure of device types
>
>
>
>
> Thanks and Regards,
>
> *~ EMM / IOT Team ~*
>
>
>
> 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
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM][Analytics] Calculatiing percentile in Spark

[Isuru Perera]

Hi,

This is a separate question.

As I know, the API Manager is integrating Carbon Metrics [1] and the timers
are used to measure the time duration for handlers. A timer in Metrics is a
duration histogram and it has predefined set of percentile values (95th,
99th etc).

Will we be able to make use of metrics for alerting as well? For this, we
may need to study how the reservoir works in Metrics Histogram.

[1] https://github.com/wso2/carbon-metrics

On Mon, Feb 15, 2016 at 4:39 PM, Sachini Jayasekara 
wrote:

> Hi all,
>
> I am working on following two alert generation scenarios,
>
> 1. Abnormal response time/ backend time - If an API response time or the
> backend time lies outside the Xth percentile.
>
> 2. Abnormal request counts - Count the number of requests during last
> minute and check if it lies outside the Xth percentile.
>
> Initially, we thought of having a summarization job to calculate the
> percentile values daily. However, in DAS, spark doesn't have OOB support to
> calculate percentile even though hive has that as a built-in aggregate
> function.
>
> With DAS 3.0.1 we can define UDFs (User Defined Functions), but the
> function 'percentile'  is a user-defined aggregation function (UDAF).
> Hence, we cannot use that approach as well.
>
> Is there an alternative way in DAS to define custom aggregation function?
>
>
> Thanks,
> Sachini
>
> --
>
>
>
> *Thanks & Regards,Sachini JayasekaraSoftware Engineer; **WSO2 Inc. *
>
> *lean . enterprise . middleware |  http://wso2.com  *
>
> Mobile : +94712371165
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

[Dev] [APIM][Analytics] Calculatiing percentile in Spark

[Sachini Jayasekara]

Hi all,

I am working on following two alert generation scenarios,

1. Abnormal response time/ backend time - If an API response time or the
backend time lies outside the Xth percentile.

2. Abnormal request counts - Count the number of requests during last
minute and check if it lies outside the Xth percentile.

Initially, we thought of having a summarization job to calculate the
percentile values daily. However, in DAS, spark doesn't have OOB support to
calculate percentile even though hive has that as a built-in aggregate
function.

With DAS 3.0.1 we can define UDFs (User Defined Functions), but the
function 'percentile'  is a user-defined aggregation function (UDAF).
Hence, we cannot use that approach as well.

Is there an alternative way in DAS to define custom aggregation function?


Thanks,
Sachini

-- 



*Thanks & Regards,Sachini JayasekaraSoftware Engineer; **WSO2 Inc. *

*lean . enterprise . middleware |  http://wso2.com  *

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

Re: [Dev] [APIM] APIM Integration test classes aren't being resolved in testng.xml

[Irham Iqbal]

Hi Erandi,

In which pom you added that dependency ?. Also you don't need to copy
anything manually while using maven to build.

Thanks,
Iqbal

On Sat, Feb 13, 2016 at 5:59 PM, Erandi Ganepola  wrote:

> Hi All,
>
> I'm currently trying to automate the APIM Integration test cases in cloud
> Heartbeat system. I have added the below dependency to pom.
>
> 
> org.wso2.am
>
> org.wso2.carbon.am.integration.backend.test
> 1.10.1-SNAPSHOT
>  
>
> Then built the pom and added those resulting jar files to libraries. Still
> it doesn't resolve the classes in testng.xml. But inside those packages,
> those classes are already there.
>
> Can someone please explain what is the issue?
>
> Thanks and regards,
>
> Erandi Ganepola
> Software Engineering Intern
> +94710695692
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Irham Iqbal
Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 777888452
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev