Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 7.0.0 RC1

[Isuru Udana]

Hi All,

Did some basic smoke tests. No blockers found.

   [+] Stable - go ahead and release

Thanks.


On Mon, Oct 7, 2019 at 7:31 PM Mathuriga Thavarajah 
wrote:

> Hi All,
>
> Security Scanning reports (Static and Dynamic) were analyzed and reviewed.
> Hence +1 from the Platform Security Team for proceeding with the release.
>
> Thanks.
>
> Regards,
> Mathuriga.
>
> On Mon, Oct 7, 2019 at 6:43 PM Ridmi Lokumudali  wrote:
>
>> Hi all,
>>
>> I have tested the following in RC1 pack in windows.
>>
>>- Tested CLI tool command and a smoke test on CLI tool
>>- Pack startup
>>
>> No blocker found.
>>
>> +1 go ahead and release.
>>
>>
>> On Mon, Oct 7, 2019 at 9:58 AM Niruhan Viswarupan 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have tested the gRPC Inbound endpoint in MI and gRPC io in SI. Tested
>>> the sample interconnecting SI and MI. No blockers were found.
>>> Hence +1 Stable, go ahead and release from me.
>>>
>>> Kind Regards,
>>>
>>> On Sun, Oct 6, 2019 at 10:55 PM Senthuran Ambalavanar <
>>> senthu...@wso2.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I have tested the Quick Start Guide of Streaming Integrator, and no
>>>> blockers were found.
>>>> Hence, *+1 - Stable - Go ahead and release*, from me.
>>>>
>>>> Regards,
>>>> Senthuran.
>>>>
>>>> --
>>>> *Senthuran Ambalavanar *| Software Engineer | WSO2 Inc.
>>>> (m) +94 757 875 887 | (e) senthu...@wso2.com |
>>>> Linkedin: https://www.linkedin.com/in/senthuran-ambalavanar-001122139/
>>>>  |
>>>> Blog: https://medium.com/@senthuran16
>>>>
>>>>
>>>>
>>>
>>> --
>>> *V. Niruhan* | Software Engineer | WSO2 Inc. <http://wso2.com/>
>>> (M)+94 776468013 | (E) niru...@wso2.com
>>> Blog: https://medium.com/@niruhan
>>> LinkedIn: https://www.linkedin.com/in/niruhan/
>>>
>>
>>
>> --
>> Thanks,
>> Ridmi Rangika
>> Software Engineer, WSO2, Inc.
>> E-mail : ri...@wso2.com
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
>
> *Mathuriga Thavarajah*
> Software Engineer
> WSO2 Inc. - http ://wso2.com
>
> Email : mathur...@wso2.com
> Mobile  : +94778191300
>
>
>
> *[image: http://wso2.com/signature] <http://wso2.com/signature>*
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
*Isuru Udana*
Associate Director / Architect
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.5.0 RC1

[Isuru Udana]

 https://github.com/wso2/product-ei/releases/tag/v6.5.0-rc1
>>>>>>
>>>>>> Please test and vote as follows
>>>>>>
>>>>>> [+] Stable - go ahead and release
>>>>>> [-] Broken - do not release (explain why)
>>>>>>
>>>>>> You may find the official documentation in:
>>>>>> https://docs.wso2.com/display/EI6xx
>>>>>>
>>>>>> ~ The Enterprise Integrator Team ~
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> *M.Nirothipan* | Senior Software Engineer | WSO2 Inc.
>>>>>>
>>>>>> (m) +94772172692 | (e) nirothi...@wso2.com
>>>>>>
>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> *Chanika Geeganage* | Associate Technical Lead | WSO2 Inc.
>>>>>
>>>>> (m) +94-77-3522586 | (e) chan...@wso2.com
>>>>>
>>>>> <https://wso2.com/signature>
>>>>> ___
>>>>> Architecture mailing list
>>>>> architect...@wso2.org
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *Mathuriga Thavarajah*
>>>> Software Engineer
>>>> WSO2 Inc. - http ://wso2.com
>>>>
>>>> Email : mathur...@wso2.com
>>>> Mobile  : +94778191300
>>>>
>>>>
>>>>
>>>> *[image: http://wso2.com/signature] <http://wso2.com/signature>*
>>>> ___
>>>> Architecture mailing list
>>>> architect...@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>> --
>>
>> *M.Nirothipan* | Senior Software Engineer | WSO2 Inc.
>>
>> (m) +94772172692 | (e) nirothi...@wso2.com
>>
>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
> Sameera Gunarathne
> Senior Software Engineer, WSO2 Inc. http://wso2.com
> <http://l.facebook.com/l.php?u=http%3A%2F%2Fwso2.com=gAQEswASa>
> Email: samee...@wso2.com
> Mobile: +94714155561
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
*Isuru Udana*
Associate Director / Architect
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.3.0 RC2

[Isuru Udana]

Hi All,

Did basic tests of all artifact types in both Integrator and Micro
Integrator profiles using artifacts created from EI Tooling.

[+] Stable - go ahead and release

Thanks.


On Sat, Jun 16, 2018 at 12:07 PM Thishani Lucas  wrote:

> Hi All,
>
> Tested the following in both ESB profile and Micro Integrator profile.
>
>- Store and forward with scheduled forwarding processor and JMS
>message store in the Broker profile.
>- Sampling message processor.
>- JMS inbound endpoint.
>- File inbound endpoint (vfs).
>- Mail-To transport using a listener proxy.
>- Constructing and sending multipart form data.
>- Publishing stats to the Analytics profile.
>- Basic functionalities of some mediators and endpoints.
>
> [+] Stable - Go ahead and release.
>
> Thanks,
> Thishani
>
> On Sat, Jun 16, 2018 at 11:46 AM Lahiru Madushanka 
> wrote:
>
>> Hi all,
>>
>> Tested the following
>>
>> Ubuntu Windows
>> Test EI micro-integrator EI + MI
>> JMS inbound endpoint ✓ ✓ ✓
>> JMS listener proxy ✓ ✓ ✓
>> JMS publisher proxy ✓ ✓ ✓
>> JMS message Store ✓ ✓ ✓
>> JMS transaction and rollback ✓ ✓
>> Message sampling processor ✓ ✓ ✓
>> Class mediator ✓ ✓ ✓
>> Data Mapper mediator (using CAPP) ✓ ✓
>>
>> Smoke test management console of all profiles in windows
>> ✓
>> [+] Stable - go ahead and release
>>
>> Thanks,
>> Lahiru
>>
>> On Sat, Jun 16, 2018 at 1:11 AM Malaka Gangananda 
>> wrote:
>>
>>> Hi All,
>>>
>>> We are pleased to announce the second release candidate of WSO2
>>> Enterprise Integrator 6.3.0.
>>>
>>> Known issues: https://github.com/wso2/product-ei/issues
>>>
>>> Source and binary distribution files:
>>> https://github.com/wso2/product-ei/releases/tag/v6.3.0-rc2
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/product-ei/tree/v6.3.0-rc2
>>>
>>> Please vote as follows:
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> ~The WSO2 Integration Team~
>>>
>>> Thanks,
>>>
>>>
>>> --
>>> Malaka.
>>> --
>>> Malaka Gangananda - Software Engineer | WSO2
>>> Email : mala...@wso2.com
>>> Mobile : +94713564340
>>> Web : http://wso2.com
>>>   <http://wso2.com/signature>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> *Thishani Lucas*
> *Software Engineer*
> *WSO2 Lanka (Private) Limited**: http://wso2.com <http://wso2.com/>*
> *lean.enterprise.middle-ware*
>
> *Tel: +94 77 2556931 *
>
> *LinkedIn: https://www.linkedin.com/in/thishani-lucas/
> <https://www.linkedin.com/in/thishani-lucas/>*
>
>
> <http://wso2.com/signature>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>


-- 
*Isuru Udana*
Senior Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.3.0 RC1

[Isuru Udana]

Hi All,

We are calling off this vote as we found a blocker related to
carbon-registry.

Thanks.


On Thu, Jun 14, 2018 at 2:27 PM Malaka Gangananda  wrote:

> Hi All,
>
> We are pleased to announce the first release candidate of WSO2 Enterprise
> Integrator 6.3.0.
>
> Known issues: https://github.com/wso2/product-ei/issues
>
> Source and binary distribution files:
> https://github.com/wso2/product-ei/releases/tag/v6.3.0-rc1
>
> The tag to be voted upon:
> https://github.com/wso2/product-ei/tree/v6.3.0-rc1
>
> Please vote as follows:
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> ~The WSO2 Integration Team~
>
> Thanks,
> --
> Malaka.
> --
> Malaka Gangananda - Software Engineer | WSO2
> Email : mala...@wso2.com
> Mobile : +94713564340
> Web : http://wso2.com
>   <http://wso2.com/signature>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>


-- 
*Isuru Udana*
Senior Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Bhashinee Nirmali

[Isuru Udana]

Hi All,

It's my pleasure to announce Bhashinee Nirmali as a WSO2 Committer. She has
been a valuable contributor to WSO2 Integration team.

Congratulations Bhashinee and keep up the good work!

Thanks.


-- 
*Isuru Udana*
Senior Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Deletion of Faulty Proxy Services Not Supported

[Isuru Udana]

Hi Thishani,

Shall we check on the windows environment as well. I think there are some
issues in the logic written for windows.
And I am not sure condition in L792 is correct. Can you please check that
one also ?

Thanks.



On Wed, Jan 10, 2018 at 2:15 PM, Thishani Lucas <thish...@wso2.com> wrote:

> Hi Vinod,
>
> Of course yes I can do that. But if there is no use with that substring, I
> thought of simply removing it. But yes, for now I'll follow your suggestion.
>
> Thanks,
> Thishani
>
> On Wed, Jan 10, 2018 at 2:06 PM, Vinod Kavinda <vi...@wso2.com> wrote:
>
>> Hi Thishani,
>> Why don't you just add the file separator (/) before appending the
>> service name in line [1]? It won't break any requirement achieved by
>> substring method.
>>
>> [1] - https://github.com/wso2/carbon-deployment/blob/4.7.x/compo
>> nents/service-mgt/axis2-service-mgt/org.wso2.carbon.service.
>> mgt/src/main/java/org/wso2/carbon/service/mgt/ServiceAdmin.java#L793
>>
>> Regards,
>> Vinod
>>
>> On Wed, Jan 10, 2018 at 1:59 PM, Thishani Lucas <thish...@wso2.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> Please find the link to the relevant code below [1].
>>>
>>> [1] https://github.com/wso2/carbon-deployment/blob/4.7.x/com
>>> ponents/service-mgt/axis2-service-mgt/org.wso2.carbon.servic
>>> e.mgt/src/main/java/org/wso2/carbon/service/mgt/ServiceAdmin.java#L777
>>>
>>> Thanks.
>>>
>>> On Wed, Jan 10, 2018 at 1:26 PM, Isuru Udana <isu...@wso2.com> wrote:
>>>
>>>> Hi Thishani,
>>>>
>>>> Please discuss these type of topics in dev list. And please provide
>>>> links to relevant sources in github as explaining the logics in words is
>>>> not that useful to someone to understand the question.
>>>>
>>>> Thanks.
>>>>
>>>> On Wed, Jan 10, 2018 at 1:12 PM, Thishani Lucas <thish...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Jan 10, 2018 at 12:46 PM, Thishani Lucas <thish...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> It seems that the deletion of faulty proxy services being not
>>>>>> supported is not because to disallow modifying capp.
>>>>>>
>>>>>> The class ServiceAdmin.java in the package
>>>>>> org.wso2.carbon.service.mgt of carbon deployment, is having a method
>>>>>> 'deleteFaultyServiceGroup'. In that method we're doing a substring of the
>>>>>> variable 'repository', which holds the path to the artifacts (eg : "
>>>>>> */home/thishani/wso2ei-6.1.1/repository/deployment/server/*"). But
>>>>>> the substring method is removing the ending slash. Because of this, when
>>>>>> appending the service name that should be undeployed, the file path is
>>>>>> derived as "
>>>>>> */home/thishani/wso2ei-6.1.1/repository/deployment/serverFaultyProxy*".
>>>>>> Since this file does not exist in the system, it's not getting removed 
>>>>>> and
>>>>>> the service is also not getting undeployed.
>>>>>>
>>>>>> Therefore, I'm planning to remove that substring function. But I want
>>>>>> to make sure if there is any reason for doing that substring. Is that
>>>>>> needed for any other product's functionality? Other than EI? If so, 
>>>>>> please
>>>>>> let me know, so that I can come up with a different solution.
>>>>>>
>>>>>> Thanks,
>>>>>> Thishani
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Jan 9, 2018 at 6:12 PM, Thishani Lucas <thish...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> Currently, deleting faulty proxy services in the EI is not possible.
>>>>>>> This has been reported as an issue in [1]. This might be because since
>>>>>>> we're allowing deployment of proxies through capp and that the
>>>>>>> configurations of the capp should not be modified, the deletion of 
>>>>>>> faulty
>>>>>>> proxy services is not supported. IMO, we should support deletion of 
>>>>>>> faulty
>>>

Re: [Dev] Call vs Callout mediator performance

[Isuru Udana]

Hi Chandana,

In latest EI/ESB versions, defaultMaxConnectionsPerHost is already set to
200. That will solve the concurrency problem.
In Callout mediator, engine resources (threads) kept waiting for backend to
respond whereas in Call mediator (in non-blocking mode) threads get
released once request is submitted to the backend.
So due to the non-blocking nature of underlying transport implementation
used in Call mediator, we could expect higher performance in Call mediator.

Thanks.

On Thu, Dec 14, 2017 at 6:54 AM, Chandana Napagoda <cnapag...@gmail.com>
wrote:

> Hi Devs,
>
> WSO2 EI product documentation states that[1] call mediator has greater
> performance than callout mediator.  As per my understanding callout
> mediator has a limitation that its only allow two simultaneous connections
> per host. However, we can mitigate that limitation by adding
> "defaultMaxConnectionsPerHost" configuration[2].
>
> After adding above configuration does Callout mediator perform same as
> Call mediator for less load per the same host? Is there any performance
> round results for Callout vs Call scenario(blocking and non blocking)?
>
> [1]. *The Call mediator leverages the non-blocking transports for much
> greater performance than the Callout mediator, so you should use the Call
> mediator in most cases. *
>
> [2]. http://mytecheye.blogspot.com/2013/09/wso2-esb-
> improve-callout-mediator.html
>
> Regards,
> Chandana
>
> --
>
> Blog: http://blog.napagoda.com
> Linkedin: https://www.linkedin.com/in/chandananapagoda/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Udana*
Senior Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] nginx master_process on; (code=exited, status=1/FAILURE)

[Isuru Udana]

 - A high performance web server and a reverse proxy
>>>>> server
>>>>>Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor
>>>>> preset: enabled)
>>>>>Active: failed (Result: exit-code) since Tue 2017-11-28 16:33:48
>>>>> +0530; 50s ago
>>>>>  Docs: man:nginx(8)
>>>>>   Process: 953 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on;
>>>>> master_process on; (code=exited, status=1/FAILURE)
>>>>>
>>>>> නෙවැ 28 16:44:57 dushantha-ThinkPad-X1-Carbon-5th nginx[2996]: nginx:
>>>>> [emerg] bind() to [::]:80 failed (98: Address already in use)
>>>>> නෙවැ 28 16:44:58 dushantha-ThinkPad-X1-Carbon-5th nginx[2996]: nginx:
>>>>> [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
>>>>> නෙවැ 28 16:44:58 dushantha-ThinkPad-X1-Carbon-5th nginx[2996]: nginx:
>>>>> [emerg] bind() to [::]:80 failed (98: Address already in use)
>>>>> නෙවැ 28 16:44:58 dushantha-ThinkPad-X1-Carbon-5th nginx[2996]: nginx:
>>>>> [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
>>>>> නෙවැ 28 16:44:58 dushantha-ThinkPad-X1-Carbon-5th nginx[2996]: nginx:
>>>>> [emerg] bind() to [::]:80 failed (98: Address already in use)
>>>>> නෙවැ 28 16:44:59 dushantha-ThinkPad-X1-Carbon-5th nginx[2996]: nginx:
>>>>> [emerg] still could not bind()
>>>>> නෙවැ 28 16:44:59 dushantha-ThinkPad-X1-Carbon-5th systemd[1]:
>>>>> nginx.service: Control process exited, code=exited status=1
>>>>> නෙවැ 28 16:44:59 dushantha-ThinkPad-X1-Carbon-5th systemd[1]: Failed
>>>>> to start A high performance web server and a reverse proxy server.
>>>>> නෙවැ 28 16:44:59 dushantha-ThinkPad-X1-Carbon-5th systemd[1]:
>>>>> nginx.service: Unit entered failed state.
>>>>> නෙවැ 28 16:44:59 dushantha-ThinkPad-X1-Carbon-5th systemd[1]:
>>>>> nginx.service: Failed with result 'exit-code'.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Is there any possible solution to get rid of the error
>>>>> regards
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Dushantha Nayanajith Chandima Batuwita*
>>>>> Software Engineer Support | WSO2
>>>>> dushan...@wso2.com
>>>>> mobile : 0094777453010 <077%20745%203010>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> *Dushantha Nayanajith Chandima Batuwita*
>>> Software Engineer Support | WSO2
>>> dushan...@wso2.com
>>> mobile : 0094777453010 <077%20745%203010>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Senduran *
>> Senior Software Engineer,
>> WSO2, Inc.;  http://wso2.com/ <http://wso2.com/>
>> Mobile: +94 77 952 6548 <+94%2077%20952%206548>
>>
>
>
>
> --
> *Dushantha Nayanajith Chandima Batuwita*
> Software Engineer Support | WSO2
> dushan...@wso2.com
> mobile : 0094777453010 <077%20745%203010>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Udana*
Senior Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] In a ESB sequence, how to continue process in case of error

[Isuru Udana]

Hi Thomas,

In ESB, 404 response is treated as a legitimate message (as similar to
other responses like 200 OK). So neither flow getting stopped nor fault
sequence is getting invoked in this case. Basically message flow behaves
same for both 404 and 200 responses.

If you can provide more details about the issue including your synapse
configurations, we'll able to help you to achieve your requirement.

Thanks.

On Wed, Oct 25, 2017 at 2:40 PM, Vinod Kavinda <vi...@wso2.com> wrote:

> Hi Thomas,
> You can control the error scenarios in your Fault Sequence. If you haven't
> added a fault sequence to your proxy service/ API the default fault
> sequence will be invoked. If you want to control the error scenario, add a
> fault sequence to your synapse configuration and include the relevant logic.
>
> Refer [1] for more info.
>
> [1] - https://docs.wso2.com/display/ESB500/Error+Handling
>
> Regards,
> Vinod
>
> On Mon, Oct 23, 2017 at 4:02 PM, Thomas LEGRAND <
> thomas.legr...@versusmind.eu> wrote:
>
>> Hello,
>>
>> I have an inbound endpoint calling a sequence once triggered. In this
>> sequence, I call a REST API which can return a 404 causing the whole
>> sequence and subsequences to stop. But the return of the API is useful and
>> I would like to continue the process with it even if it is a 404.
>>
>> Have you any idea how I can achieve that ?
>>
>> Regards,
>>
>> Thomas
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Vinod Kavinda
> Senior Software Engineer
> *WSO2 Inc. - lean . enterprise . middleware <http://www.wso2.com>.*
> Mobile : +94 (0) 712 415544
> Blog : http://soatechflicks.blogspot.com/
> [image: http://wso2.com/signature]
> <http://wso2.com/signature>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Udana*
Senior Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Entitlement Mediator is Content Aware

[Isuru Udana]

Hi IsuruH,

I think it shouldn't be content-aware. XACML request generation does not
depend on the incoming request message payload.

Thanks.

On Fri, Oct 13, 2017 at 11:28 AM, Abimaran Kugathasan <abima...@wso2.com>
wrote:

> Because it has to create XACML request for PDP based on the content and
> process response.
>
>
>
> On Fri, Oct 13, 2017 at 6:03 AM, Isuru Haththotuwa <isu...@wso2.com>
> wrote:
>
>> Hi,
>>
>> It seems $subject [1]. Any specific reason?
>>
>> [1]. https://github.com/wso2/carbon-mediation/blob/master/compone
>> nts/mediators/entitlement/org.wso2.carbon.identity.
>> entitlement.mediator/src/main/java/org/wso2/carbon/identity/
>> entitlement/mediator/EntitlementMediator.java
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048 <+94%2071%20635%208048>* <http://wso2.com/>*
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer - API Technologies
>
> Email : abima...@wso2.com
> Mobile : +94 773922820 <077%20392%202820>
>
> <http://stackoverflow.com/users/515034>
> <http://lk.linkedin.com/in/abimaran>
> <http://www.lkabimaran.blogspot.com/>  <https://github.com/abimarank>
> <https://twitter.com/abimaran>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Udana*
Senior Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fixing the cache mediator

[Isuru Udana]

Hi,

On Tue, Jul 4, 2017 at 3:10 PM, Vijitha Ekanayake <vijit...@wso2.com> wrote:

> Hi Riyafa,
>
> Apart from the issues that you have mentioned, we may need to consider
> following points while refactoring the cache mediator implementation.
>
> 1). Verify the cache mediator functionality with different configuration
> parameters and fix if there is anything broken.
> 2). Implement a mechanism to support caching when using the call mediator.
> 3). Feasibility to introduce native JSON caching support to cache mediator.
> 4). Feasibility to introduce service level caching which isn't support at
> the moment.
>
IMO, service level caching is not a requirement as long as we can achieve
all the requirements through the Cache Mediator.

Thanks.

>
>
> Thanks.
>
>
> On Tue, Jul 4, 2017 at 12:06 PM, Riyafa Abdul Hameed <riy...@wso2.com>
> wrote:
>
>> Dear all,
>>
>> By going through the issues faced by the customers in the past I
>> discovered the following issues:
>>
>>1. Continue the execution on cache hit. Reported as an issue in
>>github[1]
>>2. Issue in processing JSON array (payload) with a single element
>>when response caching is enabled where expected response is:
>>
>> [
>>{
>>   "msg":"Hello",
>>   "services":[
>>  "elec",
>>  "patrol"
>>   ],
>>   "test":"World."
>>},
>>{
>>   "msg":"Hi",
>>   "services":[
>>  "water"
>>   ],
>>   "test":"Sri Lanka."
>>}
>> ]
>>
>> but received response is:
>>
>> [
>> { "msg": "Hello", "services": [ "elec", "patrol" ], "test": "World." }
>>
>> ,
>> { "msg": "Hi", "services": "water", "test": "Sri Lanka." }
>>
>> ]
>>
>> This issue has been fixed in the carbon mediation[2].
>>
>>3.  When a xml body with processing instructions is stored in
>> cache and sent back as json it fails with an exception. Issue was reported
>> in 2015 and already has a fix in current EI.
>>
>> Since the last two issues have been already fixed, I would like to know
>> what other issues if any needs to be addressed and if a complete rewrite of
>> the cache mediator would be required.
>>
>> [1] https://github.com/wso2/product-ei/issues/695
>>
>> [2]https://github.com/riyafa/carbon-mediation/commit/7aaf597
>> 988a333e1cad36dc0b5057e24fb779a5c
>>
>>
>> Thank you.
>>
>> Riyafa
>>
>> --
>> Riyafa Abdul Hameed
>> Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>
>>
>> Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
>> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
>> <http://facebook.com/riyafa.ahf>  <http://lk.linkedin.com/in/riyafa>
>> <http://twitter.com/Riyafa1>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Vijitha Ekanayake
> Software Engineer*, *WSO2, Inc.; http://wso2.com/
> Mobile : +94 777 24 73 39 | +94 718 74 44 08
> lean.enterprise.middleware
>



-- 
*Isuru Udana*
Senior Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] EI 6.1.1 - Dev studio mediator project issues

[Isuru Udana]

Hi Sohani,

We also need to include axis2 kernel (this is to get access to axis2
message context)

Thanks.

On Thu, Jun 29, 2017 at 10:45 AM, Sohani Weerasinghe <soh...@wso2.com>
wrote:

> Hi All,
>
> Based on the offline discussion had with Vijitha, shall we only have 
> synapse-core
> (the latest version 2.1.7-wso2v15) and commons-logging?
>
>   
>   commons-logging
>   commons-logging
>   1.1.1
> 
> 
>   org.apache.synapse
>   synapse-core
>   2.1.7-wso2v15
> 
>
> Please confirm.
>
>
> Thanks,
> Sohani Weerasinghe
> Senior Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774 <071%20643%209774>
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Wed, Jun 28, 2017 at 8:31 AM, Sohani Weerasinghe <soh...@wso2.com>
> wrote:
>
>> Reported the issue at [1] and will work on fixing it
>>
>> [1] https://wso2.org/jira/browse/DEVTOOLEI-1117
>>
>> Thanks,
>> Sohani Weerasinghe
>> Senior Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774 <071%20643%209774>
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> On Wed, Jun 28, 2017 at 8:15 AM, Sohani Weerasinghe <soh...@wso2.com>
>> wrote:
>>
>>> Hi Kasun,
>>>
>>> Sure. will have a look
>>>
>>>
>>> Thanks,
>>> Sohani Weerasinghe
>>> Senior Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774 <071%20643%209774>
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>> On Wed, Jun 28, 2017 at 12:04 AM, Kasun Indrasiri <ka...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> When creating the mediator project, there are a bunch of unnecessary
>>>> dependencies added to pom and most of the dependencies are way too old. Can
>>>> we please review this and fix, please.
>>>>
>>>>
>>>>
>>>>   
>>>> 
>>>>   commons-codec.wso2
>>>>   commons-codec
>>>>   1.4.0.wso2v1
>>>> 
>>>> 
>>>>   org.apache.httpcomponents.wso2
>>>>   httpcore
>>>>   4.3.3.wso2v1
>>>> 
>>>> 
>>>>   org.apache.woden.wso2
>>>>   woden
>>>>   1.0.0.M9-wso2v1
>>>> 
>>>> 
>>>>   org.wso2.orbit.commons-httpclient
>>>>   commons-httpclient
>>>>   3.1.0.wso2v3
>>>> 
>>>> 
>>>>   wsdl4j.wso2
>>>>   wsdl4j
>>>>   1.6.2.wso2v4
>>>> 
>>>> 
>>>>   commons-logging
>>>>   commons-logging
>>>>   1.1.1
>>>> 
>>>> 
>>>>   commons-io.wso2
>>>>   commons-io
>>>>   2.4.0.wso2v1
>>>> 
>>>> 
>>>>   org.apache.synapse
>>>>   synapse-core
>>>>   2.1.7-wso2v7
>>>> 
>>>> 
>>>>   org.apache.ws.commons.schema.wso2
>>>>   XmlSchema
>>>>   1.4.7.wso2v3
>>>> 
>>>> 
>>>>   org.apache.geronimo.specs.wso2
>>>>   geronimo-stax-api_1.0_spec
>>>>   1.0.1.wso2v2
>>>> 
>>>> 
>>>>   org.wso2.orbit.org.apache.neethi
>>>>   neethi
>>>>   2.0.4.wso2v5
>>>> 
>>>>   
>>>>
>>>> --
>>>> Kasun Indrasiri
>>>> Director - Integration Architecture
>>>> WSO2, Inc.; http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> cell: +1 650 450 2293 <+1%20650-450-2293>
>>>> Blog : http://kasunpanorama.blogspot.com/
>>>>
>>>
>>>
>>
>


-- 
*Isuru Udana*
Senior Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Use URL re-write mediator with recipient list endpoint

[Isuru Udana]

Hi IsuruH,

URLRewite mediator only works with a single url at a given time.

Thanks.

On Sun, Oct 30, 2016 at 10:44 PM, Isuru Haththotuwa <isu...@wso2.com> wrote:

> Hi Devs,
>
> Can we do $subject? [1, 2]
>
> The endpoints are passed as a comma separated list, and used in recipient
> list endpoint with call mediator:
>
> 
>   
> 
>
> 
>   
> 
>
> The requirement is to do the same URL change in all the endpoints of the
> recipientlist.
>
>
> [1]. https://docs.wso2.com/display/ESB490/Recipient+List+Endpoint
>
> [2]. https://docs.wso2.com/display/ESB490/URLRewrite+Mediator
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
>


-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Scatter and Gather Pattern for Dynamic Endpoints

[Isuru Udana]

On Wed, Oct 5, 2016 at 8:06 PM, Isuru Haththotuwa <isu...@wso2.com> wrote:

> It seems we can't dynamically set min and max values for messageCount of
> completeCondition.
>
> If I omit the min, max response message counts and the timeout, still it
> aggregates the responses. The defaults are -1 for min and max message
> counts and 0 for timeout [1]. How does the mediator figure out when to
> complete the aggregation?
>
Similar to Clone and Iterate mediators, RecepientList endpoint set the
MESSAGE_SEQUENCE before sending the message out, using that Aggregate
Mediator figure out what's needed to be aggregated.

>
> [1]. https://github.com/wso2/wso2-synapse/blob/Apache-Synapse-2.
> 1.5-wso2v2/modules/core/src/main/java/org/apache/synapse/
> mediators/eip/aggregator/Aggregate.java#L42
>
> On Wed, Oct 5, 2016 at 7:11 AM, Isuru Haththotuwa <isu...@wso2.com> wrote:
>
>>
>>
>> On Wed, Oct 5, 2016 at 7:10 AM, Isuru Haththotuwa <isu...@wso2.com>
>> wrote:
>>
>>> Additionally, is it possible to set min and max values for messageCount
>>> of completeCondition to be dynamically picked, preferably property, etc?
>>>
>> Meant to say 'preferably from a msg context property'
>>
>>>
>>> On Mon, Oct 3, 2016 at 9:57 PM, Isuru Haththotuwa <isu...@wso2.com>
>>> wrote:
>>>
>>>> Thanks for the info IsuruU and Viraj. Will check this.
>>>>
>>>> On Mon, Oct 3, 2016 at 10:03 AM, Viraj Rajaguru <vi...@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> On Mon, Oct 3, 2016 at 7:43 AM, Isuru Udana <isu...@wso2.com> wrote:
>>>>>
>>>>>> Hi Isuru,
>>>>>>
>>>>>> By looking at the synapse code of RecipientListEndpoint, I can see
>>>>>> that there is an option to pick endpoint list dynamically. I am not sure
>>>>>> whether that is configurable through tooling. You may have a look on 
>>>>>> that.
>>>>>>
>>>>>
>>>>> ESB Tooling supports RecipientListEndpoint configurations.
>>>>>
>>>>> Thanks,
>>>>> Viraj.
>>>>>
>>>>>>
>>>>>> Please note that I haven't tried it out.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>>
>>>>>> On Sun, Oct 2, 2016 at 11:12 AM, Isuru Haththotuwa <isu...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Missed the link:
>>>>>>>
>>>>>>> [1]. https://docs.wso2.com/display/IntegrationPatterns/Scatter-Ga
>>>>>>> ther
>>>>>>>
>>>>>>> On Sun, Oct 2, 2016 at 11:12 AM, Isuru Haththotuwa <isu...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Devs,
>>>>>>>>
>>>>>>>> Do we support $subject with latest ESB? The use case is as follows:
>>>>>>>>
>>>>>>>>- The endpoints are dynamically picked up during the mediation
>>>>>>>>flow (Ex. via a DB query, etc.). The number of endpoints are not 
>>>>>>>> fixed
>>>>>>>>- In the aggregation, need to wait till the all the endpoints
>>>>>>>>to which the request were sent returns a response
>>>>>>>>
>>>>>>>> In the EIP sample [1], we can achieve the same with a fixed number
>>>>>>>> of endpoints. Can we do the same with a dynamic number of endpoints?
>>>>>>>>
>>>>>>>> --
>>>>>>>> Thanks and Regards,
>>>>>>>>
>>>>>>>> Isuru H.
>>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Thanks and Regards,
>>>>>>>
>>>>>>> Isuru H.
>>>>>>> +94 716 358 048* <http://wso2.com/>*
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Isuru Udana*
>>>>>> Technical Lead
>>>>>> WSO2 Inc.; http://wso2.com
>>>>>> email: isu...@wso2.com cell: +94 77 3791887
>>>>>> blog: http://mytecheye.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Viraj Rajaguru
>>>>> Associate Technical Lead
>>>>> WSO2 Inc. : http://wso2.com
>>>>>
>>>>> Mobile: +94 77 3683068
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> +94 716 358 048* <http://wso2.com/>*
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* <http://wso2.com/>*
>>>
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
>


-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Aggregate Mediator Disregarding 'enclosingElementProperty'

[Isuru Udana]

Hi Isuru,

Property name is "aggregated_response" and the value is following.

* http://abc.com/>" />*

So message is getting added to above element as a child.

Thanks.

On Mon, Oct 3, 2016 at 10:17 PM, Isuru Haththotuwa <isu...@wso2.com> wrote:

> Hi,
>
> $subject. The relevant in and out sequences are at [1]. Here, I expect the
> aggregated response to be in a root element element named
> 'aggregated_response'. But the actual response has the root element as
> 'Information' [2]. This is APIM 1.10, synapse version is 2.1.5.wso2v2. Any
> idea why this is happening?
>
> [1].
>   
> 
>  
> 
>  expression="get-property('SYSTEM_TIME')"/>
>
>   
>  
>  
>  
>   
>
> 
> 
>
>   
>  
>   
>
> 
>  
>   
>   
>   
>
>
> * 
> http://abc.com>" />
> *
>   
>  
> 
>  
> *  enclosingElementProperty="aggregated_response">*
> 
>  
>  
>   
>
> [2].
> {
>   "Information": [
> {
>   "msg": "hello world!"
> },
> {
>   "msg": "new Hello World!!"
> }
>   ]
> }
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
>


-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Scatter and Gather Pattern for Dynamic Endpoints

[Isuru Udana]

Hi Isuru,

By looking at the synapse code of RecipientListEndpoint, I can see that
there is an option to pick endpoint list dynamically. I am not sure whether
that is configurable through tooling. You may have a look on that.

Please note that I haven't tried it out.

Thanks.


On Sun, Oct 2, 2016 at 11:12 AM, Isuru Haththotuwa <isu...@wso2.com> wrote:

> Missed the link:
>
> [1]. https://docs.wso2.com/display/IntegrationPatterns/Scatter-Gather
>
> On Sun, Oct 2, 2016 at 11:12 AM, Isuru Haththotuwa <isu...@wso2.com>
> wrote:
>
>> Hi Devs,
>>
>> Do we support $subject with latest ESB? The use case is as follows:
>>
>>- The endpoints are dynamically picked up during the mediation flow
>>(Ex. via a DB query, etc.). The number of endpoints are not fixed
>>- In the aggregation, need to wait till the all the endpoints to
>>which the request were sent returns a response
>>
>> In the EIP sample [1], we can achieve the same with a fixed number of
>> endpoints. Can we do the same with a dynamic number of endpoints?
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
>


-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading Java version

[Isuru Udana]

Hi Harshana,

Please refer to following documentation link for ESB 4.9.0 supported JDK
version.

https://docs.wso2.com/display/ESB490/Installation+Prerequisites

Thanks.

On Fri, Sep 2, 2016 at 5:30 PM, Harshana Porawagama <harsh...@techcert.lk>
wrote:

> Hi Thusitha,
>
> Thank you for the information.
>
> On 02/09/2016 04:55 PM, Thusitha Thilina Dayaratne wrote:
>
> Hi Hashana,
>
> All the WSO2 products which are based on carbon kernel 4.4.x are
> compatible with Java 7 and 8. Therefore there won;t be any compatibility
> issues.
>
> Thanks
>
> On Fri, Sep 2, 2016 at 4:26 PM, Harshana Porawagama <harsh...@techcert.lk>
> wrote:
>
>> Hi,
>>
>> We are using WSO2 ESB version 4.9 on Ubuntu 14.04 LTS. In this server we
>> have Oracle Java version 1.7.0 _45 installed. We need to upgrade this to
>> version 1.8.0 _91 due to some critical vulnerabilities in the current
>> version. Will there be any compatibility issues with ESB 4.9 if we upgrade
>> Oracle Java ?
>>
>> --
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
> <http://wso2.com/signature>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Appending the property to HTTP endpoint

[Isuru Udana]

Hi Shamran,

I assume that you are trying to fetch some value from the request using
xpath //ticket and assigning it to the endpoint url.

First you need to set a property extracting the value from xpath.



Please note that property name must have the prefix uri.var .

Then at the HTTPEndpoint, we can assign that property value to the
uri-template as follows.

http://localhost:8080/alfresco/s/api/site/folder/
site1/documentLibrary/f1/f2?alf_ticket={uri.var.prop1}


Thanks.

On Thu, Aug 18, 2016 at 9:36 AM, Shamran Siddique <ssiddi...@zaizi.com>
wrote:

> Hi there,
>
> I was trying to append the property to the HTTP endpoint which will
> connect the wso2 esb with Alfresco.
>
> *This is my property variable:*
>
> //ticket
>
> *This is my endpoint API looks like: *
>
> http://localhost:8080/alfresco/s/api/site/folder/
> site1/documentLibrary/f1/f2?alf_ticket={here I have to add the property -
> ticket}
>
> I dont know how to add it. Please help.
>
> Thanks in Advance!
>
> Regards,
> Shamran.
>
> --
> This message should be regarded as confidential. If you have received this
> email in error please notify the sender and destroy it immediately.
> Statements of intent shall only become binding when confirmed in hard copy
> by an authorised signatory.
>
> Zaizi Ltd is registered in England and Wales with the registration number
> 6440931. The Registered Office is Brook House, 229 Shepherds Bush Road,
> London W6 7AN.
>



-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Misleading Aggregate Mediator Description

[Isuru Udana]

Hi Praneesha,

I will get back soon.


On Wed, Jul 27, 2016 at 8:15 PM, Praneesha Chandrasiri <pranee...@wso2.com>
wrote:

> hi Isuru,
>
> A kind reminder on this, in case you missed this email.
>
>
> On Thu, Jul 21, 2016 at 5:05 PM, Praneesha Chandrasiri <pranee...@wso2.com
> > wrote:
>
>> hi Isuru,
>>
>> This is a kind reminder on the above.
>>
>> On Tue, Jul 12, 2016 at 6:30 PM, Praneesha Chandrasiri <
>> pranee...@wso2.com> wrote:
>>
>>> hi Isuru,
>>>
>>> Could you please review the above description given by Rajeevan, so that
>>> I can work on [1] to add it to ESB docs.
>>>
>>> [1] https://wso2.org/jira/browse/DOCUMENTATION-3539
>>>
>>> On Wed, Jun 29, 2016 at 7:46 AM, Vimalanathan Rajeevan <
>>> rajeev...@wso2.com> wrote:
>>>
>>>> Thanks Isuru for your response.
>>>>
>>>> What about the description below?
>>>>
>>>> The *Aggregate mediator* implements the Aggregator enterprise
>>>> integration pattern
>>>> <http://docs.wso2.org/wiki/display/IntegrationPatterns/Aggregator> and
>>>> aggregates the *response messages* for messages that were split by the
>>>> Clone <https://docs.wso2.com/display/ESB490/Clone+Mediator> or Iterate
>>>> <https://docs.wso2.com/display/ESB490/Iterate+Mediator> mediator.
>>>>
>>>> Does this explain the full functionality of Aggregate mediator?
>>>> Appreciate your response on this.
>>>>
>>>> Thanks,
>>>> Rajeevan
>>>>
>>>> On Tue, Jun 28, 2016 at 1:48 AM, Isuru Udana <isu...@wso2.com> wrote:
>>>>
>>>>> Hi Rajeevan,
>>>>>
>>>>> On Tue, Jun 28, 2016 at 10:11 AM, Vimalanathan Rajeevan <
>>>>> rajeev...@wso2.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> The description[1] is as below,
>>>>>>
>>>>>> The *Aggregate mediator* implements the Aggregator enterprise
>>>>>> integration pattern
>>>>>> <http://docs.wso2.org/wiki/display/IntegrationPatterns/Aggregator>
>>>>>> and aggregates the *response messages* for messages that were split
>>>>>> by the Clone <https://docs.wso2.com/display/ESB490/Clone+Mediator>
>>>>>> or Iterate <https://docs.wso2.com/display/ESB490/Iterate+Mediator>
>>>>>> mediator and sent using the Send
>>>>>> <https://docs.wso2.com/display/ESB490/Send+Mediator> mediator.
>>>>>>
>>>>>> Doesn't above paragraph mean that Aggregate mediator will aggregate
>>>>>> messages and send that using a Send mediator even if we don't explicitly
>>>>>> call Send mediator?
>>>>>> Also as I believe there are some places we don't even use a Send
>>>>>> mediator when there is an Aggregate mediator.
>>>>>> Appreciate your thoughts on this.
>>>>>>
>>>>> Thanks for pointing this, It seems above statement is confusing. And
>>>>> as you mentioned there are situations where we are not using the send
>>>>> mediator.
>>>>>
>>>>> We need a better description which explains the behaviour.
>>>>>
>>>>>
>>>>>> [1] https://docs.wso2.com/display/ESB490/Aggregate+Mediator
>>>>>>
>>>>>> Thanks,
>>>>>> Rajeevan
>>>>>> --
>>>>>> Vimalanathan Rajeevan
>>>>>> Software Engineer,
>>>>>> WSO2, Inc. *http://wso2.com* <http://wso2.com>
>>>>>> Lean.Enterprise.Middleware
>>>>>>
>>>>>> Mobile:
>>>>>> *+94 773090875 <%2B94%20773090875>*
>>>>>> LinkedIn:
>>>>>> *https://www.linkedin.com/in/RajeevanVimalanathan
>>>>>> <https://www.linkedin.com/in/rajeevanvimalanathan>*
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Isuru Udana*
>>>>> Technical Lead
>>>>> WSO2 Inc.; http://wso2.com
>>>>> email: isu...@wso2.com cell: +94 77 3791887
>>>>> blog: http://mytecheye.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Vimalanathan Rajeevan
>>>> Software Engineer,
>>>> WSO2, Inc. *http://wso2.com* <http://wso2.com>
>>>> Lean.Enterprise.Middleware
>>>>
>>>> Mobile:
>>>> *+94 773090875 <%2B94%20773090875>*
>>>> LinkedIn:
>>>> *https://www.linkedin.com/in/RajeevanVimalanathan
>>>> <https://www.linkedin.com/in/rajeevanvimalanathan>*
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks & Best Regards,
>>> *Praneesha Chandrasiri*
>>> *Technical Writer*
>>> *WSO2 Inc. *
>>> *Mobile: +(94) 718156888 <%2B%2894%29%20718156888>*
>>> *E-mail: pranee...@wso2.com <pranee...@wso2.com>*
>>>
>>>
>>
>>
>> --
>> Thanks & Best Regards,
>> *Praneesha Chandrasiri*
>> *Technical Writer*
>> *WSO2 Inc. *
>> *Mobile: +(94) 718156888 <%2B%2894%29%20718156888>*
>> *E-mail: pranee...@wso2.com <pranee...@wso2.com>*
>> <http://wso2.com/signature>
>>
>>
>
>
> --
> Thanks & Best Regards,
> *Praneesha Chandrasiri*
> *Technical Writer*
> *WSO2 Inc. *
> *Mobile: +(94) 718156888 <%2B%2894%29%20718156888>*
> *E-mail: pranee...@wso2.com <pranee...@wso2.com>*
> <http://wso2.com/signature>
>
>


-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Continous SSL handshake requests triggering from ESB 5.0.0-Pre-Beta2 after latest component updates

[Isuru Udana]

4 54  .bO.._Zg...T
> 0010: AF A3 8F DB 4B EE 7D A6   F0 21 9B 40 B4 64 59 C7  K!.@.dY.
> 0020: 1A 46 6B 06 B2 59 F9 3D   5B 41 A4 38 F6 C0 3B B2  .Fk..Y.=[A.8..;.
> Client MAC write Secret:
> : B9 23 FE 7E AA 03 36 0B   C1 AB 8C 3C F2 C4 43 03  .#6<..C.
> 0010: A8 28 DF DB 07 3C FA 48   F4 60 D6 8D B6 09 E0 49  .(...<.H.`.I
> Server MAC write Secret:
> : 79 7A AF 05 68 CA E7 40   C2 AF 2E 05 02 1C ED 4E  yz..h..@...N
> 0010: 74 03 4F E6 26 BD 47 60   40 B7 47 90 D0 95 74 04  t.O.&.G`@.G...t.
> Client write key:
> : 9B C5 33 41 CB 46 E4 27   80 00 D8 26 22 51 62 66  ..3A.F.'...&"Qbf
> Server write key:
> : 99 F8 08 74 95 B8 4F CA   10 56 41 25 0C 6D 7D 6E  ...t..O..VA%.m.n
> ... no IV derived for this protocol
> http-nio-9443-exec-14, WRITE: TLSv1.2 Handshake, length = 81
> http-nio-9443-exec-14, WRITE: TLSv1.2 Change Cipher Spec, length = 1
> *** Finished
> verify_data:  { 34, 13, 158, 199, 232, 62, 238, 170, 75, 167, 35, 35 }
> ***
> http-nio-9443-exec-14, WRITE: TLSv1.2 Handshake, length = 80
> http-nio-9443-exec-17, READ: TLSv1.2 Change Cipher Spec, length = 1
> http-nio-9443-exec-9, READ: TLSv1.2 Handshake, length = 80
> *** Finished
> verify_data:  { 227, 105, 49, 249, 16, 87, 205, 237, 68, 143, 188, 57 }
> ***
> http-nio-9443-exec-9, WRITE: TLSv1.2 Application Data, length = 374
> http-nio-9443-exec-21, READ: TLSv1.2 Alert, length = 64
> http-nio-9443-exec-21, RECV TLSv1.2 ALERT:  warning, close_notify
> http-nio-9443-exec-21, closeInboundInternal()
> http-nio-9443-exec-21, closeOutboundInternal()
> http-nio-9443-exec-21, SEND TLSv1.2 ALERT:  warning, description =
> close_notify
> http-nio-9443-exec-21, WRITE: TLSv1.2 Alert, length = 64
> http-nio-9443-exec-21, called closeOutbound()
> http-nio-9443-exec-21, closeOutboundInternal()
> Using SSLEngineImpl.
> Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_GCM_SHA384
> Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA
> Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
> Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
> Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
> Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256
> Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA
> Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384
> Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
> Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_GCM_SHA384
> Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
> Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
> Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
> Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384
> Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
> Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
> Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
> Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
> Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
> Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
> Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
> Allow unsafe renegotiation: false
> Allow legacy hello messages: true
> Is initial handshake: true
> Is secure renegotiation: false
> Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
> for TLSv1
> Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
> for TLSv1
> Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
> for TLSv1
> Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
> for TLSv1
> Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 for
> TLSv1
> Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 for
> TLSv1
> Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
> for TLSv1.1
> Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
> for TLSv1.1
> Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
> for TLSv1.1
> Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
> for TLSv1.1
> Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 for
> TLSv1.1
> Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 for
> TLSv1.1
> http-nio-9443-exec-16, READ: TLSv1.2 Handshake, length = 267
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; ht

Re: [Dev] Misleading Aggregate Mediator Description

[Isuru Udana]

Hi Rajeevan,

On Tue, Jun 28, 2016 at 10:11 AM, Vimalanathan Rajeevan <rajeev...@wso2.com>
wrote:

> Hi,
>
> The description[1] is as below,
>
> The *Aggregate mediator* implements the Aggregator enterprise integration
> pattern <http://docs.wso2.org/wiki/display/IntegrationPatterns/Aggregator>
> and aggregates the *response messages* for messages that were split by
> the Clone <https://docs.wso2.com/display/ESB490/Clone+Mediator> or Iterate
> <https://docs.wso2.com/display/ESB490/Iterate+Mediator> mediator and sent
> using the Send <https://docs.wso2.com/display/ESB490/Send+Mediator>
> mediator.
>
> Doesn't above paragraph mean that Aggregate mediator will aggregate
> messages and send that using a Send mediator even if we don't explicitly
> call Send mediator?
> Also as I believe there are some places we don't even use a Send mediator
> when there is an Aggregate mediator.
> Appreciate your thoughts on this.
>
Thanks for pointing this, It seems above statement is confusing. And as you
mentioned there are situations where we are not using the send mediator.

We need a better description which explains the behaviour.


> [1] https://docs.wso2.com/display/ESB490/Aggregate+Mediator
>
> Thanks,
> Rajeevan
> --
> Vimalanathan Rajeevan
> Software Engineer,
> WSO2, Inc. *http://wso2.com* <http://wso2.com>
> Lean.Enterprise.Middleware
>
> Mobile:
> *+94 773090875 <%2B94%20773090875>*
> LinkedIn:
> *https://www.linkedin.com/in/RajeevanVimalanathan
> <https://www.linkedin.com/in/rajeevanvimalanathan>*
>



-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Carbon Netty ] Default value for "executor.workerpool.size"

[Isuru Udana]

Hi Sagara,

Yes, we are working on setting sensible default values from the code, which
will be available in next transport release.

Thanks.

On Wed, Jun 22, 2016 at 10:36 PM, Sagara Gunathunga <sag...@wso2.com> wrote:

>
> It seems there is no default value available for
>  "executor.workerpool.size" setting, when explicitly not set  transport
> fail with NPE, can we have a sensible default value here ?
>
> Thanks !
> --
> Sagara Gunathunga
>
> Architect; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>


-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB Tooling] Can we activate "event statistics" on global level?

[Isuru Udana]

Hi,


On Wed, Jun 22, 2016 at 1:45 PM, Chanaka Fernando <chana...@wso2.com> wrote:

> Hi Viraj,
>
> The configuration we have in the synapse.properties file is to globally
> enable/disable the statistics/tracing for the server. By enabling that, we
> prepare the server to publish events to DAS server. But, if you need to
> publish real events, you need to enable them in individual artifacts
> (proxy, api, sequence, etc). Iranga's suggestion is to provide a global
> parameter to enable/disable them all at once (per CAPP or at global level).
> This is a valid requirement which a particular user might have.
>
> Enable/disable statistics per CAR from the tool is ok, but should we do
the global level controlling at the tool level ?
Enabling statics globally is a management task.
CARs are for packaging and deployable artifacts.
Using CARs to control global level parameters doesn't sound nice to me.


> This will require a considerable effort to support in the current model
> and we will not be able to support in the upcoming ESB 5.0.0 version.
>
> @Iranga: Please create a public JIRA and we will fix this in a future
> release.
>
> Thanks,
> Chanaka
>
> On Wed, Jun 22, 2016 at 12:38 PM, Viraj Rajaguru <vi...@wso2.com> wrote:
>
>> Hi Iranga,
>>
>> IIUC, requirement is to setting a global level setting with CAR files to
>> enable event statistics publishing. As per this document[1], we need to set
>> a property in synapse.properties file + relevant config changes in artifact
>> files to enable statistics publishing. With CAR files we are not modifying
>> config files such as synapse.properties. So how can we achieve this?
>>
>> Thanks,
>> Viraj.
>>
>> [1] -
>> https://docs.wso2.com/display/ESB500/Prerequisites+to+Publish+Statistics
>>
>> On Fri, Apr 29, 2016 at 12:12 PM, Iranga Muthuthanthri <ira...@wso2.com>
>> wrote:
>>
>>>
>>>
>>> On Fri, Apr 29, 2016 at 11:35 AM, Malaka Silva <mal...@wso2.com> wrote:
>>>
>>>> +1 and it make sense to do it since we are having the
>>>> a separate analytics server for ESB.
>>>>
>>>> Iranga when you say global do you mean for a CAPP or for the complete
>>>> deployment? I think you are referring to the second option.
>>>>
>>>
>>> Global setting -Having it at complete deployment  , having it at the
>>> C-App level  would also be a useful option as well IMO
>>>
>>>>
>>>> On Fri, Apr 29, 2016 at 11:20 AM, Iranga Muthuthanthri <ira...@wso2.com
>>>> > wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> When creating a C-App to publish event statistics to ESB Analytics we
>>>>> have to enable event statistics for each configuration ( proxy service,
>>>>> API,) , would there be an option to set this at a global level?
>>>>>
>>>>> --
>>>>> Thanks & Regards
>>>>>
>>>>> Iranga Muthuthanthri
>>>>> (M) -0777-255773
>>>>> Team Product Management
>>>>>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Best Regards,
>>>>
>>>> Malaka Silva
>>>> Senior Tech Lead
>>>> M: +94 777 219 791
>>>> Tel : 94 11 214 5345
>>>> Fax :94 11 2145300
>>>> Skype : malaka.sampath.silva
>>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>>> Blog : http://mrmalakasilva.blogspot.com/
>>>>
>>>> WSO2, Inc.
>>>> lean . enterprise . middleware
>>>> http://www.wso2.com/
>>>> http://www.wso2.com/about/team/malaka-silva/
>>>> <http://wso2.com/about/team/malaka-silva/>
>>>> https://store.wso2.com/store/
>>>>
>>>> Save a tree -Conserve nature & Save the world for your future. Print
>>>> this email only if it is absolutely necessary.
>>>>
>>>
>>>
>>>
>>> --
>>> Thanks & Regards
>>>
>>> Iranga Muthuthanthri
>>> (M) -0777-255773
>>> Team Product Management
>>>
>>>
>>
>>
>> --
>> Viraj Rajaguru
>> Associate Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>
>
>
> --
> 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
>
>
>
>
>


-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Encrypting VFS URL

[Isuru Udana]

Hi Manu,

Values for these parameters are set at the deploy time and can only have
static values.
Unfortunately there is no way achieve this using vfs proxy.

In inbound endpoints, we have provided a way to fetch parameters from the
registry.
However still we cannot use expressions like vault-lookup for inbound
parameters.

Thanks.


On Fri, Jun 10, 2016 at 2:48 AM, Manuranga Perera <m...@wso2.com> wrote:

> I have a FTP secured by a password/username. I want to secure the
> password.I can use vfs encrypt utils [1], but it is trivially decodable.
>
> Is there a way to use a secure vault for this?
>
> I tried following
>
> http://ws.apache.org/ns/synapse; name="vfsy"
> transports="https http vfs" startOnLoad="true" trace="disable">
>
>   
>  
>   
>
>*{wso2:vault-lookup('vfsUrl')}*
> 
>text/plain
>...
> 
>
> but unfortunately that didn't work
>
> [2016-06-09] ERROR - VFSTransportListener Repeatedly failed to resolve the
> file URI: {wso2:vault-lookup('vfsUrl')}
> org.apache.commons.vfs2.FileSystemException: Could not find file with URI
> "{wso2:vault-lookup('vfsUrl')}" because it is a relative path, and no base
> URI was provided.
>
>
> [1]
> http://wso2.com/library/articles/2012/01/wso2-esb-example-file-exchanging-hub-part-1/
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>



-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Option to ship MQTT client lib with ESB

[Isuru Udana]

Hi Pamod, Ramith,

I think we should try to de-couple our component from external libs as much
as we can. If we do this even for a minor version upgrade either we have
wait until the next release or else we need to patch the server. In the
current approach it is just a matter of dropping the new library.
If we don't have direct code level dependancies to a particular library,
IMO we should not pack it.

Thanks.


On Wed, Jun 8, 2016 at 1:39 PM, Pamod Sylvester <pa...@wso2.com> wrote:

> Hi Ramith,
>
> Yes. That's something to think about.
>
> AFAIK currently there's no explicit way to handle the library upgrades.
> Unless the upgrade includes with either a new ESB release or a patch.
>
> Since the client library generic and is tested for interoperability for a
> given version of MQTT protocol, AFAIU the chance would be less for client
> library to require a mandatory upgrade for each broker release, unless the
> broker changes the supporting protocol version.
>
> Thanks,
> Pamod
>
> On Wed, Jun 8, 2016 at 12:27 PM, Ramith Jayasinghe <ram...@wso2.com>
> wrote:
>
>> +1. that's a good idea. BTW, how are we going to handle version upgrades
>> (for client lib) ?
>>
>> On Wed, Jun 8, 2016 at 7:19 AM, Pamod Sylvester <pa...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> Could we consider the $Subject, (since the library is interoperable with
>>> all standard MQTT brokers).
>>>
>>> Currently it requires client lib to be separately downloaded when
>>> integrating with a broker [1]
>>>
>>> [1]
>>> https://docs.wso2.com/display/ESB490/Sample+906%3A+Inbound+Endpoint+MQTT+Protocol+Sample
>>>
>>> Thanks,
>>> Pamod
>>>
>>> --
>>> *Pamod Sylvester *
>>>
>>> *WSO2 Inc.; http://wso2.com <http://wso2.com>*
>>> cell: +94 77 7779495
>>>
>>
>>
>>
>> --
>> Ramith Jayasinghe
>> Technical Lead
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> E: ram...@wso2.com
>> P: +94 772534930
>>
>
>
>
> --
> *Pamod Sylvester *
>
> *WSO2 Inc.; http://wso2.com <http://wso2.com>*
> cell: +94 77 7779495
>



-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB Blocking call mediator

[Isuru Udana]

Hi Godwin,

I think key-expressions are not supported in blocking mode.
@Kathees,
Can you please confirm ?

Thanks.

On Wed, Jun 8, 2016 at 3:08 AM, Godwin Shrimal <god...@wso2.com> wrote:

> Hi All,
>
> When I use call mediator in my sequence as below it gives error [1].
>
> 
>
> 
>
> 
> If I change the code as any of below, its works fine.
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> Do we have a problem in Call mediator with the combination of *blocking=true
> *and *key-expression *in endpoint ?
>
>
> [1] org.apache.synapse.SynapseException: Error while performing the call
> operation
> at
> org.apache.synapse.mediators.builtin.CallMediator.handleFault(CallMediator.java:306)
> at
> org.apache.synapse.mediators.builtin.CallMediator.handleBlockingCall(CallMediator.java:119)
> at
> org.apache.synapse.mediators.builtin.CallMediator.mediate(CallMediator.java:85)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
> at
> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
> at
> org.apache.synapse.message.processor.impl.sampler.SamplingService$1.run(SamplingService.java:211)
> 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(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at
> org.apache.synapse.message.senders.blocking.BlockingMsgSender.send(BlockingMsgSender.java:114)
> at
> org.apache.synapse.mediators.builtin.CallMediator.handleBlockingCall(CallMediator.java:113)
>
>
> Thanks
> Godwin
>
> --
> *Godwin Amila Shrimal*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D <http://lnkd.in/KUum6D>*
> twitter: https://twitter.com/godwinamila
>



-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Pass dynamic values to class mediator

[Isuru Udana]

Hi Godwin,

For now we only have the option I suggested above and yes supporting
expressions as class mediator parameters is a good improvement we can do in
a future release.

Thanks.

On Thu, Jun 2, 2016 at 7:31 PM, Godwin Shrimal <god...@wso2.com> wrote:

> Hi Kathees/Isuru,
>
> I think we can solve the issue using property straightforward. But still
> there are good use cases which need to pass dynamic values to class
> mediator may be we can improve in future release. Passing parameter to a
> class mediator is more readable for developers/users from API perception
> other than reading a property inside it.
>
>
> Thanks
> Godwin
>
>
> On Thu, Jun 2, 2016 at 12:54 AM, Kathees Rajendram <kath...@wso2.com>
> wrote:
>
>> Hi Godwin/Isuru,
>>
>> This may not be a good approach. You can define a static property. In
>> static property you can dynamically assign dynamic properties and values as
>> key value pairs with the patterns (dynamicProperty1: value1,
>> dynamicProperty2: value2, etc.).
>>
>> dynamicProperty1: value1, dynamicProperty2:
>> value2
>>
>> In the class mediator, you can read the static property and you need to
>> write a login to get each values of the dynamic properties.
>> Thanks,
>> Kathees
>>
>> On Thu, Jun 2, 2016 at 10:46 AM, Isuru Udana <isu...@wso2.com> wrote:
>>
>>> Hi Rajjaz,
>>>
>>> Godwin is asking about class mediators not connectors.
>>>
>>>
>>>
>>> On Thu, Jun 2, 2016 at 10:38 AM, Rajjaz Mohammed <raj...@wso2.com>
>>> wrote:
>>>
>>>> Hi Godwin,
>>>> You can receive dynamic values in class level without set in the
>>>> property configuration.
>>>>
>>>> for example:
>>>> 
>>>> raj
>>>> >>> >com.sun.enterprise.naming.SerialInitContextFactory>>> raj.java.naming.factory.initial>
>>>> localhost>>> raj.org.omg.CORBA.ORBInitialHost>
>>>> 3700>>> raj.org.omg.CORBA.ORBInitialPort>
>>>> 
>>>>
>>>> these values are dynamic values so we can receive these values in code
>>>> level without set property[1].
>>>>
>>>> [1]
>>>> https://github.com/wso2-extensions/esb-connector-ejb2.0/blob/master/src/main/java/org/wso2/carbon/custom/connector/EJBUtil.java#L131
>>>>
>>>>
>>>>
>>>> On Thu, Jun 2, 2016 at 9:09 AM, Godwin Shrimal <god...@wso2.com> wrote:
>>>>
>>>>> Hi Isuru,
>>>>>
>>>>> Thanks for quick response, I'll proceed with by setting property.
>>>>>
>>>>>
>>>>> Thanks
>>>>> Godwin
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Jun 1, 2016 at 10:32 PM, Isuru Udana <isu...@wso2.com> wrote:
>>>>>
>>>>>> Hi Godwin,
>>>>>>
>>>>>> It is not possible to pass dynamic values using the property
>>>>>> configuration element. It only support static values.
>>>>>>
>>>>>> The only option is to set some property using the property mediator
>>>>>> and within the class mediator code read that property using
>>>>>> synCtx.getProperty('prop_name_here')
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> On Thu, Jun 2, 2016 at 8:54 AM, Godwin Shrimal <god...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> How can we pass dynamic values to class mediator ?, if we try to do
>>>>>>> as below it give a error *A Class mediator property must specify
>>>>>>> name and value attributes, or a name and a child XML fragment*
>>>>>>>
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>
>>>>>>> How can we achieve this ?
>>>>>>>
>>>>>>> Thanks
>>>>>>> Godwin
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Godwin Amila Shrimal*
>>>>>>> Senior Software Engineer
>>>>>>> WSO2 Inc.; http://wso2.com
>>>>>>> lean.enterprise.middleware
>>>>>>>
>>>>>>> mobile: *+94772264165*
>>

Re: [Dev] Pass dynamic values to class mediator

[Isuru Udana]

Hi Rajjaz,

Godwin is asking about class mediators not connectors.



On Thu, Jun 2, 2016 at 10:38 AM, Rajjaz Mohammed <raj...@wso2.com> wrote:

> Hi Godwin,
> You can receive dynamic values in class level without set in the property
> configuration.
>
> for example:
> 
> raj
>  >com.sun.enterprise.naming.SerialInitContextFactory raj.java.naming.factory.initial>
> localhost raj.org.omg.CORBA.ORBInitialHost>
> 3700 raj.org.omg.CORBA.ORBInitialPort>
> 
>
> these values are dynamic values so we can receive these values in code
> level without set property[1].
>
> [1]
> https://github.com/wso2-extensions/esb-connector-ejb2.0/blob/master/src/main/java/org/wso2/carbon/custom/connector/EJBUtil.java#L131
>
>
>
> On Thu, Jun 2, 2016 at 9:09 AM, Godwin Shrimal <god...@wso2.com> wrote:
>
>> Hi Isuru,
>>
>> Thanks for quick response, I'll proceed with by setting property.
>>
>>
>> Thanks
>> Godwin
>>
>>
>>
>> On Wed, Jun 1, 2016 at 10:32 PM, Isuru Udana <isu...@wso2.com> wrote:
>>
>>> Hi Godwin,
>>>
>>> It is not possible to pass dynamic values using the property
>>> configuration element. It only support static values.
>>>
>>> The only option is to set some property using the property mediator and
>>> within the class mediator code read that property using
>>> synCtx.getProperty('prop_name_here')
>>>
>>> Thanks.
>>>
>>> On Thu, Jun 2, 2016 at 8:54 AM, Godwin Shrimal <god...@wso2.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> How can we pass dynamic values to class mediator ?, if we try to do as
>>>> below it give a error *A Class mediator property must specify name and
>>>> value attributes, or a name and a child XML fragment*
>>>>
>>>> 
>>>> 
>>>> 
>>>>
>>>> How can we achieve this ?
>>>>
>>>> Thanks
>>>> Godwin
>>>>
>>>>
>>>> --
>>>> *Godwin Amila Shrimal*
>>>> Senior Software Engineer
>>>> WSO2 Inc.; http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> mobile: *+94772264165*
>>>> linkedin: *http://lnkd.in/KUum6D <http://lnkd.in/KUum6D>*
>>>> twitter: https://twitter.com/godwinamila
>>>>
>>>
>>>
>>>
>>> --
>>> *Isuru Udana*
>>> Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>> email: isu...@wso2.com cell: +94 77 3791887
>>> blog: http://mytecheye.blogspot.com/
>>>
>>
>>
>>
>> --
>> *Godwin Amila Shrimal*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *http://lnkd.in/KUum6D <http://lnkd.in/KUum6D>*
>> twitter: https://twitter.com/godwinamila
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thank you
> Best Regards
>
> *Rajjaz HM*
> Associate Software Engineer
> Platform Extension Team
> WSO2 Inc. <http://wso2.com/>
> lean | enterprise | middleware
> Mobile | +94752833834|+94777226874
> Email   | raj...@wso2.com
> LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger
> <http://wso2experience.blogspot.com/> | WSO2 Profile
> <http://wso2.com/about/team/mohammer-rajjaz/>
>



-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Pass dynamic values to class mediator

[Isuru Udana]

Hi Godwin,

It is not possible to pass dynamic values using the property configuration
element. It only support static values.

The only option is to set some property using the property mediator and
within the class mediator code read that property using
synCtx.getProperty('prop_name_here')

Thanks.

On Thu, Jun 2, 2016 at 8:54 AM, Godwin Shrimal <god...@wso2.com> wrote:

> Hi All,
>
> How can we pass dynamic values to class mediator ?, if we try to do as
> below it give a error *A Class mediator property must specify name and
> value attributes, or a name and a child XML fragment*
>
> 
> 
> 
>
> How can we achieve this ?
>
> Thanks
> Godwin
>
>
> --
> *Godwin Amila Shrimal*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D <http://lnkd.in/KUum6D>*
> twitter: https://twitter.com/godwinamila
>



-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] What is the Jira project for "carbon-gateway-framework"

[Isuru Udana]

Hi Lahiru,

Jira project is,

https://wso2.org/jira/browse/CGF

Readme updated.

Thanks.


On Wed, May 25, 2016 at 9:41 PM, Lahiru Sandaruwan <lahi...@wso2.com> wrote:

> Hi,
>
> $subject? Shall we update in Readme?
>
> Thanks.
>
> --
> --
> Lahiru Sandaruwan
> Committer and PMC member, Apache Stratos,
> Senior Software Engineer,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> phone: +94773325954
> email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Isuru Udana]

[+Anjana, Gihan, Gokul]

On Mon, May 23, 2016 at 11:52 AM, Iranga Muthuthanthri <ira...@wso2.com>
wrote:

> Hi Isuru,
>
> The requirement would be to install ESB Analytics features to DAS from a
> p2-repo,
>
> On Mon, May 23, 2016 at 11:45 AM, Isuru Udana <isu...@wso2.com> wrote:
>
>> Hi Iranga,
>>
>> On Mon, May 23, 2016 at 11:38 AM, Iranga Muthuthanthri <ira...@wso2.com>
>> wrote:
>>
>>> Would it be possible to get the p2-repo (with the analytics features
>>> included?)
>>>
>>  Analytics features related to ESB core side is included within the ESB
>> pack itself. And as mentioned above ESB Analytics pack can be found from
>> following.
>> https://github.com/wso2/analytics-esb/releases/tag/v1.0.0-beta
>>
>> Any other need for a p2-repo ?
>>
>> Thanks.
>>
>>
>>
>>>
>>>
>>> On Sat, May 21, 2016 at 2:17 AM, Buddhima Wijeweera <buddh...@wso2.com>
>>> wrote:
>>>
>>>> *WSO2 ESB 5.0.0-BETA Released*
>>>>
>>>> ESB Team is pleased to announce the WSO2 ESB 5.0.0 - BETA release.
>>>>
>>>> The distribution is available to download at [1].
>>>>
>>>> [1] https://github.com/wso2/product-esb/releases/tag/v5.0.0-BETA
>>>>
>>>>
>>>> *WSO2 **ESB Tooling 5.0.0**-BETA Released*
>>>>
>>>> The distribution is available to download at [3].
>>>>
>>>> [3] *https://github.com/wso2/devstudio-tooling-esb/releases/tag/v5.0.0-beta
>>>> <https://github.com/wso2/devstudio-tooling-esb/releases/tag/v5.0.0-beta>*
>>>>
>>>>
>>>> *WSO2 **ESB Analytics 1.0.0**-BETA Released*
>>>>
>>>> The distribution is available to download at [2].
>>>>
>>>> [2] https://github.com/wso2/analytics-esb/releases/tag/v1.0.0-beta
>>>>
>>>>
>>>> WSO2 ESB 5.0.0-BETA contains following improvement and bug fixes.
>>>>
>>>> Bug
>>>>
>>>>- [ESBJAVA-3117 <https://wso2.org/jira/browse/ESBJAVA-3117>] - The
>>>>bind-address feature was not implemented for Pass-through transport
>>>>- [ESBJAVA-3801 <https://wso2.org/jira/browse/ESBJAVA-3801>] -
>>>>java.lang.IllegalStateException: Trying to set the domain from 8 to 6 
>>>> when
>>>>invoking the same service from two tenant domains
>>>>- [ESBJAVA-4014 <https://wso2.org/jira/browse/ESBJAVA-4014>] -
>>>>Proxy services can be invoked using invalid URL in super tenant mode.
>>>>- [ESBJAVA-4137 <https://wso2.org/jira/browse/ESBJAVA-4137>] -
>>>>Empty POST body with application/json content-type throws an Error
>>>>- [ESBJAVA-4225 <https://wso2.org/jira/browse/ESBJAVA-4225>] -
>>>>Endpoint re-deployment issue via a CAR while invoking the same endpoint
>>>>- [ESBJAVA-4244 <https://wso2.org/jira/browse/ESBJAVA-4244>] -
>>>>JsonUtil #newJsonPayload. Could not save JSON payload. Invalid input 
>>>> stream
>>>>found.
>>>>- [ESBJAVA-4297 <https://wso2.org/jira/browse/ESBJAVA-4297>] - [ESB
>>>>4.9.0]Sample 57: Error when updating from admin UI.
>>>>- [ESBJAVA-4319 <https://wso2.org/jira/browse/ESBJAVA-4319>] - WSO2
>>>>ESB Problems
>>>>- [ESBJAVA-4326 <https://wso2.org/jira/browse/ESBJAVA-4326>] -
>>>>Overriding the Host Header in an HTTP Call from the ESB does not work 
>>>> with
>>>>service chaining scenario
>>>>- [ESBJAVA-4345 <https://wso2.org/jira/browse/ESBJAVA-4345>] -
>>>>Possibilities of two or more proxies trying to lock and read the same 
>>>> file
>>>>at the same time.
>>>>- [ESBJAVA-4356 <https://wso2.org/jira/browse/ESBJAVA-4356>] -
>>>>Inbound endpoint interval shows null in editInbound.jsp although source
>>>>configuration have interval specified
>>>>- [ESBJAVA-4384 <https://wso2.org/jira/browse/ESBJAVA-4384>] -
>>>>Unable to use multiple mailto senders
>>>>- [ESBJAVA-4387 <https://wso2.org/jira/browse/ESBJAVA-4387>] -
>>>>Mediation debugger failed to set breakpoints for Aggragete mediator 
>>>> inlined
>>>>sequence.
>>>>- [ESBJAVA-4397 <https://wso2.org/jira/browse/ESBJAVA-4397>] - The
>>>>display

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

[Isuru Udana]

s-net to 3.4
>>- [ESBJAVA-4520 <https://wso2.org/jira/browse/ESBJAVA-4520>] -
>>Improve the Kafka Inbound performance
>>- [ESBJAVA-4530 <https://wso2.org/jira/browse/ESBJAVA-4530>] -
>>Support to map primitive array types in Datamaper
>>- [ESBJAVA-4569 <https://wso2.org/jira/browse/ESBJAVA-4569>] -
>>RabbitMQ message store and message processor not support SSL
>>- [ESBJAVA-4580 <https://wso2.org/jira/browse/ESBJAVA-4580>] -
>>xsi:type support in datamapper engine side
>>
>> Patch
>>
>>- [ESBJAVA-4572 <https://wso2.org/jira/browse/ESBJAVA-4572>] -
>>"false" or "true" String values send as JSON, autoprimtives and
>>autoprimtive disable regex has lower precedance
>>- [ESBJAVA-4578 <https://wso2.org/jira/browse/ESBJAVA-4578>] -
>>enableMTOM property does not check in SynapseCallBackReceiver when 
>> Enabling
>>MTOM
>>
>> Task
>>
>>- [ESBJAVA-4382 <https://wso2.org/jira/browse/ESBJAVA-4382>] - Update
>>MQTT Client library version
>>
>>
>>
>>
>>
>> - WSO2 Team -
>>
>> --
>> Buddhima Wijeweera
>> Software Engineer; WSO2 Inc.; http://wso2.com ,
>>
>> Mobile: +94 71 427 9966
>> Email: buddh...@wso2.com
>> Blog:   https://buddhimawijeweera.wordpress.com
>> GitHub Profile: https://github.com/Buddhima
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Thanks & Regards
>
> Iranga Muthuthanthri
> (M) -0777-255773
> Team Product Management
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Kernel RC3

[Isuru Udana]

Hi,

Tested with ESB tools and found no major issues.

+1.

On Wed, May 18, 2016 at 9:05 AM, Sohani Weerasinghe <soh...@wso2.com> wrote:

> Hi All,
>
> I have tested the updater tool functionality including installing features
> and also the updater tool preferences.
>
> +1
>
> Thanks,
> Sohani
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Wed, May 18, 2016 at 8:32 AM, Awanthika Senarath <awanth...@wso2.com>
> wrote:
>
>> I have tested,
>>
>> Installation of Developer Studio Platform, ESB and CEP tools on top of
>> kernel
>> Updater tool functionality, installation and job running
>>
>>
>>
>>  +1,
>>
>> Regards
>> Awanthika
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>> On Mon, May 16, 2016 at 3:10 PM, Awanthika Senarath <awanth...@wso2.com>
>> wrote:
>>
>>> Hello Devs,
>>>
>>>
>>> We are pleased to announce the vote for RC-3 of
>>> *WSO2 Developer Studio Kernel 4.1.0.*
>>>
>>> P2 repository of WSO2 developer Studio kernel 4.1.0 is available here
>>> <http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/kernel/releases/>.
>>>  Source
>>> and Tag Location to be voted upon is available here
>>> <https://github.com/wso2/developer-studio/releases/tag/Released-developer-studio-kernel-4.1.0-RC3-2016-05-13-165804>
>>> .
>>>
>>> Developer Studio 4.1.0 Kernel is released on Eclipse Mars (Eclipse 4.5)
>>>
>>> Developer Studio Kernel contains a single feature which has the bundles
>>> that are required to implement WSO2 specific product tooling on Eclipse.
>>>
>>>- This release contains Developer Studio migration to Eclipse mars
>>>- Improvements in the Developer Studio Updater tool for automatic
>>>updates
>>>
>>>
>>>
>>>1. [+] Stable - go ahead and release
>>>2. [-]  Broken - do not release (please explain why)
>>>
>>>
>>>
>>> Regards,
>>> Dev Studio Team
>>>
>>> Awanthika Senarath
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94717681791
>>>
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.9.0 OOM error.

[Isuru Udana]

e.transport.passthru.Pipe
>>>> Details »
>>>> Problem Suspect 2
>>>>
>>>> 7,380 instances of
>>>> *"org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection"*,
>>>> loaded by *"synapse-nhttp-transport"* occupy *129,473,928 (15.58%)*
>>>> bytes.
>>>>
>>>> *Keywords*
>>>> synapse-nhttp-transport
>>>> org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection
>>>> Details »
>>>> Problem Suspect 3
>>>>
>>>> 7,379 instances of
>>>> *"org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection"*,
>>>> loaded by *"synapse-nhttp-transport"* occupy *127,685,424 (15.37%)*
>>>> bytes. These instances are referenced from one instance of
>>>> *"java.lang.Object[]"*, loaded by *""*
>>>>
>>>> *Keywords*
>>>> java.lang.Object[]
>>>> synapse-nhttp-transport
>>>> org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection
>>>> Details »
>>>> Problem Suspect 4
>>>>
>>>> 7,380 instances of *"org.apache.http.nio.util.SimpleOutputBuffer"*,
>>>> loaded by *"httpcore-nio"* occupy *121,740,480 (14.65%)* bytes.
>>>>
>>>> *Keywords*
>>>> org.apache.http.nio.util.SimpleOutputBuffer
>>>> httpcore-nio
>>>> --
>>>> Ajith, Ahangama Vitharanalage.
>>>>
>>>> WSO2 Inc. - http://wso2.com
>>>> Email  : aji...@wso2.com
>>>> Blog: http://vitharana.org
>>>> Mobile : +1-812-360-5335
>>>>
>>>>
>>>
>>>
>>> --
>>> 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
>>>
>>>
>>>
>>>
>>>
>>
>
>
> --
> Ajith, Ahangama Vitharanalage.
>
> WSO2 Inc. - http://wso2.com
> Email  : aji...@wso2.com
> Blog: http://vitharana.org
> Mobile : +1-812-360-5335
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Proposal 8: [ESB/GW] HTTP Load balancer on top of WSO2 Gateway - Reg

[Isuru Udana]

Hi Venkat,

You should be able to build the product without an issue in the following
order.

1. https://github.com/wso2/carbon-transports
2. https://github.com/isudana/carbon-gateway
3. https://github.com/isudana/product-integration-server

Thanks.



On Sun, Apr 10, 2016 at 12:03 AM, Venkat Raman <vraman2...@gmail.com> wrote:

> Hi Isuru Udana,
>
> Good Morning.   I'm aspiring to participate in GSoC 2016 with HTTP LB on
> top of gw as my project.  As suggested by Kasun, this LB will be built on
> top of your Integration Server.
>
> So far I've been working on Senduran's version of gw My Repo
> <https://github.com/Venkat2811/MockEngineWithJAXB>.  I was able to
> connect to OSGi and perform mediation.
>
>
> Now I'm working on your version of gw.  I'm very well aware that, Your
> carbon-gateway <https://github.com/isudana/carbon-gateway> is under
> development.  I'm getting few checkstyle errors in it.  So kindly have a
> look at it.
>
> I've corrected those errors and I was able to build
> product-integration-server
> <https://github.com/isudana/product-integration-server> locally in
> eclipse.
>
> I've tried to see the working of this gateway in action by installing all
> jars through OSGi console of Senduran's gateway server.  But, it seems that
> your carbon-gateway has few other dependency jars that are required in turn.
>
> So, could you kindly provide me your version of gateway server (a pre
> release) similar to Senduran's release, so that I can install product
> integration server through OSGi and play with it.?
>
> Will be awaiting for your response.
> <https://github.com/isudana/carbon-gateway>
>
>
>
>
> *Thanks,*
> *Venkat.*
>
> On Wed, Apr 6, 2016 at 10:08 AM, Venkat Raman <vraman2...@gmail.com>
> wrote:
>
>> Hi Isuru & Kasun,
>>
>> Good morning.  Will it be ok to use JAXB for reading XML configurations
>> for our project..??
>>
>>
>>
>>
>> *Thanks,*
>> *Venkat.*
>>
>> On Tue, Apr 5, 2016 at 3:14 PM, Venkat Raman <vraman2...@gmail.com>
>> wrote:
>>
>>> Hi Senduran,
>>>
>>> I've found and rectified the error.  The behavior of JAXB in OSGi is not
>>> the same as it will be in standalone mode.
>>>
>>> Kindly find the porject here
>>> <https://github.com/Venkat2811/MockEngineWithJAXB>.
>>>
>>>
>>>
>>>
>>> *Thanks,*
>>> *Venkat.*
>>>
>>> On Sun, Apr 3, 2016 at 10:31 PM, Venkat Raman <vraman2...@gmail.com>
>>> wrote:
>>>
>>>> Hi Senduran,
>>>>
>>>> I've tried your samples and they are working fine.  Now I'm pretty
>>>> comfortable with messaging internals.
>>>>
>>>> Since I am able to get response back from BE server, I thought of
>>>> starting off by defining custom XML XSD's.  I'm using JAXB for reading XML
>>>> objects.  When I run it as a standalone program, it is working fine.  But,
>>>> when I run it within OSGi, I'm getting exception.
>>>>
>>>>  I tried all possible solutions given here
>>>> <http://stackoverflow.com/questions/1043109/why-cant-jaxb-find-my-jaxb-index-when-running-inside-apache-felix>.
>>>>
>>>>
>>>> Kindly find the project here
>>>> <https://github.com/Venkat2811/MockEngineWithJAXB>.
>>>>
>>>> Could you kindly help me with this.?  Is it advisable to use JAXB with
>>>> OSGi..?
>>>>
>>>> Meanwhile I'll try other ways also.
>>>>
>>>>
>>>>
>>>>
>>>> *Thanks,*
>>>> *Venkat.*
>>>>
>>>> On Thu, Mar 31, 2016 at 10:47 AM, Venkat Raman <vraman2...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Isuru & Kasun,
>>>>>
>>>>> Good morning.  Senduran has shared gw-engine-samples
>>>>> <https://github.com/bsenduran/gw-sample-engines>.  Meanwhile, I'll
>>>>> try out those samples and get comfortable in writing LB with sender.
>>>>>
>>>>> Would also like to thank Senduran for his suggestions, guidance and
>>>>> for his time in hangouts.
>>>>>
>>>>>
>>>>>
>>>>> *Thanks,*
>>>>> *Venkat.*
>>>>>
>>>>> On Mon, Mar 28, 2016 at 5:59 PM, Venkat Raman <vraman2...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Kasun,
>>>>>>

Re: [Dev] C5 - mention the port in use as part of error message

[Isuru Udana]

Hi All,

+1. It should be handled at the transport level. We will see the
possibility of handling this.

Created a jira to track this.
https://wso2.org/jira/browse/CTRANSPORT-5

Thanks.

On Mon, Apr 4, 2016 at 1:09 PM, Sameera Jayasoma <same...@wso2.com> wrote:

> +1 This should be handled at the Carbon-transport layer.
>
> On Mon, Apr 4, 2016 at 12:50 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Yes, the error message needs to be more descriptive. Looks like this is
>> coming all the way from NettyListener (carbon-transports) [1] and we do not
>> have a way to catch this error as the bind call is started using a thread
>> in netty and it is the one which logs this error too.
>>
>> @IsuruR and IsuruU, do we have way to fix this from calling netty api
>> level?
>>
>> [1]
>> https://github.com/wso2/carbon-transports/blob/master/http/netty/components/org.wso2.carbon.transport.http.netty/src/main/java/org/wso2/carbon/transport/http/netty/listener/NettyListener.java#L106
>>
>> On Mon, Apr 4, 2016 at 8:40 AM, Sumedha Rubasinghe <sume...@wso2.com>
>> wrote:
>>
>>> It's port 8080 that is being used here. But no way to find that through
>>> the exception through from
>>> Netty HTTP Transport listener.
>>>
>>>
>>> >>>>
>>> [2016-04-04 08:37:03,872]  INFO
>>> {org.wso2.carbon.transport.http.netty.listener.NettyListener} - Starting
>>> Netty Http Transport Listener
>>> [2016-04-04 08:37:03,876]  INFO
>>> {org.wso2.msf4j.internal.MicroservicesRegistry} - Added microservice:
>>> org.wso2.carbon.uuf.UUFService@5f33122c
>>> Exception in thread "Timer-0" java.net.BindException: Address already in
>>> use
>>> at sun.nio.ch.Net.bind0(Native Method)
>>> at sun.nio.ch.Net.bind(Net.java:433)
>>> at sun.nio.ch.Net.bind(Net.java:425)
>>> at
>>> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
>>> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>>> at
>>> io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:125)
>>> at
>>> io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:485)
>>> at
>>> io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1089)
>>> at
>>> io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:430)
>>> at
>>> io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:415)
>>> at
>>> io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:903)
>>> at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:198)
>>> at
>>> io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:348)
>>> at
>>> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:356)
>>> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
>>> at
>>> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:110)
>>> at
>>> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
>>> at java.lang.Thread.run(Thread.java:745)
>>> >>>
>>>
>>>
>>> --
>>> /sumedha
>>>
>>>
>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Associate Technical Lead,
>> Platform Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com
>> <http://kishanthan.wordpress.com>*
>> Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
>>
>
>
>
> --
> 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
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2016: Proposal 7

[Isuru Udana]

Hi Dinanjana,



On Sat, Mar 26, 2016 at 8:31 AM, Dinanjana Gunaratne <
dinanjanagunara...@gmail.com> wrote:

> Hi Kasun,
> So shall I update the draft ? What do you think. I think the best approach
> is to make this a separate application. Otherwise it will anyways have an
> effect on the performance of ESB. Because this tool includes some serious
> IO operations
>
Even though we built it as a separate application while we are taking
thread-dumps, etc, can lead to a degrade in performance to a great extent,
that's why we need to design it carefully.

Thanks.

>
> On Sat, Mar 26, 2016 at 8:25 AM, Kasun Indrasiri <ka...@wso2.com> wrote:
>
>> It's fine. But just want to make sure this is added to the project plan
>> as we move forward.
>>
>> On Sat, Mar 26, 2016 at 8:01 AM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Hi Kasun ,
>>> It's now I saw this mail. Can I do the change now ? I guess it's too
>>> late now. Anyway on your second point I have said that making flight
>>> recorder a separate application will stop applying any performance
>>> degradation on ESB. Anyway it would have been better if I have added the
>>> comparison.Can I do those changes now ?And i am really sorry for the late
>>> reply.
>>>
>>> On Fri, Mar 25, 2016 at 11:54 PM, Kasun Indrasiri <ka...@wso2.com>
>>> wrote:
>>>
>>>> Dinanjana, can you please include several use cases related to possible
>>>> production issues in an ESB (such as out of memory, CPU spinning, deadlock
>>>> etc.). Also, running the ESB flight recorder should have minimal impact on
>>>> the ESB performance. Hence your proposal should include an ESB performance
>>>> comparison with and without flight recorder.
>>>>
>>>> The proposal looks good.
>>>>
>>>> Thanks,
>>>> Kasun
>>>>
>>>> On Fri, Mar 25, 2016 at 6:37 PM, Dinanjana Gunaratne <
>>>> dinanjanagunara...@gmail.com> wrote:
>>>>
>>>>> Hi Isuru ,
>>>>> Thanks for the input :)
>>>>>
>>>>> On Fri, Mar 25, 2016 at 6:37 PM, Dinanjana Gunaratne <
>>>>> dinanjanagunara...@gmail.com> wrote:
>>>>>
>>>>>> Hi Isuru ,
>>>>>> Thanks for the input :)
>>>>>>
>>>>>> On Fri, Mar 25, 2016 at 6:34 PM, Isuru Udana <isu...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi Dinanjana,
>>>>>>>
>>>>>>> Proposal looks really good to me. Added several comments as well.
>>>>>>>
>>>>>>> On Fri, Mar 25, 2016 at 8:21 AM, Dinanjana Gunaratne <
>>>>>>> dinanjanagunara...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hello all,
>>>>>>>> I submitted my proposal to gsoc site and shared the draft with WSO2
>>>>>>>> earlier this week. Any thoughts on my proposal ?
>>>>>>>>
>>>>>>>> On Sun, Mar 20, 2016 at 7:04 PM, Dinanjana Gunaratne <
>>>>>>>> dinanjanagunara...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>> Can i have the location of source of carbondump tool ?
>>>>>>>>>
>>>>>>>>> On Wed, Mar 9, 2016 at 12:05 PM, Dinanjana Gunaratne <
>>>>>>>>> dinanjanagunara...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>> I went through webinar and actually through the code of ESB. I
>>>>>>>>>> couldn't grasped much with the code though. Now I have a high level
>>>>>>>>>> understanding on what ESB does. I assumed that the esb is built on 
>>>>>>>>>> carbon
>>>>>>>>>> kernel. So we can have our monitoring service there inside the 
>>>>>>>>>> carbon or
>>>>>>>>>> else we can have a seperate microservice which can remotely monitor 
>>>>>>>>>> the
>>>>>>>>>> mbean server of the relevant JVM and extract metrics we require
>>>>>>>>>>
>>>>>>>>>> On Thu, Mar 3, 2016 at 5:35 PM, Isuru Ranawaka <isu...@wso2.com>
>>>>>>>

Re: [Dev] GSOC 2016: Proposal 7

[Isuru Udana]

Hi Dinanjana,

Proposal looks really good to me. Added several comments as well.

On Fri, Mar 25, 2016 at 8:21 AM, Dinanjana Gunaratne <
dinanjanagunara...@gmail.com> wrote:

> Hello all,
> I submitted my proposal to gsoc site and shared the draft with WSO2
> earlier this week. Any thoughts on my proposal ?
>
> On Sun, Mar 20, 2016 at 7:04 PM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Hi all,
>> Can i have the location of source of carbondump tool ?
>>
>> On Wed, Mar 9, 2016 at 12:05 PM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Hi all,
>>> I went through webinar and actually through the code of ESB. I couldn't
>>> grasped much with the code though. Now I have a high level understanding on
>>> what ESB does. I assumed that the esb is built on carbon kernel. So we can
>>> have our monitoring service there inside the carbon or else we can have a
>>> seperate microservice which can remotely monitor the mbean server of the
>>> relevant JVM and extract metrics we require
>>>
>>> On Thu, Mar 3, 2016 at 5:35 PM, Isuru Ranawaka <isu...@wso2.com> wrote:
>>>
>>>> Hi Dinanjana,
>>>>
>>>> While you are reading the  documentation you can figure out important
>>>> features that needs to be included  and come up with a set of features.Then
>>>> we can finalize the scope of the project and start working on it. Since you
>>>> have already worked on  this kind of project can you propose set of
>>>> features and informations that will be helpfull to implement them.
>>>>
>>>>
>>>> thanks
>>>>
>>>> On Thu, Mar 3, 2016 at 9:56 AM, Dinanjana Gunaratne <
>>>> dinanjanagunara...@gmail.com> wrote:
>>>>
>>>>> Hi all,
>>>>> Not currently. I am going through the documentation :) Thanks for the
>>>>> help :)
>>>>>
>>>>> On Thu, Mar 3, 2016 at 9:52 AM, Isuru Udana <isu...@wso2.com> wrote:
>>>>>
>>>>>> Hi Dinanjana,
>>>>>>
>>>>>> Do you need further help to understand the ESB architecture ?
>>>>>>
>>>>>> On Mon, Feb 29, 2016 at 6:01 PM, Nadeeshaan Gunasinghe <
>>>>>> nadeesh...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi Dinanjana,
>>>>>>>
>>>>>>> In order to have a better understanding about the underlying
>>>>>>> functionalities of WSO2 ESB, it would be better if you take a look at 
>>>>>>> the
>>>>>>> architecture first. Please find [1] which is a very informative webinar
>>>>>>> about WSO2 ESB's architecture as well as the message flow.
>>>>>>>
>>>>>>> Also if you are trying to get familiar how ESB handles the mediation
>>>>>>> at the core level, I would like to suggest going through [2] which 
>>>>>>> covers
>>>>>>> the transport level functionality mapping to the ESB core level. This
>>>>>>> contains three parts and it would be great if you go through them :) .
>>>>>>>
>>>>>>> Additionally try to deploy a simple synapse configuration and debug
>>>>>>> the code base to identify how the message flows through synapse. If you 
>>>>>>> do
>>>>>>> so you will be able to get a firm grasp of the message flow mentioned at
>>>>>>> [2].
>>>>>>>
>>>>>>> [1]
>>>>>>> http://wso2.com/library/webinars/2014/09/understanding-wso2-esb-introduction-to-esb-architecture-and-message-flow/
>>>>>>> [2]
>>>>>>> http://wso2.com/library/articles/2013/12/demystifying-wso2-esb-pass-through-transport-part-i/
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> *Nadeeshaan Gunasinghe*
>>>>>>> Software Engineer, WSO2 Inc. http://wso2.com
>>>>>>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>>>>>>> <#m_6485817575745999246_m_265559619745955743_3779151517627746345_-555366748_-88362740_816856320_1348862296_-537557168_478758164_>
>>>>>>> <http://www.facebook.com/nadeeshaan.gunasinghe>
>>>>>>> <http://lk.linkedin.com/in/nadeeshaan>
>>>>>&

Re: [Dev] If OUT_ONLY is true, call mediator failed to send the request body to backend service

[Isuru Udana]

Hi Nuwan,

We are cloning the message because we need to keep the original message to
proceed with the rest of the meditators in the message flow. We we do not
clone at the Call, since the stream is getting consumed for the first
invocation, we won't be able to continue.

Thanks.

On Wed, Mar 9, 2016 at 5:41 PM, Viraj Senevirathne <vir...@wso2.com> wrote:

> Hi Nuwan,
>
> In call mediator if OUT_ONLY is true it will clone the message and will
> send that new message context to the backend. If there are other mediators
> after call mediator mediation will continue with the original message
> context. This is happening as call mediator is a non blocking sender (It
> will not wait).
>
> But if you don't want cloning you will have to use call mediator in
> *blocking* mode. Then original message context will be passed and it will
> wait till request send out to the backend before starting mediating
> subsequent mediators.
>
> Thank You,
>
>
> On Wed, Mar 9, 2016 at 5:32 PM, Nuwan Wimalasekara <nuw...@wso2.com>
> wrote:
>
>> Hi
>>
>> Call mediator is not submitting the request body to backend service if
>> OUT_ONLY is true. When the TargetHandler try to send the message body by
>> reading the Buffer_source, It already got cleared.
>>
>> The problem is that inside the call mediator, messageContext is cloned.
>> Then the buffer is not created in Pipe class. so the buffer has zero length
>> content.
>> Is there any reason to clone the message if OUT_ONLY is true inside the
>> call mediator?
>>
>> if we remove cloning the message and proceed with the incomming message
>> context, the issue is resolved.
>>
>>
>> boolean outOnlyMessage =
>> "true".equals(synInCtx.getProperty(SynapseConstants.OUT_ONLY));
>>
>> // Prepare the outgoing message context
>> MessageContext synOutCtx = null;
>> if (outOnlyMessage) {
>> try {
>> *synOutCtx =
>> MessageHelper.cloneMessageContext(synInCtx);*
>> } catch (AxisFault axisFault) {
>> handleException("Error occurred while cloning msg
>> context", axisFault, synInCtx);
>> }
>> } else {
>> synOutCtx = synInCtx;
>> }
>>
>>
>> Proxy configuration introduce issue.
>>
>>   
>>  
>>  
>>  
>> 
>>http://localhost:9000/services/SimpleStockQuoteService"/>
>> 
>>  
>>   
>>
>> [1] https://wso2.org/jira/browse/ESBJAVA-4469
>>
>> Thanks,
>> Nuwanw
>>
>> --
>> Nuwan Wimalasekara
>> Senior Software Engineer - Test Automation
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> phone: +94 71 668 4620
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Viraj Senevirathne
> Software Engineer; WSO2, Inc.
>
> Mobile : +94 71 958 0269
> Email : vir...@wso2.com
>



-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoc Project Proposal 26 : [CDMF] Dynamic Server side Policy Enforcement to the Users and Devices

[Isuru Udana]

[Looping project mentors]

On Tue, Feb 23, 2016 at 6:06 PM, Menaka Madushanka <menaka12...@gmail.com>
wrote:

> Hello,
>
> I'm a final year Computer Engineering undergraduate at Faculty of
> Engineering University of Peradeniya. I'm very much interested in doing the
> above project for GSoC this year as I have experience in Java, Javascript
> programming and used some WSO2 products.
>
> So, I need to know some more information about this project and
> instructions on how to proceed.
>
> Thank you very much
> Menaka Madushanka
>
> --
> Menaka Madushanka Jayawardena
> Faculty of Engineering, <http://www.pdn.ac.lk/eng>
> University of Peradeniyaya.
> LinkedIn <http://lk.linkedin.com/in/menakajayawardena>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC'16] Proposal 3 : Visual (Deep) Neural Network Builder

[Isuru Udana]

[Looping project mentors]

On Wed, Mar 9, 2016 at 11:11 AM, vimuth fernando <vim...@gmail.com> wrote:

> Hi,
>
> I am a full time MSc student in the Dept. of Computer Science at
> University of Moratuwa. I am thinking about taking part in GSOC this year
> and saw that WSO2 has some interesting project ideas especially in the
> Machine Learner project.
>
> I am interested in working on either Proposal 3 (Visual Neural Network
> Builder) or Proposal 4 (Ensemble Methods Support for WSO2 Machine Learner).
> I am open to working on either project.
>
> In Proposal 3, am i correct in understanding that the goal is to build the
> UI that will use the algorithms implemented in spark?
>
> I have started to familiarize myself with the WSO2 Machine Learner using
> the samples provided with the documentation.
>
> Your help in preparing a good proposal is much appreciated.
>
> Thank you very much.
>
> --
> Vimuth Dinuka Fernando
> Research Assistant, Department Of Computer Science and Engineering,
> University Of Moratuwa,
> Sri Lanka
>
> phone: 0777559890
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Clarification regarding BuilderMediator

[Isuru Udana]

On Sat, Mar 5, 2016 at 3:19 PM, Malintha Amarasinghe <malint...@wso2.com>
wrote:

> Hi Isuru,
>
> Thanks a lot for the input. I was able to get it working using a handler
> that replaces the content-type header with text/plain media type. Now a
> small problem is the client receives the response with text/plain media
> type. It seems the current PlainTextFormatter [1] has "text/plain" message
> format hardcoded in getContentType() method, so I guess we will have to use
> a custom message formatter in order to change it. WDYT?
>
+1. We may able to extend from existing formatter.

>
> Thanks,
> Malintha
>
> [1]
> https://github.com/wso2/wso2-axis2/blob/master/modules/transport/base/src/main/java/org/apache/axis2/format/PlainTextFormatter.java#L67
>
> On Sat, Mar 5, 2016 at 11:49 AM, Isuru Udana <isu...@wso2.com> wrote:
>
>> Hi Malintha,
>>
>> Builder mediator approach is adding lot of overhead to the configuration
>> as we have to add it for all the APIs in ESB which handles json.
>> Handling malformed json is a special case. For this special API which
>> handles malformed json, let's engage an API handler. At the handler in the
>> response path we can change the content-type.
>>
>>
>> On Saturday, March 5, 2016, Malintha Amarasinghe <malint...@wso2.com>
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Thanks for looking in to this.
>>>
>>> 1. We have an API and lets say it points to a backend which sometimes
>>> give invalid payloads with application/json content type.
>>> 2. We have added a content aware mediator along the mediation flow. (Ex:
>>> the API is response caching enabled)
>>> 3. If the backend gives an invalid payload the cache mediator will fail
>>> when it tries to build the message.
>>>
>>> If we had set the PlainTextBuilder/PlainTextFormatter for application/json
>>> mediatype in axis2.xml, we can overcome the above issue. But the problem
>>> is, that applies globally to all the APIs / Services etc in ESB. If we
>>> could set the PlainTextBuilder/PlainTextFormatter for application/json
>>> content type only to the API we have the problem with the backend while
>>> keeping default JsonBuilder/JsonFormatter, it would be a better
>>> solution IMO as our solution would not affect other APIs/Services.
>>>
>>> Thanks,
>>> Malintha
>>>
>>>
>>>
>>>
>>>
>>> On Sat, Mar 5, 2016 at 10:26 AM, Isuru Udana <isu...@wso2.com> wrote:
>>>
>>>> Hi Malintha,
>>>>
>>>> Can you please explain the use case you are trying to implement using
>>>> builder mediator.
>>>>
>>>>
>>>> On Saturday, March 5, 2016, Malintha Amarasinghe <malint...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I was trying a sample for Builder Mediator [1] to override the default
>>>>> message formatter/builder and use PlainTextBuilder/PlainTextFormatter for
>>>>> application/json content type. As per the documentation [1] we should be
>>>>> enable BinaryRealyBuilder/ExpandingMessageFormatter for at least one
>>>>> content type in axis2.xml.
>>>>>
>>>>> 1. I tried enabling a different content-type for
>>>>> BinaryRealyBuilder/ExpandingMessageFormatter and kept the defaults for
>>>>> application/json type and then tried to override it using the builder
>>>>> mediator. But then the Builder mediator does not work as expected and it
>>>>> uses default JsonBuilder/JsonBuilder to build the message.
>>>>>
>>>>> 2. If I enable BinaryRealyBuilder/ExpandingMessageFormatter for
>>>>> application/json in axis2.xml, Builder mediator works as expected.
>>>>>
>>>>> Am I doing anything wrong when I am trying the first option? Or is (2)
>>>>> the correct behaviour and we should
>>>>> set BinaryRealyBuilder/ExpandingMessageFormatter for the same content type
>>>>> we are trying to override?
>>>>>
>>>>> Kindly appreciate your help on this.
>>>>>
>>>>> Thanks,
>>>>> Malintha
>>>>>
>>>>> [1] https://docs.wso2.com/display/ESB490/Builder+Mediator
>>>>>
>>>>> --
>>>>> Malintha Amarasinghe
>>>>> Software Engineer
>>>>> *WSO2, Inc. - lean | enterprise | middleware*
>>>>> http://wso2.com/
>>>>>
>>>>> Mobile : +94 712383306
>>>>>
>>>>
>>>>
>>>> --
>>>> Sent from Mobile
>>>>
>>>
>>>
>>>
>>> --
>>> Malintha Amarasinghe
>>> Software Engineer
>>> *WSO2, Inc. - lean | enterprise | middleware*
>>> http://wso2.com/
>>>
>>> Mobile : +94 712383306
>>>
>>
>>
>> --
>> Sent from Mobile
>>
>
>
>
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306
>



-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Clarification regarding BuilderMediator

[Isuru Udana]

Hi Malintha,

Builder mediator approach is adding lot of overhead to the configuration as
we have to add it for all the APIs in ESB which handles json.
Handling malformed json is a special case. For this special API which
handles malformed json, let's engage an API handler. At the handler in the
response path we can change the content-type.

On Saturday, March 5, 2016, Malintha Amarasinghe <malint...@wso2.com> wrote:

> Hi Isuru,
>
> Thanks for looking in to this.
>
> 1. We have an API and lets say it points to a backend which sometimes give
> invalid payloads with application/json content type.
> 2. We have added a content aware mediator along the mediation flow. (Ex:
> the API is response caching enabled)
> 3. If the backend gives an invalid payload the cache mediator will fail
> when it tries to build the message.
>
> If we had set the PlainTextBuilder/PlainTextFormatter for application/json
> mediatype in axis2.xml, we can overcome the above issue. But the problem
> is, that applies globally to all the APIs / Services etc in ESB. If we
> could set the PlainTextBuilder/PlainTextFormatter for application/json
> content type only to the API we have the problem with the backend while
> keeping default JsonBuilder/JsonFormatter, it would be a better solution
> IMO as our solution would not affect other APIs/Services.
>
> Thanks,
> Malintha
>
>
>
>
>
> On Sat, Mar 5, 2016 at 10:26 AM, Isuru Udana <isu...@wso2.com
> <javascript:_e(%7B%7D,'cvml','isu...@wso2.com');>> wrote:
>
>> Hi Malintha,
>>
>> Can you please explain the use case you are trying to implement using
>> builder mediator.
>>
>>
>> On Saturday, March 5, 2016, Malintha Amarasinghe <malint...@wso2.com
>> <javascript:_e(%7B%7D,'cvml','malint...@wso2.com');>> wrote:
>>
>>> Hi,
>>>
>>> I was trying a sample for Builder Mediator [1] to override the default
>>> message formatter/builder and use PlainTextBuilder/PlainTextFormatter for
>>> application/json content type. As per the documentation [1] we should be
>>> enable BinaryRealyBuilder/ExpandingMessageFormatter for at least one
>>> content type in axis2.xml.
>>>
>>> 1. I tried enabling a different content-type for
>>> BinaryRealyBuilder/ExpandingMessageFormatter and kept the defaults for
>>> application/json type and then tried to override it using the builder
>>> mediator. But then the Builder mediator does not work as expected and it
>>> uses default JsonBuilder/JsonBuilder to build the message.
>>>
>>> 2. If I enable BinaryRealyBuilder/ExpandingMessageFormatter for
>>> application/json in axis2.xml, Builder mediator works as expected.
>>>
>>> Am I doing anything wrong when I am trying the first option? Or is (2)
>>> the correct behaviour and we should
>>> set BinaryRealyBuilder/ExpandingMessageFormatter for the same content type
>>> we are trying to override?
>>>
>>> Kindly appreciate your help on this.
>>>
>>> Thanks,
>>> Malintha
>>>
>>> [1] https://docs.wso2.com/display/ESB490/Builder+Mediator
>>>
>>> --
>>> Malintha Amarasinghe
>>> Software Engineer
>>> *WSO2, Inc. - lean | enterprise | middleware*
>>> http://wso2.com/
>>>
>>> Mobile : +94 712383306
>>>
>>
>>
>> --
>> Sent from Mobile
>>
>
>
>
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306
>


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

Re: [Dev] Clarification regarding BuilderMediator

[Isuru Udana]

Hi Malintha,

Can you please explain the use case you are trying to implement using
builder mediator.

On Saturday, March 5, 2016, Malintha Amarasinghe  wrote:

> Hi,
>
> I was trying a sample for Builder Mediator [1] to override the default
> message formatter/builder and use PlainTextBuilder/PlainTextFormatter for
> application/json content type. As per the documentation [1] we should be
> enable BinaryRealyBuilder/ExpandingMessageFormatter for at least one
> content type in axis2.xml.
>
> 1. I tried enabling a different content-type for
> BinaryRealyBuilder/ExpandingMessageFormatter and kept the defaults for
> application/json type and then tried to override it using the builder
> mediator. But then the Builder mediator does not work as expected and it
> uses default JsonBuilder/JsonBuilder to build the message.
>
> 2. If I enable BinaryRealyBuilder/ExpandingMessageFormatter for
> application/json in axis2.xml, Builder mediator works as expected.
>
> Am I doing anything wrong when I am trying the first option? Or is (2) the
> correct behaviour and we should
> set BinaryRealyBuilder/ExpandingMessageFormatter for the same content type
> we are trying to override?
>
> Kindly appreciate your help on this.
>
> Thanks,
> Malintha
>
> [1] https://docs.wso2.com/display/ESB490/Builder+Mediator
>
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306
>


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

Re: [Dev] GSOC 2016: Proposal 7

[Isuru Udana]

Hi Dinanjana,

Do you need further help to understand the ESB architecture ?

On Mon, Feb 29, 2016 at 6:01 PM, Nadeeshaan Gunasinghe <nadeesh...@wso2.com>
wrote:

> Hi Dinanjana,
>
> In order to have a better understanding about the underlying
> functionalities of WSO2 ESB, it would be better if you take a look at the
> architecture first. Please find [1] which is a very informative webinar
> about WSO2 ESB's architecture as well as the message flow.
>
> Also if you are trying to get familiar how ESB handles the mediation at
> the core level, I would like to suggest going through [2] which covers the
> transport level functionality mapping to the ESB core level. This contains
> three parts and it would be great if you go through them :) .
>
> Additionally try to deploy a simple synapse configuration and debug the
> code base to identify how the message flows through synapse. If you do so
> you will be able to get a firm grasp of the message flow mentioned at [2].
>
> [1]
> http://wso2.com/library/webinars/2014/09/understanding-wso2-esb-introduction-to-esb-architecture-and-message-flow/
> [2]
> http://wso2.com/library/articles/2013/12/demystifying-wso2-esb-pass-through-transport-part-i/
>
> Thanks,
>
> *Nadeeshaan Gunasinghe*
> Software Engineer, WSO2 Inc. http://wso2.com
> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
> <#-537557168_478758164_>
> <http://www.facebook.com/nadeeshaan.gunasinghe>
> <http://lk.linkedin.com/in/nadeeshaan>  <http://twitter.com/Nadeeshaan>
> <http://nadeeshaan.blogspot.com/>
> Get a signature like this: Click here!
> <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0==987873371783644>
>
> On Mon, Feb 29, 2016 at 1:09 PM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Hi all,
>> As Nadeeshan has suggested earlier i built all 3 projects from the
>> source. Many of the details of JVM Isuru suggested can be gained from
>> java.lang.management. Other specific data i think can be gained from
>> management package of carbon. I still have a very little understanding
>> about the architecture of ESB. So what I can't understand is where to do
>> the implementation?Are we talking about a "feature"  to ESB ?
>>
>>
>>
>> On Mon, Feb 29, 2016 at 9:32 AM, Isuru Udana <isu...@wso2.com> wrote:
>>
>>> Hi Dinanjana,
>>>
>>> Intention of this project is to build a tool which ease production
>>> incident analysis.
>>> Some of the common production incidents are,
>>> - Server goes OOM
>>> - Increase of CPU usage
>>> - Server goes to an unresponsive state
>>>
>>> We need to detect those situations and need to extract useful
>>> information to debug the issue before the server goes to a catastrophic
>>> state.
>>>
>>> For an example, when the server goes OOM, it will automatically generate
>>> the heap dump. However heap dump is not sufficient to analyse the incident.
>>> We need to see what causes the increase of heap. That may be due to
>>> increase of load (requests) or may be due to a bug. So we need to extract
>>> information like TPS of the server, thread dumps to do the further analysis.
>>>
>>> Thanks.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Feb 26, 2016 at 1:38 PM, Nadeeshaan Gunasinghe <
>>> nadeesh...@wso2.com> wrote:
>>>
>>>> Hi Dinanjana,
>>>>
>>>> First let's try to build WSO2 ESB from source and then dig in deep to
>>>> the source. In order to do so you will need build the following
>>>> repositories in the order.
>>>>
>>>> [1] https://github.com/wso2/wso2-synapse
>>>> [2] https://github.com/wso2/carbon-mediation
>>>> [3] https://github.com/wso2/product-esb
>>>>
>>>> Thanks,
>>>>
>>>> *Nadeeshaan Gunasinghe*
>>>> Software Engineer, WSO2 Inc. http://wso2.com
>>>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>>>> <#-537557168_478758164_1912754997_-722133546_-1073985791_>
>>>> <http://www.facebook.com/nadeeshaan.gunasinghe>
>>>> <http://lk.linkedin.com/in/nadeeshaan>  <http://twitter.com/Nadeeshaan>
>>>>   <http://nadeeshaan.blogspot.com/>
>>>> Get

Re: [Dev] GSOC 2016: Proposal 7

[Isuru Udana]

Hi Dinanjana,

Intention of this project is to build a tool which ease production incident
analysis.
Some of the common production incidents are,
- Server goes OOM
- Increase of CPU usage
- Server goes to an unresponsive state

We need to detect those situations and need to extract useful information
to debug the issue before the server goes to a catastrophic state.

For an example, when the server goes OOM, it will automatically generate
the heap dump. However heap dump is not sufficient to analyse the incident.
We need to see what causes the increase of heap. That may be due to
increase of load (requests) or may be due to a bug. So we need to extract
information like TPS of the server, thread dumps to do the further analysis.

Thanks.







On Fri, Feb 26, 2016 at 1:38 PM, Nadeeshaan Gunasinghe <nadeesh...@wso2.com>
wrote:

> Hi Dinanjana,
>
> First let's try to build WSO2 ESB from source and then dig in deep to the
> source. In order to do so you will need build the following repositories in
> the order.
>
> [1] https://github.com/wso2/wso2-synapse
> [2] https://github.com/wso2/carbon-mediation
> [3] https://github.com/wso2/product-esb
>
> Thanks,
>
> *Nadeeshaan Gunasinghe*
> Software Engineer, WSO2 Inc. http://wso2.com
> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
> <#-1073985791_>
> <http://www.facebook.com/nadeeshaan.gunasinghe>
> <http://lk.linkedin.com/in/nadeeshaan>  <http://twitter.com/Nadeeshaan>
> <http://nadeeshaan.blogspot.com/>
> Get a signature like this: Click here!
> <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0==153303653327748>
>
> On Thu, Feb 25, 2016 at 6:24 AM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Dear Isuru,
>>
>> Can you send me a link of api documentation of management package of ESB ?
>>
>> On Sun, Feb 21, 2016 at 2:34 PM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Dear Isuru,
>>>
>>> Sorry for bothering you again. I created a sample module with some of
>>> the requirements you mentioned in gsoc project page. Those requirements are
>>> creating thread dumps when resources usage increased unexpectedly. Now I
>>> like to know how to integrate this in to ESB and test the functionality. I
>>> couldn't find the location of ESB source.
>>> On Feb 20, 2016 9:33 AM, "Dinanjana Gunaratne" <
>>> dinanjanagunara...@gmail.com> wrote:
>>>
>>>> Dear Isuru,
>>>>
>>>> Are we looking at an implementation like this ?
>>>> "Dashboard is a remote monitoring system which was developed to monitor
>>>> the status(server's aliveness and management details) of software deployed
>>>> remotely. This monitoring system is highly scalable and does not depend on
>>>> any component which is being monitored. With Dashboard comes a Java library
>>>> called "HeartBeat".HeartBeat is a client which was developed by us for
>>>> connects to Dashboard and share information. So any component wish to
>>>> register with Dashboard monitoring system must implement that Java
>>>> library."
>>>>
>>>> I did this during my internship. I think we are looking at an
>>>> implementation within esb for debugging and monitoring. am i correct ? :)
>>>>
>>>>
>>>> On Sat, Feb 20, 2016 at 9:12 AM, Isuru Udana <isu...@wso2.com> wrote:
>>>>
>>>>> Great...!
>>>>>
>>>>> btw, don't call me "Sir" :)
>>>>>
>>>>> On Sat, Feb 20, 2016 at 8:58 AM, Dinanjana Gunaratne <
>>>>> dinanjanagunara...@gmail.com> wrote:
>>>>>
>>>>>> Dear Isuru,
>>>>>> Found the solution :)
>>>>>>
>>>>>> On Sat, Feb 20, 2016 at 8:49 AM, Dinanjana Gunaratne <
>>>>>> dinanjanagunara...@gmail.com> wrote:
>>>>>>
>>>>>>> Dear Isuru,
>>>>>>> Sorry for bothering you. Found the solution for earlier problem from
>>>>>>> here [1
>>>>>>> <http://stackoverflow.com/questions/32866263/axis2server-packed-with-esb-4-9-0-doesnt-start-while-it-works-fine-4-8-0>].
>>>>>>> Now i am facing a new problem. axis2 server looking for axis

Re: [Dev] GSOC 2016: Proposal 7

[Isuru Udana]

Hi Dinanjana,

Thank you for your interest in this project.
As a starting point, you can download WSO2 ESB[1] and start play with it.
You may run few samples[2] to get familiar with the product first.


[1] http://wso2.com/products/enterprise-service-bus/
[2] http://docs.wso2.org/wiki/display/ESB490/Samples

Thanks.

On Mon, Feb 15, 2016 at 9:31 PM, Dinanjana Gunaratne <
dinanjanagunara...@gmail.com> wrote:

>
> From: Dinanjana Gunaratne <dinanjanagunara...@gmail.com>
> Date: Mon, Feb 15, 2016 at 9:27 PM
> Subject: [Dev]GSOC 2016: Proposal 7
>
>
> Dear Sir,
>
> I m a 3rd year Computer Engineering undergraduate at University of
> Peradeniya. I would like to contribute to open source community by taking
> part in GSOC 2016.
>
> Recently i developed a remote monitoring system for an organization which
> had some of those mentioned features. Such as alerting when resources are
> over used and alerting when server stop responding. The monitoring system
> developed in such a manner that the implementation of monitoring system
> does not depend on components that are been monitored. The solution is
> built using Java and Spring framework.
>
> So i wold like to know how to proceed on this project.
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error Adding File Connector v2 to Developer Studio

[Isuru Udana]

Hi,

I am getting following error when importing the File connector ver 2.0 to
the ESB Config project.

"Connector directory name file-connector-2.0.0 doesn’t match with the
connector name fileconnector valid connector should have
‘name-connector-1.0.0’ format"

It looks like name mismatch in file name and connector.xml (In
connector.xml we have "fileconnector" as the component name).

Thanks.

-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Synapse failure while moving App Manager data publisher to new version

[Isuru Udana]

Hi Visitha,

Synapse does not depend on data publishers.

Thanks.

On Tue, Jan 5, 2016 at 10:32 AM, Visitha Wijesinghe <visi...@wso2.com>
wrote:

>
> Hi
>
> When App Manager moving to the new data publisher which is provided by
> DAS, we are getting a synapse failure.
>
>-
>
>org.wso2.carbon.databridge.commons_4.4.4
>-
>
>org.wso2.carbon.databridge.commons.thrift_4.4.4
>-
>
>org.wso2.carbon.databridge.agent.thrift_4.4.4
>
> Reason for this failure is above mentioned old version of jar's contains
> synapse dependencies which are not supported by the new versions mentioned
> bellow.
>
>-
>
>org.wso2.carbon.databridge.agent-5.0.6
>-
>
>org.wso2.carbon.databridge.commons.thrift_5.0.6
>-
>
>org.wso2.carbon.databridge.commons_5.0.6
>
> App Manager – DAS migration blocks due to this. Is there any plans of
> migrating synapse to the latest data publisher ? If so can we get time line
> for it ? Else do we have any alternative solution?
>
> --
>
> *Visitha Wijesinghe*
> Software Engineer Trainee.
> WSO2 Lanka (pvt) Ltd.
>
> Mobile - +94772617187
>



-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Isuru Udana]

Hi Amila,

On Fri, Dec 18, 2015 at 11:12 AM, Amila Maha Arachchi <ami...@wso2.com>
wrote:

> Have you seen *Enqueue* and *RMSequence* mediators being used when
> implementing mediation logics?
>
We have already removed RMSequence mediator in 4.9.0.
I haven't seen anyone using Enqueue Mediator in a real use case.

I think we should deprecate Topic feature and Event Mediator as well.

Thanks.

>
> On Wed, Dec 9, 2015 at 12:11 PM, Kasun Indrasiri <ka...@wso2.com> wrote:
>
>> Shall we deprecate following mediators in 4.10 release.
>>
>> *- Callout mediator :*
>>  All the callout functionality is supported with 'call' mediator with
>> blocking=true. Having two similar mediators will be create a bit of a
>> confusion.
>>
>> *- DBReport/DBLookup mediator*
>> These mediators offer very limited functionality and we always recommend
>> to integrate with databases with the use of DSS (using a separate DSS or
>> using DSS features inside ESB)
>>
>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>> development happens on these.
>> *- Router* : Same as filter mediator, so no use of having this.
>> *- In, Out * : Rarely used and often not required with the new
>> call/respond mediator approach.
>>
>> Any comments  on these or any other features that we should deprecate
>> from 4.10 release?
>>
>> Thanks,
>> Kasun.
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Amila Maharachchi*
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Isuru Udana]

Hi Harshana,

On Wed, Dec 9, 2015 at 6:46 PM, Harshana Eranga Martin <harshan...@gmail.com
> wrote:

> Hi Kasun,
>
> Please see the comments inline.
>
> Thanks and Regards,
> Harshana
> --
> Harshana Eranga Martin
>
> Committer - Eclipse ECF: http://www.eclipse.org/ecf/
> Blog: http://harshana05.blogspot.com
> Profile: https://www.google.com/profiles/harshana05
>
> On 9 December 2015 at 17:41, Kasun Indrasiri <ka...@wso2.com> wrote:
>
>> Shall we deprecate following mediators in 4.10 release.
>>
>> *- Callout mediator :*
>>  All the callout functionality is supported with 'call' mediator with
>> blocking=true. Having two similar mediators will be create a bit of a
>> confusion.
>>
>
> Can we use the Call mediator with blocking=true instead of Callout
> mediator for the NTLM scenarios?
>
> I have tried a NTLM scenario recently with Call mediator and blocking=true
> in ESB 4.9.0 but it didn't work while the Callout mediator works fine for
> the same scenario. I also assumed Call mediator would work but it didn't.
> Can you please check and verify?
>
> If that the case, we need to fix that bug.

>
>
>> *- DBReport/DBLookup mediator*
>> These mediators offer very limited functionality and we always recommend
>> to integrate with databases with the use of DSS (using a separate DSS or
>> using DSS features inside ESB)
>>
>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>> development happens on these.
>> *- Router* : Same as filter mediator, so no use of having this.
>> *- In, Out * : Rarely used and often not required with the new
>> call/respond mediator approach.
>>
>> Any comments  on these or any other features that we should deprecate
>> from 4.10 release?
>>
>> Thanks,
>> Kasun.
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [ESB] Deprecated features in ESB 4.10

[Isuru Udana]

Hi Kathees,

I think we should do a comparison once more to make sure that we have
covered everything before removing Callout. NTLM one which Harshana pointed
out may be due to absence of initClientOptions configuration option.

Hi Vidura,
Point you raised on the POJOCommand mediator is really interesting. We
haven't seen any usage of that over years. But now we found at least one
user who has found it useful. Thanks for pointing that out. So we should
reconsider how useful it is.

Thanks.



On Thu, Dec 10, 2015 at 10:39 AM, Kathees Rajendram <kath...@wso2.com>
wrote:

> +1 to deprecate Callout mediator since we have the Callout mediator
> functionalities in Call mediator.
>
> On Thu, Dec 10, 2015 at 1:18 AM, Vidura Gamini Abhaya <vid...@wso2.com>
> wrote:
>
>> I've found DBReport / DBLookup to be quite useful for simple DB
>> operations as they are easy to do OOTB. While DB Lookup mediator maybe
>> limited in it's ability to only being able to return a single row of data,
>> DB Report mediator is still quite useful in writing to a database,
>> especially when we use a DB as part of the mediation sequences.
>>
>> I also feel it is worth continuing with POJOCommand, as it is the most
>> simplest way of executing some custom code as part of a sequence. Although
>> it is possible to do the same with a Class mediator, one doesn't have to
>> worry about adding the proper jars, working with MessageContext etc. with
>> the POJOCommand. I think we should retain it for the sake of simplicity of
>> use.
>>
>> I'm +1 to deprecate the rest of the mediators.
>>
>> Thanks,
>>
>> Vidura
>>
>>
>>
>> On 9 December 2015 at 12:11, Kasun Indrasiri <ka...@wso2.com> wrote:
>>
>>> Shall we deprecate following mediators in 4.10 release.
>>>
>>> *- Callout mediator :*
>>>  All the callout functionality is supported with 'call' mediator with
>>> blocking=true. Having two similar mediators will be create a bit of a
>>> confusion.
>>>
>>> *- DBReport/DBLookup mediator*
>>> These mediators offer very limited functionality and we always recommend
>>> to integrate with databases with the use of DSS (using a separate DSS or
>>> using DSS features inside ESB)
>>>
>>> *- Bean, POJOCommand, Spring* : Rarely used mediators and no active
>>> development happens on these.
>>> *- Router* : Same as filter mediator, so no use of having this.
>>> *- In, Out * : Rarely used and often not required with the new
>>> call/respond mediator approach.
>>>
>>> Any comments  on these or any other features that we should deprecate
>>> from 4.10 release?
>>>
>>> Thanks,
>>> Kasun.
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Vidura Gamini Abhaya, Ph.D.
>> Director of Engineering
>> M:+94 77 034 7754
>> E: vid...@wso2.com
>>
>> WSO2 Inc. (http://wso2.com)
>> lean.enterprise.middleware
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Kathees
> Software Engineer,
> email: kath...@wso2.com
> mobile: +94772596173
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] "hostname in certificate didn't match:" issue when accessing IS dashboard

[Isuru Udana]

Hi Aparna,

Bundles are coming from features, whatever version defined in the product
pom have no relationship for that.

 Thanks.

On Wed, Oct 28, 2015 at 11:20 AM, Aparna Karunarathna <apa...@wso2.com>
wrote:

> Hi Isuru,
>
> I checked version from the ESB master branch pom[1].
>
> 4.1.2
>
> [1] https://github.com/wso2/product-esb/blob/master/pom.xml
>
> Regards,
> Aparna.
>
> On Tue, Oct 27, 2015 at 5:41 AM, Isuru Udana <isu...@wso2.com> wrote:
>
>> Hi Aparna,
>>
>> We are using 4.3.1.
>>
>>
>> Thanks.
>>
>> On Mon, Oct 26, 2015 at 10:36 AM, Aparna Karunarathna <apa...@wso2.com>
>> wrote:
>>
>>> Hi Kasun/Isuru,
>>>
>>> Currently ESB uses Apache httpclient 4.1.2, shouldn't it upgrade to
>>> newer version?
>>>
>>> @Deep, Thanks for the clarification.
>>>
>>> Regards,
>>> Aparna
>>>
>>> On Sat, Oct 24, 2015 at 11:38 AM, Deependra Ariyadewa <d...@wso2.com>
>>> wrote:
>>>
>>>> Hi Aparna,
>>>>
>>>> This can happen when the client does not send the SNI[1][2] to the
>>>> server side to select the proper HTTPS virtual host. In this case NGINX
>>>> reverse proxy created in the vhost. Most of the modern browsers send SNI to
>>>> server, therefore you will not observe this when you make the request via a
>>>> modern browser.
>>>>
>>>> Most of the new Java HTTP client libraries also support SNI. As an
>>>> example, Apache httpclient library support SNI from version 4.3.2 [3]. If
>>>> you use a library which does not support SNI, you will get this error for
>>>> HTTPS call going towards services hosted in virtual host environments.
>>>>
>>>> [1] https://en.wikipedia.org/wiki/Server_Name_Indication
>>>> [2] https://www.ietf.org/rfc/rfc3546.txt
>>>> [3] https://hc.apache.org/news.html
>>>>
>>>> On Fri, Oct 23, 2015 at 11:07 AM, Aparna Karunarathna <apa...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I have encountered a weird "hostname in certificate didn't match:"
>>>>> issue when accessing IS dashboard. My setup details are as follows.
>>>>>
>>>>> *Setup Details*
>>>>> *IS cluster*
>>>>> - 3 nodes cluster
>>>>> - Hostname - mgt.is.wso2.com
>>>>> - Certificate CN - mgt.is.wso2.com
>>>>>
>>>>> *BPS cluster*
>>>>> - 2 nodes cluster (manager/worker)
>>>>> - Hostnames - Manager - mgt.bps.wso2.com / Worker - wrk.bps.wso2.com
>>>>> - Certificate CN - *.bps.wso2.com
>>>>>
>>>>> * Both nodes are fronted by same Nginx plus load balancer.
>>>>>
>>>>> [1]
>>>>> javax.net.ssl.SSLException: hostname in certificate didn't match: <
>>>>> mgt.is.wso2.com> != <*.bps.wso2.com>
>>>>> at
>>>>> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:238)
>>>>> at
>>>>> org.apache.http.conn.ssl.BrowserCompatHostnameVerifier.verify(BrowserCompatHostnameVerifier.java:54)
>>>>> 
>>>>> 
>>>>>
>>>>> When we check the browser cookie, it gave correct certificate. (
>>>>> mgt.is.wso2.com), but when we check it from java client[2] it gives
>>>>> the bps certificate (*.bps.wso2.com) instead of IS.
>>>>>
>>>>> [2]
>>>>> https://darray.wordpress.com/2015/07/12/freak-vulnerability-and-disabling-weak-export-cipher-suites-in-wso2-carbon-4-2-0-based-products/
>>>>>
>>>>> What is the reason for this? Is it my config issue or Nginx issue or
>>>>> our product issue?
>>>>>
>>>>> --
>>>>> *Regards,*
>>>>>
>>>>> *Aparna Karunarathna.*
>>>>>
>>>>>
>>>>> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>*
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Deependra Ariyadewa
>>>> WSO2, Inc. http://wso2.com/ http://wso2.org
>>>>
>>>> email d...@wso2.com; cell +94 71 403 5996 ;
>>>> Blog http://risenfall.wordpress.com/
>>>> PGP info: KeyID: 'DC627E6F'
>>>>
>>>> *WSO2 - Lean . Enterprise . Middleware*
>>>>
>>>
>>>
>>>
>>> --
>>> *Regards,*
>>>
>>> *Aparna Karunarathna.*
>>>
>>>
>>> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>*
>>>
>>
>>
>>
>> --
>> *Isuru Udana*
>> Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> email: isu...@wso2.com cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>>
>
>
>
> --
> *Regards,*
>
> *Aparna Karunarathna.*
>
>
> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>*
>



-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] "hostname in certificate didn't match:" issue when accessing IS dashboard

[Isuru Udana]

Hi Aparna,

We are using 4.3.1.


Thanks.

On Mon, Oct 26, 2015 at 10:36 AM, Aparna Karunarathna <apa...@wso2.com>
wrote:

> Hi Kasun/Isuru,
>
> Currently ESB uses Apache httpclient 4.1.2, shouldn't it upgrade to newer
> version?
>
> @Deep, Thanks for the clarification.
>
> Regards,
> Aparna
>
> On Sat, Oct 24, 2015 at 11:38 AM, Deependra Ariyadewa <d...@wso2.com>
> wrote:
>
>> Hi Aparna,
>>
>> This can happen when the client does not send the SNI[1][2] to the server
>> side to select the proper HTTPS virtual host. In this case NGINX reverse
>> proxy created in the vhost. Most of the modern browsers send SNI to server,
>> therefore you will not observe this when you make the request via a modern
>> browser.
>>
>> Most of the new Java HTTP client libraries also support SNI. As an
>> example, Apache httpclient library support SNI from version 4.3.2 [3]. If
>> you use a library which does not support SNI, you will get this error for
>> HTTPS call going towards services hosted in virtual host environments.
>>
>> [1] https://en.wikipedia.org/wiki/Server_Name_Indication
>> [2] https://www.ietf.org/rfc/rfc3546.txt
>> [3] https://hc.apache.org/news.html
>>
>> On Fri, Oct 23, 2015 at 11:07 AM, Aparna Karunarathna <apa...@wso2.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> I have encountered a weird "hostname in certificate didn't match:" issue
>>> when accessing IS dashboard. My setup details are as follows.
>>>
>>> *Setup Details*
>>> *IS cluster*
>>> - 3 nodes cluster
>>> - Hostname - mgt.is.wso2.com
>>> - Certificate CN - mgt.is.wso2.com
>>>
>>> *BPS cluster*
>>> - 2 nodes cluster (manager/worker)
>>> - Hostnames - Manager - mgt.bps.wso2.com / Worker - wrk.bps.wso2.com
>>> - Certificate CN - *.bps.wso2.com
>>>
>>> * Both nodes are fronted by same Nginx plus load balancer.
>>>
>>> [1]
>>> javax.net.ssl.SSLException: hostname in certificate didn't match: <
>>> mgt.is.wso2.com> != <*.bps.wso2.com>
>>> at
>>> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:238)
>>> at
>>> org.apache.http.conn.ssl.BrowserCompatHostnameVerifier.verify(BrowserCompatHostnameVerifier.java:54)
>>> 
>>> 
>>>
>>> When we check the browser cookie, it gave correct certificate. (
>>> mgt.is.wso2.com), but when we check it from java client[2] it gives the
>>> bps certificate (*.bps.wso2.com) instead of IS.
>>>
>>> [2]
>>> https://darray.wordpress.com/2015/07/12/freak-vulnerability-and-disabling-weak-export-cipher-suites-in-wso2-carbon-4-2-0-based-products/
>>>
>>> What is the reason for this? Is it my config issue or Nginx issue or our
>>> product issue?
>>>
>>> --
>>> *Regards,*
>>>
>>> *Aparna Karunarathna.*
>>>
>>>
>>> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>*
>>>
>>
>>
>>
>> --
>> Deependra Ariyadewa
>> WSO2, Inc. http://wso2.com/ http://wso2.org
>>
>> email d...@wso2.com; cell +94 71 403 5996 ;
>> Blog http://risenfall.wordpress.com/
>> PGP info: KeyID: 'DC627E6F'
>>
>> *WSO2 - Lean . Enterprise . Middleware*
>>
>
>
>
> --
> *Regards,*
>
> *Aparna Karunarathna.*
>
>
> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>*
>



-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error in executing Groovy scripts using WSO2 API Manager

[Isuru Udana]

Hi Shenavi,

I think script mediator functionality has been broken from API Manager
version 1.7.0.
There was some change done in API Manager synapse branch which made script
mediator to work only with Javascript.

Thanks.

On Tue, Oct 13, 2015 at 7:04 AM, Shenavi de Mel <shen...@wso2.com> wrote:

> Hi,
>
> I was trying to write a groovy script mediator to be executed within an
> API hosted in the API Manager 1.9.1 locally and i am getting the following
> error on my console. I have attached the full stack trace in this mail.
>
> {ERROR}
>
> [2015-10-13 18:10:56,987] ERROR - ScriptMediator No script engine found
> for language: groovy
> [2015-10-13 18:10:56,988] ERROR - CarbonDeploymentSchedulerTask Error
> while running deployment scheduler..
> org.apache.synapse.SynapseException: No script engine found for language:
> groovy
>
> {ERROR}
>
> This is the script i included in the in sequence which was a simple script
> to check if it works.
>
> println "The current time is: ${new
> Date()}"
>
> I have also included the groovy-all-1.1-rc-1.jar into
> APIM_HOME/repository/components/lib/ and i checked the OSGI service and it
> is active as well.
>
> When i tried this scenario as mentioned in the blog [1] for the ESB i was
> able to get the result successfully. Do i need to add any other
> dependencies to the API Manager to support groovy?
>
> Your help would be much appreciated.
>
> [1]
> http://heshans.blogspot.com/2011/05/executing-groovy-scripts-using-wso2-esb.html
>
> Thanks
> Shenavi
>
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC 2

[Isuru Udana]

Hi Susinda / Jasintha,

As we discussed offline, I found following blockers in ESB Graphical
Editor. Can we get these fixed before 3.8.0 ?

https://wso2.org/jira/browse/TOOLS-3252
https://wso2.org/jira/browse/TOOLS-3253

Thanks,
IsuruU


On Fri, Oct 9, 2015 at 12:11 AM, Susinda Perera <susi...@wso2.com> wrote:

> Hi Malala
> Thanks for reporting this issue. I also observed an error of hanging the
> UI when we give an wrong endpoint. At Jasintha/viraj can we hard code the
> endpoint url or we have to give a connection timeout value.
>
> Thanks
> Susinda
>
> On Fri, Oct 9, 2015 at 12:22 PM, Malaka Silva <mal...@wso2.com> wrote:
>
>> Tested connectors with ESB and found the following minor issue.
>>
>> https://wso2.org/jira/browse/TOOLS-3249
>>
>> On Fri, Oct 9, 2015 at 7:49 AM, Nuwan Pallewela <nuw...@wso2.com> wrote:
>>
>>> I have tested the following areas,
>>> App server tools
>>> ESB Basic Functionalities
>>> Registry Basic Functionalities
>>> Carbon servers instances
>>> BRS drl file importing
>>> Capp deployment
>>>
>>> And found following issues
>>> https://wso2.org/jira/browse/TOOLS-3235
>>> https://wso2.org/jira/browse/TOOLS-3236
>>> https://wso2.org/jira/browse/TOOLS-3237
>>> https://wso2.org/jira/browse/TOOLS-3238
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> On Thu, Oct 8, 2015 at 5:00 PM, Susinda Perera <susi...@wso2.com> wrote:
>>>
>>>> Issues found when testing inbound endpoints is listed below
>>>> https://wso2.org/jira/browse/TOOLS-3243
>>>> https://wso2.org/jira/browse/TOOLS-3244
>>>>
>>>>
>>>> On Thu, Oct 8, 2015 at 4:51 PM, Susinda Perera <susi...@wso2.com>
>>>> wrote:
>>>>
>>>>> I have tested following Areas.
>>>>>
>>>>> All inbound endpoints
>>>>> All registry resources
>>>>> Fixes given from 3.8.0 3.8.0-Rc and RC1
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Oct 8, 2015 at 4:43 PM, Awanthika Senarath <awanth...@wso2.com
>>>>> > wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I have tested the basic functionalities related to :
>>>>>>
>>>>>> *Basic Functionalities :*
>>>>>>
>>>>>>
>>>>>>- ESB projects
>>>>>>- DSS projects
>>>>>>- Registry Resource projects
>>>>>>- Carbon servers (remote/local) instances
>>>>>>- Capp deployment/Redeployment with changes in ESB project
>>>>>>- AppFactory/ Cloud perspectives
>>>>>>- Maven Car deploy plugin
>>>>>>
>>>>>>
>>>>>> *New Features Added :*
>>>>>>
>>>>>>
>>>>>>- Publisher/Foreach new mediator addition, Custom class mediator
>>>>>>- Artifact Renaming
>>>>>>- War file Deployment/Exploded web apps/ Automatic updating(hot
>>>>>>deployment)
>>>>>>- APIM perspective- artifact creation/deletion/renaming
>>>>>>redeployment with changes
>>>>>>- Carbon 4.4.0 based servers
>>>>>>
>>>>>>
>>>>>> All functionalities are functioning satisfactorily and have no
>>>>>> blockers were observed on testing, +1
>>>>>>
>>>>>> Regards
>>>>>> Awanthika Senarath
>>>>>> Software Engineer, WSO2 Inc.
>>>>>> Mobile: +94717681791
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *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
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *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 1

Re: [Dev] (ESBJAVA-3183) Could it affect the endpoints defined in two different APIs

[Isuru Udana]

Hi Pamod,

If the HTTP Endpoint url-template is dynamic (which contains a parameter)
and if you use the same endpoint in two or more APIs to send the request
out from ESB, yes same issue will occur.

Thanks.

On Thu, Oct 8, 2015 at 4:16 AM, Pamod Sylvester <pa...@wso2.com> wrote:

> Hi ESB Team,
>
> Based on the fix provided for [1] it seems that the issue was due to the,
>
> getAddress() method processing from the address instance variable in the
> EndpointDefinition ?
>
> Could this also affect if multiple APIs are being invoked in parallel.
> Which points to the same named endpoint. i.e
>
> if API 1 and API 2 calls the same dynamic http endpoint EP_1, is there a
> possibility where the (API 2 ) calls being duplicated and API 1 call uri
> would not resolve ? AFAIU since EndpointDefinition is global to Synapse
> environment rather than the context this could affect ?
>
> [1] https://wso2.org/jira/browse/ESBJAVA-3183
>
> Thanks,
> Pamod
>
> --
> *Pamod Sylvester *
>
> *WSO2 Inc.; http://wso2.com <http://wso2.com>*
> cell: +94 77 7779495
>



-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DevStudio][ESB] Acceptable transports for a secure proxy

[Isuru Udana]

Hi Rajeevan,

Proxy can contain both http and https transports depending on the security
scenario. For an example UTOverTransport case only https is allowed and for
scenarios like SignOnly etc, both http and https should be there.





On Mon, Sep 21, 2015 at 2:24 PM, Rajeevan Vimalanathan <rajeev...@wso2.com>
wrote:

> Hi,
>
> The default transports for a secure proxy created through Developer Studio
> are HTTP and HTTPS. And there is a public JIRA [1] mentioning that only
> HTTPS transport should be allowed for a secure proxy. But when we create a
> secure proxy through ESB management console, the default transport values
> are HTTP and HTTPS same as Developer Studio. So should it be fixed at
> Developer Studio to use only HTTPS as the transport?
>
> Appreciate your inputs.
>
> Sample ESB proxy config,
>
> http://ws.apache.org/ns/synapse;
>name="testsecure"
>*transports="http,https"*
>statistics="disable"
>trace="disable"
>startOnLoad="true">
>
>   
>  http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> "
>  name="wsse:Security"
>  action="remove"/>
>   
>   
>  
>   
>   
>  https://test.com"/>
>   
>
>
> key="conf:/repository/components/org.wso2.carbon.security.mgt/policy/scenario1"/>
>
> 
>
> Sample Developer Studio proxy config,
>
> 
>*transports="https http"* xmlns="http://ws.apache.org/ns/synapse;>
>   
>  name="endpoint_urn_uuid_8c25b551-87a9-40b8-80f6-e1f0bd74483b">
>   https://test.com"/>
> 
> 
>xmlns:wsse="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> "/>
> 
> 
>   
> 
> 
>   
>   
>   
>   
> 
>
> [1] https://wso2.org/jira/browse/TOOLS-1636
>
> Thanks,
> Rajeevan
>
> --
> Vimalanathan Rajeevan
> Software Engineer,
> WSO2, Inc. *http://wso2.com* <http://wso2.com>
> Lean.Enterprise.Middleware
>
> Mobile:
> *+94 773090875 <%2B94%20773090875>*
> LinkedIn:
> *https://www.linkedin.com/in/RajeevanVimalanathan
> <https://www.linkedin.com/in/rajeevanvimalanathan>*
>



-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Throttling] Moving throttle.core out from Synapse

[Isuru Udana]

Hi AmilaD,

Can you please point us the changes need to be merged in synapse (in
MEPClient and SynapseCallbackReceiver) ?

On Mon, Sep 14, 2015 at 2:58 PM, Amila De Silva <ami...@wso2.com> wrote:

> Hi All,
>
> While carrying out this task, came to a point where certain classes cannot
> be moved out of synapse.
>
> For some of the improvements done recently, ConcurrentAccessController
> (which is one of the classes that originally resided in throttle core) has
> been used from SynapseCallbackReceiver and Axis2FlexibleMEPClient. So now
> either ConcurrentAccessController has to reside inside synapse, or else it
> has to go into another different component on which synapse would have to
> depend on. The whole point of moving throttling related code out of synapse
> is to prevent synapse depending on any carbon components.
>
> Since synapse depending on Hazelcast is not something that can be
> eliminated completely, is it fine to keep throttle.core inside synapse and
> merge new changes? When merging throttling fixes, either we have to
> introduce a service component to synapse, which would
> consume hazelcast.instance.service or we have to provide a method to set
> the HazelcastInstance that will be used for replicating throttling counts.
>
> On Fri, Sep 11, 2015 at 9:01 PM, Amila De Silva <ami...@wso2.com> wrote:
>
>> Hi Chanaka,
>>
>> Since throttle core can be used on its own, thought of creating a
>> separate feature out of that - so a new place to put throttle component. If
>> we put it under mediation-throttle, that would imply two components have to
>> be used together, isn't it?
>>
>> On Fri, Sep 11, 2015 at 6:45 PM, Chanaka Fernando <chana...@wso2.com>
>> wrote:
>>
>>> Hi Amila,
>>>
>>> You can find [1] which already has the throttle policy editor related
>>> packages and named as mediation-throttle. You can move the throttle-core
>>> packages to this component.
>>>
>>> [1]
>>> https://github.com/wso2/carbon-mediation/tree/master/components/mediation-throttle
>>>
>>> On Fri, Sep 11, 2015 at 6:23 PM, Sanjeewa Malalgoda <sanje...@wso2.com>
>>> wrote:
>>>
>>>> +1.
>>>>
>>>>
>>>> On Fri, Sep 11, 2015 at 5:20 PM, Amila De Silva <ami...@wso2.com>
>>>> wrote:
>>>>
>>>>> Will be moving throttle.core to a new component under
>>>>> carbon-mediation. The new component name will be throttle-core and a new
>>>>> feature with the same name will be created. Planning to do these changes 
>>>>> on
>>>>> carbon-mediation 4.4.11-SNAPSHOT and synapse 2.1.3-wso2v12-SNAPSHOT.
>>>>>
>>>>> On Mon, Sep 7, 2015 at 6:25 PM, Amila De Silva <ami...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> One of the changes done while moving to Git was, moving source code
>>>>>> which was under org.wso2.carbon.throttle.core to wso2-synapse. Throttle
>>>>>> core is used by both ESB (in Throttle mediator) and by API Manager (in
>>>>>> APIThrottleHandler - to keep track of the number of API calls made over 
>>>>>> the
>>>>>> cluster). At the time throttle core was moved, it was depending on Axis2
>>>>>> only, making it possible to move the source code to wso2-synapse - which 
>>>>>> is
>>>>>> not depending on any carbon components.
>>>>>>
>>>>>> While doing several improvements on throttling, Hazelcast AtomicLongs
>>>>>> were used for keeping cluster-wide counts, which now creates a coupling
>>>>>> between Hazelcast and Throttle Core. If these changes are to be merged 
>>>>>> with
>>>>>> synapse, we would have to add a dependency to Hazelcast.
>>>>>>
>>>>>> The other option is to move Throttle Core into carbon-mediation.
>>>>>> Since this already depends on several carbon components adding Hazelcast 
>>>>>> as
>>>>>> a dependancy won't be an issue.
>>>>>>
>>>>>> --
>>>>>> *Amila De Silva*
>>>>>>
>>>>>> WSO2 Inc.
>>>>>> mobile :(+94) 775119302
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Amila De Silva*
>>>>>
>>>>> WSO2 Inc.
>>>>>

Re: [Dev] [VOTE] Release WSO2 ESB 4.9.0 RC6

[Isuru Udana]

ransaction
>>>>>>> - JMS Quad Channel transaction
>>>>>>>
>>>>>>> VFS Transport and inbound use case in standalone and in a cluster
>>>>>>>- File system to file system transactions
>>>>>>>- File system to ftp, ftp to file system transactions
>>>>>>>
>>>>>>> [+] Stable - go ahead and release
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> *Nadeeshaan Gunasinghe*
>>>>>>> Software Engineer, WSO2 Inc. http://wso2.com
>>>>>>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>>>>>>> <#14fb6c594582bf02_14fb6bf90e4fad21_14fb6949ac9771b5_14fb67e5088e0e56_14fb65af995eeae0_14fb6428edd2065d_14fb620b6ace39a8_>
>>>>>>> <http://www.facebook.com/nadeeshaan.gunasinghe>
>>>>>>> <http://lk.linkedin.com/in/nadeeshaan>
>>>>>>> <http://twitter.com/Nadeeshaan>  <http://nadeeshaan.blogspot.com/>
>>>>>>> Get a signature like this: Click here!
>>>>>>> <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0=>
>>>>>>>
>>>>>>> On Thu, Sep 10, 2015 at 1:16 AM, Chanaka Fernando <chana...@wso2.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hi Devs,
>>>>>>>>
>>>>>>>> WSO2 ESB 4.9.0 RC6 Release Vote
>>>>>>>>
>>>>>>>> This release fixes the following issues:
>>>>>>>> https://wso2.org/jira/issues/?filter=12393
>>>>>>>>
>>>>>>>> Please download ESB 4.9.0 RC6 and test the functionality and vote.
>>>>>>>> Vote will be open for 72 hours or as needed.
>>>>>>>>
>>>>>>>> Source & binary distribution files:
>>>>>>>>
>>>>>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2esb-068/org/wso2/esb/wso2esb/4.9.0/
>>>>>>>>
>>>>>>>> Maven staging repository:
>>>>>>>> http://maven.wso2.org/nexus/content/repositories/orgwso2esb-068/
>>>>>>>>
>>>>>>>> The tag to be voted upon :
>>>>>>>> https://github.com/wso2/product-esb/tree/esb-parent-4.9.0-RC6
>>>>>>>>
>>>>>>>>
>>>>>>>> [-] Broken - do not release (explain why)
>>>>>>>> [+] Stable - go ahead and release
>>>>>>>>
>>>>>>>> Thanks and Regards,
>>>>>>>> ~ WSO2 ESB Team ~
>>>>>>>>
>>>>>>>> --
>>>>>>>> --
>>>>>>>> Chanaka Fernando
>>>>>>>> Senior Technical Lead
>>>>>>>> WSO2, Inc.; http://wso2.com
>>>>>>>> lean.enterprise.middleware
>>>>>>>>
>>>>>>>> mobile: +94 773337238
>>>>>>>> Blog : http://soatutorials.blogspot.com
>>>>>>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>>>>>>>> Twitter:https://twitter.com/chanakaudaya
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ___
>>>>>>>> Dev mailing list
>>>>>>>> Dev@wso2.org
>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ___
>>>>>>> Dev mailing list
>>>>>>> Dev@wso2.org
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jagath Ariyarathne
>>>>>> Technical Lead
>>>>>> WSO2 Inc.  http://wso2.com/
>>>>>> Email: jaga...@wso2.com
>>>>>> Mob  : +94 77 386 7048
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Buddhima Wijeweera
>>>>> Software Engineer; WSO2 Inc.; http://wso2.com ,
>>>>>
>>>>> Mobile: +94 71 427 9966
>>>>> Email: buddh...@wso2.com
>>>>> Blog:   https://buddhimawijeweera.wordpress.com
>>>>> GitHub Profile: https://github.com/Buddhima
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> *Prabath Ariyarathna*
>>>
>>> *Associate Technical Lead*
>>>
>>> *WSO2, Inc. *
>>>
>>> *lean . enterprise . middleware *
>>>
>>>
>>> *Email: prabat...@wso2.com <prabat...@wso2.com>*
>>>
>>> *Blog: http://prabu-lk.blogspot.com <http://prabu-lk.blogspot.com>*
>>>
>>> *Flicker : https://www.flickr.com/photos/47759189@N08
>>> <https://www.flickr.com/photos/47759189@N08>*
>>>
>>> *Mobile: +94 77 699 4730 *
>>>
>>>
>>>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Senduran *
>> Software Engineer,
>> WSO2, Inc.;  http://wso2.com/ <http://wso2.com/>
>> Mobile: +94 77 952 6548
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Yasassri Ratnayake
> Software Engineer - QA
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
> *Mobile : +94715933168 <%2B94715933168>*
> *Blogs : http://yasassriratnayake.blogspot.com
> <http://yasassriratnayake.blogspot.com/>*
> *http://wso2logs.blogspot.com <http://wso2logs.blogspot.com>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Retrieving the API name within a handler

[Isuru Udana]

Hi Supun,

You should be able to get the API name using the property 'SYNAPSE_REST_API'
in the synapse message context.



On Tue, Sep 8, 2015 at 8:26 PM, Supun Sethunga <sup...@wso2.com> wrote:

> Hi,
>
> I have a handler applied for several APIs in ESB 4.8.1. Is it possible to
> do $subject? If not, any workaround to know which API has been invoked,
> inside the handler?
>
> Thanks,
> Supun
>
> --
> *Supun Sethunga*
> Software Engineer
> WSO2, Inc.
> http://wso2.com/
> lean | enterprise | middleware
> Mobile : +94 716546324
>



-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB - 4.8.1] Clarification regarding message processor

[Isuru Udana]

On Sun, Aug 2, 2015 at 12:51 PM, Tishan Dahanayakage tis...@wso2.com
wrote:

 Hi Shafreen/Isuru,

 On Sun, Aug 2, 2015 at 10:38 AM, Isuru Udana isu...@wso2.com wrote:

 Hi Shafreen,

 On Sun, Aug 2, 2015 at 10:11 AM, Shafreen Anfar shafr...@wso2.com
 wrote:

 Hi Tishan,

 We haven't tested for each and every status code. But ideally, it should
 retry for most of the non 200 series status codes.

 AFAIK, by default we are retrying only for connection errors/timeouts
 etc. but not for business level faults of the backend. But we have the
 option to retry for business level errors also by specifying retry codes,
 non-retry codes.


 ​Which means if we receive HTTP 400 from BE message will not be retried
 for default configuration. Isn't it? ​

 ​

Yes.

 ​I have setup a sample to test this with a mocked BE service which
 responds with 400. I observed that messages are getting removed from store.


To confirm the behavior I enabled wire logs. But wire logs did not show the
 request to BE through message processor and response from BE. Is this the
 expected behavior? Are we bypassing transport layer when using Message
 Processor? If so please point a way to confirm mock BE service is sending
 400 to ESB.

MP doesn't use the non-blocking http transports, It uses the blocking
transport (CommonsHTTPSender). So the way to enable wirelogs for MP is
different. Please refer to ESB troubleshoot guide.

Thanks.



 Thanks
 Tishan


 Thanks.


 On Fri, Jul 31, 2015 at 2:37 PM, Tishan Dahanayakage tis...@wso2.com
 wrote:

 Hi,

 What HTTP status codes will be retried by default when using message
 processor?

 Thanks
 Tishan

 --
 Tishan Dahanayakage
 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.




 --
 Regards,
 *Shafreen*
 Software Engineer
 WSO2 Inc
 Mobile : 077-556-395-1




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 Tishan Dahanayakage
 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.




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB - 4.8.1] Clarification regarding message processor

[Isuru Udana]

Hi Shafreen,

On Sun, Aug 2, 2015 at 10:11 AM, Shafreen Anfar shafr...@wso2.com wrote:

 Hi Tishan,

 We haven't tested for each and every status code. But ideally, it should
 retry for most of the non 200 series status codes.

AFAIK, by default we are retrying only for connection errors/timeouts etc.
but not for business level faults of the backend. But we have the option to
retry for business level errors also by specifying retry codes, non-retry
codes.

Thanks.


 On Fri, Jul 31, 2015 at 2:37 PM, Tishan Dahanayakage tis...@wso2.com
 wrote:

 Hi,

 What HTTP status codes will be retried by default when using message
 processor?

 Thanks
 Tishan

 --
 Tishan Dahanayakage
 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.




 --
 Regards,
 *Shafreen*
 Software Engineer
 WSO2 Inc
 Mobile : 077-556-395-1




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to handle REST_URL_POSTFIX property when Query Parameter values are defined

[Isuru Udana]

It's related to the API Resource not to the HTTP Endpoint.

Please note that there is no relationship between how we define resource
url (whether it is url-template or url-mapping) with the HTTP Endpoint url.
And we can't even introduce a such relationship.



On Fri, Jul 24, 2015 at 2:41 PM, Uvindra Dias Jayasinha uvin...@wso2.com
wrote:

 Im referring to the attribute in the* resource* tag, that how we are
 triggering the different functionalities

 On 24 July 2015 at 14:39, Isuru Udana isu...@wso2.com wrote:

 In both scenarios you can see, HTTP Endpoint contains an url-template.

 endpoint name=admin--pathParam_APIproductionEndpoint_0

  http uri-template=
 http://ws.cdyne.com/phoneverify/phoneverify.asmx?name={uri.var.name}/

   /endpoint

  endpoint name=admin--noPathParam_APIproductionEndpoint_0

  http uri-template=
 http://ws.cdyne.com/phoneverify/phoneverify.asmx/

   /endpoint

 On Fri, Jul 24, 2015 at 2:35 PM, Uvindra Dias Jayasinha uvin...@wso2.com
  wrote:

 Attached are two synpase files generated with API Manager for the above
 use cases. Ok end of the day we need to support both attributes, its
 critical to API Manager functionality. Do you agree that from a functional
 perspective our expectation is correct? Because there is nothing to stop
 someone from writing an API in this manner.

 On 24 July 2015 at 14:23, Isuru Udana isu...@wso2.com wrote:



 On Fri, Jul 24, 2015 at 2:10 PM, Uvindra Dias Jayasinha 
 uvin...@wso2.com wrote:

 In our velocity template we are conditionally deciding when the
 url-mapping attribute or uri-template attribute should be used in the
 synapse config generated for each API, eher is the velocity template 
 logic,

 #if($resource.getUriTemplate().contains({) ||
 ($resource.getUriTemplate().contains(*) 
 !$resource.getUriTemplate().endsWith(/*)))
 *uri-template=*$resource.getUriTemplate()
 #else
 *url-mapping=*$resource.getUriTemplate()
 #end

 So we are specifying this attribute based on API Managers requirement.
 The synapse engine does not consider this as invalid so we expect that the
 synapse engine should honour the attribute defined.

 HTTP Endpoint in synapse doesn't support url-mapping attribute. Can you
 post a sample generated API Config with this ?


 So we need the functionality of both the uri-template and url-mapping
 attributes for our HTTP endpoint based APIs, but not at the same time
 obviously. Its either one or the other for a given resource.

 There is no relationship between API resources and HTTP endpoint

 By specifying these two attributes we are already implying that we are
 expecting different functionality(the user expects the same). So its a bit
 difficult justifying having to manually set this from the publisher.

 WDYT?

 +1. If we can handle this automatically without a user interaction,
 that's the best way to handle it. And we need to consider the impact of the
 changes (config migration issues, etc.)


 On 24 July 2015 at 13:45, Isuru Udana isu...@wso2.com wrote:

 Hi Uvindra,

 I think the correct approach is to completely remove REST_URL_POSTFIX
 getting appended for HTTP Endpoint. And append only if the user configure
 to do so.
 Initially we implemented HTTP Endpoint in that way. But somehow
 implementation has changed now.
 I am not sure whether we are too late to revert to the original
 implementation now.

 If we cannot revert back,
 For ESB, we can simply remove the REST_URL_POSTFIX from the config
 and for AM, we need a easy way to do that from UI.

 On Fri, Jul 24, 2015 at 1:31 PM, Uvindra Dias Jayasinha 
 uvin...@wso2.com wrote:

 We need to come up with $subject.

 The issue related to this has been highlighted in [1]

 The REST_URL_POSTFIX property appends the url-mapping of a given
 resource to the end of the api endpoint in synapse. This is applied by
 synapse for all APIs that are defined.

 For example,

 *API URL* - http://localhost:8280/noPathParam/1.0/
 *Endpoint URL* - http://localhost:8281/sampleAPI
 *GET Resource(url-mapping)* - somepath

 Now invoking the above GET resource of the API,

GET
 http://localhost:8280/noPathParam/1.0/somepath

 will translate to,

 GET http://localhost:8281/sampleAPI/somepath



 The problem happens when there are Query Parameters. Since resource
 url-mapping or uri-template attribute is getting appended by default to 
 the
 end of the URL, it is getting added after the Query Parameter, as 
 follows,


 *API URL* - http://localhost:8280/pathParam/1.0/
 *Endpoint URL* - http://localhost:8281/sampleAPI?name={uri.var.name}
 *GET Resource(url-template)* - {name}

 Now invoking the above GET resource of the API

GET http://localhost:8280/pathParam/1.0/somename


 will translate to,

 GET http://localhost:8281/sampleAPI?name=
 *somename/somename*

 instead of the expected

Re: [Dev] How to handle REST_URL_POSTFIX property when Query Parameter values are defined

[Isuru Udana]

Hi Uvindra,

I think the correct approach is to completely remove REST_URL_POSTFIX
getting appended for HTTP Endpoint. And append only if the user configure
to do so.
Initially we implemented HTTP Endpoint in that way. But somehow
implementation has changed now.
I am not sure whether we are too late to revert to the original
implementation now.

If we cannot revert back,
For ESB, we can simply remove the REST_URL_POSTFIX from the config and for
AM, we need a easy way to do that from UI.

On Fri, Jul 24, 2015 at 1:31 PM, Uvindra Dias Jayasinha uvin...@wso2.com
wrote:

 We need to come up with $subject.

 The issue related to this has been highlighted in [1]

 The REST_URL_POSTFIX property appends the url-mapping of a given resource
 to the end of the api endpoint in synapse. This is applied by synapse for
 all APIs that are defined.

 For example,

 *API URL* - http://localhost:8280/noPathParam/1.0/
 *Endpoint URL* - http://localhost:8281/sampleAPI
 *GET Resource(url-mapping)* - somepath

 Now invoking the above GET resource of the API,

GET http://localhost:8280/noPathParam/1.0/somepath

 will translate to,

 GET http://localhost:8281/sampleAPI/somepath



 The problem happens when there are Query Parameters. Since resource
 url-mapping or uri-template attribute is getting appended by default to the
 end of the URL, it is getting added after the Query Parameter, as follows,


 *API URL* - http://localhost:8280/pathParam/1.0/
 *Endpoint URL* - http://localhost:8281/sampleAPI?name={uri.var.name}
 *GET Resource(url-template)* - {name}

 Now invoking the above GET resource of the API

GET http://localhost:8280/pathParam/1.0/somename


 will translate to,

 GET http://localhost:8281/sampleAPI?name=
 *somename/somename*

 instead of the expected,

 GET http://localhost:8281/sampleAPI?name=somename


 So the problem here is that synapse treats both url-mapping and
 url-template resources the same way. What should happen is that the
 REST_URL_POSTFIX property should only be considered if the url-mapping
 attribute is specified *and not when uri-template attribute exists*.

There is no url mapping involved with HTTP endpoint (only url template is
there). And there is no relationship between API resources and HTTP
Endpoint.

Thanks.



 So can we get this fixed at synapse level? We believe this is the correct
 place to solve this issue


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

 --
 Regards,
 Uvindra

 Mobile: 33962




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to handle REST_URL_POSTFIX property when Query Parameter values are defined

[Isuru Udana]

On Fri, Jul 24, 2015 at 2:10 PM, Uvindra Dias Jayasinha uvin...@wso2.com
wrote:

 In our velocity template we are conditionally deciding when the
 url-mapping attribute or uri-template attribute should be used in the
 synapse config generated for each API, eher is the velocity template logic,

 #if($resource.getUriTemplate().contains({) ||
 ($resource.getUriTemplate().contains(*) 
 !$resource.getUriTemplate().endsWith(/*)))
 *uri-template=*$resource.getUriTemplate()
 #else
 *url-mapping=*$resource.getUriTemplate()
 #end

 So we are specifying this attribute based on API Managers requirement.
 The synapse engine does not consider this as invalid so we expect that the
 synapse engine should honour the attribute defined.

HTTP Endpoint in synapse doesn't support url-mapping attribute. Can you
post a sample generated API Config with this ?


 So we need the functionality of both the uri-template and url-mapping
 attributes for our HTTP endpoint based APIs, but not at the same time
 obviously. Its either one or the other for a given resource.

There is no relationship between API resources and HTTP endpoint

 By specifying these two attributes we are already implying that we are
 expecting different functionality(the user expects the same). So its a bit
 difficult justifying having to manually set this from the publisher.

 WDYT?

+1. If we can handle this automatically without a user interaction, that's
the best way to handle it. And we need to consider the impact of the
changes (config migration issues, etc.)


 On 24 July 2015 at 13:45, Isuru Udana isu...@wso2.com wrote:

 Hi Uvindra,

 I think the correct approach is to completely remove REST_URL_POSTFIX
 getting appended for HTTP Endpoint. And append only if the user configure
 to do so.
 Initially we implemented HTTP Endpoint in that way. But somehow
 implementation has changed now.
 I am not sure whether we are too late to revert to the original
 implementation now.

 If we cannot revert back,
 For ESB, we can simply remove the REST_URL_POSTFIX from the config and
 for AM, we need a easy way to do that from UI.

 On Fri, Jul 24, 2015 at 1:31 PM, Uvindra Dias Jayasinha uvin...@wso2.com
  wrote:

 We need to come up with $subject.

 The issue related to this has been highlighted in [1]

 The REST_URL_POSTFIX property appends the url-mapping of a given
 resource to the end of the api endpoint in synapse. This is applied by
 synapse for all APIs that are defined.

 For example,

 *API URL* - http://localhost:8280/noPathParam/1.0/
 *Endpoint URL* - http://localhost:8281/sampleAPI
 *GET Resource(url-mapping)* - somepath

 Now invoking the above GET resource of the API,

GET http://localhost:8280/noPathParam/1.0/somepath

 will translate to,

 GET http://localhost:8281/sampleAPI/somepath



 The problem happens when there are Query Parameters. Since resource
 url-mapping or uri-template attribute is getting appended by default to the
 end of the URL, it is getting added after the Query Parameter, as follows,


 *API URL* - http://localhost:8280/pathParam/1.0/
 *Endpoint URL* - http://localhost:8281/sampleAPI?name={uri.var.name}
 *GET Resource(url-template)* - {name}

 Now invoking the above GET resource of the API

GET http://localhost:8280/pathParam/1.0/somename


 will translate to,

 GET http://localhost:8281/sampleAPI?name=
 *somename/somename*

 instead of the expected,

 GET http://localhost:8281/sampleAPI?name=somename


 So the problem here is that synapse treats both url-mapping and
 url-template resources the same way. What should happen is that the
 REST_URL_POSTFIX property should only be considered if the url-mapping
 attribute is specified *and not when uri-template attribute exists*.

 There is no url mapping involved with HTTP endpoint (only url template is
 there). And there is no relationship between API resources and HTTP
 Endpoint.

 Thanks.



 So can we get this fixed at synapse level? We believe this is the
 correct place to solve this issue


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

 --
 Regards,
 Uvindra

 Mobile: 33962




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 Regards,
 Uvindra

 Mobile: 33962




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to handle REST_URL_POSTFIX property when Query Parameter values are defined

[Isuru Udana]

In both scenarios you can see, HTTP Endpoint contains an url-template.

endpoint name=admin--pathParam_APIproductionEndpoint_0

 http uri-template=
http://ws.cdyne.com/phoneverify/phoneverify.asmx?name={uri.var.name}/

  /endpoint

 endpoint name=admin--noPathParam_APIproductionEndpoint_0

 http uri-template=
http://ws.cdyne.com/phoneverify/phoneverify.asmx/

  /endpoint

On Fri, Jul 24, 2015 at 2:35 PM, Uvindra Dias Jayasinha uvin...@wso2.com
wrote:

 Attached are two synpase files generated with API Manager for the above
 use cases. Ok end of the day we need to support both attributes, its
 critical to API Manager functionality. Do you agree that from a functional
 perspective our expectation is correct? Because there is nothing to stop
 someone from writing an API in this manner.

 On 24 July 2015 at 14:23, Isuru Udana isu...@wso2.com wrote:



 On Fri, Jul 24, 2015 at 2:10 PM, Uvindra Dias Jayasinha uvin...@wso2.com
  wrote:

 In our velocity template we are conditionally deciding when the
 url-mapping attribute or uri-template attribute should be used in the
 synapse config generated for each API, eher is the velocity template logic,

 #if($resource.getUriTemplate().contains({) ||
 ($resource.getUriTemplate().contains(*) 
 !$resource.getUriTemplate().endsWith(/*)))
 *uri-template=*$resource.getUriTemplate()
 #else
 *url-mapping=*$resource.getUriTemplate()
 #end

 So we are specifying this attribute based on API Managers requirement.
 The synapse engine does not consider this as invalid so we expect that the
 synapse engine should honour the attribute defined.

 HTTP Endpoint in synapse doesn't support url-mapping attribute. Can you
 post a sample generated API Config with this ?


 So we need the functionality of both the uri-template and url-mapping
 attributes for our HTTP endpoint based APIs, but not at the same time
 obviously. Its either one or the other for a given resource.

 There is no relationship between API resources and HTTP endpoint

 By specifying these two attributes we are already implying that we are
 expecting different functionality(the user expects the same). So its a bit
 difficult justifying having to manually set this from the publisher.

 WDYT?

 +1. If we can handle this automatically without a user interaction,
 that's the best way to handle it. And we need to consider the impact of the
 changes (config migration issues, etc.)


 On 24 July 2015 at 13:45, Isuru Udana isu...@wso2.com wrote:

 Hi Uvindra,

 I think the correct approach is to completely remove REST_URL_POSTFIX
 getting appended for HTTP Endpoint. And append only if the user configure
 to do so.
 Initially we implemented HTTP Endpoint in that way. But somehow
 implementation has changed now.
 I am not sure whether we are too late to revert to the original
 implementation now.

 If we cannot revert back,
 For ESB, we can simply remove the REST_URL_POSTFIX from the config and
 for AM, we need a easy way to do that from UI.

 On Fri, Jul 24, 2015 at 1:31 PM, Uvindra Dias Jayasinha 
 uvin...@wso2.com wrote:

 We need to come up with $subject.

 The issue related to this has been highlighted in [1]

 The REST_URL_POSTFIX property appends the url-mapping of a given
 resource to the end of the api endpoint in synapse. This is applied by
 synapse for all APIs that are defined.

 For example,

 *API URL* - http://localhost:8280/noPathParam/1.0/
 *Endpoint URL* - http://localhost:8281/sampleAPI
 *GET Resource(url-mapping)* - somepath

 Now invoking the above GET resource of the API,

GET http://localhost:8280/noPathParam/1.0/somepath

 will translate to,

 GET http://localhost:8281/sampleAPI/somepath



 The problem happens when there are Query Parameters. Since resource
 url-mapping or uri-template attribute is getting appended by default to 
 the
 end of the URL, it is getting added after the Query Parameter, as follows,


 *API URL* - http://localhost:8280/pathParam/1.0/
 *Endpoint URL* - http://localhost:8281/sampleAPI?name={uri.var.name}
 *GET Resource(url-template)* - {name}

 Now invoking the above GET resource of the API

GET http://localhost:8280/pathParam/1.0/somename


 will translate to,

 GET http://localhost:8281/sampleAPI?name=
 *somename/somename*

 instead of the expected,

 GET http://localhost:8281/sampleAPI?name=somename


 So the problem here is that synapse treats both url-mapping and
 url-template resources the same way. What should happen is that the
 REST_URL_POSTFIX property should only be considered if the url-mapping
 attribute is specified *and not when uri-template attribute exists*.

 There is no url mapping involved with HTTP endpoint (only url template
 is there). And there is no relationship between API resources and HTTP
 Endpoint.

 Thanks.



 So can we get this fixed

Re: [Dev] WSO2 Committers += Ravindra Ranwala

[Isuru Udana]

Congratulations Ravindra..!

On Thu, Jul 16, 2015 at 1:42 PM, Chanaka Fernando chana...@wso2.com wrote:

 Congratulations Ravindra ...

 On Thu, Jul 16, 2015 at 1:39 PM, Viraj Senevirathne vir...@wso2.com
 wrote:

 Congrats, Ravindra.

 Best Regards,

 On Thu, Jul 16, 2015 at 11:53 AM, Dilan Udara Ariyaratne dil...@wso2.com
  wrote:

 Congratulations, Ravindra !!!

 Regards,
 Dilan.


 *Dilan U. Ariyaratne*
 Software Engineer
 WSO2 Inc. http://wso2.com/
 Mobile: +94775149066
 lean . enterprise . middleware

 On Thu, Jul 16, 2015 at 11:25 AM, Kasun Indrasiri ka...@wso2.com
 wrote:

 Hi devs,

 Its my pleasure to welcome Ravindra Ranwala as a WSO2 Committer.
 Ravindra, welcome aboard and keep up the good work!

 Thanks.

 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/

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



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




 --
 Viraj Senevirathne
 Software Engineer; WSO2, Inc.

 Mobile : +94 71 818 4742 %2B94%20%280%29%20773%20451194
 Email : vir...@wso2.com thili...@wso2.com

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




 --
 --
 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
 Wordpress:http://chanakaudaya.wordpress.com




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




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Can we have SSL profiles for https transport sender in axis2_blocking_client.xml

[Isuru Udana]

Hi Hasitha,

AFAIK, it is not possible. But better to check the code and see.

We use the axis2 CommonsHTTPSender in axis2_blocking_client.xml.
Can you check whether it is possible to have profiles in axis2
CommonsHTTPSender level ?

Thanks.

On Thu, Jul 9, 2015 at 8:33 AM, Hasitha Aravinda hasi...@wso2.com wrote:

 Hi Devs,

 I am using Callout mediator in one of my JMS proxy services. I have to use
 callout since I am using JMS transactions.

 In this proxy service, I am sending a request to https backend, where
 mutual SSL is enabled. According to [1] we have set keystore information
 using System properties. But it doesn't allow me to have multiple SSL
 profiles like in PTT https.

 Can we have $Subject.

 [1] -
 https://docs.wso2.com/display/ESB481/Callout+Mediator#CalloutMediator-Setup


 Thanks,
 Hasitha.


 Hasitha Aravinda,
 Senior Software Engineer,
 WSO2 Inc.
 Email: hasi...@wso2.com
 Mobile : +1 201 887 1971, +94 718 210 200




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Adding an Endpoint Property as an expression

[Isuru Udana]

Hi Kasun,

On Tue, Jul 7, 2015 at 1:04 AM, Kasun Indrasiri ka...@wso2.com wrote:


 I don't recall the exact use case for using endpoint level properties? Is
 that related to LB/FO endpoints?

There are two use cases I can recall.
1. Identify the last endpoint the message is sent in FO/LB endpoint.
2. Allow setting some property specific to an environment from dynamic
endpoints.

 IMO, if that can be done at mediation level it self, we should get rid of
 this kind of usage of properties.

 On Tue, Jul 7, 2015 at 12:48 PM, Sohani Weerasinghe soh...@wso2.com
 wrote:

 Hi ESB Team,

 Currently in the ESB Management console UI, it is not supported to add a
 property to an Endpoint as an expression. But it seems it is a valid
 requirement as in [1].

 Is there any specific reason for allowing to add properties only as
 Literals but not as expressions?

 [1]
 https://github.com/wso2/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/config/xml/MediatorPropertySerializer.java

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

 Mobile  : +94 716439774
 Blog :http://christinetechtips.blogspot.com/
 Twitter  : https://twitter.com/sohanichristine




 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Review and merge the PR

[Isuru Udana]

merged.

On Mon, Jun 29, 2015 at 2:56 PM, Prabath Ariyarathna prabat...@wso2.com
wrote:

 Hi.

 Please review and merge the PR[1] for ESBJAVA-3836 [2].

 [1] - https://github.com/wso2/product-esb/pull/201
 [2] = tps://wso2.org/jira/browse/ESBJAVA-3836


 Thanks
 --

 *Prabath Ariyarathna*

 *Associate Technical Lead*

 *WSO2, Inc. *

 *lean . enterprise . middleware *


 *Email: prabat...@wso2.com prabat...@wso2.com*

 *Blog: http://prabu-lk.blogspot.com http://prabu-lk.blogspot.com*

 *Flicker : https://www.flickr.com/photos/47759189@N08
 https://www.flickr.com/photos/47759189@N08*

 *Mobile: +94 77 699 4730 *








-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.9.0 Release Testing Update

[Isuru Udana]

Hi PrabathAR,

I believe we test this when we are implementing java8 support.
Can you please look into these issues? There should be a common issue for
all UIs.

Thanks.

On Wed, Jun 24, 2015 at 3:16 PM, Sandapa Handakumbura sand...@wso2.com
wrote:

 Hi,
 When using Java 8 (jdk1.8.0_45), many pages (APIs, Inbound Endpoints, Add
 custom proxy, Master source view, etc..) of ESB4.9.0 gives dead pages.
 Public jira for this Blocking issue is reported at [1].

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

 Regards,
 Sandapa


 On Mon, Jun 22, 2015 at 1:15 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Sandapa,

 Thanks for the update mail.
 We will provide a new pack today from the jenkins builder.

 Thanks.

 On Mon, Jun 22, 2015 at 12:37 PM, Sandapa Handakumbura sand...@wso2.com
 wrote:

 Hi,

 During past couple of weeks we tested the new features(listed below) in
 ESB4.9.0-Alpha pack and has done the initial round of testing for 80% of
 those. Some features have blocking issues and hence cannot be tested
 comprehensively. ESB team is currently fixing the reported issues and we're
 planning to verify the fixes and continue blocked areas in Beta pack.

 Inbound Endpoint support in multi-tenant environments
 - HTTP Inbound Endpoint
 - JMS Inbound Endpoint
 - VFS Inbound Endpoint
 - CXF WS-RM Inbound Endpoint
 - HL7 Inbound Endpoint
 Coordination support for Message Stores and Processors
 For-each Mediator
 JDBC Message Store
 RabbitMQ Transport
 Dynamic SSLProfiles for sender and listener
 Coordination support for Scheduled Tasks.
 Enabling HTTP Cache Control headers (Etag)
 Kafka support in ESB (Experimental)


 Applying QOS for services and other ESB related new features(Indbound
 endpoints etc) are currently being tested with Developer Studio 3.8.0 - M5.

 We will continue testing rest of the new features and the core features
 in ESB 4.9.0 Alpha pack.

 @Shashika and Asanthi,
 Please add if I have missed anything important.

 Thanks,
 Sandapa

 --
 Sandapa Handakumbura
 Associate Technical Lead
 WSO2.Inc. ; http://wso2.com/
 M : +94777115866




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 Sandapa Handakumbura
 Associate Technical Lead
 WSO2.Inc. ; http://wso2.com/
 M : +94777115866




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Can't brows registry resource when WSO2 starting using Developer Studio 3.8.0 m5

[Isuru Udana]

)
 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.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:604)
 at
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:543)
 at
 org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:37)
 at
 org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
 at
 org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:954)
 at
 org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:656)
 at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:98)
 ... 78 more
 Caused by: org.apache.jasper.JasperException: An exception occurred
 processing JSP page /relations/relations.jsp at line 28

 25: jsp:include page=../relations/relations-i18n-ajaxprocessor.jsp/
 26: script type=text/javascript
 src=../relations/js/relations.js/script
 27:
 28: jsp:include page=../relations/dependencies.jsp/
 29:
 30: jsp:include page=../relations/associations.jsp/

 Thanks.
 /Susankha.



 --
 Susankha Nirmala
 Software Engineer
 WSO2, Inc.: http://wso2.com
 lean.enterprise.middleware
 Mobile : +94 77 593 2146




 --

 *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
 email: kasung AT spamfree wso2.com
 linked-in: http://lk.linkedin.com/in/gajasinghe
 blog: http://kasunbg.org






 --
 *Chandana Napagoda*
 Senior Software Engineer
 WSO2 Inc. - http://wso2.org

 *Email  :  chand...@wso2.com chand...@wso2.com**Mobile : +94718169299
 %2B94718169299*

 *Blog  :http://cnapagoda.blogspot.com http://cnapagoda.blogspot.com*




 --
 Susankha Nirmala
 Software Engineer
 WSO2, Inc.: http://wso2.com
 lean.enterprise.middleware
 Mobile : +94 77 593 2146




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.9.0 Release Testing Update

[Isuru Udana]

Hi Sandapa,

Thanks for the update mail.
We will provide a new pack today from the jenkins builder.

Thanks.

On Mon, Jun 22, 2015 at 12:37 PM, Sandapa Handakumbura sand...@wso2.com
wrote:

 Hi,

 During past couple of weeks we tested the new features(listed below) in
 ESB4.9.0-Alpha pack and has done the initial round of testing for 80% of
 those. Some features have blocking issues and hence cannot be tested
 comprehensively. ESB team is currently fixing the reported issues and we're
 planning to verify the fixes and continue blocked areas in Beta pack.

 Inbound Endpoint support in multi-tenant environments
 - HTTP Inbound Endpoint
 - JMS Inbound Endpoint
 - VFS Inbound Endpoint
 - CXF WS-RM Inbound Endpoint
 - HL7 Inbound Endpoint
 Coordination support for Message Stores and Processors
 For-each Mediator
 JDBC Message Store
 RabbitMQ Transport
 Dynamic SSLProfiles for sender and listener
 Coordination support for Scheduled Tasks.
 Enabling HTTP Cache Control headers (Etag)
 Kafka support in ESB (Experimental)


 Applying QOS for services and other ESB related new features(Indbound
 endpoints etc) are currently being tested with Developer Studio 3.8.0 - M5.

 We will continue testing rest of the new features and the core features in
 ESB 4.9.0 Alpha pack.

 @Shashika and Asanthi,
 Please add if I have missed anything important.

 Thanks,
 Sandapa

 --
 Sandapa Handakumbura
 Associate Technical Lead
 WSO2.Inc. ; http://wso2.com/
 M : +94777115866




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB Alpha] NamespaceHandlerRegisterer INFO logs at startup

[Isuru Udana]

Hi Nirmal,

Yes those are unnecessary logs getting printed at the startup. But we don't
have a way to make it to debug level as it's coming from the cxf bundle.
We are evaluating possible ways of removing these log statements.

Thanks.

On Tue, Jun 16, 2015 at 9:05 AM, Nirmal Fernando nir...@wso2.com wrote:

 Hi,

 Should following logs be debug?

 INFO - NamespaceHandlerRegisterer Registered blueprint namespace handler
 for http://cxf.apache.org/blueprint/core

 [2015-06-16 09:06:24,934]  INFO - NamespaceHandlerRegisterer Registered
 blueprint namespace handler for http://cxf.apache.org/configuration/beans

 [2015-06-16 09:06:24,934]  INFO - NamespaceHandlerRegisterer Registered
 blueprint namespace handler for
 http://cxf.apache.org/configuration/parameterized-types

 [2015-06-16 09:06:24,934]  INFO - NamespaceHandlerRegisterer Registered
 blueprint namespace handler for
 http://cxf.apache.org/configuration/security

 [2015-06-16 09:06:24,934]  INFO - NamespaceHandlerRegisterer Registered
 blueprint namespace handler for http://schemas.xmlsoap.org/wsdl/

 [2015-06-16 09:06:24,934]  INFO - NamespaceHandlerRegisterer Registered
 blueprint namespace handler for http://www.w3.org/2005/08/addressing

 [2015-06-16 09:06:24,934]  INFO - NamespaceHandlerRegisterer Registered
 blueprint namespace handler for
 http://schemas.xmlsoap.org/ws/2004/08/addressing

 --

 Thanks  regards,
 Nirmal

 Associate Technical Lead - Data Technologies Team, WSO2 Inc.
 Mobile: +94715779733
 Blog: http://nirmalfdo.blogspot.com/





-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge

[Isuru Udana]

done.

On Wed, Jun 10, 2015 at 1:35 PM, Jagath Sisirakumara Ariyarathne 
jaga...@wso2.com wrote:

 Hi,

 Please review and merge PR[1] for JIRA issue [2].

 [1] - https://github.com/wso2/carbon-mediation/pull/208
 [2] - https://wso2.org/jira/browse/ESBJAVA-3742


 Thanks.
 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge PR

[Isuru Udana]

done.

On Wed, Jun 10, 2015 at 9:05 AM, Jagath Sisirakumara Ariyarathne 
jaga...@wso2.com wrote:

 Hi,

 Please review and merge PR[1] for JIRA issue[2].

 [1] - https://github.com/wso2/wso2-synapse/pull/220
 [2] - https://wso2.org/jira/browse/ESBJAVA-3735

 Thanks.
 --
 Jagath Ariyarathne
 Technical Lead
 WSO2 Inc.  http://wso2.com/
 Email: jaga...@wso2.com
 Mob  : +94 77 386 7048




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2-uri-templates (1.6.4) public git repository

[Isuru Udana]

Hi,

1.6.4 version was released from svn.
Is this available in somewhere in git ? Or else do we need to bring it into
in git ?


Thanks.


On Tue, Jun 9, 2015 at 1:57 PM, Kevin Ratnasekera ke...@wso2.com wrote:

 Hi all,
 I need some fixes to be included with $subject with related to public
 jira[1]. Where can I find the released version of $subject?
 [1]https://wso2.org/jira/browse/ESBJAVA-3751
 Regards
 Kevin

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




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Review PR for synapse - Changes in endpint timeout behaviour

[Isuru Udana]

On Wed, May 27, 2015 at 4:46 PM, Isuru Udana isu...@wso2.com wrote:

 Hi All,

 Can you please review the PR[1] for wso2-synapse. I have done following
 changes to endpoint timeout behaviour.


- When timeout action is set to FAULT or DISCARD and leave the timeout
duration field, synapse will put 30s as the timeout. Ideally it should use
global timeout interval.
- When timeout action is NONE, timeout duration is set to global
timeout interval, even though we set a timeout interval at the endpoint
- Correct the log message getting printed from TimeoutHandler upon
callback expiration. Earlier it was always printing global timeout interval
as the expiring time.


 [1] https://github.com/wso2/wso2-synapse/pull/213

 Thanks.

 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Callbacks recycling analysis for standard transports

[Isuru Udana]

Hi Suhan,

You can enabled debug logs. In debug log statements are getting printed for
callback addition and removal.

Thanks.

On Mon, May 25, 2015 at 2:23 PM, Suhan Dharmasuriya suh...@wso2.com wrote:

 Hi,

 How can I analyze whether Callbacks are getting recycled or not for
 standard transports
 (say HTTP) in ESB 4.8.1?
 What is the best way?

 Thanks,
 Suhan

 --
 Suhan Dharmasuriya
 Software Engineer - Test Automation

 *WSO2, Inc. *

 lean . enterprise . middleware
 Tel: +94 112 145345
 Mob: +94 779 869138
 Blog: http://suhan-opensource.blogspot.com/




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.9.0 with carbon-commons 4.4.2

[Isuru Udana]

)
 at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at
 org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
 at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
 at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at
 org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
 at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
 at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
 at
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
 at
 org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
 at
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
 at
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
 at
 org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
 at
 org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49)
 at
 org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
 at
 org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
 at
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
 at
 org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
 at
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
 at
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
 at
 org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
 at
 org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
 at
 org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739)
 at
 org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698)
 at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at
 org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
 at java.lang.Thread.run(Thread.java:745)



 --
 *Ravi Undupitiya*
 Senior Software Engineer; WSO2 http://wso2.com


 *E-mail: r...@wso2.com http://wso2.com**M: **+94 772 930 712
 %2B94%C2%A0772%20930%20712*

 Lean . Enterprise . Middleware




 --
 *Ravi Undupitiya*
 Senior Software Engineer; WSO2 http://wso2.com


 *E-mail: r...@wso2.com http://wso2.com**M: **+94 772 930 712
 %2B94%C2%A0772%20930%20712*

 Lean . Enterprise . Middleware





 --
 *Ravi Undupitiya*
 Senior Software Engineer; WSO2 http://wso2.com


 *E-mail: r...@wso2.com http://wso2.com**M: **+94 772 930 712
 %2B94%C2%A0772%20930%20712*

 Lean . Enterprise . Middleware





-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB SendMediator : synapse properties from the cache - synapse.timeout_handler_interval

[Isuru Udana]

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




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.9.0 with carbon-commons 4.4.2

[Isuru Udana]

Hi All,

We have encountered lot of issues after upgrading carbon-commons and
carbon-identity (not released yet).

We have to release following repos.

carbon-commons, carbon-identity, carbon-multitenancy, carbon-deployment


Carbon-commons


Got the following error in p2 profile gen.

Installation failed.
An error occurred while configuring the installed items
 session context was:(profile=worker,
phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
-- [R]org.wso2.carbon.tenant.mgt.common.server.feature.group 4.4.2,
action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
 I/O Error while copying
/Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.tenant.mgt.common.server_4.4.2/conf/stratos.xml
- see details.
Caused by:  java.io.IOException: Source:
/Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.tenant.mgt.common.server_4.4.2/conf/stratos.xmldoes
not exists
Application failed, log file location:
/Users/isuruu/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1432223824690.log



This is due to
https://github.com/wso2/carbon-commons/blob/1b946695cf10f0e4ae6c526675ecfc1db81e9f7d/features/tenant-mgt-common/org.wso2.carbon.tenant.mgt.common.server.feature/resources/p2.inf
We need to remove line #6 here.


Carbon-identity
——--

Got issues due to massive refactoring has made.
Ex.
In captcha orbit packages are exported without a version
http://maven.wso2.org/nexus/content/groups/wso2-public/kaptcha/wso2/kaptcha/2.3.0.wso2v1/kaptcha-2.3.0.wso2v1.pom
But in identity packages are imported with a version.

Diff attached to fix the issues. Please review and commit.


Carnbon-multitenancy and carbon-deployment
—— ——
Need to upgrade carbon-identity version and do a release as features coming
form these repos cannot co-exist with features coming from carbon-identity.

Thanks.


On Thu, May 21, 2015 at 3:52 PM, Malithi Edirisinghe malit...@wso2.com
wrote:

 Hi Isuru,

 We are not packing that bundle. Neither we use entitlement.proxy in our
 pack.
 However, org.wso2.carbon.identity.entitlement component which we use, also
 requests for 'org.apache.xerces.util' and it comes from the osgi framework
 (org.eclipse.osgi_3.9.1.v20130814-1242). The same package is used
 with 'org.wso2.carbon.identity.entitlement.proxy'

 Thanks,
 Malithi.

 On Thu, May 21, 2015 at 3:18 PM, Isuru Udana isu...@wso2.com wrote:

 IS also packing the same bundle. Are they also facing the same issue ?
 Actually we packed this jar from entitlement.mediator feature since
 entitlement.proxy (in carbon-identity) requires it.

 On Thu, May 21, 2015 at 3:10 PM, Manoj Kumara ma...@wso2.com wrote:

 Hi Ravi,

 I manually deleted 'xercesImpl_2.8.1.wso2v2.jar' from the pack and
 things seems to be working fine. You may required to bundle that one. I
 think the root course is it export unnecessary packages and this cause
 issue.

 Regards,
 Manoj


 *Manoj Kumara*
 Software Engineer
 WSO2 Inc. http://wso2.com/
 *lean.enterprise.middleware*
 Mobile: +94713448188

 On Thu, May 21, 2015 at 2:59 PM, Ravi Undupitiya r...@wso2.com wrote:

 Hi Manoj,

 You can find the pack at [1].

 [1]
 https://svn.wso2.com/wso2/custom/projects/scratch/ravi/commons-4.4.2/wso2esb-4.9.0-M8-SNAPSHOT.zip

 On Thu, May 21, 2015 at 2:54 PM, Manoj Kumara ma...@wso2.com wrote:

 Hi Ravi,

 Can you share a ESB server.

 Regards,
 Manoj


 *Manoj Kumara*
 Software Engineer
 WSO2 Inc. http://wso2.com/
 *lean.enterprise.middleware*
 Mobile: +94713448188

 On Thu, May 21, 2015 at 2:49 PM, Ravi Undupitiya r...@wso2.com
 wrote:

 We're also seeing this error when trying to upload a CApp after
 upgrade to carbon-commons 4.4.2.

 [2015-05-21 14:07:31,654]  INFO - ApplicationManager Deploying Carbon
 Application : esb-test_1.0.0.car...
 [2015-05-21 14:07:32,797] ERROR - CappAxis2Deployer Error while
 deploying carbon application
 /home/wso2builder/WSO2/product-esb/modules/distribution/target/wso2esb-4.9.0-M8-SNAPSHOT/repository/deployment/server/carbonapps/esb-test_1.0.0.car
 java.lang.NullPointerException
 at
 org.wso2.carbon.application.deployer.AppDeployerUtils.areAllFeaturesInstalled(AppDeployerUtils.java:610)
 at
 org.wso2.carbon.application.deployer.AppDeployerUtils.buildAcceptanceList(AppDeployerUtils.java:634)
 at
 org.wso2.carbon.application.deployer.handler.DefaultAppDeployer.isAccepted(DefaultAppDeployer.java:214)
 at
 org.wso2.carbon.application.deployer.handler.DefaultAppDeployer.deployRecursively(DefaultAppDeployer.java:152)
 at
 org.wso2.carbon.application.deployer.handler.DefaultAppDeployer.deployArtifacts(DefaultAppDeployer.java:69)
 at
 org.wso2.carbon.application.deployer.internal.ApplicationManager.deployCarbonApp(ApplicationManager.java:263)
 at
 org.wso2

Re: [Dev] Please review and release carbon-identity-4.4.1

[Isuru Udana]

Hi All,

When are we releasing carbon-identity ? Appreciate if you can release today
morning to prevent ESB 4.9.0 Alpha getting delayed further.

Thanks.

On Wed, May 20, 2015 at 8:06 PM, Manoj Kumara ma...@wso2.com wrote:

 Hi,

 release:perform operation failed due to [1] unmappable character on a
 javadoc :(
 Now starting the release process again. Will update once done.

 [1]
 https://github.com/wso2/carbon-commons/commit/00f01029aaa6df5d53eca25f5c1d2d1b927e1386


 *Manoj Kumara*
 Software Engineer
 WSO2 Inc. http://wso2.com/
 *lean.enterprise.middleware*
 Mobile: +94713448188

 On Wed, May 20, 2015 at 7:08 PM, Malithi Edirisinghe malit...@wso2.com
 wrote:

 Hi All,

 we are waiting till carbon-commons is released. Will release soon after
 that.

 On Tue, May 19, 2015 at 2:29 PM, Prasad Tissera pras...@wso2.com wrote:

 added identity.base component to security.mgt.server feature.

 [1].https://github.com/wso2/carbon-identity/pull/303

 On Tue, May 19, 2015 at 1:52 PM, Johann Nallathamby joh...@wso2.com
 wrote:

 Lets go with packing it into security.mgt.server feature. Having
 feature for just one bundle doesn't seem right.

 On Tue, May 19, 2015 at 1:49 PM, Isuru Udana isu...@wso2.com wrote:



 On Mon, May 18, 2015 at 4:42 PM, Kasun Indrasiri ka...@wso2.com
 wrote:

 Can we get a new release of carbon-identity before Wed? I think we
 have sent all the required PRs.

 On Mon, May 18, 2015 at 4:36 PM, Isuru Udana isu...@wso2.com wrote:

 Hi,

 In ESB we are installing org.wso2.carbon.security.mgt.server.feature
 coming from carbon-identity.

 org.wso2.carbon.identity.sts.store is also getting packed from the
 same feature.

 In sts store IdentityException is used in DBStsDAO class. That
 exception class is located in org.wso2.carbon.identity.base package 
 which
 is packing from org.wso2.carbon.identity.core.server.feature.
 So we have to ship that feature with ESB.
 But since identity.core is also getting packed from that feature,
 there are lot of unnecessary files like identity.xml getting added to 
 the
 ESB server. And also I noticed a significant delay in server start-up.

 So can we please create a more lightweight feature which packs only
 the org.wso2.carbon.identity.base, so that we can ship that with ESB ?

 We have the option to pack the identity.base with security.mgt.server
 feature too. Please evaluate the available options and release the
 carbon-identity asap.

 Thanks.


 This is applicable to other servers like AS,DSS as well.

 Thanks.

 On Mon, May 18, 2015 at 3:07 PM, Isuru Udana isu...@wso2.com
 wrote:

 Hi,

 Few more issues.

 1.

 Installation failed.
 An error occurred while configuring the installed items
  session context was:(profile=worker,
 phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, 
 operand=null
 -- [R]org.wso2.carbon.security.mgt.server.feature.group 4.4.1,
 action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
  I/O Error while copying
 /Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.security.mgt.server_4.4.1/conf/jaas.conf
 - see details.
 Caused by:  java.io.IOException: Source:
 /Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.security.mgt.server_4.4.1/conf/jaas.confdoes
 not exists
 Application failed, log file location:
 /Users/isuruu/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1431939984331.log

 2.

 !MESSAGE session context was:(profile=worker,
 phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, 
 operand=null
 -- [R]org.wso2.carbon.identity.core.server.feature.group 4.4.1,
 action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
 !SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.natives 4 0
 2015-05-18 14:13:26.117
 !MESSAGE I/O Error while copying
 /Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.identity.core.server_4.4.1/identity.xml
 - see details.
 !STACK 0
 java.io.IOException: Source:
 /Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.identity.core.server_4.4.1/identity.xmldoes
 not exists

 This is something related to following commit.


 https://github.com/wso2/carbon-identity/commit/2e4316d253df5068eb20696663de483629b5ad47

 Error went away by reverting changes made to the following files in
 the above commit.


 features/identity-core/org.wso2.carbon.identity.core.server.feature/resources/p2.inf

 features/security-mgt/org.wso2.carbon.security.mgt.server.feature/src/main/resources/p2.inf

 Please have a look on this as well.

 Thanks.

 On Mon, May 18, 2015 at 1:18 PM, Malithi Edirisinghe

Re: [Dev] Please review and release carbon-identity-4.4.1

[Isuru Udana]

On Mon, May 18, 2015 at 4:42 PM, Kasun Indrasiri ka...@wso2.com wrote:

 Can we get a new release of carbon-identity before Wed? I think we have
 sent all the required PRs.

 On Mon, May 18, 2015 at 4:36 PM, Isuru Udana isu...@wso2.com wrote:

 Hi,

 In ESB we are installing org.wso2.carbon.security.mgt.server.feature
 coming from carbon-identity.

 org.wso2.carbon.identity.sts.store is also getting packed from the same
 feature.

 In sts store IdentityException is used in DBStsDAO class. That exception
 class is located in org.wso2.carbon.identity.base package which is packing
 from org.wso2.carbon.identity.core.server.feature.
 So we have to ship that feature with ESB.
 But since identity.core is also getting packed from that feature, there
 are lot of unnecessary files like identity.xml getting added to the ESB
 server. And also I noticed a significant delay in server start-up.

 So can we please create a more lightweight feature which packs only the
 org.wso2.carbon.identity.base, so that we can ship that with ESB ?

 We have the option to pack the identity.base with security.mgt.server
feature too. Please evaluate the available options and release the
carbon-identity asap.

Thanks.


 This is applicable to other servers like AS,DSS as well.

 Thanks.

 On Mon, May 18, 2015 at 3:07 PM, Isuru Udana isu...@wso2.com wrote:

 Hi,

 Few more issues.

 1.

 Installation failed.
 An error occurred while configuring the installed items
  session context was:(profile=worker,
 phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
 -- [R]org.wso2.carbon.security.mgt.server.feature.group 4.4.1,
 action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
  I/O Error while copying
 /Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.security.mgt.server_4.4.1/conf/jaas.conf
 - see details.
 Caused by:  java.io.IOException: Source:
 /Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.security.mgt.server_4.4.1/conf/jaas.confdoes
 not exists
 Application failed, log file location:
 /Users/isuruu/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1431939984331.log

 2.

 !MESSAGE session context was:(profile=worker,
 phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
 -- [R]org.wso2.carbon.identity.core.server.feature.group 4.4.1,
 action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
 !SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.natives 4 0 2015-05-18
 14:13:26.117
 !MESSAGE I/O Error while copying
 /Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.identity.core.server_4.4.1/identity.xml
 - see details.
 !STACK 0
 java.io.IOException: Source:
 /Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.identity.core.server_4.4.1/identity.xmldoes
 not exists

 This is something related to following commit.


 https://github.com/wso2/carbon-identity/commit/2e4316d253df5068eb20696663de483629b5ad47

 Error went away by reverting changes made to the following files in the
 above commit.


 features/identity-core/org.wso2.carbon.identity.core.server.feature/resources/p2.inf

 features/security-mgt/org.wso2.carbon.security.mgt.server.feature/src/main/resources/p2.inf

 Please have a look on this as well.

 Thanks.

 On Mon, May 18, 2015 at 1:18 PM, Malithi Edirisinghe malit...@wso2.com
 wrote:

 Hi Isuru,

 Thank you for pointing this out. We will release the next
 carbon-identity version with above fixed, by Wednesday.

 Thanks,
 Malithi.

 On Mon, May 18, 2015 at 12:31 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Johann/Prasad,

 We are getting lot of build errors when build p2-profile of product
 ESB.
 It looks to me massive refactoring made in the pom files has caused
 this.

 Most of them got fixed by packing the missing dependancies from
 Entitlement mediator feature. But we cannot do anything from our end for
 following error.


 Installation failed.
 Cannot complete the install because one or more required items could
 not be found.
  Software being installed: WSO2 Carbon - XACML Mediation Feature
 4.4.1.SNAPSHOT (org.wso2.carbon.identity.xacml.mediator.feature.group
 4.4.1.SNAPSHOT)
  Missing requirement: org.wso2.carbon.identity.entitlement.proxy 4.4.1
 (org.wso2.carbon.identity.entitlement.proxy 4.4.1) requires 'package
 javax.cache [4.4.0,4.5.0)' but it could not be found
  Cannot satisfy dependency:
   From: org.wso2.carbon.identity.entitlement.mediator 4.4.1.SNAPSHOT
 (org.wso2.carbon.identity.entitlement.mediator 4.4.1.SNAPSHOT)
   To: package org.wso2

Re: [Dev] Please review and release carbon-identity-4.4.1

[Isuru Udana]

Hi Johann/Prasad,

We are getting lot of build errors when build p2-profile of product ESB.
It looks to me massive refactoring made in the pom files has caused this.

Most of them got fixed by packing the missing dependancies from Entitlement
mediator feature. But we cannot do anything from our end for following
error.


Installation failed.
Cannot complete the install because one or more required items could not be
found.
 Software being installed: WSO2 Carbon - XACML Mediation Feature
4.4.1.SNAPSHOT (org.wso2.carbon.identity.xacml.mediator.feature.group
4.4.1.SNAPSHOT)
 Missing requirement: org.wso2.carbon.identity.entitlement.proxy 4.4.1
(org.wso2.carbon.identity.entitlement.proxy 4.4.1) requires 'package
javax.cache [4.4.0,4.5.0)' but it could not be found
 Cannot satisfy dependency:
  From: org.wso2.carbon.identity.entitlement.mediator 4.4.1.SNAPSHOT
(org.wso2.carbon.identity.entitlement.mediator 4.4.1.SNAPSHOT)
  To: package org.wso2.carbon.identity.entitlement.proxy [4.4.0,5.0.0)
 Cannot satisfy dependency:
  From: WSO2 Carbon - XACML Mediation Feature 4.4.1.SNAPSHOT
(org.wso2.carbon.identity.xacml.mediator.feature.group 4.4.1.SNAPSHOT)
  To: org.wso2.carbon.identity.entitlement.mediator [4.4.1.SNAPSHOT]


In Carbon 4.4.0 kernel, javax.cache package is exported without a
version[1]. But in carbon-identity it is imported with a version
[4.4.0,4.5.0).
I have sent a PR[2] to remove the import version. Please merge the PR and
release a new carbon-identity version as released 4.4.1 is useless at the
moment.

[1]
https://github.com/wso2/carbon4-kernel/blob/master/core/javax.cache/pom.xml
[2] https://github.com/wso2/carbon-identity/pull/293

Thanks.



On Thu, May 14, 2015 at 6:44 PM, Isuru Udana isu...@wso2.com wrote:

 Thanks IS Team and Jayanga..!

 On Thu, May 14, 2015 at 6:40 PM, Jayanga Dissanayake jaya...@wso2.com
 wrote:

 Hi,

 carbon-identity-4.4.1 is released.

 Thanks,
 Jayanga.

 *Jayanga Dissanayake*
 Senior Software Engineer
 WSO2 Inc. - http://wso2.com/
 lean . enterprise . middleware
 email: jaya...@wso2.com
 mobile: +94772207259

 On Thu, May 14, 2015 at 6:07 PM, Jayanga Dissanayake jaya...@wso2.com
 wrote:

 Hi,

 Repo [1] is closed.
 Please verify.

 [1]
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbonidentity-005/

 Thanks,
 Jayanga.

 *Jayanga Dissanayake*
 Senior Software Engineer
 WSO2 Inc. - http://wso2.com/
 lean . enterprise . middleware
 email: jaya...@wso2.com
 mobile: +94772207259

 On Thu, May 14, 2015 at 5:52 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Kernel Team,

 Can we please get this released. We need this for ESB 4.9.0 alpha.

 Thanks.

 On Wed, May 13, 2015 at 6:06 PM, Prasad Tissera pras...@wso2.com
 wrote:

 Hi Kernal Team,

 carbon-identity-4.4.1 is released to the staging. Please review and
 release. Thanks.

 [1].
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbonidentity-005/

 --
 Prasad Tissera
 Software Engineer.
 Mobile : +94777223444




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/

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






 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and release carbon-identity-4.4.1

[Isuru Udana]

Hi,

Few more issues.

1.

Installation failed.
An error occurred while configuring the installed items
 session context was:(profile=worker,
phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
-- [R]org.wso2.carbon.security.mgt.server.feature.group 4.4.1,
action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
 I/O Error while copying
/Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.security.mgt.server_4.4.1/conf/jaas.conf
- see details.
Caused by:  java.io.IOException: Source:
/Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.security.mgt.server_4.4.1/conf/jaas.confdoes
not exists
Application failed, log file location:
/Users/isuruu/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1431939984331.log

2.

!MESSAGE session context was:(profile=worker,
phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
-- [R]org.wso2.carbon.identity.core.server.feature.group 4.4.1,
action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
!SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.natives 4 0 2015-05-18
14:13:26.117
!MESSAGE I/O Error while copying
/Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.identity.core.server_4.4.1/identity.xml
- see details.
!STACK 0
java.io.IOException: Source:
/Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.identity.core.server_4.4.1/identity.xmldoes
not exists

This is something related to following commit.

https://github.com/wso2/carbon-identity/commit/2e4316d253df5068eb20696663de483629b5ad47

Error went away by reverting changes made to the following files in the
above commit.

features/identity-core/org.wso2.carbon.identity.core.server.feature/resources/p2.inf
features/security-mgt/org.wso2.carbon.security.mgt.server.feature/src/main/resources/p2.inf

Please have a look on this as well.

Thanks.

On Mon, May 18, 2015 at 1:18 PM, Malithi Edirisinghe malit...@wso2.com
wrote:

 Hi Isuru,

 Thank you for pointing this out. We will release the next carbon-identity
 version with above fixed, by Wednesday.

 Thanks,
 Malithi.

 On Mon, May 18, 2015 at 12:31 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Johann/Prasad,

 We are getting lot of build errors when build p2-profile of product ESB.
 It looks to me massive refactoring made in the pom files has caused this.

 Most of them got fixed by packing the missing dependancies from
 Entitlement mediator feature. But we cannot do anything from our end for
 following error.


 Installation failed.
 Cannot complete the install because one or more required items could not
 be found.
  Software being installed: WSO2 Carbon - XACML Mediation Feature
 4.4.1.SNAPSHOT (org.wso2.carbon.identity.xacml.mediator.feature.group
 4.4.1.SNAPSHOT)
  Missing requirement: org.wso2.carbon.identity.entitlement.proxy 4.4.1
 (org.wso2.carbon.identity.entitlement.proxy 4.4.1) requires 'package
 javax.cache [4.4.0,4.5.0)' but it could not be found
  Cannot satisfy dependency:
   From: org.wso2.carbon.identity.entitlement.mediator 4.4.1.SNAPSHOT
 (org.wso2.carbon.identity.entitlement.mediator 4.4.1.SNAPSHOT)
   To: package org.wso2.carbon.identity.entitlement.proxy [4.4.0,5.0.0)
  Cannot satisfy dependency:
   From: WSO2 Carbon - XACML Mediation Feature 4.4.1.SNAPSHOT
 (org.wso2.carbon.identity.xacml.mediator.feature.group 4.4.1.SNAPSHOT)
   To: org.wso2.carbon.identity.entitlement.mediator [4.4.1.SNAPSHOT]


 In Carbon 4.4.0 kernel, javax.cache package is exported without a
 version[1]. But in carbon-identity it is imported with a version
 [4.4.0,4.5.0).
 I have sent a PR[2] to remove the import version. Please merge the PR and
 release a new carbon-identity version as released 4.4.1 is useless at the
 moment.

 [1]
 https://github.com/wso2/carbon4-kernel/blob/master/core/javax.cache/pom.xml
 [2] https://github.com/wso2/carbon-identity/pull/293

 Thanks.



 On Thu, May 14, 2015 at 6:44 PM, Isuru Udana isu...@wso2.com wrote:

 Thanks IS Team and Jayanga..!

 On Thu, May 14, 2015 at 6:40 PM, Jayanga Dissanayake jaya...@wso2.com
 wrote:

 Hi,

 carbon-identity-4.4.1 is released.

 Thanks,
 Jayanga.

 *Jayanga Dissanayake*
 Senior Software Engineer
 WSO2 Inc. - http://wso2.com/
 lean . enterprise . middleware
 email: jaya...@wso2.com
 mobile: +94772207259

 On Thu, May 14, 2015 at 6:07 PM, Jayanga Dissanayake jaya...@wso2.com
 wrote:

 Hi,

 Repo [1] is closed.
 Please verify.

 [1]
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbonidentity-005/

 Thanks,
 Jayanga.

 *Jayanga Dissanayake*
 Senior

[Dev] carbon-deployment release required for ESB 4.9.0 Alpha

[Isuru Udana]

Hi All,

We are getting following build error in ESB p2 profile generation.

Cannot complete the install because of a conflicting dependency.
 Software being installed: Key Store Management Feature 4.4.1
(org.wso2.carbon.security.mgt.feature.group 4.4.1)
 Software being installed: WSO2 Carbon - Service Management Feature 4.4.0
(org.wso2.carbon.service.mgt.feature.group 4.4.0)
 Only one of the following can be installed at once:
  WSO2 Carbon - Security Management UI Feature 4.4.0
(org.wso2.carbon.security.mgt.ui.feature.jar 4.4.0)
  WSO2 Carbon - Security Management UI Feature 4.4.1
(org.wso2.carbon.security.mgt.ui.feature.jar 4.4.1)
 Cannot satisfy dependency:
  From: Key Store Management Feature 4.4.1
(org.wso2.carbon.security.mgt.feature.group 4.4.1)
  To: org.wso2.carbon.security.mgt.ui.feature.group [4.4.1]
 Cannot satisfy dependency:
  From: WSO2 Carbon - Security Management UI Feature 4.4.0
(org.wso2.carbon.security.mgt.ui.feature.group 4.4.0)
  To: org.wso2.carbon.security.mgt.ui.feature.jar [4.4.0]
 Cannot satisfy dependency:
  From: WSO2 Carbon - Security Management UI Feature 4.4.1
(org.wso2.carbon.security.mgt.ui.feature.group 4.4.1)
  To: org.wso2.carbon.security.mgt.ui.feature.jar [4.4.1]
 Cannot satisfy dependency:
  From: WSO2 Carbon - Service Management Feature 4.4.0
(org.wso2.carbon.service.mgt.feature.group 4.4.0)
  To: org.wso2.carbon.service.mgt.ui.feature.group [4.4.0]
 Cannot satisfy dependency:
  From: WSO2 Carbon - Service Management UI Feature 4.4.0
(org.wso2.carbon.service.mgt.ui.feature.group 4.4.0)
  To: org.wso2.carbon.security.mgt.ui.feature.group [4.4.0]


Service management feature (in carbon-deployment) incorrectly packing
security management feature. Hence carbon-deployment 4.4.0 and
carbon-identity 4.4.1 cannot exit together.

We need to fix this in service management and need to release new version.
And also we have to remove policy editor getting packed from service
management ui feature.

Please consider this as urgent as this is blocking ESB 4.9.0 Alpha release.

Thanks.




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and release carbon-identity-4.4.1

[Isuru Udana]

Hi,

In ESB we are installing org.wso2.carbon.security.mgt.server.feature coming
from carbon-identity.

org.wso2.carbon.identity.sts.store is also getting packed from the same
feature.

In sts store IdentityException is used in DBStsDAO class. That exception
class is located in org.wso2.carbon.identity.base package which is packing
from org.wso2.carbon.identity.core.server.feature.
So we have to ship that feature with ESB.
But since identity.core is also getting packed from that feature, there are
lot of unnecessary files like identity.xml getting added to the ESB server.
And also I noticed a significant delay in server start-up.

So can we please create a more lightweight feature which packs only the
org.wso2.carbon.identity.base, so that we can ship that with ESB ?

This is applicable to other servers like AS,DSS as well.

Thanks.

On Mon, May 18, 2015 at 3:07 PM, Isuru Udana isu...@wso2.com wrote:

 Hi,

 Few more issues.

 1.

 Installation failed.
 An error occurred while configuring the installed items
  session context was:(profile=worker,
 phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
 -- [R]org.wso2.carbon.security.mgt.server.feature.group 4.4.1,
 action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
  I/O Error while copying
 /Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.security.mgt.server_4.4.1/conf/jaas.conf
 - see details.
 Caused by:  java.io.IOException: Source:
 /Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.security.mgt.server_4.4.1/conf/jaas.confdoes
 not exists
 Application failed, log file location:
 /Users/isuruu/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1431939984331.log

 2.

 !MESSAGE session context was:(profile=worker,
 phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
 -- [R]org.wso2.carbon.identity.core.server.feature.group 4.4.1,
 action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
 !SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.natives 4 0 2015-05-18
 14:13:26.117
 !MESSAGE I/O Error while copying
 /Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.identity.core.server_4.4.1/identity.xml
 - see details.
 !STACK 0
 java.io.IOException: Source:
 /Users/isuruu/wso2/source/public/git/isudana/product-esb/modules/p2-profile/target/wso2carbon-core-4.4.0/repository/components/worker/../features/org.wso2.carbon.identity.core.server_4.4.1/identity.xmldoes
 not exists

 This is something related to following commit.


 https://github.com/wso2/carbon-identity/commit/2e4316d253df5068eb20696663de483629b5ad47

 Error went away by reverting changes made to the following files in the
 above commit.


 features/identity-core/org.wso2.carbon.identity.core.server.feature/resources/p2.inf

 features/security-mgt/org.wso2.carbon.security.mgt.server.feature/src/main/resources/p2.inf

 Please have a look on this as well.

 Thanks.

 On Mon, May 18, 2015 at 1:18 PM, Malithi Edirisinghe malit...@wso2.com
 wrote:

 Hi Isuru,

 Thank you for pointing this out. We will release the next carbon-identity
 version with above fixed, by Wednesday.

 Thanks,
 Malithi.

 On Mon, May 18, 2015 at 12:31 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Johann/Prasad,

 We are getting lot of build errors when build p2-profile of product ESB.
 It looks to me massive refactoring made in the pom files has caused
 this.

 Most of them got fixed by packing the missing dependancies from
 Entitlement mediator feature. But we cannot do anything from our end for
 following error.


 Installation failed.
 Cannot complete the install because one or more required items could not
 be found.
  Software being installed: WSO2 Carbon - XACML Mediation Feature
 4.4.1.SNAPSHOT (org.wso2.carbon.identity.xacml.mediator.feature.group
 4.4.1.SNAPSHOT)
  Missing requirement: org.wso2.carbon.identity.entitlement.proxy 4.4.1
 (org.wso2.carbon.identity.entitlement.proxy 4.4.1) requires 'package
 javax.cache [4.4.0,4.5.0)' but it could not be found
  Cannot satisfy dependency:
   From: org.wso2.carbon.identity.entitlement.mediator 4.4.1.SNAPSHOT
 (org.wso2.carbon.identity.entitlement.mediator 4.4.1.SNAPSHOT)
   To: package org.wso2.carbon.identity.entitlement.proxy [4.4.0,5.0.0)
  Cannot satisfy dependency:
   From: WSO2 Carbon - XACML Mediation Feature 4.4.1.SNAPSHOT
 (org.wso2.carbon.identity.xacml.mediator.feature.group 4.4.1.SNAPSHOT)
   To: org.wso2.carbon.identity.entitlement.mediator [4.4.1.SNAPSHOT]


 In Carbon 4.4.0 kernel, javax.cache package is exported without a
 version[1]. But in carbon-identity it is imported with a version
 [4.4.0,4.5.0).
 I have sent

Re: [Dev] Please review and release carbon-identity-4.4.1

[Isuru Udana]

Thanks IS Team and Jayanga..!

On Thu, May 14, 2015 at 6:40 PM, Jayanga Dissanayake jaya...@wso2.com
wrote:

 Hi,

 carbon-identity-4.4.1 is released.

 Thanks,
 Jayanga.

 *Jayanga Dissanayake*
 Senior Software Engineer
 WSO2 Inc. - http://wso2.com/
 lean . enterprise . middleware
 email: jaya...@wso2.com
 mobile: +94772207259

 On Thu, May 14, 2015 at 6:07 PM, Jayanga Dissanayake jaya...@wso2.com
 wrote:

 Hi,

 Repo [1] is closed.
 Please verify.

 [1]
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbonidentity-005/

 Thanks,
 Jayanga.

 *Jayanga Dissanayake*
 Senior Software Engineer
 WSO2 Inc. - http://wso2.com/
 lean . enterprise . middleware
 email: jaya...@wso2.com
 mobile: +94772207259

 On Thu, May 14, 2015 at 5:52 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Kernel Team,

 Can we please get this released. We need this for ESB 4.9.0 alpha.

 Thanks.

 On Wed, May 13, 2015 at 6:06 PM, Prasad Tissera pras...@wso2.com
 wrote:

 Hi Kernal Team,

 carbon-identity-4.4.1 is released to the staging. Please review and
 release. Thanks.

 [1].
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbonidentity-005/

 --
 Prasad Tissera
 Software Engineer.
 Mobile : +94777223444




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/

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






-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and release carbon-identity-4.4.1

[Isuru Udana]

Hi Kernel Team,

Can we please get this released. We need this for ESB 4.9.0 alpha.

Thanks.

On Wed, May 13, 2015 at 6:06 PM, Prasad Tissera pras...@wso2.com wrote:

 Hi Kernal Team,

 carbon-identity-4.4.1 is released to the staging. Please review and
 release. Thanks.

 [1].
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbonidentity-005/

 --
 Prasad Tissera
 Software Engineer.
 Mobile : +94777223444




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Reading 'transport.vfs.FileURI' from governance registry

[Isuru Udana]

Hi Suhan,

Fetching from registry is not supported for service parameters.

Thanks.




On Tue, May 12, 2015 at 11:00 AM, Suhan Dharmasuriya suh...@wso2.com
wrote:

 Hi,

 I'm referring [1] and trying to customise the proxy [2] by transferring
 the endpoint and FileURI reading from registry.

 I have tested this for the endpoint successfully.

 Can you please let me know whether the 'transport.vfs.FileURI' can be read
 from governance registry?
 e.g.: *parameter name=transport.vfs.FileURI*
 gov:/elearning/filetransfers/v1/endpoints/articleDownloadInputEP
 */parameter*

 [1]
 http://suhan-opensource.blogspot.com/2015/03/using-file-system-as-transport-medium.html
 [2]
proxy name=StockQuoteProxy
   transports=vfs
   startOnLoad=true
   trace=disable
   description/
   target
  endpoint
 key=gov:/elearning/filetransfers/v1/endpoints/StockQuoteEPNew/
  outSequence
 property name=transport.vfs.ReplyFileName

 expression=fn:concat(fn:substring-after(get-property('MessageID'),
 'urn:uuid:'), '.xml')
   scope=transport/
 property name=OUT_ONLY value=true/
 send
endpoint
   address
 uri=vfs:file:///WSO2/XXX-NN/articledownload/out/
/endpoint
 /send
  /outSequence
   /target
   publishWSDL
 uri=file:repository/samples/resources/proxy/sample_proxy_1.wsdl/
   parameter name=transport.vfs.ActionAfterProcessMOVE/parameter
   parameter name=transport.PollInterval15/parameter
   parameter
 name=transport.vfs.MoveAfterProcessfile:///WSO2/XXX-NN/articledownload/original/parameter
 *  parameter
 name=transport.vfs.FileURIfile:///WSO2/XXX-NN/articledownload/in/parameter*
   parameter
 name=transport.vfs.MoveAfterFailurefile:///WSO2/XXX-NN/articledownload/error/parameter
   parameter name=transport.vfs.FileNamePattern.*\.xml/parameter
   parameter name=transport.vfs.ContentTypetext/xml/parameter
   parameter name=transport.vfs.ActionAfterFailureMOVE/parameter
/proxy

 Thanks,
 Suhan

 --
 Suhan Dharmasuriya
 Software Engineer - Test Automation

 *WSO2, Inc. *

 lean . enterprise . middleware
 Tel: +94 112 145345
 Mob: +94 779 869138
 Blog: http://suhan-opensource.blogspot.com/




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Message processor - forward to a sequence

[Isuru Udana]

Hi Hasitha,

This not possible for Forwarding message processor.

On Sun, May 3, 2015 at 8:24 PM, Hasitha Hiranya hasit...@wso2.com wrote:

 Hi,

 I am trying to forward a message to a sequence after receiving it from the
 queue/topic using message processor.

 How can we configure this?

 I tried giving a sequence as an endpoint hoping it would work, but did not
 (message processor deactivates not recognizing it)

 [image: Inline image 1]

 Is there a way to achieve this in ESB?

 Thanks

 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Message processor - forward to a sequence

[Isuru Udana]

Hi Maheeka,

On Sun, May 3, 2015 at 11:16 PM, Maheeka Jayasuriya mahe...@wso2.com
wrote:

 Hi Hasitha,

 Use the message.processor.reply.sequence property to define the
 forwarding sequence.

Reply sequence is to get the response received from the backend service. I
thought Hasitha's requirement is to direct the message in the message
store, to a sequence from the message processor.


 In management console click on Show Additional Parameters and provide
 sequence name to Reply sequence name parameter.

 Thanks,
 Maheeka

 [1] https://docs.wso2.com/display/ESB481/Message+Forwarding+Processor

 Maheeka Jayasuriya
 Software Engineer
 Mobile : +9450661

 On Sun, May 3, 2015 at 8:24 PM, Hasitha Hiranya hasit...@wso2.com wrote:

 Hi,

 I am trying to forward a message to a sequence after receiving it from
 the queue/topic using message processor.

 How can we configure this?

 I tried giving a sequence as an endpoint hoping it would work, but did
 not (message processor deactivates not recognizing it)

 [image: Inline image 1]

 Is there a way to achieve this in ESB?

 Thanks

 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com


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





-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Message processor - forward to a sequence

[Isuru Udana]

On Sun, May 3, 2015 at 11:33 PM, Hasitha Hiranya hasit...@wso2.com wrote:

 OK. I am trying a reliable delivery scenario.

 1. Get message.
 2. Go thro mediation flow.
 3. If something went wrong put the original message to a queue (message
 store)
 4. re-try the failed message (using message processor) and and let it go
 thro above mediation flow (it is not sending to a BE, but several steps)

If it is not sent to a BE, why we need reliable delivery, retry, etc. here
? I mean if there is no BE, there is nothing to do with reliable delivery.
I think this is not a store and forward scenario.


 @4 I need to go thro the flow again.

 Thanks

 On Sun, May 3, 2015 at 12:55 PM, Isuru Udana isu...@wso2.com wrote:

 What's your requirement to direct to a sequence ?


 On Sun, May 3, 2015 at 11:23 PM, Hasitha Hiranya hasit...@wso2.com
 wrote:

 Hi Maheeka/Isuru,

 Yes. I need to get the JMS message from the queue/topic and direct it to
 a sequence rather than sending it to the BE directly.

 If so, what are the alternative options here?
 A JMS proxy? But I need reliable delivery. re-try configurations, re-try
 interval etc.

 Thanks

 On Sun, May 3, 2015 at 12:49 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Maheeka,

 On Sun, May 3, 2015 at 11:16 PM, Maheeka Jayasuriya mahe...@wso2.com
 wrote:

 Hi Hasitha,

 Use the message.processor.reply.sequence property to define the
 forwarding sequence.

 Reply sequence is to get the response received from the backend
 service. I thought Hasitha's requirement is to direct the message in the
 message store, to a sequence from the message processor.


 In management console click on Show Additional Parameters and
 provide sequence name to Reply sequence name parameter.

 Thanks,
 Maheeka

 [1] https://docs.wso2.com/display/ESB481/Message+Forwarding+Processor

 Maheeka Jayasuriya
 Software Engineer
 Mobile : +9450661

 On Sun, May 3, 2015 at 8:24 PM, Hasitha Hiranya hasit...@wso2.com
 wrote:

 Hi,

 I am trying to forward a message to a sequence after receiving it
 from the queue/topic using message processor.

 How can we configure this?

 I tried giving a sequence as an endpoint hoping it would work, but
 did not (message processor deactivates not recognizing it)

 [image: Inline image 1]

 Is there a way to achieve this in ESB?

 Thanks

 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com


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





 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Message processor - forward to a sequence

[Isuru Udana]

On Mon, May 4, 2015 at 12:00 AM, Hasitha Hiranya hasit...@wso2.com wrote:

 Hi Isuru,

 Thanks for the clarification.
 Suppose your suggestion is to use MS/MP in a more granular manner.
 So if the calls to all these BE's should be reliable, does that mean at
 each point we need to have a MS/MP integration separately?

Yes exactly.


 Thanks

 On Sun, May 3, 2015 at 1:23 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Hasitha,

 On Sun, May 3, 2015 at 11:42 PM, Hasitha Hiranya hasit...@wso2.com
 wrote:

 Hi Isuru,

 Above mediation flow has several BE calls. Not one. And message
 transformations in the middle of them.
 That is why I was trying to direct it to the same sequence.

 Is this approach is wrong?

 Yes it is not correct.

 Basically if you need to guaranteed delivery we need to send the message
 using the Forwarding message processor directly to the backend. Forwarding
 message processor internally uses a blocking client to invoke the backend.
 If you want to do some transformation, you can do that before putting to
 the to the store. However if you have some kind of service chaining
 scenario you have to re-design flows using reply sequences etc.

 Thanks.


 Thanks

 On Sun, May 3, 2015 at 1:09 PM, Isuru Udana isu...@wso2.com wrote:



 On Sun, May 3, 2015 at 11:33 PM, Hasitha Hiranya hasit...@wso2.com
 wrote:

 OK. I am trying a reliable delivery scenario.

 1. Get message.
 2. Go thro mediation flow.
 3. If something went wrong put the original message to a queue
 (message store)
 4. re-try the failed message (using message processor) and and let it
 go thro above mediation flow (it is not sending to a BE, but several 
 steps)

 If it is not sent to a BE, why we need reliable delivery, retry, etc.
 here ? I mean if there is no BE, there is nothing to do with reliable
 delivery. I think this is not a store and forward scenario.


 @4 I need to go thro the flow again.

 Thanks

 On Sun, May 3, 2015 at 12:55 PM, Isuru Udana isu...@wso2.com wrote:

 What's your requirement to direct to a sequence ?


 On Sun, May 3, 2015 at 11:23 PM, Hasitha Hiranya hasit...@wso2.com
 wrote:

 Hi Maheeka/Isuru,

 Yes. I need to get the JMS message from the queue/topic and direct
 it to a sequence rather than sending it to the BE directly.

 If so, what are the alternative options here?
 A JMS proxy? But I need reliable delivery. re-try configurations,
 re-try interval etc.

 Thanks

 On Sun, May 3, 2015 at 12:49 PM, Isuru Udana isu...@wso2.com
 wrote:

 Hi Maheeka,

 On Sun, May 3, 2015 at 11:16 PM, Maheeka Jayasuriya 
 mahe...@wso2.com wrote:

 Hi Hasitha,

 Use the message.processor.reply.sequence property to define the
 forwarding sequence.

 Reply sequence is to get the response received from the backend
 service. I thought Hasitha's requirement is to direct the message in 
 the
 message store, to a sequence from the message processor.


 In management console click on Show Additional Parameters and
 provide sequence name to Reply sequence name parameter.

 Thanks,
 Maheeka

 [1]
 https://docs.wso2.com/display/ESB481/Message+Forwarding+Processor

 Maheeka Jayasuriya
 Software Engineer
 Mobile : +9450661

 On Sun, May 3, 2015 at 8:24 PM, Hasitha Hiranya hasit...@wso2.com
  wrote:

 Hi,

 I am trying to forward a message to a sequence after receiving it
 from the queue/topic using message processor.

 How can we configure this?

 I tried giving a sequence as an endpoint hoping it would work,
 but did not (message processor deactivates not recognizing it)

 [image: Inline image 1]

 Is there a way to achieve this in ESB?

 Thanks

 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com


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





 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887

Re: [Dev] Message processor - forward to a sequence

[Isuru Udana]

What's your requirement to direct to a sequence ?

On Sun, May 3, 2015 at 11:23 PM, Hasitha Hiranya hasit...@wso2.com wrote:

 Hi Maheeka/Isuru,

 Yes. I need to get the JMS message from the queue/topic and direct it to a
 sequence rather than sending it to the BE directly.

 If so, what are the alternative options here?
 A JMS proxy? But I need reliable delivery. re-try configurations, re-try
 interval etc.

 Thanks

 On Sun, May 3, 2015 at 12:49 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Maheeka,

 On Sun, May 3, 2015 at 11:16 PM, Maheeka Jayasuriya mahe...@wso2.com
 wrote:

 Hi Hasitha,

 Use the message.processor.reply.sequence property to define the
 forwarding sequence.

 Reply sequence is to get the response received from the backend service.
 I thought Hasitha's requirement is to direct the message in the message
 store, to a sequence from the message processor.


 In management console click on Show Additional Parameters and provide
 sequence name to Reply sequence name parameter.

 Thanks,
 Maheeka

 [1] https://docs.wso2.com/display/ESB481/Message+Forwarding+Processor

 Maheeka Jayasuriya
 Software Engineer
 Mobile : +9450661

 On Sun, May 3, 2015 at 8:24 PM, Hasitha Hiranya hasit...@wso2.com
 wrote:

 Hi,

 I am trying to forward a message to a sequence after receiving it from
 the queue/topic using message processor.

 How can we configure this?

 I tried giving a sequence as an endpoint hoping it would work, but did
 not (message processor deactivates not recognizing it)

 [image: Inline image 1]

 Is there a way to achieve this in ESB?

 Thanks

 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com


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





 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Message processor - forward to a sequence

[Isuru Udana]

Hi Hasitha,

On Sun, May 3, 2015 at 11:42 PM, Hasitha Hiranya hasit...@wso2.com wrote:

 Hi Isuru,

 Above mediation flow has several BE calls. Not one. And message
 transformations in the middle of them.
 That is why I was trying to direct it to the same sequence.

 Is this approach is wrong?

Yes it is not correct.

Basically if you need to guaranteed delivery we need to send the message
using the Forwarding message processor directly to the backend. Forwarding
message processor internally uses a blocking client to invoke the backend.
If you want to do some transformation, you can do that before putting to
the to the store. However if you have some kind of service chaining
scenario you have to re-design flows using reply sequences etc.

Thanks.


 Thanks

 On Sun, May 3, 2015 at 1:09 PM, Isuru Udana isu...@wso2.com wrote:



 On Sun, May 3, 2015 at 11:33 PM, Hasitha Hiranya hasit...@wso2.com
 wrote:

 OK. I am trying a reliable delivery scenario.

 1. Get message.
 2. Go thro mediation flow.
 3. If something went wrong put the original message to a queue (message
 store)
 4. re-try the failed message (using message processor) and and let it go
 thro above mediation flow (it is not sending to a BE, but several steps)

 If it is not sent to a BE, why we need reliable delivery, retry, etc.
 here ? I mean if there is no BE, there is nothing to do with reliable
 delivery. I think this is not a store and forward scenario.


 @4 I need to go thro the flow again.

 Thanks

 On Sun, May 3, 2015 at 12:55 PM, Isuru Udana isu...@wso2.com wrote:

 What's your requirement to direct to a sequence ?


 On Sun, May 3, 2015 at 11:23 PM, Hasitha Hiranya hasit...@wso2.com
 wrote:

 Hi Maheeka/Isuru,

 Yes. I need to get the JMS message from the queue/topic and direct it
 to a sequence rather than sending it to the BE directly.

 If so, what are the alternative options here?
 A JMS proxy? But I need reliable delivery. re-try configurations,
 re-try interval etc.

 Thanks

 On Sun, May 3, 2015 at 12:49 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Maheeka,

 On Sun, May 3, 2015 at 11:16 PM, Maheeka Jayasuriya mahe...@wso2.com
  wrote:

 Hi Hasitha,

 Use the message.processor.reply.sequence property to define the
 forwarding sequence.

 Reply sequence is to get the response received from the backend
 service. I thought Hasitha's requirement is to direct the message in the
 message store, to a sequence from the message processor.


 In management console click on Show Additional Parameters and
 provide sequence name to Reply sequence name parameter.

 Thanks,
 Maheeka

 [1]
 https://docs.wso2.com/display/ESB481/Message+Forwarding+Processor

 Maheeka Jayasuriya
 Software Engineer
 Mobile : +9450661

 On Sun, May 3, 2015 at 8:24 PM, Hasitha Hiranya hasit...@wso2.com
 wrote:

 Hi,

 I am trying to forward a message to a sequence after receiving it
 from the queue/topic using message processor.

 How can we configure this?

 I tried giving a sequence as an endpoint hoping it would work, but
 did not (message processor deactivates not recognizing it)

 [image: Inline image 1]

 Is there a way to achieve this in ESB?

 Thanks

 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com


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





 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/




 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Loopback mediator for ESB 4.7.0

[Isuru Udana]

Hi Hemika,

Loopback was introduced in ESB 4.8.0.

If you can explain the requirement, we'll able to help you.

On Fri, May 1, 2015 at 1:27 PM, Hemika Kodikara hem...@wso2.com wrote:

 Hi All,

 Is there loopback mediator in ESB 4.7.0 ? I am trying to use the following
 synapse in 4.7.0 which I copied from ESB 4.8.1.

 api xmlns=http://ws.apache.org/ns/synapse; name=jsonTest
 context=/json
resource methods=POST
   inSequence
  loopback/
   /inSequence
   outSequence
  script language=jsvar older = mc.getPayloadJSON(); var
 newer=older; mc.setPayloadJSON(newer);/script
  send/
   /outSequence
/resource
 /api

 I get the following error :

 org.apache.synapse.SynapseException: Unknown mediator referenced by
 configuration element : {http://ws.apache.org/ns/synapse}loopback

 Or is there a workaround ?

 Regards,
 Hemika

 Hemika Kodikara
 Software Engineer
 WSO2 Inc.
 lean . enterprise . middleware
 http://wso2.com

 Mobile : +9477762

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




-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Loopback mediator for ESB 4.7.0

[Isuru Udana]

I can't see a clear relationship between Loopback mediator and what you are
trying out.

But according to the proxy configuration you have given above, I guess you
are trying to send a response back to the client from the proxy itself
without sending the request to a backend service. For that you can reverse
the message within the inSequence as follows.

api xmlns=http://ws.apache.org/ns/synapse; name=jsonTest
context=/json
   resource methods=POST
  inSequence
 script language=jsvar older = mc.getPayloadJSON(); var
newer=older; mc.setPayloadJSON(newer);/script
* header name=To action=remove/*
* property name=RESPONSE value=true/*
 send/
  /inSequence
   /resource
/api

Please note the highlighted lines.

Thanks.

On Fri, May 1, 2015 at 2:06 PM, Hemika Kodikara hem...@wso2.com wrote:

 Hi Isuru,

 Thanks for the reply.

 Ideally I want to experiment the following message builders(axis2.xml).

 !--JSON Message Builders--
 messageBuilder contentType=application/json

 class=org.apache.synapse.commons.json.JsonBuilder/
 !--messageBuilder contentType=application/json

 class=org.apache.synapse.commons.json.JsonStreamBuilder/--
 messageBuilder contentType=application/json
 class=org.apache.axis2.json.JSONBuilder/
 !--messageBuilder contentType=application/json
 class=org.apache.axis2.json.JSONStreamBuilder/--

 I am invoking the following curl to invoke the api.

 curl -X POST -d {\origin\:\202.37.75.130\} -H Content-Type:
 application/json http://10.113.56.222:8280/json
 http://10.113.56.222:8281/json

 Is there a better or easier way to try them out ?

 Regards,
 Hemika

 Hemika Kodikara
 Software Engineer
 WSO2 Inc.
 lean . enterprise . middleware
 http://wso2.com

 Mobile : +9477762

 On Fri, May 1, 2015 at 1:38 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Hemika,

 Loopback was introduced in ESB 4.8.0.

 If you can explain the requirement, we'll able to help you.

 On Fri, May 1, 2015 at 1:27 PM, Hemika Kodikara hem...@wso2.com wrote:

 Hi All,

 Is there loopback mediator in ESB 4.7.0 ? I am trying to use the
 following synapse in 4.7.0 which I copied from ESB 4.8.1.

 api xmlns=http://ws.apache.org/ns/synapse; name=jsonTest
 context=/json
resource methods=POST
   inSequence
  loopback/
   /inSequence
   outSequence
  script language=jsvar older = mc.getPayloadJSON(); var
 newer=older; mc.setPayloadJSON(newer);/script
  send/
   /outSequence
/resource
 /api

 I get the following error :

 org.apache.synapse.SynapseException: Unknown mediator referenced by
 configuration element : {http://ws.apache.org/ns/synapse}loopback

 Or is there a workaround ?

 Regards,
 Hemika

 Hemika Kodikara
 Software Engineer
 WSO2 Inc.
 lean . enterprise . middleware
 http://wso2.com

 Mobile : +9477762

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




 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/





-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev