Re: [Dev] [EI Analytics] Permission for Event publisher user

2017-11-21 Thread Gimantha Bandara
Hi,

Following are the necessary permissions.

/permission/admin/publish
/permission/admin/publish/wso2event
login


On Wed, Nov 22, 2017 at 7:16 AM, Godwin Shrimal  wrote:

> Hi Devs,
>
> What are the required permissions for the user who is configuring in
> eventpublishers to publish events to DAS?
>
> Thanks
> Godwin
>
> --
> *Godwin Amila Shrimal*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
> *
> twitter: https://twitter.com/godwinamila
> 
>



-- 
Gimantha Bandara
Software Engineer
WSO2. Inc : http://wso2.com
Mobile : +94714961919
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Handler in ESB proxy service

2017-11-21 Thread Piriya Sivalingam
Hi Nadeeshaan,

Thank you for the description and I think your second method will work for
my scenario. I will try it and let you know.

Thank you.
Piriya

On Wed, Nov 22, 2017 at 10:48 AM, Nadeeshaan Gunasinghe  wrote:

> Hi Piriya,
>
> AFIK, we usually don't use handlers in Proxy services, we use handlers
> with REST APIs. The second approach you have followed, only valid for the
> axis2 handlers and I think that's why it wasn't getting invoked in your
> scenario. In order to handle your requirement, there are two other options
> to follow. I think the second option will be a better approach if I
> understood your requirement properly.
>
> *1. Implement a Synapse Handler as in [1]*
> *2. Implements a custom class mediator and invoke it inside the proxy
> service*
>
> [1] https://docs.wso2.com/display/ESB490/Writing+a+Synapse+Handler
>
> Cheers,
> *Nadeeshaan Gunasinghe*
> Senior Software Engineer, WSO2 Inc. http://wso2.com
> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
> <#m_8314147440188394561_>
> 
>  
> 
> Get your own email signature
> 
>
> On Wed, Nov 22, 2017 at 10:18 AM, Piriya Sivalingam 
> wrote:
>
>> Hi,
>>
>> I have already copied the JAR to /repository/components/lib
>> folder.
>> And also I have tried adding handler to the proxy via management console.
>> It gets removed when I save the proxy.
>>
>> On Wed, Nov 22, 2017 at 5:52 AM, Mushthaq Rumy  wrote:
>>
>>> Hi Piriya,
>>>
>>> Have you included the JAR or the OSGI bundle in your ESB pack? If not
>>> could you please add it. Can you try adding the handler to your proxy
>>> through management console?
>>>
>>> Thanks & Regards,
>>> Mushthaq
>>>
>>> On Tue, Nov 21, 2017 at 4:55 PM, Piriya Sivalingam 
>>> wrote:
>>>
 Hi,

 I have a scenario where I have to decode the JWT token at the ESB layer
 and fetch the user role from that token and validate at the ESB. I have a
 handler to decode the generated JWT token and extract the role. I have
 tried different ways in order to call that handler in my ESB proxy service.

 1. Added the below code inside the synapse configuration of my proxy
 service located at /repository/deployme
 nt/server/synapse-configs/default/proxy-services.

 
   


 2. Added the above code into the axis2.xml file located at
 /repository/conf/axis2/axis2.xml.

 I start the server in debug mode and noticed that handler does not get
 executed.

 And according to the first method, whenever I make any changes to the
 proxy, that (handler) gets removed. If I am not wrong, this is the expected
 behavior.


 Could you please suggest how can I call the handler inside my ESB proxy
 service?

 The ESB version is ESB 5.0.0.

 Thanks,
 Piriya

 --
 Regards,

 *Piriya Sivalingam*

 *Software Engineer - Support Team*

 *WSO2*
 *Mobile : +94 77 8462039 <+94%2077%20846%202039>*

 [image: http://wso2.com/signature] 


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


>>>
>>>
>>> --
>>> Mushthaq Rumy
>>> *Software Engineer*
>>> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
>>> Email : musht...@wso2.com
>>> WSO2, Inc.; http://wso2.com/
>>> lean . enterprise . middleware.
>>>
>>> 
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> *Piriya Sivalingam*
>>
>> *Software Engineer - Support Team*
>>
>> *WSO2*
>> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>>
>> [image: http://wso2.com/signature] 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Regards,

*Piriya Sivalingam*

*Software Engineer - Support Team*

*WSO2*
*Mobile : +94 77 8462039*

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Pass user details into the out sequence.

2017-11-21 Thread Senuwan Withana
Hi Guys,

Thanks for the replies .

I was able to take the user role from class mediator in the in sequence But
I could not able to pass that value into the out sequence.

Thanks,
*Senuwan Withana*
Software Engineer - Support Team | WSO2

Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com



On Wed, Nov 22, 2017 at 10:51 AM, Himasha Guruge  wrote:

> Hi Senuwan,
>
> What is your requirement here? Could you post your complete synapse
> configuration?
>
> Thanks,
> Himasha
>
> On Wed, Nov 22, 2017 at 10:09 AM, Senuwan Withana 
> wrote:
>
>> Hi Team,
>>
>>
>> I have created the below class mediator to call my JWTRoleReder, in
>> Sequence .
>>
>> 
>>   
>>
>>
>>
>> However I could not able to pass above details into the outSequence .
>> Kindly suggest solutions?
>>
>> Thanks.
>> *Senuwan Withana*
>> Software Engineer - Support Team | WSO2
>>
>> Email : senu...@wso2.com
>> Mobile: 94773212853
>> Web: http://www.wso2.com
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Himasha Guruge
> Senior Software Engineer
> WS*O2* *Inc.*
> Mobile: +94 777459299 <+94%2077%20745%209299>
> himas...@wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Pass user details into the out sequence.

2017-11-21 Thread Rukshan Premathunga
Hi Senuwan,

You can add required property to message context inside the class mediator.
So that you can read them back in out-sequence.

Thanks and Regards

On Wed, Nov 22, 2017 at 10:09 AM, Senuwan Withana  wrote:

> Hi Team,
>
>
> I have created the below class mediator to call my JWTRoleReder, in
> Sequence .
>
> 
>   
>
>
>
> However I could not able to pass above details into the outSequence .
> Kindly suggest solutions?
>
> Thanks.
> *Senuwan Withana*
> Software Engineer - Support Team | WSO2
>
> Email : senu...@wso2.com
> Mobile: 94773212853
> Web: http://www.wso2.com
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
+94711822074
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Pass user details into the out sequence.

2017-11-21 Thread Senuwan Withana
Hi Team,


I have created the below class mediator to call my JWTRoleReder, inSequence
 .


  
   


However I could not able to pass above details into the outSequence .
Kindly suggest solutions?

Thanks.
*Senuwan Withana*
Software Engineer - Support Team | WSO2

Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Handler in ESB proxy service

2017-11-21 Thread Piriya Sivalingam
Hi,

I have already copied the JAR to /repository/components/lib
folder.
And also I have tried adding handler to the proxy via management console.
It gets removed when I save the proxy.

On Wed, Nov 22, 2017 at 5:52 AM, Mushthaq Rumy  wrote:

> Hi Piriya,
>
> Have you included the JAR or the OSGI bundle in your ESB pack? If not
> could you please add it. Can you try adding the handler to your proxy
> through management console?
>
> Thanks & Regards,
> Mushthaq
>
> On Tue, Nov 21, 2017 at 4:55 PM, Piriya Sivalingam 
> wrote:
>
>> Hi,
>>
>> I have a scenario where I have to decode the JWT token at the ESB layer
>> and fetch the user role from that token and validate at the ESB. I have a
>> handler to decode the generated JWT token and extract the role. I have
>> tried different ways in order to call that handler in my ESB proxy service.
>>
>> 1. Added the below code inside the synapse configuration of my proxy
>> service located at /repository/deployme
>> nt/server/synapse-configs/default/proxy-services.
>>
>> 
>>   
>>
>>
>> 2. Added the above code into the axis2.xml file located at
>> /repository/conf/axis2/axis2.xml.
>>
>> I start the server in debug mode and noticed that handler does not get
>> executed.
>>
>> And according to the first method, whenever I make any changes to the
>> proxy, that (handler) gets removed. If I am not wrong, this is the expected
>> behavior.
>>
>>
>> Could you please suggest how can I call the handler inside my ESB proxy
>> service?
>>
>> The ESB version is ESB 5.0.0.
>>
>> Thanks,
>> Piriya
>>
>> --
>> Regards,
>>
>> *Piriya Sivalingam*
>>
>> *Software Engineer - Support Team*
>>
>> *WSO2*
>> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>>
>> [image: http://wso2.com/signature] 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Mushthaq Rumy
> *Software Engineer*
> Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
> Email : musht...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
> 
>



-- 
Regards,

*Piriya Sivalingam*

*Software Engineer - Support Team*

*WSO2*
*Mobile : +94 77 8462039*

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Invoking an API through Android Application

2017-11-21 Thread Isuru Uyanage
Hi All,

I have an Android application developed and need to invoke an API created
in WSO2 API Manager(2.1.0) through the Android app.

The following tasks have been done.

1. I have created an API using an existing SOAP Endpoint(wsdl)

2. Downloaded the SDK from API Manager for Android.

3. Android application has been developed.

4. As in the README.md file(which has been downloaded with the SDK), when
I'm trying to generate the jar by executing *'mvn package' *command, the
build gets failed as below. The API which I created was TestApi1.

/TestApi1_1.0.0_android/src/main/java/org/wso2/client/api/
TestApi1/DefaultApi.java:[31,1] package org.wso2.client.model.TestApi1 does
not exist

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
*(default-compile)* on projectorg.wso2.client.TestApi1: *Compilation
failure*

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
MojoExecutor.java:213)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
MojoExecutor.java:154)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
MojoExecutor.java:146)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
LifecycleModuleBuilder.java:117)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
LifecycleModuleBuilder.java:81)

at org.apache.maven.lifecycle.internal.builder.singlethreaded.
SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

at org.apache.maven.lifecycle.internal.LifecycleStarter.
execute(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at org.codehaus.plexus.classworlds.launcher.Launcher.
launchEnhanced(Launcher.java:289)

at org.codehaus.plexus.classworlds.launcher.Launcher.
launch(Launcher.java:229)

at org.codehaus.plexus.classworlds.launcher.Launcher.
mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: org.apache.maven.plugin.compiler.CompilationFailureException:
Compilation failure

at org.apache.maven.plugin.compiler.AbstractCompilerMojo.
execute(AbstractCompilerMojo.java:972)

at org.apache.maven.plugin.compiler.CompilerMojo.execute(
CompilerMojo.java:129)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
DefaultBuildPluginManager.java:134)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
MojoExecutor.java:208)

... 20 more

Any thoughts on what should be done to invoke API created through the
Android Application. And any comments are appreciated on what has gone
wrong here in step 4.


*Thanks and Best Regards,*

*Isuru Uyanage*
*Software Engineer - QA | WSO2*
*Mobile : **+94 77 <+94%2077%20767%201807> 55 30752*
*LinkedIn: **https://www.linkedin.com/in/isuru-uyanage/
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Handler in ESB proxy service

2017-11-21 Thread Mushthaq Rumy
Hi Piriya,

Have you included the JAR or the OSGI bundle in your ESB pack? If not could
you please add it. Can you try adding the handler to your proxy through
management console?

Thanks & Regards,
Mushthaq

On Tue, Nov 21, 2017 at 4:55 PM, Piriya Sivalingam  wrote:

> Hi,
>
> I have a scenario where I have to decode the JWT token at the ESB layer
> and fetch the user role from that token and validate at the ESB. I have a
> handler to decode the generated JWT token and extract the role. I have
> tried different ways in order to call that handler in my ESB proxy service.
>
> 1. Added the below code inside the synapse configuration of my proxy
> service located at /repository/deployment/server/synapse-
> configs/default/proxy-services.
>
> 
>   
>
>
> 2. Added the above code into the axis2.xml file located at
> /repository/conf/axis2/axis2.xml.
>
> I start the server in debug mode and noticed that handler does not get
> executed.
>
> And according to the first method, whenever I make any changes to the
> proxy, that (handler) gets removed. If I am not wrong, this is the expected
> behavior.
>
>
> Could you please suggest how can I call the handler inside my ESB proxy
> service?
>
> The ESB version is ESB 5.0.0.
>
> Thanks,
> Piriya
>
> --
> Regards,
>
> *Piriya Sivalingam*
>
> *Software Engineer - Support Team*
>
> *WSO2*
> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>
> [image: http://wso2.com/signature] 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.


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


[Dev] Handler in ESB proxy service

2017-11-21 Thread Piriya Sivalingam
Hi,

I have a scenario where I have to decode the JWT token at the ESB layer and
fetch the user role from that token and validate at the ESB. I have a
handler to decode the generated JWT token and extract the role. I have
tried different ways in order to call that handler in my ESB proxy service.

1. Added the below code inside the synapse configuration of my proxy
service located at
/repository/deployment/server/synapse-configs/default/proxy-services.


  
   

2. Added the above code into the axis2.xml file located at
/repository/conf/axis2/axis2.xml.

I start the server in debug mode and noticed that handler does not get
executed.

And according to the first method, whenever I make any changes to the
proxy, that (handler) gets removed. If I am not wrong, this is the expected
behavior.


Could you please suggest how can I call the handler inside my ESB proxy
service?

The ESB version is ESB 5.0.0.

Thanks,
Piriya

-- 
Regards,

*Piriya Sivalingam*

*Software Engineer - Support Team*

*WSO2*
*Mobile : +94 77 8462039*

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [EI Analytics] Change port offset

2017-11-21 Thread Godwin Shrimal
Thanks for reply Vijitha. It worked as u suggested. above port generated
using the port, we are specifying in event publisher.


Thanks
Godwin

On Tue, Nov 21, 2017 at 11:36 AM, Vijitha Ekanayake 
wrote:

> Hi Godwin,
>
> You can change the portOffset of the EI analytics distribution by changing
> the carbon.xml file resides in (EI_HOME)/wso2/analytics/conf directory.
> Once you change the port of the EI analytics, please make sure to change
> the MessageFlowConfigurationPublisher and MessageFlowStatisticsPublisher
> to point to the correct EI analytics server. you can find relevant files
> inside (EI_HOME)/repository/deployment/server/eventpublishers/ directory.
> Further, refer[1] for more details.
>
>
> [1]. https://docs.wso2.com/display/EI611/Prerequisites+
> to+Publish+Statistics
>
> Thanks.
>
> On Tue, Nov 21, 2017 at 9:39 AM, Godwin Shrimal  wrote:
>
>> Hi All,
>>
>> Can't we change the port offset of the EI analytics? By default, it's 1
>> and I set it to 0 and run and got below error in EI nodes. IS there any
>> place to configure 7712 port complaining below? I couldn't find any
>> configs.
>>
>> TID: [-1] [] [2017-11-21 11:05:32,476] ERROR {
>> org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnectionWorker}
>> -  Error while trying to connect to the endpoint. Cannot borrow client for
>> ssl://10.50.139.12:7712 {org.wso2.carbon.databridge.ag
>> ent.endpoint.DataEndpointConnectionWorker}
>> org.wso2.carbon.databridge.agent.exception.DataEndpointAuthenticationException:
>> Cannot borrow client for ssl://10.50.139.12:7712
>> at org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnec
>> tionWorker.connect(DataEndpointConnectionWorker.java:99)
>> at org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnec
>> tionWorker.run(DataEndpointConnectionWorker.java:42)
>> at java.util.concurrent.Executors$RunnableAdapter.call(
>> Executors.java:511)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused by: 
>> org.wso2.carbon.databridge.agent.exception.DataEndpointSecurityException:
>> Error while trying to connect to ssl://10.50.139.12:7712
>> at org.wso2.carbon.databridge.agent.endpoint.thrift.ThriftSecur
>> eClientPoolFactory.createClient(ThriftSecureClientPoolFactory.java:81)
>> at org.wso2.carbon.databridge.agent.client.AbstractClientPoolFa
>> ctory.makeObject(AbstractClientPoolFactory.java:39)
>> at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowOb
>> ject(GenericKeyedObjectPool.java:1212)
>> at org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnec
>> tionWorker.connect(DataEndpointConnectionWorker.java:91)
>> ... 6 more
>> Caused by: org.apache.thrift.transport.TTransportException: Could not
>> connect to 10.50.139.12 on port 7712
>> at org.apache.thrift.transport.TSSLTransportFactory.createClien
>> t(TSSLTransportFactory.java:237)
>> at org.apache.thrift.transport.TSSLTransportFactory.getClientSo
>> cket(TSSLTransportFactory.java:169)
>> at org.wso2.carbon.databridge.agent.endpoint.thrift.ThriftSecur
>> eClientPoolFactory.createClient(ThriftSecureClientPoolFactory.java:63)
>> ... 9 more
>> Caused by: java.net.ConnectException: Connection refused
>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSock
>> etImpl.java:350)
>> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPl
>> ainSocketImpl.java:206)
>> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocket
>> Impl.java:188)
>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>> at java.net.Socket.connect(Socket.java:589)
>> at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
>> at sun.security.ssl.SSLSocketImpl.(SSLSocketImpl.java:427)
>> at sun.security.ssl.SSLSocketFactoryImpl.createSocket(SSLSocket
>> FactoryImpl.java:88)
>> at org.apache.thrift.transport.TSSLTransportFactory.createClien
>> t(TSSLTransportFactory.java:233)
>> ... 11 more
>>
>>
>> Thanks
>> Godwin
>>
>> --
>> *Godwin Amila Shrimal*
>> Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
>> *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>
>
>
> --
> Vijitha Ekanayake
> Senior Software Engineer*, *WSO2, Inc.; http://wso2.com/
> Mobile : +94 777 24 73 39 | +94 718 74 44 08
> lean.enterprise.middleware
>



-- 
*Godwin Amila Shrimal*
Associate 

[Dev] WSO2 Committers += Maryam Ziyad

2017-11-21 Thread Hasitha Hiranya
Hi Devs,

It is my pleasure to welcome Maryam Ziyad as a WSO2 Committer. Maryam has
made a great contributions to Integration Team during the last few months
and in recognition of her commitment and contributions, she has been voted
as a Committer for WSO2.

@Maryam, welcome aboard and keep up the good work.

Thanks
-- 
*Hasitha Abeykoon*
Associate Technical Lead; WSO2 Inc.; http://wso2.com
*cell:* *+94 719363063*
*blog: **abeykoon.blogspot.com* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Not able to access xslt from inside wso2 xslt mediator. Please guide.

2017-11-21 Thread Vinod Kavinda
Hi Aditya,
You need to use the registry UI in the Mangement console. The registry is a
DB based repository. Refer [1] on managing the registry.

[1] - https://docs.wso2.com/display/ADMIN44x/Managing+the+Registry

Regards,
Vinod

On Tue, Nov 21, 2017 at 8:31 PM, aditya shivankar <
shivankar.adit...@gmail.com> wrote:

> Respected Sir,
>
> I think I need to learn by the word registry, where actually I am suppose
> to keep the xslt file.
>
> Went through all the links pasted in the mail chain, but still not clear.
>
> As shown in the screenshot attached, I creted the xsl file inside registry
> folder that gets created when we create "ESB Solution project".
>
> Please let me know , how to correct it( if wrong ). Please consider I am
> very new to wso2.
>
> With Regards,
> Aditya
>
>
>
> On Mon, Nov 20, 2017 at 10:16 PM, Vijitha Ekanayake 
> wrote:
>
>> Hi Aditya,
>>
>> It seems that the reason for xsl file not picking up from the registry
>> is, you are not referring the registry entry in the correct way inside XSLT
>> mediator configurations. You need to point the relevant registry entry with
>> XSLT mediator as below.
>>
>> 
>>
>>
>> Also make sure to provide correct registry (whether config or govanance 
>> registry) as key to XSLT mediator.
>>
>>
>> Thanks.
>>
>> On Mon, Nov 20, 2017 at 9:55 PM, aditya shivankar <
>> shivankar.adit...@gmail.com> wrote:
>>
>>> Respected Sir,
>>>
>>> Now I tried  putting xsl file  under registry, still not able to use it.
>>> Please check  the screenshot attached.
>>> Could you please send the screenshot of your workspace in eclipse
>>> (similar to the attached screenshot), showing where to keep the xslt in
>>> project structure and also project xml file showing how you access it.
>>>
>>> With Regards,
>>> Aditya
>>>
>>>
>>> On Mon, Nov 20, 2017 at 11:42 AM, aditya shivankar <
>>> shivankar.adit...@gmail.com> wrote:
>>>
 Respected Sir/Madam,

 Now I tried  putting xsl file  under registry, still not able to use
 it. Please check  the screenshot attached.
 Could you please send the screenshot of your workspace in eclipse
 (similar to the attached screenshot), showing where to keep the xslt in
 project structure and also project xml file showing how you access it.

 With Regards,
 Aditya

 On Wed, Nov 15, 2017 at 7:41 PM, Saneth Dharmakeerthi  wrote:

> Hi Aditya,
>
> It seems you have put the XSLT in API folder and try to access it in
> incorrect way.
>
> You can do this by either one of following ways and the first one is
> the recommended.
>
>
>1.  Put the XSLT to the registry. you can find more information
>in[1][3]. If you change the xslt in registry it will effect imidiatly.
>2. Put it as local entry[1][2], XSLT change exffect only after
>next API or peoxy deployment.
>   - 
>
> 
>
>
> [1]https://docs.wso2.com/display/ESB500/Sample+8%3A+Introduc
> tion+to+Static+and+Dynamic+Registry+Resources+and+Using+XSLT
> +Transformations
> [2] http://mytecheye.blogspot.com/2013/12/wso2-esb-xslt-medi
> ator-xslt-imports.html
> [3] https://www.linkedin.com/pulse/wso2-esb-message-transfor
> mation-mapping-using-xslt-isuru-jayakantha
>
>
>
> Thanks and Best Regards,
>
> Saneth Dharmakeerthi
> *Associate Technical Lead*
> WSO2, Inc.
> Mobile: +94772325511 <+94%2077%20232%205511>
>
> 
>
> On Wed, Nov 15, 2017 at 6:40 PM, aditya shivankar <
> shivankar.adit...@gmail.com> wrote:
>
>> Respected Sir,
>>
>> I have one xslt .
>> I have saved it inside api(src/main/synapse-config/api) folder in my
>> project.
>> I am trying to access it using xslt mediator like below.
>>
>> 
>>
>> But getting below error.Full logs can be found in attachment .
>>
>> [2017-11-15 18:11:39,128] [EI-Core]  INFO - DependencyTracker Local
>> entry : api/test.xsl was added to the Synapse configuration successfully
>> [2017-11-15 18:11:39,129] [EI-Core]  WARN - SynapseConfigUtils Cannot
>> convert null to a StreamSource
>> [2017-11-15 18:11:39,131] [EI-Core] ERROR - XSLTMediator Error
>> creating XSLT transformer using : Value {name ='null', keyValue
>> ='api/test.xsl'}
>> org.apache.synapse.SynapseException: Cannot convert null to a
>> StreamSource
>> at org.apache.synapse.config.SynapseConfigUtils.handleException
>> (SynapseConfigUtils.java:580)
>> at org.apache.synapse.config.SynapseConfigUtils.getStreamSource
>> (SynapseConfigUtils.java:81)
>> at org.apache.synapse.mediators.transform.XSLTMediator.createTe
>> mplate(XSLTMediator.java:420)
>> at org.apache.synapse.mediators.transform.XSLTMediator.performX
>> SLT(XSLTMediator.java:268)
>> at org.apache.synapse.mediators.transform.XSLTMediator.mediate(

Re: [Dev] [TokenBinding][OAuth] Need to add a sample application to IS

2017-11-21 Thread Inthirakumaaran Tharmakulasingham
Hi Thanuja,

Thanks for the info.I have sent the PR to product IS.Please find the link
for that below.

PR:https://github.com/wso2/product-is/pull/1447

Thanks

On Tue, Nov 21, 2017 at 10:08 AM, Thanuja Jayasinghe 
wrote:

> Hi Inthirakumaaran,
>
> You need to add your sample to https://github.com/wso2/
> product-is/tree/5.x.x/modules/samples/oauth2. Please send a pull request.
>
> Thanks,
> Thanuja
>
> On Mon, Nov 20, 2017 at 3:17 PM, Inthirakumaaran Tharmakulasingham <
> inthirakumaa...@wso2.com> wrote:
>
>> Hi all,
>> I developed a sample application to send OAuth requests to IS server with
>> token binding support.Need to add that to product IS samples.
>>
>> git hub link for that application: https://github.co
>> m/inthirakumaaran/TokenBindingSample
>>
>> Thank you,
>>
>> Regards,
>> kumar
>>
>> --
>> Inthirakumaaran
>> Software Engineering - Intern | WSO2
>>
>> Email: inthirakumaa...@wso2.com
>> Mobile:0766598050
>>
>>
>
>
> --
> *Thanuja Lakmal*
> Associate Technical Lead
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94715979891
>



-- 
Inthirakumaaran
Software Engineering - Intern | WSO2

Email: inthirakumaa...@wso2.com
Mobile:0766598050
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Cannot see the response when invoking the service

2017-11-21 Thread Mushthaq Rumy
Hi Buddhimala,

By looking at the ESB wire-log, it seems like the data is converted to
JSON. Were there any errors logged in the APIM console or in the ESB
console?

Thanks & Regards,
Mushthaq

On Tue, Nov 21, 2017 at 10:07 AM, Buddhimala Ranasinghe  wrote:

> Hi All,
>
> I'm trying to implement the scenario as shown in the following diagram.
> [image: Inline image 1]
>
> The WSDL for my BE can be found in the following location.
> http://192.168.55.160:9763/services/NawalokaPatientService?wsdl
>
> I created an API with CRUD operations inside API Manager. For GET method
> I'm sending the request to the "read" method in my legacy BE. The sample
> response from my BE for the request will be as follows.
>
> http://schemas.xmlsoap.org/soap/envelope/
> ">
>
>   http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
> 1.0.xsd">
>  http://docs.oasis-open.org/wss/2004/01/oasis-
> 200401-wss-wssecurity-utility-1.0.xsd">
> 2017-11-20T10:30:41.878Z
> 2017-11-20T10:35:41.878Z
>  
>   
>
>
>   http://service.sample.nawaloka.com;>
>  http://dto.
> service.sample.nawaloka.com/xsd" xmlns:ax25="http://service.
> sample.nawaloka.com/xsd" xmlns:xsi="http://www.w3.org/
> 2001/XMLSchema-instance">
> 
>?
>?
>?
> 
> 
> 
>?
>?
>?
> 
> 
>?
>?
>?
> 
> abc
> a...@abc.com
> 
>M.Rajan
>?
>?
> 
>  
>   
>
> 
>
> But my response should be in JSON format so that I tried to convert the
> response into JSON using " value="application/json"/>"
>
> But my problem is, in my response to the client, it should only contain 
> *insurer
> details, parentGuardian, patientContact, patientFullName and patientId*.
> Therefore, I tried of defining a custom payload as follows.
>
> 
>
>   
> {
> "patient":{
> "insurer": "$1",
> "parentGuardian": "$2",
> "patientContact": "$3",
> "patientFullName": "$4",
> "patientId": "$5"
>
>
> }
> }
> 
>   
>  
>  
>  
>  
>  
>   
>
>
>
> But, when I invoke the service, I cannot see any response at client side.
> I'm attaching the wirelogs for my ESB and APIM.
>
> Can you please help me to solve this problem?Where am I doing wrong?
> --
>
>
> *Buddhimala Ranasinghe*
> Software Engineer-Support Team | WSO2
> Emil: buddhim...@wso2.com
> Mobile:+94771563138 <+94%2077%20156%203138>
> Web:http://wso2.com
> [image: https://wso2.com/signature] 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.


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


Re: [Dev] Cannot see the response when invoking the service

2017-11-21 Thread Samitha Chathuranga
Hi Buddhimala,

Did you call the api via curl? Don't you receive any response when invoked
the api ? Does the client hangs not receiving any response? You may try
with curl options* -i *and *-v *to get more information on the response.
And if you called via Postman,etc. tool I suggest to test with curl.
Because this might be caused by a similar issue with content-length header,
previously I had encountered.

Regards,
Samitha

On Tue, Nov 21, 2017 at 10:07 AM, Buddhimala Ranasinghe  wrote:

> Hi All,
>
> I'm trying to implement the scenario as shown in the following diagram.
> [image: Inline image 1]
>
> The WSDL for my BE can be found in the following location.
> http://192.168.55.160:9763/services/NawalokaPatientService?wsdl
>
> I created an API with CRUD operations inside API Manager. For GET method
> I'm sending the request to the "read" method in my legacy BE. The sample
> response from my BE for the request will be as follows.
>
> http://schemas.xmlsoap.org/soap/envelope/
> ">
>
>   http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
> 1.0.xsd">
>  http://docs.oasis-open.org/wss/2004/01/oasis-
> 200401-wss-wssecurity-utility-1.0.xsd">
> 2017-11-20T10:30:41.878Z
> 2017-11-20T10:35:41.878Z
>  
>   
>
>
>   http://service.sample.nawaloka.com;>
>  http://dto.
> service.sample.nawaloka.com/xsd" xmlns:ax25="http://service.
> sample.nawaloka.com/xsd" xmlns:xsi="http://www.w3.org/
> 2001/XMLSchema-instance">
> 
>?
>?
>?
> 
> 
> 
>?
>?
>?
> 
> 
>?
>?
>?
> 
> abc
> a...@abc.com
> 
>M.Rajan
>?
>?
> 
>  
>   
>
> 
>
> But my response should be in JSON format so that I tried to convert the
> response into JSON using " value="application/json"/>"
>
> But my problem is, in my response to the client, it should only contain 
> *insurer
> details, parentGuardian, patientContact, patientFullName and patientId*.
> Therefore, I tried of defining a custom payload as follows.
>
> 
>
>   
> {
> "patient":{
> "insurer": "$1",
> "parentGuardian": "$2",
> "patientContact": "$3",
> "patientFullName": "$4",
> "patientId": "$5"
>
>
> }
> }
> 
>   
>  
>  
>  
>  
>  
>   
>
>
>
> But, when I invoke the service, I cannot see any response at client side.
> I'm attaching the wirelogs for my ESB and APIM.
>
> Can you please help me to solve this problem?Where am I doing wrong?
> --
>
>
> *Buddhimala Ranasinghe*
> Software Engineer-Support Team | WSO2
> Emil: buddhim...@wso2.com
> Mobile:+94771563138 <+94%2077%20156%203138>
> Web:http://wso2.com
> [image: https://wso2.com/signature] 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Samitha Chathuranga
Software Engineer, WSO2 Inc.
lean.enterprise.middleware
Mobile: +94715123761

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Fwd: Anomaly Detection in JIra Using CEP

2017-11-21 Thread Isham Mohamed
Hi Kumar,

Thanks for the response. That's the problem. if I was able to get access to
the public key of the mail server I would  have done it straightforward.
but dev_ops has some difficulty getting me the public key.
is that what u suggested??


On Tue, Nov 21, 2017 at 9:46 AM, Inthirakumaaran Tharmakulasingham <
inthirakumaa...@wso2.com> wrote:

> +Dev
>
> On Mon, Nov 20, 2017 at 11:07 PM, Inthirakumaaran Tharmakulasingham <
> inthirakumaa...@wso2.com> wrote:
>
>> Hi Isham,
>>
>> Did you add proper certificates to Java keystore? ( $JAVA_HOME/
>> jre/lib/security/cacerts).If you want you can run your server with
>> "-Djavax.net.debug=all" see more about your problem.Hope this could help :)
>>
>> regards,
>> kumar
>>
>>
>> On Mon, Nov 20, 2017 at 5:50 PM, Isham Mohamed  wrote:
>>
>>> Hi All,
>>> This is regarding configuring email publisher of the wso2das3.1.0
>>> I configured output-event-adapter.xml as bellow
>>>
>>> * *
>>> **
>>> *no-re...@wso2.com
>>> *
>>> *[username]*
>>> *[password]*
>>> *tygra.wso2.com
>>> *
>>> *25*
>>> *true*
>>> *true*
>>> **
>>> *8*
>>> *100*
>>> *2*
>>> *1*
>>> **
>>>
>>> when I tried to send a mail there was an error saying,
>>>
>>> javax.net.ssl.SSLHandshakeException: 
>>> sun.security.validator.ValidatorException:
>>> PKIX path building failed: 
>>> sun.security.provider.certpath.SunCertPathBuilderException:
>>> unable to find valid certification path to requested target
>>>
>>> so we did a workaround by disabling "mail.smtp.starttls" .
>>> The mails are used only for internal purpose.
>>> is this recommended??
>>>
>>> Thanks
>>>
>>> On Mon, Nov 20, 2017 at 5:38 PM, Isham Mohamed  wrote:
>>>
 adding Srinath,Suho,Sajith,Isuru

>>>
>>>
>>>
>>> --
>>>
>>> Isham Mohamed
>>> *Trainee Software Engineer*
>>> WSO2
>>>
>>> p: +94778696585 <+94%2077%20869%206585>
>>>
>>> .
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Inthirakumaaran
>> Software Engineering - Intern | WSO2
>>
>> Email: inthirakumaa...@wso2.com
>> Mobile:0766598050
>>
>>
>
>
> --
> Inthirakumaaran
> Software Engineering - Intern | WSO2
>
> Email: inthirakumaa...@wso2.com
> Mobile:0766598050
>
>


-- 

Isham Mohamed
*Trainee Software Engineer*
WSO2

p: +94778696585

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


Re: [Dev] [EI] Error while running ciphertool

2017-11-21 Thread Vinod Kavinda
Hi Godwin,
This is a known issue. It is already fixed in master branches.

Regards,
Vinod

On Tue, Nov 21, 2017 at 12:22 PM, Godwin Shrimal  wrote:

> Hi Devs,
>
> I am getting an error when running ciphertool from /bin
> directory. It works when running from . Please see the error
> below. I think this is a bug.
>
> Exception in thread "main" org.wso2.ciphertool.exception.CipherToolException:
> File, cipher-standalone-config.properties does not exist.
> at org.wso2.ciphertool.utils.Utils.setSystemProperties(
> Utils.java:247)
> at org.wso2.ciphertool.CipherTool.initialize(CipherTool.java:93)
> at org.wso2.ciphertool.CipherTool.main(CipherTool.java:52)
>
> Thanks
> Godwin
>
> --
> *Godwin Amila Shrimal*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
> *
> twitter: https://twitter.com/godwinamila
> 
>



-- 
Vinod Kavinda
Senior Software Engineer
*WSO2 Inc. - lean . enterprise . middleware .*
Mobile : +94 (0) 712 415544
Blog : http://soatechflicks.blogspot.com/
[image: http://wso2.com/signature]

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