date:20160127

Re: [Architecture] [EMM] Android agent auto enrollment

2016-01-27 Thread Harshan Liyanage

Hi,

Is the service app signed by the vendor? if it so why don't we use the
service app to get the serial number?

Good point. I think that should be possible. If so we can skip steps 6 and
7.

Thanks,

Harshan Liyanage
Software Engineer
Mobile: *+94724423048*
Email: hars...@wso2.com
Blog : http://harshanliyanage.blogspot.com/
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.

On Thu, Jan 28, 2016 at 11:05 AM, Chathura Dilan  wrote:

> Hi Inosh,
>
> Could you explain why do you need connect it with the computer to retrieve
> the serial number?
> Is the service app signed by the vendor? if it so why don't we use the
> service app to get the serial number?
>
> On Thu, Jan 28, 2016 at 10:34 AM, Harshan Liyanage 
> wrote:
>
>> Hi Inosh,
>>
>> In the step 11, you have mentioned that the device sends authentication
>> request, generate access and refresh tokens and send it to device. However
>> you need client credentials (client key, secret) in-order to generate
>> access tokens. How are you planing to get these client credentials prior to
>> generating access tokens? In the existing EMM implementation we use
>> Dynamic-client-registration to do that. I think we can use the same here.
>> However we need to modify the flow diagram to reflect that.
>>
>> Thanks.
>>
>> Harshan Liyanage
>> Software Engineer
>> Mobile: *+94724423048*
>> Email: hars...@wso2.com
>> Blog : http://harshanliyanage.blogspot.com/
>> *WSO2, Inc. :** wso2.com *
>> lean.enterprise.middleware.
>>
>> On Tue, Jan 26, 2016 at 2:07 PM, Inosh Perera  wrote:
>>
>>> Hi Milan,
>>>
>>> +1 Cant we use an embedded QR code reader or some other way to retrieve
>>> this token?
>>> Using QR code is possible and it would make the process usable in all
>>> many platforms oppose to ADB where only Android is able to work with.
>>> Although when it comes to COPE scenario, mostly it is Android devices and
>>> it is a set of known devices so we can assume the driver change is not much
>>> of a concern. So under the above assumption at the time of device getting
>>> connected, we can think the drivers are already installed, which makes it
>>> much easier to enroll because the user only needs to plugin the device. In
>>> BYOP/CYOD scenario, this can be problematic.
>>>
>>> Regards,
>>> Inosh
>>>
>>>
>>> On Tue, Jan 26, 2016 at 12:29 PM, Milan Perera  wrote:
>>>
 Hi Inosh,

 My concerns for the above proposed method as follows.

 AFAIU, in here what we are trying to do is to minimize the user
 interaction with the device as much as possible for the auto enrolment
 scenario.
 However according to above method, user should have to connect the
 device to a machine and has to run a script as well, hence it needs more
 interaction.
 Also, if we use ADB for this, there may be instance where PC does not
 recognize the device, which ends up manually installing drivers and etc.

 Why do we have to use ADB in order to do this?

 Cant we use an embedded QR code reader or some other way to retrieve
 this token?

 Regards,

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

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


>>>
>>>
>>> --
>>> Inosh Perera
>>> Software Engineer, WSO2 Inc.
>>> Tel: 077813 7285, 0785293686
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Regards,
>
> Chatura Dilan Perera
> *Senior Software Engineer** - WSO2 Inc.*
> www.dilan.me
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [EMM] Android agent auto enrollment

2016-01-27 Thread Chathura Dilan

Hi Inosh,

Could you explain why do you need connect it with the computer to retrieve
the serial number?
Is the service app signed by the vendor? if it so why don't we use the
service app to get the serial number?

On Thu, Jan 28, 2016 at 10:34 AM, Harshan Liyanage  wrote:

> Hi Inosh,
>
> In the step 11, you have mentioned that the device sends authentication
> request, generate access and refresh tokens and send it to device. However
> you need client credentials (client key, secret) in-order to generate
> access tokens. How are you planing to get these client credentials prior to
> generating access tokens? In the existing EMM implementation we use
> Dynamic-client-registration to do that. I think we can use the same here.
> However we need to modify the flow diagram to reflect that.
>
> Thanks.
>
> Harshan Liyanage
> Software Engineer
> Mobile: *+94724423048*
> Email: hars...@wso2.com
> Blog : http://harshanliyanage.blogspot.com/
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>
> On Tue, Jan 26, 2016 at 2:07 PM, Inosh Perera  wrote:
>
>> Hi Milan,
>>
>> +1 Cant we use an embedded QR code reader or some other way to retrieve
>> this token?
>> Using QR code is possible and it would make the process usable in all
>> many platforms oppose to ADB where only Android is able to work with.
>> Although when it comes to COPE scenario, mostly it is Android devices and
>> it is a set of known devices so we can assume the driver change is not much
>> of a concern. So under the above assumption at the time of device getting
>> connected, we can think the drivers are already installed, which makes it
>> much easier to enroll because the user only needs to plugin the device. In
>> BYOP/CYOD scenario, this can be problematic.
>>
>> Regards,
>> Inosh
>>
>>
>> On Tue, Jan 26, 2016 at 12:29 PM, Milan Perera  wrote:
>>
>>> Hi Inosh,
>>>
>>> My concerns for the above proposed method as follows.
>>>
>>> AFAIU, in here what we are trying to do is to minimize the user
>>> interaction with the device as much as possible for the auto enrolment
>>> scenario.
>>> However according to above method, user should have to connect the
>>> device to a machine and has to run a script as well, hence it needs more
>>> interaction.
>>> Also, if we use ADB for this, there may be instance where PC does not
>>> recognize the device, which ends up manually installing drivers and etc.
>>>
>>> Why do we have to use ADB in order to do this?
>>>
>>> Cant we use an embedded QR code reader or some other way to retrieve
>>> this token?
>>>
>>> Regards,
>>>
>>> --
>>> *Milan Perera *| Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
>>> Email: mi...@wso2.com  | Web: www.wso2.com
>>> 
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Inosh Perera
>> Software Engineer, WSO2 Inc.
>> Tel: 077813 7285, 0785293686
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Regards,

Chatura Dilan Perera
*Senior Software Engineer** - WSO2 Inc.*
www.dilan.me
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [EMM] Android agent auto enrollment

2016-01-27 Thread Harshan Liyanage

Hi Inosh,

In the step 11, you have mentioned that the device sends authentication
request, generate access and refresh tokens and send it to device. However
you need client credentials (client key, secret) in-order to generate
access tokens. How are you planing to get these client credentials prior to
generating access tokens? In the existing EMM implementation we use
Dynamic-client-registration to do that. I think we can use the same here.
However we need to modify the flow diagram to reflect that.

Thanks.

Harshan Liyanage
Software Engineer
Mobile: *+94724423048*
Email: hars...@wso2.com
Blog : http://harshanliyanage.blogspot.com/
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.

On Tue, Jan 26, 2016 at 2:07 PM, Inosh Perera  wrote:

> Hi Milan,
>
> +1 Cant we use an embedded QR code reader or some other way to retrieve
> this token?
> Using QR code is possible and it would make the process usable in all many
> platforms oppose to ADB where only Android is able to work with. Although
> when it comes to COPE scenario, mostly it is Android devices and it is a
> set of known devices so we can assume the driver change is not much of a
> concern. So under the above assumption at the time of device getting
> connected, we can think the drivers are already installed, which makes it
> much easier to enroll because the user only needs to plugin the device. In
> BYOP/CYOD scenario, this can be problematic.
>
> Regards,
> Inosh
>
>
> On Tue, Jan 26, 2016 at 12:29 PM, Milan Perera  wrote:
>
>> Hi Inosh,
>>
>> My concerns for the above proposed method as follows.
>>
>> AFAIU, in here what we are trying to do is to minimize the user
>> interaction with the device as much as possible for the auto enrolment
>> scenario.
>> However according to above method, user should have to connect the device
>> to a machine and has to run a script as well, hence it needs more
>> interaction.
>> Also, if we use ADB for this, there may be instance where PC does not
>> recognize the device, which ends up manually installing drivers and etc.
>>
>> Why do we have to use ADB in order to do this?
>>
>> Cant we use an embedded QR code reader or some other way to retrieve this
>> token?
>>
>> Regards,
>>
>> --
>> *Milan Perera *| Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
>> Email: mi...@wso2.com  | Web: www.wso2.com
>> 
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Inosh Perera
> Software Engineer, WSO2 Inc.
> Tel: 077813 7285, 0785293686
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] WSO2 IoTServer 1.0.0 M2 Released!

2016-01-27 Thread Ruwan Yatawara

*WSO2 IoT Server 1.0.0 M2 Released*
Please find below, download link of the Second Milestone of WSO2 IoTServer
1.0.0.

http://builder1.us1.wso2.org/~iots/M2/wso2iots-1.0.0-SNAPSHOT.zip


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

Features

   - Implementation of Grouping Functionality in CDMF

Bug

   - [IOTS-14 ] - Issue when
   downloading Advanced Agent for virtual Fire Alarm
   - [IOTS-16 ] - Drone Analyzer
   agent download is broken
   - [IOTS-22 ] - Drone Analyzer
   agent can't download, redirect to admin page
   - [IOTS-24 ] - Digital display
   operations are not working due to access token generation failed.
   - [IOTS-25 ] - When trying to log
   into a page, login redirection drops query parameters
   - [IOTS-33 ] - Add user button
   returns 404
   - [IOTS-35 ] - Operations not
   working with API manager
   - [IOTS-36 ] - Improve
   Connected-Cup sample UI

Sub-task

   - [IOTS-29 ] - When deleting a
   user, confirmation message says EMM




Thanks and Regards,

*~ EMM / IOT Team ~*
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

2016-01-27 Thread Nadeeshaan Gunasinghe

Hi Thulasika,

This feature is not available in the WSO2 ESB 4.9.0. This is available from
in 4.10.

Thanks

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

  

Get a signature like this: Click here!


On Wed, Jan 27, 2016 at 2:05 PM, Thulasika Vijayanathan 
wrote:

> Hi ,
>
> I am implementing common init method for ESB 4.9 and 4.10. For ESB 4.10 I
> use the property mediator to store new persistent content(accessToken) in
> the registry as following:
>   expression="get-property('uri.var.accessToken')" scope="registry"/>
>
> when I enabling the connector artifact in ESB 4.9.0 I'm getting the
> following error due to scope "registry".How to proceed further?
>
> ERROR - PropertyMediatorFactory Only 'axis2' or 'transport' or
> 'axis2-client' or 'default' or 'operation' values are allowed for attribute
> scope for a property mediator, Unsupported scope registry
> [2016-01-27 13:31:53,717] ERROR - MediationLibraryAdminService Unable to
> update status for :  {org.wso2.carbon.connector}salesforcerest :: Template
> configuration : null cannot be builtfor Synapse Library artifact : newInit1
> org.apache.synapse.deployers.SynapseArtifactDeploymentException: Template
> configuration : null cannot be builtfor Synapse Library artifact : newInit1
> at
> org.apache.synapse.libraries.model.LibraryArtifact$TemplateArtifactFile.build(LibraryArtifact.java:196)
> at
> org.apache.synapse.libraries.model.LibraryArtifact.loadComponentsInto(LibraryArtifact.java:100)
> at
> org.apache.synapse.libraries.model.SynapseLibrary.loadLibrary(SynapseLibrary.java:144)
> at
> org.apache.synapse.libraries.model.SynapseLibrary.loadLibrary(SynapseLibrary.java:129)
> at
> org.apache.synapse.libraries.util.LibDeployerUtils.loadLibArtifacts(LibDeployerUtils.java:340)
> at
> org.wso2.carbon.mediation.library.service.MediationLibraryAdminService.addImport(MediationLibraryAdminService.java:100)
> at
> org.wso2.carbon.mediation.library.service.MediationLibraryAdminService.addImport(MediationLibraryAdminService.java:124)
> at
> org.wso2.carbon.mediation.library.service.MediationLibraryAdminService.updateStatus(MediationLibraryAdminService.java:436)
> 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.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
> at
> org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
> at
> org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
> at
> org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.carbon.mediation.library.stub.MediationLibraryAdminServiceStub.updateStatus(MediationLibraryAdminServiceStub.java:1476)
> at
> org.wso2.carbon.mediation.library.ui.LibraryAdminClient.updateStatus(LibraryAdminClient.java:114)
> at
> org.apache.jsp.mediation_005flibrary.import_005flib_jsp._jspService(import_005flib_jsp.java:114)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
> 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:727)
> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
> at org.wso2.carbon

Re: [Architecture] Location of SAML Components in Carbon 5

2016-01-27 Thread Supun Malinga

What are the SAML components there is for C5 ?.

On Wed, Jan 27, 2016 at 2:58 PM, Sameera Jayasoma  wrote:

> We can maintain this module inside the carbon-jaas/carbon-security
> repository.
>
> Thanks,
> Sameera.
>
> On Wed, Jan 27, 2016 at 2:31 PM, Yasiru Kassapa  wrote:
>
>> Hi,
>> During the process of developing a JAAS LoginModule for SAML
>> authentication the question arose as to which module the SAML components
>> should be put in. Because the SAML features will be used in other modules
>> as well, what would the ideal location to put these components?
>>
>> Thank you & Regards.
>>
>> --
>> Yasiru Kassapa
>> *Software Engineering Intern | WSO2*
>> Mobile : +94 (0) 77 <+94%20(0)%2077%201166613> 1166613
>> <+94+(0)+77+1166613>
>> yas...@wso2.com
>>
>
>
>
> --
> Sameera Jayasoma,
> Software Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://blog.sameera.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
> Lean . Enterprise . Middleware
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Supun Malinga,

Senior Software Engineer,
WSO2 Inc.
http://wso2.com
email: sup...@wso2.com 
mobile: +94 (0)71 56 91 321
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Location of SAML Components in Carbon 5

2016-01-27 Thread Sameera Jayasoma

We can maintain this module inside the carbon-jaas/carbon-security
repository.

Thanks,
Sameera.

On Wed, Jan 27, 2016 at 2:31 PM, Yasiru Kassapa  wrote:

> Hi,
> During the process of developing a JAAS LoginModule for SAML
> authentication the question arose as to which module the SAML components
> should be put in. Because the SAML features will be used in other modules
> as well, what would the ideal location to put these components?
>
> Thank you & Regards.
>
> --
> Yasiru Kassapa
> *Software Engineering Intern | WSO2*
> Mobile : +94 (0) 77 <+94%20(0)%2077%201166613> 1166613
> <+94+(0)+77+1166613>
> yas...@wso2.com
>

-- 
Sameera Jayasoma,
Software Architect,

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

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

[Architecture] Location of SAML Components in Carbon 5

2016-01-27 Thread Yasiru Kassapa

Hi,
During the process of developing a JAAS LoginModule for SAML authentication
the question arose as to which module the SAML components should be put in.
Because the SAML features will be used in other modules as well, what would
the ideal location to put these components?

Thank you & Regards.

-- 
Yasiru Kassapa
*Software Engineering Intern | WSO2*
Mobile : +94 (0) 77 <+94%20(0)%2077%201166613> 1166613 <+94+(0)+77+1166613>
yas...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Script tools for ESB Artifacts

2016-01-27 Thread Chanaka Fernando

Hi Dulitha,

AFAIU, we can use this tool to write our synapse configurations in a way
that we write a code in a scripting language. This tool will convert the
script into a synapse configuration. In that perspective, this is like
another DSL, but here we need to build the synapse configuration ans use
them rather than directly deploying these into the server. Is that the use
case or something else?

On Wed, Jan 27, 2016 at 10:19 AM, Susinda Perera  wrote:

> Hi Dulitha
>
> Can you also share the spreadsheet which has the sample configs? Also i
> think it would be good if we can read configs from local file. Can we use
> this script to implement something like 'Import endpoint from
> File/spreadsheet' ? Is that the use case here?
>
> Thanks
> Susinda
>
>
>
> On Tue, Jan 26, 2016 at 8:32 PM, Dulitha Wijewantha 
> wrote:
>
>> Hi guys,
>> I wrote a bunch of script tools that can be used to easily work with ESB
>> artifacts. For example - if we want to generate Endpoint definitions based
>> of a Google Spreadsheet we can use the w-python lib[1].
>>
>> Below is how a http endpoint definition can be generated.
>>
>> generator = wpy.ArtifactGenerator()
>> data = {
>> 'name' : "id",
>> 'type' : "http",
>> 'http' : True,
>> 'http_props': {
>> 'uri': "/.id",
>> 'method': "HEAD GET"
>> }
>> }
>> artifact = generator.generateEndpoint(data)
>>
>>
>> There is also another interesting feature I built for this. Below snippet
>> can be used to generate the artifact.xml based on a configuration
>> directory. This will be useful when the directory needs to be open from Dev
>> Studio. I also added the feature to generate the car POM based off the
>> directory.
>> data = {
>> 'parentGroupId' : "com.example.esb",
>> 'parentArtifactId' : "gateway",
>> 'parentVersion' : "1.0.0",
>> 'groupId' : "com.example.esb",
>> 'artifactId' : "gateway-car",
>> 'version' : "1.0.0",
>> 'name' : "gateway-car",
>> 'description' : "gateway-car",
>> 'serverRole' : "EnterpriseServiceBus",
>> 'resourceVersion' : "1.0.0",
>> 'resourceFileType' : "xml"
>> }
>> directory = "configs"
>> artifactTu = generator.generateArtifact(data, directory)
>> artifact = artifactTu
>> artifact.setName("artifact")
>> artifact.setType("POM")
>> generator.hold(artifact)
>>
>> [1] - https://github.com/dulichan/wpython
>>
>>
>> Cheers~
>>
>> --
>> Dulitha Wijewantha (Chan)
>> Software Engineer - Mobile Development
>> WSO2 Inc
>> Lean.Enterprise.Middleware
>>  * ~Email   duli...@wso2.com *
>> *  ~Mobile +94712112165 <%2B94712112165>*
>> *  ~Website   dulitha.me *
>> *  ~Twitter @dulitharw *
>>   *~Github @dulichan *
>>   *~SO @chan *
>>
>
>
>
> --
> *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
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

2016-01-27 Thread Thulasika Vijayanathan

Hi ,

I am implementing common init method for ESB 4.9 and 4.10. For ESB 4.10 I
use the property mediator to store new persistent content(accessToken) in
the registry as following:
 

when I enabling the connector artifact in ESB 4.9.0 I'm getting the
following error due to scope "registry".How to proceed further?

ERROR - PropertyMediatorFactory Only 'axis2' or 'transport' or
'axis2-client' or 'default' or 'operation' values are allowed for attribute
scope for a property mediator, Unsupported scope registry
[2016-01-27 13:31:53,717] ERROR - MediationLibraryAdminService Unable to
update status for :  {org.wso2.carbon.connector}salesforcerest :: Template
configuration : null cannot be builtfor Synapse Library artifact : newInit1
org.apache.synapse.deployers.SynapseArtifactDeploymentException: Template
configuration : null cannot be builtfor Synapse Library artifact : newInit1
at
org.apache.synapse.libraries.model.LibraryArtifact$TemplateArtifactFile.build(LibraryArtifact.java:196)
at
org.apache.synapse.libraries.model.LibraryArtifact.loadComponentsInto(LibraryArtifact.java:100)
at
org.apache.synapse.libraries.model.SynapseLibrary.loadLibrary(SynapseLibrary.java:144)
at
org.apache.synapse.libraries.model.SynapseLibrary.loadLibrary(SynapseLibrary.java:129)
at
org.apache.synapse.libraries.util.LibDeployerUtils.loadLibArtifacts(LibDeployerUtils.java:340)
at
org.wso2.carbon.mediation.library.service.MediationLibraryAdminService.addImport(MediationLibraryAdminService.java:100)
at
org.wso2.carbon.mediation.library.service.MediationLibraryAdminService.addImport(MediationLibraryAdminService.java:124)
at
org.wso2.carbon.mediation.library.service.MediationLibraryAdminService.updateStatus(MediationLibraryAdminService.java:436)
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.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
at
org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
at
org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.OutOnlyAxisOperationClient.executeImpl(OutOnlyAxisOperation.java:297)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.wso2.carbon.mediation.library.stub.MediationLibraryAdminServiceStub.updateStatus(MediationLibraryAdminServiceStub.java:1476)
at
org.wso2.carbon.mediation.library.ui.LibraryAdminClient.updateStatus(LibraryAdminClient.java:114)
at
org.apache.jsp.mediation_005flibrary.import_005flib_jsp._jspService(import_005flib_jsp.java:114)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
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:727)
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:727)
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: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.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
at
org.apache.catalina.core.ApplicationDispatch

Re: [Architecture] [EMM] Android agent auto enrollment

Re: [Architecture] [EMM] Android agent auto enrollment

Re: [Architecture] [EMM] Android agent auto enrollment

[Architecture] WSO2 IoTServer 1.0.0 M2 Released!

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Re: [Architecture] Location of SAML Components in Carbon 5

Re: [Architecture] Location of SAML Components in Carbon 5

[Architecture] Location of SAML Components in Carbon 5

Re: [Architecture] Script tools for ESB Artifacts

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

10 matches

Site Navigation

Mail list logo

Footer information