[Dev] [EMM]Issues in calling admin services as a tenant user from a jaggery app

[Megala Uthayakumar]

Hi All,

I am working on a jira [1] which is related with an exception that is
thrown when trying to add a user/role in tenant mode using EMM console.
This is particularly happens when we call the admin service to get the
secondary user store configurations related to particular tenant [2].
Following is the root cause behind this exception,

*Caused by: java.lang.SecurityException: Illegal access attempt to cache ]
owned by tenant*
*{[test.com ],[1]} by tenant {[test.com
],[-1234]}*

When trying to access the cache, the caller's tenant id has changed to
super-tenant id, although tenant domain is correct. I tried to start the
tenant flow before calling the admin service, but still I got the same
error. While debugging I found, [3] is the point where the tenant domain is
set to correct domain, while the tenant id still set to super-tenant id.
Locally I changed that particular line as per below,

PrivilegedCarbonContext.getThreadLocalCarbonContext().setTenantDomain(
userTenantDomain,*true*);

After that I could get the secondary user-store configurations related to
that particular tenant. Is this a bug from carbon-level or is there any
work-around to avoid this? Any comments or suggestions on this regard is
highly appreciated.

[1] https://wso2.org/jira/browse/EMM-1762
[2]
https://github.com/wso2/carbon-device-mgt/blob/master/components/device-mgt/org.wso2.carbon.device.mgt.ui/src/main/resources/jaggeryapps/devicemgt/app/modules/business-controllers/user.js#L607
[3]
https://github.com/wso2/carbon-kernel/blob/v4.4.9/core/org.wso2.carbon.server.admin/src/main/java/org/wso2/carbon/server/admin/module/handler/AuthenticationHandler.java#L93

Thanks.

Regards,
Megala
-- 
Megala Uthayakumar

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

Re: [Dev] API Manager 2.0.0 - Cannot add SAML inbound authentication config to Service Provider

[Tharindu Edirisinghe]

Thanks !

On Wed, Oct 19, 2016 at 10:45 AM, Abimaran Kugathasan 
wrote:

> Hi Tharindu,
>
> Yes, This is a known issue, yet to be fixed. Reported through [1]
>
> [1] : https://wso2.org/jira/browse/APIMANAGER-4493
>
> On Wed, Oct 19, 2016 at 10:27 AM, Tharindu Edirisinghe  > wrote:
>
>> Hi Devs,
>>
>> I'm using a fresh pack of API Manager 2.0.0 and added a Service Provider.
>> It got registered correctly.
>>
>> Then I edit the SP and try to add SAML inbound authentication and then I
>> get an empty page. Tested this on both Firefox and Chrome and the behavior
>> is same.
>>
>> Here's the backend error. Is this known issue ? or is there a patch ?
>>
>>
>> TID: [-1234] [] [2016-10-19 10:15:36,464] ERROR
>> {org.apache.tiles.jsp.context.JspTilesRequestContext} -  JSPException
>> while including path '/sso-saml/add_service_provider.jsp'.
>> {org.apache.tiles.jsp.context.JspTilesRequestContext}
>> javax.servlet.jsp.JspException: ServletException while including page.
>> at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:102)
>> at org.apache.tiles.jsp.context.JspTilesRequestContext.include(
>> JspTilesRequestContext.java:88)
>> at org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch
>> (JspTilesRequestContext.java:82)
>> at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesC
>> ontainer.java:465)
>> at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(Insert
>> AttributeTag.java:140)
>> at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(Insert
>> AttributeTag.java:117)
>> at org.apache.tiles.jsp.taglib.RenderTagSupport.execute(RenderT
>> agSupport.java:171)
>> at org.apache.tiles.jsp.taglib.RoleSecurityTagSupport.doEndTag(
>> RoleSecurityTagSupport.java:75)
>> at org.apache.tiles.jsp.taglib.ContainerTagSupport.doEndTag(Con
>> tainerTagSupport.java:80)
>> at org.apache.jsp.admin.layout.template_jsp._jspx_meth_tiles_00
>> 5finsertAttribute_005f7(template_jsp.java:661)
>> at org.apache.jsp.admin.layout.template_jsp._jspService(templat
>> e_jsp.java:377)
>> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.apache.jasper.servlet.JspServletWrapper.service(JspServl
>> etWrapper.java:439)
>> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServl
>> et.java:395)
>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
>> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.
>> java:80)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.se
>> rvice(ContextPathServletAdaptor.java:37)
>> at org.eclipse.equinox.http.servlet.internal.ServletRegistratio
>> n.service(ServletRegistration.java:61)
>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce
>> ssAlias(ProxyServlet.java:128)
>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi
>> ce(ProxyServlet.java:68)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service
>> (DelegationServlet.java:68)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>> lter(ApplicationFilterChain.java:303)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>> licationFilterChain.java:208)
>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilte
>> r.java:52)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>> lter(ApplicationFilterChain.java:241)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>> licationFilterChain.java:208)
>> at org.apache.catalina.core.ApplicationDispatcher.invoke(Applic
>> ationDispatcher.java:747)
>> at org.apache.catalina.core.ApplicationDispatcher.processReques
>> t(ApplicationDispatcher.java:485)
>> at org.apache.catalina.core.ApplicationDispatcher.doForward(App
>> licationDispatcher.java:410)
>> at org.apache.catalina.core.ApplicationDispatcher.forward(Appli
>> cationDispatcher.java:337)
>> at org.eclipse.equinox.http.servlet.internal.RequestDispatcherA
>> daptor.forward(RequestDispatcherAdaptor.java:30)
>> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$Re
>> questDispatcherAdaptor.forward(ContextPathServletAdaptor.java:362)
>> at org.apache.tiles.servlet.context.ServletTilesRequestContext.
>> forward(ServletTilesRequestContext.java:198)
>> at org.apache.tiles.servlet.context.ServletTilesRequestContext.
>> dispatch(ServletTilesRequestContext.java:185)
>> at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesC
>> ontainer.java:419)
>> at 

Re: [Dev] API Manager 2.0.0 - Cannot add SAML inbound authentication config to Service Provider

[Abimaran Kugathasan]

Hi Tharindu,

Yes, This is a known issue, yet to be fixed. Reported through [1]

[1] : https://wso2.org/jira/browse/APIMANAGER-4493

On Wed, Oct 19, 2016 at 10:27 AM, Tharindu Edirisinghe 
wrote:

> Hi Devs,
>
> I'm using a fresh pack of API Manager 2.0.0 and added a Service Provider.
> It got registered correctly.
>
> Then I edit the SP and try to add SAML inbound authentication and then I
> get an empty page. Tested this on both Firefox and Chrome and the behavior
> is same.
>
> Here's the backend error. Is this known issue ? or is there a patch ?
>
>
> TID: [-1234] [] [2016-10-19 10:15:36,464] ERROR
> {org.apache.tiles.jsp.context.JspTilesRequestContext} -  JSPException
> while including path '/sso-saml/add_service_provider.jsp'.
> {org.apache.tiles.jsp.context.JspTilesRequestContext}
> javax.servlet.jsp.JspException: ServletException while including page.
> at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:102)
> at org.apache.tiles.jsp.context.JspTilesRequestContext.include(
> JspTilesRequestContext.java:88)
> at org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch(
> JspTilesRequestContext.java:82)
> at org.apache.tiles.impl.BasicTilesContainer.render(
> BasicTilesContainer.java:465)
> at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(
> InsertAttributeTag.java:140)
> at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(
> InsertAttributeTag.java:117)
> at org.apache.tiles.jsp.taglib.RenderTagSupport.execute(
> RenderTagSupport.java:171)
> at org.apache.tiles.jsp.taglib.RoleSecurityTagSupport.doEndTag(
> RoleSecurityTagSupport.java:75)
> at org.apache.tiles.jsp.taglib.ContainerTagSupport.doEndTag(
> ContainerTagSupport.java:80)
> at org.apache.jsp.admin.layout.template_jsp._jspx_meth_tiles_
> 005finsertAttribute_005f7(template_jsp.java:661)
> at org.apache.jsp.admin.layout.template_jsp._jspService(
> template_jsp.java:377)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.apache.jasper.servlet.JspServletWrapper.service(
> JspServletWrapper.java:439)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(
> JspServlet.java:395)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(
> ContextPathServletAdaptor.java:37)
> 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:731)
> 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.apache.catalina.core.ApplicationDispatcher.invoke(
> ApplicationDispatcher.java:747)
> at org.apache.catalina.core.ApplicationDispatcher.processRequest(
> ApplicationDispatcher.java:485)
> at org.apache.catalina.core.ApplicationDispatcher.doForward(
> ApplicationDispatcher.java:410)
> at org.apache.catalina.core.ApplicationDispatcher.forward(
> ApplicationDispatcher.java:337)
> at org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.
> forward(RequestDispatcherAdaptor.java:30)
> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$
> RequestDispatcherAdaptor.forward(ContextPathServletAdaptor.java:362)
> at org.apache.tiles.servlet.context.ServletTilesRequestContext.
> forward(ServletTilesRequestContext.java:198)
> at org.apache.tiles.servlet.context.ServletTilesRequestContext.
> dispatch(ServletTilesRequestContext.java:185)
> at org.apache.tiles.impl.BasicTilesContainer.render(
> BasicTilesContainer.java:419)
> at org.apache.tiles.impl.BasicTilesContainer.render(
> BasicTilesContainer.java:370)
> at org.wso2.carbon.ui.action.ActionHelper.render(ActionHelper.java:52)
> at org.wso2.carbon.ui.TilesJspServlet.service(
> TilesJspServlet.java:101)
> at 

[Dev] API Manager 2.0.0 - Cannot add SAML inbound authentication config to Service Provider

[Tharindu Edirisinghe]

Hi Devs,

I'm using a fresh pack of API Manager 2.0.0 and added a Service Provider.
It got registered correctly.

Then I edit the SP and try to add SAML inbound authentication and then I
get an empty page. Tested this on both Firefox and Chrome and the behavior
is same.

Here's the backend error. Is this known issue ? or is there a patch ?


TID: [-1234] [] [2016-10-19 10:15:36,464] ERROR
{org.apache.tiles.jsp.context.JspTilesRequestContext} -  JSPException while
including path '/sso-saml/add_service_provider.jsp'.
{org.apache.tiles.jsp.context.JspTilesRequestContext}
javax.servlet.jsp.JspException: ServletException while including page.
at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:102)
at
org.apache.tiles.jsp.context.JspTilesRequestContext.include(JspTilesRequestContext.java:88)
at
org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch(JspTilesRequestContext.java:82)
at
org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:465)
at
org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:140)
at
org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:117)
at
org.apache.tiles.jsp.taglib.RenderTagSupport.execute(RenderTagSupport.java:171)
at
org.apache.tiles.jsp.taglib.RoleSecurityTagSupport.doEndTag(RoleSecurityTagSupport.java:75)
at
org.apache.tiles.jsp.taglib.ContainerTagSupport.doEndTag(ContainerTagSupport.java:80)
at
org.apache.jsp.admin.layout.template_jsp._jspx_meth_tiles_005finsertAttribute_005f7(template_jsp.java:661)
at
org.apache.jsp.admin.layout.template_jsp._jspService(template_jsp.java:377)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:439)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
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:731)
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.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:747)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:485)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:410)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:337)
at
org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.forward(RequestDispatcherAdaptor.java:30)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.forward(ContextPathServletAdaptor.java:362)
at
org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(ServletTilesRequestContext.java:198)
at
org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(ServletTilesRequestContext.java:185)
at
org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:419)
at
org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:370)
at org.wso2.carbon.ui.action.ActionHelper.render(ActionHelper.java:52)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:101)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
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

[Dev] WSO2 EMM 2.2.0-BETA2 is Released.

[Kamidu Punchihewa]

WSO2 Enterprise Mobility Manager 2.2.0-BETA2 is released!

WSO2 Enterprise Mobility Manager (WSO2 EMM) is a 100% open source,
comprehensive platform that addresses mobile computing challenges which
enterprises face today. WSO2 EMM supports iOS, Android & Windows devices
and helps organizations deal with both "corporate-owned,
personally-enabled" (COPE) devices and employee owned devices with the
"bring-your-own-device" (BYOD) ownership schemes.

Built on a generic device management framework (i.e. WSO2 Connected Device
Management Framework) that can be extended to support many other device
platforms, WSO2 EMM offers better scalability with its rich architecture,
supporting horizontal as well as vertical scaling of associated components.
Whether it is device configuration management, policy enforcement,
app-management, device data security or compliance monitoring, WSO2 EMM
offers a single enterprise grade platform for all your mobile computing
needs.



*Please find the additional bug fixes and Improvements introduced in this
release :*
Bug Fixes

   - [EMM-1620 ] - Enrolment iOS 10
   error


   - [EMM-1129 ] - Unable to log in
   to EMM console after configuring SSO
   - [EMM-1185 ] - Sort policies by
   platform and status is not functioning
   - [EMM-1249 ] - Unnecessary
   Jaggery related logs are printed on the console during the server start-up
   - [EMM-1321 ] - WindowLeaked
   exception in Android agent
   - [EMM-1333 ] - Users created
   through EMM console can not be given permission to login to AppStore
   - [EMM-1342 ] - When policy
   bundle apply, existing policy should revoke
   - [EMM-1420 ] - Profile doesn't
   get applied when device is locked
   - [EMM-1445 ] - "Mobile App"
   permission for "store-admin" role should be assigned by default
   - [EMM-1461 ] - Edit, Delete,
   Change Password option buttons on top of the User views in User Management
   page, will not show the option in word however the API name is shown in the
   browser
   - [EMM-1515 ] - Irregular
   failures for Register Oauth App, Access Token Generation and Device
   Registration calls when the concurrency reaches at around 10 threads
   - [EMM-1523 ] - Device Monitoring
   Dashboard not found (EMM analytics dashboard)
   - [EMM-1530 ] - During load test
   - Failed to authenticate the incoming request due to error in permission
   initialization - For the actually working API methods
   - [EMM-1587 ] - Unneccessary
   details included in user enrollment invitation email body
   - [EMM-1596 ] -
   NullPointerException thrown when editing a user of secondary user store
   - [EMM-1601 ] - Sorting doesn't
   apply for enrolled devices according to sorting options
   - [EMM-1619 ] - Unable to sort
   according to platform and status for policies
   - [EMM-1629 ] -
   EventAdapterConfigHelper error at server startup
   - [EMM-1637 ] - SQLException
   observed in MySQL Dsetup
   - [EMM-1639 ] - Continous
   clicking of a notification header redirects to a 404 Page
   - [EMM-1649 ] - iOS agent
   unregistration fails
   - [EMM-1654 ] - Difficult to view
   the OK button on device when the message has few characters
   - [EMM-1656 ] - Platform
   Configurations - Android Configurations Save page does not do any
   interaction action while the configuration is saved
   - [EMM-1657 ] - Unable to change
   the password of logged in user in EMM Console
   - [EMM-1658 ] - A user with only
   'login' and 'view users' permissions can change passwords of admin users in
   EMM Console
   - [EMM-1660 ] - Device
   Information Page load error at the first loading after device registration
   - Windows
   - [EMM-1661 ] - Unable to change
   the password of a user of secondary user store in EMM Console
   - [EMM-1662 ] - [UI] Change of
   name of the highest priority policy doesn't affect the name under Policy
   Compliance at first
   - [EMM-1663 

Re: [Dev] [IS] C5 Support for filtering

[Chamila Wijayarathna]

Hi Johann, Vindula,

On Tue, Oct 18, 2016 at 3:59 PM, Johann Nallathamby  wrote:

>
>
> On Tue, Oct 18, 2016 at 10:05 AM, Vindula Jayawardana 
> wrote:
>
>> Hi All,
>>
>> With the current user core implementation we support only the equal
>> filter (e.g. userName Eq "john"). However SCIM 2.0 specification [1]
>> specify total of 10 such simple filters and complex filters which are
>> combinations of simple filters using logical and grouping operators (e.g.
>> userType ne "Employee" and not (emails co "example.com" or emails.value
>> co "example.org")). As we are in the process of C5 implementation, have
>> we considered the other filter type implementations as well?
>>
>
> Yes we need to consider these features in the extended user-core
> implementation.
>
>>
>> Moreover if we are supporting the complex filters, are we supporting it
>> by simple filter by filter basis or the entire complex filter as a whole?
>> If we are looking for the simple filter by filter basis, there will be
>> performance issues as well.
>>
>
> It is better if we provide complex filters from extended user-core itself
> for performance reasons. However if time doesn't permit to implement all
> those APIs, we can have a scim UserManager implementation which will call
> multiple simple filters and combine the result and return. Obviously as you
> said performance of such implementation will be low. But it is acceptable
> as an interim solution until extended user-core implementation supports all
> the filters.
>
Can you please explain, what you refer as complex filters here? I think we
need to implement operators listed in table 3 and 4 in the specification
and implement a generic way to build complex queries reusing them. I don't
think it would be practical to more complex filters, there can be large
amount of complex filters that can be created by combining these simple
filter. Please correct me if I'm wrong.

Also what different would it made when we are handling these filters in
user-core level and when handling using scimUserManager level? Are you
reffering to the fact that when we need "username sw a" , we can retrieve
only  the users who have username start with 'a' from database/ldap, so
that we can achieve higher performance?

In addition to that, I believe it would be good to consider other SCIM
operations such as sorting and pagination at the same time. If we can come
up with a generic design, that would be better. Otherwise, we'll have to
put a huge effort to embed those functionalities again.

Cheers
-Chamila

>
>> Any thoughts on the matter is highly appreciated.
>>
>> [1] https://tools.ietf.org/html/rfc7644#section-3.4.2.2
>>
>> Thank you,
>>
>> *Vindula Jayawardana*
>> Trainee Software Engineer
>> Mobile : +94 713 462554
>> vind...@wso2.com
>>
>
>
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Technical Lead & Product Lead of WSO2 Identity Server
> Governance Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Chamila Dilshan Wijayarathna,
PhD Research Student
The University of New South Wales (UNSW Canberra)
Australian Centre of Cyber Security
Australian Defence Force Academy
PO Box 7916, Canberra BA ACT 2610
Australia
Mobile:(+61)416895795
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Carbon 4.4.x] Ensure that a piece of code is run after the server is started

[Isuru Haththotuwa]

Can I use [1] to achieve $subject?

The requirement is like this. A particular resource in registry will be
updated by several components. I need to update the same resource, and need
to make sure the changes are not over written by some other component. In
other words, need to update it last.

[1]. https://docs.wso2.com/display/Carbon443/Server+Startup+Observer

-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Why some artefacts are put inside tar?

[Ruwan Abeykoon]

Thanks for the information Sajith.

-
Ruwan

On Tue, Oct 18, 2016 at 3:48 PM, SajithAR Ariyarathna 
wrote:

> Hi Ruwan,
>
> Current UUF Maven plugin bundles UUF Themes as .tar archives to identify
> them separately (from UUF Components). This is a temporary workaround. In
> future, both UUF Themes and Components will be bundle as .zip files. I'm
> currently working on this.
>
> Thanks.
>
> On Tue, Oct 18, 2016 at 3:43 PM, Ruwan Abeykoon  wrote:
>
>> Hi UUF team,
>> $subject,
>> I think we need to compress them too; to conserve the disk space on nexus
>> and local repos.
>> I checked, we can generally zip a generated tar at least 60%.
>>
>> Or, Should we comeup with another archive extension? (e.g. uar - UI
>> artefact archive) ?
>>
>> WDYT?
>>
>> Cheers,
>> Ruwan
>>
>>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Software Engineer; WSO2, Inc.;  http://wso2.com/
> 
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please release the repo

[Rushmin Fernando]

+Dinusha

Mobile : +94775615183

On Oct 18, 2016 3:43 PM, "Rushmin Fernando"  wrote:

> Staging URL : https://maven.wso2.org/nexus/content/repositories/
> orgwso2carbonidentity-1242
>
> Mobile : +94775615183
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Why some artefacts are put inside tar?

[SajithAR Ariyarathna]

Hi Ruwan,

Current UUF Maven plugin bundles UUF Themes as .tar archives to identify
them separately (from UUF Components). This is a temporary workaround. In
future, both UUF Themes and Components will be bundle as .zip files. I'm
currently working on this.

Thanks.

On Tue, Oct 18, 2016 at 3:43 PM, Ruwan Abeykoon  wrote:

> Hi UUF team,
> $subject,
> I think we need to compress them too; to conserve the disk space on nexus
> and local repos.
> I checked, we can generally zip a generated tar at least 60%.
>
> Or, Should we comeup with another archive extension? (e.g. uar - UI
> artefact archive) ?
>
> WDYT?
>
> Cheers,
> Ruwan
>
>


-- 
Sajith Janaprasad Ariyarathna
Software Engineer; WSO2, Inc.;  http://wso2.com/

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

[Dev] Please release the repo

[Rushmin Fernando]

Staging URL :
https://maven.wso2.org/nexus/content/repositories/orgwso2carbonidentity-1242

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

[Dev] [UUF] Why some artefacts are put inside tar?

[Ruwan Abeykoon]

Hi UUF team,
$subject,
I think we need to compress them too; to conserve the disk space on nexus
and local repos.
I checked, we can generally zip a generated tar at least 60%.

Or, Should we comeup with another archive extension? (e.g. uar - UI
artefact archive) ?

WDYT?

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

Re: [Dev] [IS] C5 Support for filtering

[Gayan Gunawardana]

On Tue, Oct 18, 2016 at 10:29 AM, Johann Nallathamby 
wrote:

>
>
> On Tue, Oct 18, 2016 at 10:05 AM, Vindula Jayawardana 
> wrote:
>
>> Hi All,
>>
>> With the current user core implementation we support only the equal
>> filter (e.g. userName Eq "john"). However SCIM 2.0 specification [1]
>> specify total of 10 such simple filters and complex filters which are
>> combinations of simple filters using logical and grouping operators (e.g.
>> userType ne "Employee" and not (emails co "example.com" or emails.value
>> co "example.org")). As we are in the process of C5 implementation, have
>> we considered the other filter type implementations as well?
>>
>
> Yes we need to consider these features in the extended user-core
> implementation.
>
>>
>> Moreover if we are supporting the complex filters, are we supporting it
>> by simple filter by filter basis or the entire complex filter as a whole?
>> If we are looking for the simple filter by filter basis, there will be
>> performance issues as well.
>>
>
> It is better if we provide complex filters from extended user-core itself
> for performance reasons. However if time doesn't permit to implement all
> those APIs, we can have a scim UserManager implementation which will call
> multiple simple filters and combine the result and return. Obviously as you
> said performance of such implementation will be low. But it is acceptable
> as an interim solution until extended user-core implementation supports all
> the filters.
>
+1 for the interim solution. Can't we have some caching mechanism in scim
UserManager level to improve performance ?

>
>> Any thoughts on the matter is highly appreciated.
>>
>> [1] https://tools.ietf.org/html/rfc7644#section-3.4.2.2
>>
>> Thank you,
>>
>> *Vindula Jayawardana*
>> Trainee Software Engineer
>> Mobile : +94 713 462554
>> vind...@wso2.com
>>
>
>
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Technical Lead & Product Lead of WSO2 Identity Server
> Governance Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>



-- 
Gayan Gunawardana
Software Engineer; WSO2 Inc.; http://wso2.com/
Email: ga...@wso2.com
Mobile: +94 (71) 8020933
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] Lots of MQTT connection errors after changing the port offset in carbon.xml in IoTS alpha release

[Lakshani Gamage]

Hi Zhanwen,

Did you follow all the steps in [1]?

[1]
https://docs.wso2.com/display/IoTS100/Configuring+WSO2+IoTS+with+Port+Offset

Thanks,
Lakshani

On Tue, Oct 18, 2016 at 2:48 PM, 云展智创  wrote:

> Hi all,
>
> I got lots of MQTT errors after changing the port offset in carbon.xml and
> restart the server with IoTS alpha release. The new agent could not connect
> to the IoTS with mqtt using the new offset port.
>
> The errors were:
>
> 1. [2016-10-18 17:11:29,630] ERROR - OAuth2BasedMQTTAuthenticator Error
> on connecting with the validation endpoint.
> org.apache.axis2.AxisFault: Connection refused
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>
> 2. [2016-10-18 17:11:29,684]  INFO - ProtocolProcessor Lost connection
> with client paho952169391265634
> [2016-10-18 17:11:29,684]  WARN - ProtocolProcessor
> MQTTAuthorizationSubject for client ID paho952169391265634 is not removed
> since the entry does not exist
> [2016-10-18 17:11:29,690] ERROR - MQTTAdapterListener MQTT Exception
> occurred when starting listener
> Bad user name or password (4)
> at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.
> createMqttException(ExceptionHelper.java:28)
> at org.eclipse.paho.client.mqttv3.internal.ClientState.
> notifyReceivedAck(ClientState.java:885)
> at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.
> run(CommsReceiver.java:118)
> at java.lang.Thread.run(Thread.java:745)
>
> Anyone knows what happens?
>
> －－
> Zhanwen Zhou (Jason)
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: IOT, API Management
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Lakshani Gamage

*Software Engineer, WSO2*

*Mobile : +94 71 5478184 <%2B94%20%280%29%20773%20451194>*
*Blog : http://lakshanigamage.blogspot.com/
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] No SCM URL was provided to perform the release Issue when releasing carbon-device-mgt-plugins

[Farasath Ahamed]

Hi Kamidu,

Can you check from which location you are running the* mvn release:perform*
command?

I have faced a similar issue when I accidently ran the release command from
temporary artifacts folder I created for sanity checks.


Thanks,

Farasath Ahamed
Software Engineer, WSO2 Inc.; http://wso2.com
Mobile: +94777603866
Blog: blog.farazath.com
Twitter: @farazath619 




On Tue, Oct 18, 2016 at 11:37 AM, Abimaran Kugathasan 
wrote:

> Hi Kamindu,
>
> This error can occur for many reasons, one could be you have deleted the
> temporary files which are created in the release:prepare stage. In this
> case, you have to revert the change done through release:prepare and redo
> everything from starting. :)
>
> On Mon, Oct 17, 2016 at 11:45 PM, Kamidu Punchihewa 
> wrote:
>
>> Hi All,
>>
>> I am getting this issue while releasing the "carbon-device-mgt-plugins".
>> I have tried releasing few time with different repository locations and
>> after getting a new session also. Still getting this error.
>>
>> As given below the SCM URL is available on the pom file.
>>
>> 
>> https://github.com/wso2/carbon-device-mgt-plugins.git
>> 
>> scm:git:https://github.com/wso2/carbon-device-mgt-plugins.git
>> 
>> 
>> scm:git:https://github.com/wso2/carbon-device-mgt-plugins.git
>> HEAD
>> 
>>
>> Please find the console out put given below,
>>
>> [INFO] Scanning for projects...
>> [INFO] 
>> 
>> [INFO] Reactor Build Order:
>> [INFO]
>> [INFO] WSO2 Carbon - Device Management Plugins Parent
>> [INFO] WSO2 Carbon - Mobile Plugins
>> [INFO] WSO2 Carbon - Mobile Plugins
>> [INFO] WSO2 Carbon - Mobile Device Management Impl
>> [INFO] WSO2 Carbon - Mobile Plugins
>> [INFO] WSO2 Carbon - Mobile Device Management Android Impl
>> [INFO] WSO2 Carbon - Android JAX-RS API
>> [INFO] WSO2 Carbon - Mobile Android UI
>> [INFO] WSO2 Carbon - Mobile Plugins
>> [INFO] WSO2 Carbon - Mobile Device Management Windows Impl
>> [INFO] WSO2 Carbon - Windows JAX-RS API
>> [INFO] WSO2 Carbon - Mobile Windows UI
>> [INFO] WSO2 Carbon - EMM Server UI
>> [INFO] WSO2 Carbon - Startup Handler That Prints MDM End-User Web-App URL
>> [INFO] WSO2 Carbon - IoT Plugins
>> [INFO] WSO2 Carbon - Arduino Plugin
>> [INFO] WSO2 Carbon - IoT Server Android Sense Analytics capp
>> [INFO] WSO2 Carbon - IoT Base Plugin
>> [INFO] WSO2 Carbon - IoT Device Management Common Impl
>> [INFO] WSO2 Carbon - AndroidSense DeviceType Plugin
>> [INFO] WSO2 Carbon - Android Sense API
>> [INFO] WSO2 Carbon - IoT Server Android Sense UI
>> [INFO] WSO2 Carbon - Arduino Plugin
>> [INFO] WSO2 Carbon - IoT Server Arduino Management Plugin
>> [INFO] WSO2 Carbon - IoT Server Arduino Service API
>> [INFO] WSO2 Carbon - IoT Server Arduino UI
>> [INFO] WSO2 Carbon - IoT Server Arduino Analytics capp
>> [INFO] WSO2 Carbon - Arduino Plugin
>> [INFO] WSO2 Carbon - IoT Server RaspberryPi Management Plugin
>> [INFO] WSO2 Carbon - IoT Server RaspberryPi UI
>> [INFO] WSO2 Carbon - IoT Server RaspberryPi API
>> [INFO] WSO2 Carbon - IoT Server Raspberrypi Analytics capp
>> [INFO] WSO2 Carbon - Device Mgt Input Adaptor Extensions Module
>> [INFO] WSO2 Carbon - Arduino Plugin
>> [INFO] WSO2 Carbon - IoT Server VirtualFireAlarm Management Plugin
>> [INFO] WSO2 Carbon - IoT Server Virtual Firealarm UI
>> [INFO] WSO2 Carbon - IoT Server VirtualFireAlarm Advanced Agent
>> [INFO] WSO2 Carbon - IoT Server VirtualFireAlarm Agent
>> [INFO] WSO2 Carbon - IoT Server VirtualFireAlarm API
>> [INFO] WSO2 Carbon - IoT Server SCEP Server API
>> [INFO] WSO2 Carbon - IoT Server UI
>> [INFO] WSO2 Carbon - Device Mgt Output MQTT Adaptor Module
>> [INFO] WSO2 Carbon - Device Mgt Output MQTT Adaptor Module
>> [INFO] WSO2 Carbon - Event Output UI Adapter Module
>> [INFO] WSO2 - Webapp for UI Output Event Adapter
>> [INFO] WSO2 Carbon - Device Mgt Input Adaptor Module - Http
>> [INFO] WSO2 Carbon - Device Mgt Input Adaptor Module - MQTT
>> [INFO] WSO2 Carbon - Device Mgt Input Adaptor Module - XMPP
>> [INFO] WSO2 Carbon - IoT Analytics Scripts
>> [INFO] WSO2 Carbon - IoT Server  Analytics C-APP
>> [INFO] WSO2 Carbon - Mobile Plugins Extensions
>> [INFO] WSO2 Carbon - App Manager WSO2 MDM OSGI Connector Component
>> [INFO] WSO2 Carbon - Device Management EMM Plugins Feature
>> [INFO] WSO2 Carbon - Device Management EMM Base Plugin Feature
>> [INFO] WSO2 Carbon - Mobile Device Management Feature
>> [INFO] WSO2 Carbon - Device Management Android Plugin Feature
>> [INFO] WSO2 Carbon - Android Device Management Feature
>> [INFO] WSO2 Carbon - Device Management Windows Plugin Feature
>> [INFO] WSO2 Carbon - Windows Device Management Feature
>> [INFO] WSO2 Carbon - Device Management IoT Plugins Feature
>> [INFO] WSO2 Carbon - IoT Server IoT Analytics Feature
>> [INFO] WSO2 Carbon - IoT Server Analytics Feature
>> [INFO] WSO2 Carbon - IoT Server Android 

[Dev] [IoTS] Lots of MQTT connection errors after changing the port offset in carbon.xml in IoTS alpha release

[云展智创]

Hi all,

I got lots of MQTT errors after changing the port offset in carbon.xml and 
restart the server with IoTS alpha release. The new agent could not connect to 
the IoTS with mqtt using the new offset port.

The errors were:

1. [2016-10-18 17:11:29,630] ERROR - OAuth2BasedMQTTAuthenticator Error on 
connecting with the validation endpoint.
org.apache.axis2.AxisFault: Connection refused
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)

2. [2016-10-18 17:11:29,684]  INFO - ProtocolProcessor Lost connection with 
client paho952169391265634
[2016-10-18 17:11:29,684]  WARN - ProtocolProcessor MQTTAuthorizationSubject 
for client ID paho952169391265634 is not removed since the entry does not exist
[2016-10-18 17:11:29,690] ERROR - MQTTAdapterListener MQTT Exception occurred 
when starting listener
Bad user name or password (4)
at 
org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:28)
at 
org.eclipse.paho.client.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:885)
at 
org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:118)
at java.lang.Thread.run(Thread.java:745)

Anyone knows what happens?

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

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

Re: [Dev] [Siddhi] [Markov Models Extension] What is the stored location of trained Markov matrices?

[Ashen Weerathunga]

Hi Tishan,

We don't have any non-serializable objects and we are currently using CEP
persistence option to persist the state of Markov extension. But currently,
we cannot export the Markov matrix separately as a csv. Therefore the
Markov matrix generated by the extension cannot be used externally IMO.

Thanks,
Ashen

On Tue, Oct 18, 2016 at 12:45 PM, Tishan Dahanayakage 
wrote:

> Ashen,
>
> Can't we use CEP persistence option to persist the state of Markov
> extension to file system and re-use? Do we have any non-serializable
> objects?
>
> /Tishan
>
> On Tue, Oct 18, 2016 at 12:28 PM, Ashen Weerathunga 
> wrote:
>
>> Hi Bhashinee,
>>
>> In the current implementation, we are storing the Markov matrix using a
>> hashmap. Therefore if you shut down the server it won't be persisted. But
>> we have provided a facility to input an already built Markov matrix as a
>> CSV file. So in such case, you can use that option to input the matrix
>> again and start training. Please refer docs[1] for more details.
>>
>> [1]https://docs.wso2.com/pages/viewpage.action?pageId=56993859
>>
>> Best regards,
>> Ashen
>>
>>
>> On Tue, Oct 18, 2016 at 10:08 AM, Bhashinee Nirmali > > wrote:
>>
>>> Hi All,
>>>
>>> I'm trying the Markov Models Extension of WSO2 CEP. I need to know the
>>> location where the newly built matrices are stored in. And do I need to
>>> built the matrix again after shutting down the CEP or is the created matrix
>>> still there in the memory?
>>>
>>> Thanks
>>>
>>> Undergraduate
>>> Faculty of Information Technology
>>> University of Moratuwa
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Ashen Weerathunga*
>> Software Engineer
>> WSO2 Inc.: http://wso2.com
>> lean.enterprise.middleware
>>
>> Email: as...@wso2.com
>> Mobile: tel:94716042995 <94716042995>
>> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
>> *
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Tishan Dahanayakage
> Senior Software Engineer
> WSO2, Inc.
> Mobile:+94 716481328
>
> 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, re-transmit, 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.
>



-- 
*Ashen Weerathunga*
Software Engineer
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware

Email: as...@wso2.com
Mobile: tel:94716042995 <94716042995>
LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
*

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

Re: [Dev] [Siddhi] [Markov Models Extension] What is the stored location of trained Markov matrices?

[Tishan Dahanayakage]

Ashen,

Can't we use CEP persistence option to persist the state of Markov
extension to file system and re-use? Do we have any non-serializable
objects?

/Tishan

On Tue, Oct 18, 2016 at 12:28 PM, Ashen Weerathunga  wrote:

> Hi Bhashinee,
>
> In the current implementation, we are storing the Markov matrix using a
> hashmap. Therefore if you shut down the server it won't be persisted. But
> we have provided a facility to input an already built Markov matrix as a
> CSV file. So in such case, you can use that option to input the matrix
> again and start training. Please refer docs[1] for more details.
>
> [1]https://docs.wso2.com/pages/viewpage.action?pageId=56993859
>
> Best regards,
> Ashen
>
>
> On Tue, Oct 18, 2016 at 10:08 AM, Bhashinee Nirmali 
> wrote:
>
>> Hi All,
>>
>> I'm trying the Markov Models Extension of WSO2 CEP. I need to know the
>> location where the newly built matrices are stored in. And do I need to
>> built the matrix again after shutting down the CEP or is the created matrix
>> still there in the memory?
>>
>> Thanks
>>
>> Undergraduate
>> Faculty of Information Technology
>> University of Moratuwa
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Ashen Weerathunga*
> Software Engineer
> WSO2 Inc.: http://wso2.com
> lean.enterprise.middleware
>
> Email: as...@wso2.com
> Mobile: tel:94716042995 <94716042995>
> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
> *
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Tishan Dahanayakage
Senior Software Engineer
WSO2, Inc.
Mobile:+94 716481328

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,
re-transmit, 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] [Siddhi] [Markov Models Extension] What is the stored location of trained Markov matrices?

[Ashen Weerathunga]

Hi Bhashinee,

In the current implementation, we are storing the Markov matrix using a
hashmap. Therefore if you shut down the server it won't be persisted. But
we have provided a facility to input an already built Markov matrix as a
CSV file. So in such case, you can use that option to input the matrix
again and start training. Please refer docs[1] for more details.

[1]https://docs.wso2.com/pages/viewpage.action?pageId=56993859

Best regards,
Ashen


On Tue, Oct 18, 2016 at 10:08 AM, Bhashinee Nirmali 
wrote:

> Hi All,
>
> I'm trying the Markov Models Extension of WSO2 CEP. I need to know the
> location where the newly built matrices are stored in. And do I need to
> built the matrix again after shutting down the CEP or is the created matrix
> still there in the memory?
>
> Thanks
>
> Undergraduate
> Faculty of Information Technology
> University of Moratuwa
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ashen Weerathunga*
Software Engineer
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware

Email: as...@wso2.com
Mobile: tel:94716042995 <94716042995>
LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
*

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

Re: [Dev] No SCM URL was provided to perform the release Issue when releasing carbon-device-mgt-plugins

[Abimaran Kugathasan]

Hi Kamindu,

This error can occur for many reasons, one could be you have deleted the
temporary files which are created in the release:prepare stage. In this
case, you have to revert the change done through release:prepare and redo
everything from starting. :)

On Mon, Oct 17, 2016 at 11:45 PM, Kamidu Punchihewa 
wrote:

> Hi All,
>
> I am getting this issue while releasing the "carbon-device-mgt-plugins". I
> have tried releasing few time with different repository locations and after
> getting a new session also. Still getting this error.
>
> As given below the SCM URL is available on the pom file.
>
> 
> https://github.com/wso2/carbon-device-mgt-plugins.git
> 
> scm:git:https://github.com/wso2/carbon-device-mgt-plugins.git
> 
> 
> scm:git:https://github.com/wso2/carbon-device-mgt-plugins.git
> HEAD
> 
>
> Please find the console out put given below,
>
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] WSO2 Carbon - Device Management Plugins Parent
> [INFO] WSO2 Carbon - Mobile Plugins
> [INFO] WSO2 Carbon - Mobile Plugins
> [INFO] WSO2 Carbon - Mobile Device Management Impl
> [INFO] WSO2 Carbon - Mobile Plugins
> [INFO] WSO2 Carbon - Mobile Device Management Android Impl
> [INFO] WSO2 Carbon - Android JAX-RS API
> [INFO] WSO2 Carbon - Mobile Android UI
> [INFO] WSO2 Carbon - Mobile Plugins
> [INFO] WSO2 Carbon - Mobile Device Management Windows Impl
> [INFO] WSO2 Carbon - Windows JAX-RS API
> [INFO] WSO2 Carbon - Mobile Windows UI
> [INFO] WSO2 Carbon - EMM Server UI
> [INFO] WSO2 Carbon - Startup Handler That Prints MDM End-User Web-App URL
> [INFO] WSO2 Carbon - IoT Plugins
> [INFO] WSO2 Carbon - Arduino Plugin
> [INFO] WSO2 Carbon - IoT Server Android Sense Analytics capp
> [INFO] WSO2 Carbon - IoT Base Plugin
> [INFO] WSO2 Carbon - IoT Device Management Common Impl
> [INFO] WSO2 Carbon - AndroidSense DeviceType Plugin
> [INFO] WSO2 Carbon - Android Sense API
> [INFO] WSO2 Carbon - IoT Server Android Sense UI
> [INFO] WSO2 Carbon - Arduino Plugin
> [INFO] WSO2 Carbon - IoT Server Arduino Management Plugin
> [INFO] WSO2 Carbon - IoT Server Arduino Service API
> [INFO] WSO2 Carbon - IoT Server Arduino UI
> [INFO] WSO2 Carbon - IoT Server Arduino Analytics capp
> [INFO] WSO2 Carbon - Arduino Plugin
> [INFO] WSO2 Carbon - IoT Server RaspberryPi Management Plugin
> [INFO] WSO2 Carbon - IoT Server RaspberryPi UI
> [INFO] WSO2 Carbon - IoT Server RaspberryPi API
> [INFO] WSO2 Carbon - IoT Server Raspberrypi Analytics capp
> [INFO] WSO2 Carbon - Device Mgt Input Adaptor Extensions Module
> [INFO] WSO2 Carbon - Arduino Plugin
> [INFO] WSO2 Carbon - IoT Server VirtualFireAlarm Management Plugin
> [INFO] WSO2 Carbon - IoT Server Virtual Firealarm UI
> [INFO] WSO2 Carbon - IoT Server VirtualFireAlarm Advanced Agent
> [INFO] WSO2 Carbon - IoT Server VirtualFireAlarm Agent
> [INFO] WSO2 Carbon - IoT Server VirtualFireAlarm API
> [INFO] WSO2 Carbon - IoT Server SCEP Server API
> [INFO] WSO2 Carbon - IoT Server UI
> [INFO] WSO2 Carbon - Device Mgt Output MQTT Adaptor Module
> [INFO] WSO2 Carbon - Device Mgt Output MQTT Adaptor Module
> [INFO] WSO2 Carbon - Event Output UI Adapter Module
> [INFO] WSO2 - Webapp for UI Output Event Adapter
> [INFO] WSO2 Carbon - Device Mgt Input Adaptor Module - Http
> [INFO] WSO2 Carbon - Device Mgt Input Adaptor Module - MQTT
> [INFO] WSO2 Carbon - Device Mgt Input Adaptor Module - XMPP
> [INFO] WSO2 Carbon - IoT Analytics Scripts
> [INFO] WSO2 Carbon - IoT Server  Analytics C-APP
> [INFO] WSO2 Carbon - Mobile Plugins Extensions
> [INFO] WSO2 Carbon - App Manager WSO2 MDM OSGI Connector Component
> [INFO] WSO2 Carbon - Device Management EMM Plugins Feature
> [INFO] WSO2 Carbon - Device Management EMM Base Plugin Feature
> [INFO] WSO2 Carbon - Mobile Device Management Feature
> [INFO] WSO2 Carbon - Device Management Android Plugin Feature
> [INFO] WSO2 Carbon - Android Device Management Feature
> [INFO] WSO2 Carbon - Device Management Windows Plugin Feature
> [INFO] WSO2 Carbon - Windows Device Management Feature
> [INFO] WSO2 Carbon - Device Management IoT Plugins Feature
> [INFO] WSO2 Carbon - IoT Server IoT Analytics Feature
> [INFO] WSO2 Carbon - IoT Server Analytics Feature
> [INFO] WSO2 Carbon - IoT Server Android Sense Device Feature
> [INFO] WSO2 Carbon - IoT Server Android Sense Feature
> [INFO] WSO2 Carbon - IoT Server Arduino Device Feature
> [INFO] WSO2 Carbon - IoT Server Arduino Feature
> [INFO] WSO2 Carbon - IoT Server RaspberryPi Device Feature
> [INFO] WSO2 Carbon - IoT Server RaspberryPi Feature
> [INFO] WSO2 Carbon - IoT Server VirtualFireAlarm Device Feature
> [INFO] WSO2 Carbon - IoT Server VirtualFireAlarm Feature
> [INFO] WSO2 Carbon - Device Management IoT Base Plugin Feature
> [INFO] WSO2 Carbon - IoT Device Management Feature
> [INFO] WSO2 Carbon - IoT Device Management Feature
> [INFO] IoT Server Device