[Dev] [Balana] No getter for ObligationId in Obligation

[Manujith Pallewatte]

Hi all,

I'm in the process of implementing the XACML 3.0 JSON profile for requests
and responses and in writing the responses, I need to obtain the Obligation
Id of each Obligation [1]. But as seen in [1], there's no public getter
method available to obtain the Id from the Obligation object.
Is there a workaround or can a getter be added?


[1]
https://github.com/wso2/balana/blob/master/modules/balana-core/src/main/java/org/wso2/balana/xacml3/Obligation.java

Thank You
Manujith

-- 



Manujith Pallewatte
[image: https://]about.me/manzzup

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

Re: [Dev] [GSoC 2016]Proposal 03: [ML]Visual(Deep) Neural Network Builder -Project Progress

[Upul Bandara]

Hi,

As you know we have only two weeks to complete GSOC projects.
Unfortunately, this project is a little bit lagging behind and it looks
like you have to put some additional effort during the last two week. In
order to support you, we though it is better to have a small F2F meeting
with you and it will help you to sort out any issues currently you are
facing with.

So can you please schedule a meeting with the ML team?

Thanks,
Upul

On Sat, Jul 30, 2016 at 5:45 PM, Nirmal Fernando  wrote:

>
> On Sat, Jul 30, 2016 at 1:43 PM, Lakini Senanayaka <
> lakinisenanayak...@gmail.com> wrote:
>
>> Hi,
>>
>> I have solved the above problem.I have referred the mail thread *[Dev]
>> "Error 403 - Forbidden" when session expires in admin console*[1] in dev
>> mailing list.I couldn't upload  jaggery files to the console  and when I
>> was trying to do it, it gave the* Error 403-Forbidden.*
>>
>> I have copied the jaggery files to
>> */repository/deployment/server/jaggerapps* directory as Supun
>> instructed and it worked.
>>
>> Although I have implemented the back end for feed forward neural network
>> still it has some problems.It doesn't work well.Do I need to add the
>>  neural network algorithms to the
>> *org.wso2.carbon.ml.core.spark.algorithms* in Carbon ML ?Do I need to
>> follow the same pattern which is used by the Carbon ML when implementing
>> the back end coding and APIs?
>>
>
> Yes please.
>
>>
>> I will submit the demo ASAP.
>>
>> [1]
>> https://mail.google.com/mail/u/0/#search/Re%3A+%5BDev%5D+%22Error+403++Forbidden%22+when+session+expires+in+admin%09console/155bfcbf7e98992f?projector=1
>>
>> Thank you.
>> --
>> KIND Regards,
>> *Lakini Senanayaka.*
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>


-- 
Upul Bandara,
Associate Technical Lead, WSO2, Inc.,
Mob: +94 715 468 345.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS] when will the IoTS be GA?

[云展智创]

Hi Sumedha,

Any suggestions? Thanks.

－－
Zhanwen Zhou (Jason), General Manager
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: API Management, Application Performance Management, IT Service 
Management

On Jul 31, 2016, at 9:20 PM, Sumedha Rubasinghe  wrote:

> Hi Jason,
> UIs in IoTS Master is not fully functional due to on going work I mentioned 
> b4.
> 
> Will get back to you with an alternative plan by tomorrow.
> 
> 
> On Jul 31, 2016 2:48 PM, "云展智创"  wrote:
> Hi Sumedha,
> 
> Yes, I thought the IoTS would be GA on mid of July. I have a project using 
> IoTS to manage some smart devices. IoTS is the core backend component in the 
> project.  I also need the cdmf-devicetype-archetype tools to create the 
> plugins. Could you give me some advices on how to build the latest stable 
> release from the code? 
> 
> by the way, I found that the real time device statistics data could not be 
> showed on the graph of device view in 1.0.0 Alpha release. Is that a know 
> error? Thanks.
> 
> －－
> Zhanwen Zhou (Jason), General Manager
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: API Management, IOT
> 
> On Jul 31, 2016, at 11:20 AM, Sumedha Rubasinghe  wrote:
> 
>> Hi Jason,
>> After the IoTS 1.0.0 Alpha, we are in the middle of a strategic change which 
>> involves our mobile device management capabilities. 
>> As you may already be aware, we have brought down all core device management 
>> capabilities into one level and implementing specific device management 
>> plugins on top of this. These device management plugins also cover our 
>> Android, iOS, Windows mobile plugins (as well as plugins for all other 
>> devices).
>> 
>> Originally 1.0.0 GA release date of IoTS was scheduled for July. But due to 
>> a customer commitment we have shifted our focus to stabilising Android 
>> device management until end of August.
>> 
>> Specific new release date of IoTS 1.0.0 GA will be decided after August.
>> 
>> If you have a project that gets impacted due to this shift please fill up 
>> our contact us form @ http://wso2.com/contact/ with your concern and we will 
>> see what we can do.
>>  
>> Thanks,
>> Sumedha
>> 
>> 
>> On Sat, Jul 30, 2016 at 3:03 PM, 云展智创  wrote:
>> Hi,
>> 
>> Could anyone tell me when will the IoTS be GA? Thanks a lot.
>> 
>> －－
>> Zhanwen Zhou (Jason),
>> +86 13922218435
>> zhanwen.z...@smartcloudex.com
>> Guangzhou Smart Cloudex Technology Co., Ltd.
>> Business: API Management, IOT
>> 
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>> 
>> 
>> 
>> -- 
>> /sumedha
>> m: +94 773017743
>> b :  bit.ly/sumedha
> 
> 

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

Re: [Dev] GSoC2016-Contact Development Team Feature

[Nathiesha Maddage]

Hi Kavith,

I tried creating the pom.xml by referring to the Developer Studio plugin
projects in git hub. Following the same structure as in the github plugin
projects. I came up with this, pom1.xml.

However since my project is still not under those parent projects as in
github, I created another pom2.xml as follows, by removing the parent tag,
by adding p2 repositaries and tycho plugin. After fixing couple of errors,
I could successfully build the project using pom2.xml.

Can you please have a look at the two pom.xml files and tell me if they
seem to be OK or if there are any issues in them? If that is OK, I can move
to the next milestone of the project.

Furthermore I changed the Bundle-Version in the project manifest to
4.2.0.qualifier, because the plugin projects in git hub under Developer
studio seem to have that version. I hope that is OK.

Thanks for the article on osgi services. I will go through it.

Thanks and regards

Nathiesha

On Mon, Aug 1, 2016 at 8:22 AM, Kavith Lokuhewage  wrote:

> Hi Nathiesha,
>
> How is the progress on converting project to a maven project? Please let
> us know if you face any issues.
>
> BTW, [1] is a good article on osgi services with eclipse plugins. We can
> use them for further decoupling publishers and report generators.
>
> Thanks,
>
> [1] http://www.vogella.com/tutorials/OSGiServices/article.html
>
> On 29 Jul 2016 5:19 p.m., "Nathiesha Maddage" 
> wrote:
>
>> Hi Jasintha and Kavith,
>>
>> Here is the project plan for the upcoming 3/4 weeks.
>>
>>   *July 30th-1st Aug*
>>
>>
>>-  Add and configure pom.xml
>>-  Use Maven tycho plugin
>>-  Build project using Maven
>>
>>
>>
>>   *2nd Aug-6th Aug*
>>
>>
>>- Write a REST web service to publish errors, deploy in tomcat and
>>testing.
>>-  Add options for the current plugin project to use above web service
>>-  Add current project classes and methods to be comply with above
>>changes
>>
>>
>>   *7th Aug-11th Aug*
>>
>>
>>- Define an extension point of the plugin
>>-  Add methods to get the registered plugins and their Project keys,
>>to maintain a map
>>- Add methods to group errors under their required plugins
>>-  Change the publisher methods to create multiple issues in Jira
>>
>>
>>   *12th Aug -15th Aug*
>>
>>
>>- Improve ErrorPublisher interfaces
>>-  Write OSGI services for ErrorPublisher interfaces
>>
>>
>>
>>   *16th Aug – 17th Aug*
>>
>>
>>- Create Feature Project using the plugin
>>
>>
>> * 18th Aug – 20th Aug*
>>
>>
>>-  Refine the code
>>-  Fix bugs
>>- Testing
>>
>>
>>  *21st Aug – 22nd Aug*
>>
>>
>>-  Documentation
>>
>>
>> Thanks and regards
>>
>> Nathiesha
>>
>>
>> On Fri, Jul 29, 2016 at 9:48 AM, Nathiesha Maddage <
>> nathieshamadd...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> Here are the minutes of the meeting I had yesterday (28/07/16) with
>>> Jasintha and Kavith.
>>>
>>> During the meeting the current project progress was discussed and
>>> suggestions were made to improve and finalize the development of the
>>> project. Listed below are the key points discussed during the meeting.
>>>
>>> 1.   Instructions were given on how to add pom.xml, to change its
>>> fields to match with the project , to use Maven tycho plugin and to build
>>> the project using maven.
>>>
>>> 2.   Suggestions were made on creating and improving interfaces
>>> like ErrorPublisher and ReportGenerator, and how to call the publish method
>>> of all the registered publishers using an iterator in the main controller
>>> class.
>>>
>>> 3.   We planned to add another option for the user, where he does
>>> not have any gmail and jira credentials, but a remote server would take
>>> care of publishing the error using a common general account. For that I was
>>> asked to write a REST web service that would handle this procedure, and to
>>> deploy it in tomcat for testing. Possibility of using micro services for
>>> this was also discussed.
>>>
>>> 4.   We planned to add multiple project keys for the jira create
>>> issue option where required, and to assign the project key based on the
>>> plugin that is responsible for the error. For that purpose, it was
>>> suggested to create an extension point of the project, so other plugins can
>>> extend it and define their own project key. Using this all the plugins that
>>> have extended the error reporter plugin and their respective project keys
>>> can be fetched, and a map can be maintained, to be used during the error
>>> reporting process.
>>>
>>> 5.   To expose the Publisher classes, OSGI services will be
>>> introduced to the project.
>>>
>>> 6.   It was suggested to create a feature by adding this plugin.
>>>
>>>
>>> Furthermore instructions were given on the documentation required for
>>> the project, and time frame for documentation was suggested. And I was
>>> asked to send a 

Re: [Dev] [MSF4J] [2.0.0] Illegal argument Exception Thrown when invoking a POST

[Hemika Kodikara]

Correction on my part, I misread the spec earlier.

Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com

Mobile : +9477762

On Mon, Aug 1, 2016 at 7:14 PM, Afkham Azeez  wrote:

> Header field names are case *insensitive*. So I think we have to fix this
> in MSF4J.
>
> *HTTP header* names are *case*-*insensitive*, according to RFC 2616: 4.2:
> Each*header* field consists of a name followed by a colon (":") and the
> field value. Field names are *case*-*insensitive*.
>
> On Tue, Aug 2, 2016 at 4:44 AM, Hemika Kodikara  wrote:
>
>> Hi Nadeeshaan,
>>
>> I faced the same issue with Advanced REST Client, its lowering case for
>> message header keys when sending requests. Message headers must be case
>> sensitive according to spec[1].
>>
>> [1] - https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html
>>
>> Regards,
>> Hemika
>>
>> Hemika Kodikara
>> Software Engineer
>> WSO2 Inc.
>> lean . enterprise . middleware
>> http://wso2.com
>>
>> Mobile : +9477762
>>
>> On Mon, Aug 1, 2016 at 12:32 PM, Rajith Vitharana 
>> wrote:
>>
>>> Hi Nadeeshan,
>>>
>>> As I remember, I also faced some difficulties with sending requests in
>>> latest rest client, for example AFAIR it sends content-type header with GET
>>> requests, these were working fine in earlier REST client implementations,
>>> but seems they are broken in latest somehow.
>>>
>>> Thanks,
>>>
>>> On Mon, Aug 1, 2016 at 10:58 PM, Nadeeshaan Gunasinghe <
>>> nadeesh...@wso2.com> wrote:
>>>
 Hi Azeez, Kasun,

 This works fine with the Post Man and the curl. With the Advanced REST
 Client only this issue occurred. Seems like that client sends the request
 by lowering the case of the headers.

 Thanks,

 *Nadeeshaan Gunasinghe*
 Software Engineer, WSO2 Inc. http://wso2.com
 +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
 <#m_-7154061025406337590_m_8260775494192340682_m_8585129498015183330_m_576071181468296572_>
 
   
   
 Get a signature like this: Click here!
 

 On Mon, Aug 1, 2016 at 10:39 PM, Afkham Azeez  wrote:

> We test with PostMan and it works. No magic here. Just send the proper
> request from whatever the tool.
>
> On Mon, Aug 1, 2016 at 10:20 PM, Nadeeshaan Gunasinghe <
> nadeesh...@wso2.com> wrote:
>
>> Hi Azees, Thusitha,
>>
>> Thanks for the prompt reply. When used the curl in order to invoke
>> the service, it worked fine. The issue could only observe with the 
>> Advanced
>> REST Client used to invoke the service.
>>
>> Thanks,
>>
>> *Nadeeshaan Gunasinghe*
>> Software Engineer, WSO2 Inc. http://wso2.com
>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>> <#m_-7154061025406337590_m_8260775494192340682_m_8585129498015183330_m_576071181468296572_m_-5747302383305428828_m_-7398431186153042768_>
>> 
>> 
>>   
>> Get a signature like this: Click here!
>> 
>>
>> On Mon, Aug 1, 2016 at 10:08 PM, Afkham Azeez  wrote:
>>
>>> Follow the addStock method in this sample:
>>> https://github.com/wso2/msf4j/blob/master/samples/stockquote/fatjar/src/main/java/org/wso2/msf4j/example/StockQuoteService.java#L108
>>>
>>> Then;
>>> curl -v -X POST -H "Content-Type:application/json" -d
>>> '{"symbol":"GOOG","name":"Google Inc.", "high":190.23, "low":187.45}'
>>> http://localhost:8080/stockquote
>>>
>>> On Mon, Aug 1, 2016 at 9:28 PM, Nadeeshaan Gunasinghe <
>>> nadeesh...@wso2.com> wrote:
>>>
 Hi all,

 When I try to execute the following sample [1] service's POST
 operation I could observe the bellow exception.

 *java.lang.IllegalArgumentException: argument type mismatch*
 * at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
 * at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
 * at
 

Re: [Dev] [MSF4J] [2.0.0] Illegal argument Exception Thrown when invoking a POST

[Afkham Azeez]

Header field names are case *insensitive*. So I think we have to fix this
in MSF4J.

*HTTP header* names are *case*-*insensitive*, according to RFC 2616: 4.2:
Each*header* field consists of a name followed by a colon (":") and the
field value. Field names are *case*-*insensitive*.

On Tue, Aug 2, 2016 at 4:44 AM, Hemika Kodikara  wrote:

> Hi Nadeeshaan,
>
> I faced the same issue with Advanced REST Client, its lowering case for
> message header keys when sending requests. Message headers must be case
> sensitive according to spec[1].
>
> [1] - https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html
>
> Regards,
> Hemika
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>
> On Mon, Aug 1, 2016 at 12:32 PM, Rajith Vitharana 
> wrote:
>
>> Hi Nadeeshan,
>>
>> As I remember, I also faced some difficulties with sending requests in
>> latest rest client, for example AFAIR it sends content-type header with GET
>> requests, these were working fine in earlier REST client implementations,
>> but seems they are broken in latest somehow.
>>
>> Thanks,
>>
>> On Mon, Aug 1, 2016 at 10:58 PM, Nadeeshaan Gunasinghe <
>> nadeesh...@wso2.com> wrote:
>>
>>> Hi Azeez, Kasun,
>>>
>>> This works fine with the Post Man and the curl. With the Advanced REST
>>> Client only this issue occurred. Seems like that client sends the request
>>> by lowering the case of the headers.
>>>
>>> Thanks,
>>>
>>> *Nadeeshaan Gunasinghe*
>>> Software Engineer, WSO2 Inc. http://wso2.com
>>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>>> <#m_8260775494192340682_m_8585129498015183330_m_576071181468296572_>
>>> 
>>>   
>>> 
>>> Get a signature like this: Click here!
>>> 
>>>
>>> On Mon, Aug 1, 2016 at 10:39 PM, Afkham Azeez  wrote:
>>>
 We test with PostMan and it works. No magic here. Just send the proper
 request from whatever the tool.

 On Mon, Aug 1, 2016 at 10:20 PM, Nadeeshaan Gunasinghe <
 nadeesh...@wso2.com> wrote:

> Hi Azees, Thusitha,
>
> Thanks for the prompt reply. When used the curl in order to invoke the
> service, it worked fine. The issue could only observe with the Advanced
> REST Client used to invoke the service.
>
> Thanks,
>
> *Nadeeshaan Gunasinghe*
> Software Engineer, WSO2 Inc. http://wso2.com
> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
> <#m_8260775494192340682_m_8585129498015183330_m_576071181468296572_m_-5747302383305428828_m_-7398431186153042768_>
> 
> 
>   
> Get a signature like this: Click here!
> 
>
> On Mon, Aug 1, 2016 at 10:08 PM, Afkham Azeez  wrote:
>
>> Follow the addStock method in this sample:
>> https://github.com/wso2/msf4j/blob/master/samples/stockquote/fatjar/src/main/java/org/wso2/msf4j/example/StockQuoteService.java#L108
>>
>> Then;
>> curl -v -X POST -H "Content-Type:application/json" -d
>> '{"symbol":"GOOG","name":"Google Inc.", "high":190.23, "low":187.45}'
>> http://localhost:8080/stockquote
>>
>> On Mon, Aug 1, 2016 at 9:28 PM, Nadeeshaan Gunasinghe <
>> nadeesh...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> When I try to execute the following sample [1] service's POST
>>> operation I could observe the bellow exception.
>>>
>>> *java.lang.IllegalArgumentException: argument type mismatch*
>>> * at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
>>> * at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
>>> * at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
>>> * at java.lang.reflect.Method.invoke(Method.java:497)*
>>> * at
>>> org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:108)*
>>> * at
>>> org.wso2.msf4j.internal.MSF4JMessageProcessor.dispatchMethod(MSF4JMessageProcessor.java:129)*
>>> * at
>>> 

Re: [Dev] [MSF4J] [2.0.0] Illegal argument Exception Thrown when invoking a POST

[Hemika Kodikara]

Hi Nadeeshaan,

I faced the same issue with Advanced REST Client, its lowering case for
message header keys when sending requests. Message headers must be case
sensitive according to spec[1].

[1] - https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html

Regards,
Hemika

Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com

Mobile : +9477762

On Mon, Aug 1, 2016 at 12:32 PM, Rajith Vitharana  wrote:

> Hi Nadeeshan,
>
> As I remember, I also faced some difficulties with sending requests in
> latest rest client, for example AFAIR it sends content-type header with GET
> requests, these were working fine in earlier REST client implementations,
> but seems they are broken in latest somehow.
>
> Thanks,
>
> On Mon, Aug 1, 2016 at 10:58 PM, Nadeeshaan Gunasinghe <
> nadeesh...@wso2.com> wrote:
>
>> Hi Azeez, Kasun,
>>
>> This works fine with the Post Man and the curl. With the Advanced REST
>> Client only this issue occurred. Seems like that client sends the request
>> by lowering the case of the headers.
>>
>> Thanks,
>>
>> *Nadeeshaan Gunasinghe*
>> Software Engineer, WSO2 Inc. http://wso2.com
>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>> <#m_8585129498015183330_m_576071181468296572_>
>> 
>>   
>> 
>> Get a signature like this: Click here!
>> 
>>
>> On Mon, Aug 1, 2016 at 10:39 PM, Afkham Azeez  wrote:
>>
>>> We test with PostMan and it works. No magic here. Just send the proper
>>> request from whatever the tool.
>>>
>>> On Mon, Aug 1, 2016 at 10:20 PM, Nadeeshaan Gunasinghe <
>>> nadeesh...@wso2.com> wrote:
>>>
 Hi Azees, Thusitha,

 Thanks for the prompt reply. When used the curl in order to invoke the
 service, it worked fine. The issue could only observe with the Advanced
 REST Client used to invoke the service.

 Thanks,

 *Nadeeshaan Gunasinghe*
 Software Engineer, WSO2 Inc. http://wso2.com
 +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
 <#m_8585129498015183330_m_576071181468296572_m_-5747302383305428828_m_-7398431186153042768_>
 
   
   
 Get a signature like this: Click here!
 

 On Mon, Aug 1, 2016 at 10:08 PM, Afkham Azeez  wrote:

> Follow the addStock method in this sample:
> https://github.com/wso2/msf4j/blob/master/samples/stockquote/fatjar/src/main/java/org/wso2/msf4j/example/StockQuoteService.java#L108
>
> Then;
> curl -v -X POST -H "Content-Type:application/json" -d
> '{"symbol":"GOOG","name":"Google Inc.", "high":190.23, "low":187.45}'
> http://localhost:8080/stockquote
>
> On Mon, Aug 1, 2016 at 9:28 PM, Nadeeshaan Gunasinghe <
> nadeesh...@wso2.com> wrote:
>
>> Hi all,
>>
>> When I try to execute the following sample [1] service's POST
>> operation I could observe the bellow exception.
>>
>> *java.lang.IllegalArgumentException: argument type mismatch*
>> * at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
>> * at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
>> * at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
>> * at java.lang.reflect.Method.invoke(Method.java:497)*
>> * at
>> org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:108)*
>> * at
>> org.wso2.msf4j.internal.MSF4JMessageProcessor.dispatchMethod(MSF4JMessageProcessor.java:129)*
>> * at
>> org.wso2.msf4j.internal.MSF4JMessageProcessor.receive(MSF4JMessageProcessor.java:73)*
>> * at
>> org.wso2.carbon.transport.http.netty.listener.WorkerPoolDispatchingSourceHandler$1.run(WorkerPoolDispatchingSourceHandler.java:127)*
>> * 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)*
>>
>> According to the sample service method I am going to capture the 

[Dev] Carbon-mediation 4.6.2 Released

[Jagath Sisirakumara Ariyarathne]

Hi All,

Carbon-mediation 4.6.2 released.

org.wso2.carbon.mediation
carbon-mediation
4.6.2

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

Re: [Dev] [Architecture] [IS] [Analytics] Improvement to use Siddhi streams to send notifications

[Mohanadarshan Vivekanandalingam]

On Mon, Aug 1, 2016 at 8:38 PM, Indunil Upeksha Rathnayake  wrote:

> Hi Suhothayan,
>
> Hi Indunil,

I like to add some comments on this.. Please find them below..


> There was an issue in EventPublisherServiceDS where
> setConfigurationContextService() method get invoked after the bundle get
> activated. Due to that, when we are trying to invoke
> deployEventPublisherConfiguration() of EventPublisherService from the
> activate method of an osgi bundle in IS side, it's receiving a null
> pointer(Since it refers the ConfigurationContextService object in
> EventPublisherServiceValueHolder). I think you can resolve it by changing
> the osgi reference cardinality in [1] as "1..1"(Mandatory), if there is no
> specific reason for making it optional.
>

There is a valid reason for this..
I believe, as you know we cannot guarantee about OSGI bundle loading in
carbon environment.. In this case, there is a possibility where axis2
deployment can start before bundle activation of a OSGI component. To avoid
this we'll follow a similar approach like below,



   org.wso2.carbon.event.publisher.core.EventPublisherService



Here, we are adding the reference of the corresponding OSGI service which
is exposed by relevant OSGI module.. If you want to use above approach
(Axis2RequiredServices), we cannot have 1..1 mapping for
ConfigurationContextService since it causes cyclic dependency and affects
bundle loading..

In IS side we were able to get rid of the null pointer by adding an osgi
> reference for ConfigurationContextService in the service component and
> invoked the deployEventPublisherConfiguration() in activate() method.
>

No, above solution is not correct and will not work all the time.. There is
a possibility where you'll encounter same issue when
ConfigurationContextService is bind to you component first and takes
sometime to resolve for Event Publisher..

What is the usecase for creating an Event Publisher in server restart ? Can
you ship the pack with an Event Publisher or deploy an event publisher for
first event if it is not there..


> And also there was an issue in filling out dynamic properties of an output
> adapter from the arbitrary data values, and sent a PR for that. Please
> review and merge the PR in [2].
>

Thanks, Merged it..

Regards,
Mohan


>
> [1]
> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/org.wso2.carbon.event.publisher.core/src/main/java/org/wso2/carbon/event/publisher/core/internal/ds/EventPublisherServiceDS.java#L56
> [2] https://github.com/wso2/carbon-analytics-common/pull/306/files
>
> Thanks and Regards
>
> On Mon, Aug 1, 2016 at 3:06 PM, Sriskandarajah Suhothayan 
> wrote:
>
>> HI Indunil
>>
>> Any update on this? Was the provided solution working?
>>
>> We released CEP 4.2-RC1. If we need new features/improvements for this
>> effort, we can incorporate them in the next component release.
>>
>> Regards
>> Suho
>>
>> On Fri, Jul 22, 2016 at 3:10 PM, Sriskandarajah Suhothayan > > wrote:
>>
>>>
>>>
>>> On Fri, Jul 22, 2016 at 3:00 PM, Johann Nallathamby 
>>> wrote:
>>>


 On Fri, Jul 22, 2016 at 8:33 AM, Indunil Upeksha Rathnayake <
 indu...@wso2.com> wrote:

> Hi,
>
> On Fri, Jul 22, 2016 at 12:28 PM, Sriskandarajah Suhothayan <
> s...@wso2.com> wrote:
>
>>
>>
>> On Fri, Jul 22, 2016 at 12:00 PM, Indunil Upeksha Rathnayake <
>> indu...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> Please find the meeting notes in [1].  I have following
>>> considerations regarding the improvements we have discussed.
>>>
>>> (1) Even though we have configured to load the email template from
>>> EventPublisher(analytics side), the placeholder values has to be sent as
>>> meta data/correlation data/payload data/arbitrary data, since in 
>>> analytics
>>> side, the user claim values are not getting from the user store.
>>> In order to send the placeholder values from IS side, anyway we have
>>> to load the email template and retrieve the placeholders. So as I have
>>> understood, for email notifications, it's not needed to use the email
>>> template loading part in analytics, since it'll be a redundant task. 
>>> (Refer
>>> [2])
>>>
>>
>> Here we can set the claim values as arbitrary data, and the
>> notification specific details as the meta, correlation & payload data.
>> Then we can use the template loading only at the analytics side.
>>
> In this case, from IS side, without parsing only the user claims
> needed for a particular email template(i.e.user claim values for the
> placeholders in email template), we have to pass all the user claims as
> arbitrary data values. In that case there's no need for loading the
> template from the registry in IS side. So that in analytics side, all the
> values needed for 

Re: [Dev] [MSF4J] [2.0.0] Illegal argument Exception Thrown when invoking a POST

[Rajith Vitharana]

Hi Nadeeshan,

As I remember, I also faced some difficulties with sending requests in
latest rest client, for example AFAIR it sends content-type header with GET
requests, these were working fine in earlier REST client implementations,
but seems they are broken in latest somehow.

Thanks,

On Mon, Aug 1, 2016 at 10:58 PM, Nadeeshaan Gunasinghe 
wrote:

> Hi Azeez, Kasun,
>
> This works fine with the Post Man and the curl. With the Advanced REST
> Client only this issue occurred. Seems like that client sends the request
> by lowering the case of the headers.
>
> Thanks,
>
> *Nadeeshaan Gunasinghe*
> Software Engineer, WSO2 Inc. http://wso2.com
> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
> <#m_576071181468296572_>
> 
>   
> 
> Get a signature like this: Click here!
> 
>
> On Mon, Aug 1, 2016 at 10:39 PM, Afkham Azeez  wrote:
>
>> We test with PostMan and it works. No magic here. Just send the proper
>> request from whatever the tool.
>>
>> On Mon, Aug 1, 2016 at 10:20 PM, Nadeeshaan Gunasinghe <
>> nadeesh...@wso2.com> wrote:
>>
>>> Hi Azees, Thusitha,
>>>
>>> Thanks for the prompt reply. When used the curl in order to invoke the
>>> service, it worked fine. The issue could only observe with the Advanced
>>> REST Client used to invoke the service.
>>>
>>> Thanks,
>>>
>>> *Nadeeshaan Gunasinghe*
>>> Software Engineer, WSO2 Inc. http://wso2.com
>>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>>> <#m_576071181468296572_m_-5747302383305428828_m_-7398431186153042768_>
>>> 
>>>   
>>> 
>>> Get a signature like this: Click here!
>>> 
>>>
>>> On Mon, Aug 1, 2016 at 10:08 PM, Afkham Azeez  wrote:
>>>
 Follow the addStock method in this sample:
 https://github.com/wso2/msf4j/blob/master/samples/stockquote/fatjar/src/main/java/org/wso2/msf4j/example/StockQuoteService.java#L108

 Then;
 curl -v -X POST -H "Content-Type:application/json" -d
 '{"symbol":"GOOG","name":"Google Inc.", "high":190.23, "low":187.45}'
 http://localhost:8080/stockquote

 On Mon, Aug 1, 2016 at 9:28 PM, Nadeeshaan Gunasinghe <
 nadeesh...@wso2.com> wrote:

> Hi all,
>
> When I try to execute the following sample [1] service's POST
> operation I could observe the bellow exception.
>
> *java.lang.IllegalArgumentException: argument type mismatch*
> * at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
> * at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
> * at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
> * at java.lang.reflect.Method.invoke(Method.java:497)*
> * at
> org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:108)*
> * at
> org.wso2.msf4j.internal.MSF4JMessageProcessor.dispatchMethod(MSF4JMessageProcessor.java:129)*
> * at
> org.wso2.msf4j.internal.MSF4JMessageProcessor.receive(MSF4JMessageProcessor.java:73)*
> * at
> org.wso2.carbon.transport.http.netty.listener.WorkerPoolDispatchingSourceHandler$1.run(WorkerPoolDispatchingSourceHandler.java:127)*
> * 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)*
>
> According to the sample service method I am going to capture the json
> payload as an object passed to the method as follows.
>
> @POST
> @Path("/test")
> public Response post(TestPayload testPayloadBody) {
> // TODO: Implementation for HTTP POST request
> System.out.println("POST invoked == " +testPayloadBody);
> return Response.ok().entity(testPayloadBody).build();
> }
>
>
> After further debugging the code, could find that the arguments list
> passed at [2] contains a string. But according to the implementation it
> should be a *TestPayload *object. If we observe at [3] the headers
> Map's keys 

Re: [Dev] [MSF4J] [2.0.0] Illegal argument Exception Thrown when invoking a POST

[Nadeeshaan Gunasinghe]

Hi Azeez, Kasun,

This works fine with the Post Man and the curl. With the Advanced REST
Client only this issue occurred. Seems like that client sends the request
by lowering the case of the headers.

Thanks,

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

  

Get a signature like this: Click here!


On Mon, Aug 1, 2016 at 10:39 PM, Afkham Azeez  wrote:

> We test with PostMan and it works. No magic here. Just send the proper
> request from whatever the tool.
>
> On Mon, Aug 1, 2016 at 10:20 PM, Nadeeshaan Gunasinghe <
> nadeesh...@wso2.com> wrote:
>
>> Hi Azees, Thusitha,
>>
>> Thanks for the prompt reply. When used the curl in order to invoke the
>> service, it worked fine. The issue could only observe with the Advanced
>> REST Client used to invoke the service.
>>
>> Thanks,
>>
>> *Nadeeshaan Gunasinghe*
>> Software Engineer, WSO2 Inc. http://wso2.com
>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>> <#m_-5747302383305428828_m_-7398431186153042768_>
>> 
>>   
>> 
>> Get a signature like this: Click here!
>> 
>>
>> On Mon, Aug 1, 2016 at 10:08 PM, Afkham Azeez  wrote:
>>
>>> Follow the addStock method in this sample:
>>> https://github.com/wso2/msf4j/blob/master/samples/stockquote/fatjar/src/main/java/org/wso2/msf4j/example/StockQuoteService.java#L108
>>>
>>> Then;
>>> curl -v -X POST -H "Content-Type:application/json" -d
>>> '{"symbol":"GOOG","name":"Google Inc.", "high":190.23, "low":187.45}'
>>> http://localhost:8080/stockquote
>>>
>>> On Mon, Aug 1, 2016 at 9:28 PM, Nadeeshaan Gunasinghe <
>>> nadeesh...@wso2.com> wrote:
>>>
 Hi all,

 When I try to execute the following sample [1] service's POST operation
 I could observe the bellow exception.

 *java.lang.IllegalArgumentException: argument type mismatch*
 * at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
 * at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
 * at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
 * at java.lang.reflect.Method.invoke(Method.java:497)*
 * at
 org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:108)*
 * at
 org.wso2.msf4j.internal.MSF4JMessageProcessor.dispatchMethod(MSF4JMessageProcessor.java:129)*
 * at
 org.wso2.msf4j.internal.MSF4JMessageProcessor.receive(MSF4JMessageProcessor.java:73)*
 * at
 org.wso2.carbon.transport.http.netty.listener.WorkerPoolDispatchingSourceHandler$1.run(WorkerPoolDispatchingSourceHandler.java:127)*
 * 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)*

 According to the sample service method I am going to capture the json
 payload as an object passed to the method as follows.

 @POST
 @Path("/test")
 public Response post(TestPayload testPayloadBody) {
 // TODO: Implementation for HTTP POST request
 System.out.println("POST invoked == " +testPayloadBody);
 return Response.ok().entity(testPayloadBody).build();
 }


 After further debugging the code, could find that the arguments list
 passed at [2] contains a string. But according to the implementation it
 should be a *TestPayload *object. If we observe at [3] the headers
 Map's keys are all in lowercase. In order to get the header from the map,
 we use the constant from* javax.ws.rs.core.Headers, *there the
 CONTENT_TYPE constant is not in all lowercase and Due to this reason 
 *contentTypeHeaderStr
 *becomes null and leads to convert the object to a String by the
 default text formatter, based on the wild card content-type [4].

 [1]
 https://drive.google.com/a/wso2.com/folderview?id=0Bx7aKS6MDJqSVDhVSTdWZ1JBVGc=sharing
 [2]
 

Re: [Dev] [VOTE] Release WSO2 Mesos Artifacts 1.0.0 RC1

[Tharindu Dharmarathna]

Tested the APIM Standalone and Distributed Deployment.

[x] - Stable, go ahead and release


On Mon, Aug 1, 2016 at 5:11 PM, Akila Ravihansa Perera 
wrote:

> Verified the following:
>
>  - License headers using RAT plugin
>  - Checked distribution structure
>  - Tested wso2bps 3.5.1 distributed deployment
>  - Tested wso2am with IS as KM pattern
>
> [x] - Stable, go ahead and release
>
>
>
> On Mon, Aug 1, 2016 at 5:03 PM, Isuru Haththotuwa  wrote:
>
>> Verified the following:
>>
>>1. License headers using RAT plugin
>>2. Tested the following on mesos:
>>- wso2am 1.10.0 - standalone and distributed deployments
>>   - wso2das 3.0.1 - standalone and distributed deployments
>>   - wso2cep 4.0.0 - standalone deployment with a smoke test
>>
>> *[x] - Stable, go ahead and release*
>>
>> On Tue, Jul 26, 2016 at 11:28 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the first release candidate (RC1) of WSO2 Mesos Artifacts 1.0.0.
>>>
>>> Please download, test and vote. Please refer the README files under each
>>> product for details on testing the artifacts.
>>>
>>> Source & binary distribution files:
>>> https://github.com/wso2/mesos-artifacts/releases/tag/v1.0.0-rc1
>>>
>>> Maven staging repo:
>>>
>>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbonmesosartifacts-1000/
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/mesos-artifacts/releases/tag/v1.0.0-rc1
>>>
>>> Mesos Artifacts Documentation:
>>> https://docs.wso2.com/display/MA100/Home
>>>
>>> This vote will be open for 72 hours or as needed.
>>>
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>>
>>> Regards,
>>> WSO2 PaaS team
>>>
>>> --
>>> *Pubudu Gunatilaka*
>>> Committer and PMC Member - Apache Stratos
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> mobile : +94774078049 <%2B94772207163>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>




-- 


*Tharindu Dharmarathna*Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] [MSF4J] [2.0.0] Illegal argument Exception Thrown when invoking a POST

[Afkham Azeez]

We test with PostMan and it works. No magic here. Just send the proper
request from whatever the tool.

On Mon, Aug 1, 2016 at 10:20 PM, Nadeeshaan Gunasinghe 
wrote:

> Hi Azees, Thusitha,
>
> Thanks for the prompt reply. When used the curl in order to invoke the
> service, it worked fine. The issue could only observe with the Advanced
> REST Client used to invoke the service.
>
> Thanks,
>
> *Nadeeshaan Gunasinghe*
> Software Engineer, WSO2 Inc. http://wso2.com
> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
> <#m_-7398431186153042768_>
> 
>   
> 
> Get a signature like this: Click here!
> 
>
> On Mon, Aug 1, 2016 at 10:08 PM, Afkham Azeez  wrote:
>
>> Follow the addStock method in this sample:
>> https://github.com/wso2/msf4j/blob/master/samples/stockquote/fatjar/src/main/java/org/wso2/msf4j/example/StockQuoteService.java#L108
>>
>> Then;
>> curl -v -X POST -H "Content-Type:application/json" -d
>> '{"symbol":"GOOG","name":"Google Inc.", "high":190.23, "low":187.45}'
>> http://localhost:8080/stockquote
>>
>> On Mon, Aug 1, 2016 at 9:28 PM, Nadeeshaan Gunasinghe <
>> nadeesh...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> When I try to execute the following sample [1] service's POST operation
>>> I could observe the bellow exception.
>>>
>>> *java.lang.IllegalArgumentException: argument type mismatch*
>>> * at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
>>> * at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
>>> * at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
>>> * at java.lang.reflect.Method.invoke(Method.java:497)*
>>> * at
>>> org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:108)*
>>> * at
>>> org.wso2.msf4j.internal.MSF4JMessageProcessor.dispatchMethod(MSF4JMessageProcessor.java:129)*
>>> * at
>>> org.wso2.msf4j.internal.MSF4JMessageProcessor.receive(MSF4JMessageProcessor.java:73)*
>>> * at
>>> org.wso2.carbon.transport.http.netty.listener.WorkerPoolDispatchingSourceHandler$1.run(WorkerPoolDispatchingSourceHandler.java:127)*
>>> * 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)*
>>>
>>> According to the sample service method I am going to capture the json
>>> payload as an object passed to the method as follows.
>>>
>>> @POST
>>> @Path("/test")
>>> public Response post(TestPayload testPayloadBody) {
>>> // TODO: Implementation for HTTP POST request
>>> System.out.println("POST invoked == " +testPayloadBody);
>>> return Response.ok().entity(testPayloadBody).build();
>>> }
>>>
>>>
>>> After further debugging the code, could find that the arguments list
>>> passed at [2] contains a string. But according to the implementation it
>>> should be a *TestPayload *object. If we observe at [3] the headers
>>> Map's keys are all in lowercase. In order to get the header from the map,
>>> we use the constant from* javax.ws.rs.core.Headers, *there the
>>> CONTENT_TYPE constant is not in all lowercase and Due to this reason 
>>> *contentTypeHeaderStr
>>> *becomes null and leads to convert the object to a String by the
>>> default text formatter, based on the wild card content-type [4].
>>>
>>> [1]
>>> https://drive.google.com/a/wso2.com/folderview?id=0Bx7aKS6MDJqSVDhVSTdWZ1JBVGc=sharing
>>> [2]
>>> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/router/HttpMethodInfo.java#L108
>>> [3]
>>> https://github.com/wso2/carbon-messaging/blob/master/components/src/main/java/org/wso2/carbon/messaging/CarbonMessage.java#L162
>>> [4]
>>> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/router/HttpResourceModelProcessor.java#L158
>>>
>>> Thanks,
>>>
>>> *Nadeeshaan Gunasinghe*
>>> Software Engineer, WSO2 Inc. http://wso2.com
>>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>>> <#m_-7398431186153042768_m_1214838822956125518_m_-746156207640328338_>
>>> 
>>>   
>>> 
>>> Get a signature like this: Click here!
>>> 

Re: [Dev] [MSF4J] [2.0.0] Illegal argument Exception Thrown when invoking a POST

[Kasun Indrasiri]

On Mon, Aug 1, 2016 at 9:50 AM, Nadeeshaan Gunasinghe 
wrote:

> Hi Azees, Thusitha,
>
> Thanks for the prompt reply. When used the curl in order to invoke the
> service, it worked fine. The issue could only observe with the Advanced
> REST Client used to invoke the service.
>
> Did you check the wire message and see what's the difference between two
requests?

> Thanks,
>
> *Nadeeshaan Gunasinghe*
> Software Engineer, WSO2 Inc. http://wso2.com
> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
> <#m_-2811221931977088442_>
> 
>   
> 
> Get a signature like this: Click here!
> 
>
> On Mon, Aug 1, 2016 at 10:08 PM, Afkham Azeez  wrote:
>
>> Follow the addStock method in this sample:
>> https://github.com/wso2/msf4j/blob/master/samples/stockquote/fatjar/src/main/java/org/wso2/msf4j/example/StockQuoteService.java#L108
>>
>> Then;
>> curl -v -X POST -H "Content-Type:application/json" -d
>> '{"symbol":"GOOG","name":"Google Inc.", "high":190.23, "low":187.45}'
>> http://localhost:8080/stockquote
>>
>> On Mon, Aug 1, 2016 at 9:28 PM, Nadeeshaan Gunasinghe <
>> nadeesh...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> When I try to execute the following sample [1] service's POST operation
>>> I could observe the bellow exception.
>>>
>>> *java.lang.IllegalArgumentException: argument type mismatch*
>>> * at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
>>> * at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
>>> * at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
>>> * at java.lang.reflect.Method.invoke(Method.java:497)*
>>> * at
>>> org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:108)*
>>> * at
>>> org.wso2.msf4j.internal.MSF4JMessageProcessor.dispatchMethod(MSF4JMessageProcessor.java:129)*
>>> * at
>>> org.wso2.msf4j.internal.MSF4JMessageProcessor.receive(MSF4JMessageProcessor.java:73)*
>>> * at
>>> org.wso2.carbon.transport.http.netty.listener.WorkerPoolDispatchingSourceHandler$1.run(WorkerPoolDispatchingSourceHandler.java:127)*
>>> * 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)*
>>>
>>> According to the sample service method I am going to capture the json
>>> payload as an object passed to the method as follows.
>>>
>>> @POST
>>> @Path("/test")
>>> public Response post(TestPayload testPayloadBody) {
>>> // TODO: Implementation for HTTP POST request
>>> System.out.println("POST invoked == " +testPayloadBody);
>>> return Response.ok().entity(testPayloadBody).build();
>>> }
>>>
>>>
>>> After further debugging the code, could find that the arguments list
>>> passed at [2] contains a string. But according to the implementation it
>>> should be a *TestPayload *object. If we observe at [3] the headers
>>> Map's keys are all in lowercase. In order to get the header from the map,
>>> we use the constant from* javax.ws.rs.core.Headers, *there the
>>> CONTENT_TYPE constant is not in all lowercase and Due to this reason 
>>> *contentTypeHeaderStr
>>> *becomes null and leads to convert the object to a String by the
>>> default text formatter, based on the wild card content-type [4].
>>>
>>> [1]
>>> https://drive.google.com/a/wso2.com/folderview?id=0Bx7aKS6MDJqSVDhVSTdWZ1JBVGc=sharing
>>> [2]
>>> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/router/HttpMethodInfo.java#L108
>>> [3]
>>> https://github.com/wso2/carbon-messaging/blob/master/components/src/main/java/org/wso2/carbon/messaging/CarbonMessage.java#L162
>>> [4]
>>> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/router/HttpResourceModelProcessor.java#L158
>>>
>>> Thanks,
>>>
>>> *Nadeeshaan Gunasinghe*
>>> Software Engineer, WSO2 Inc. http://wso2.com
>>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>>> <#m_-2811221931977088442_m_1214838822956125518_m_-746156207640328338_>
>>> 
>>>   
>>> 
>>> Get a signature like this: Click here!
>>> 

Re: [Dev] [MSF4J] [2.0.0] Illegal argument Exception Thrown when invoking a POST

[Nadeeshaan Gunasinghe]

Hi Azees, Thusitha,

Thanks for the prompt reply. When used the curl in order to invoke the
service, it worked fine. The issue could only observe with the Advanced
REST Client used to invoke the service.

Thanks,

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

  

Get a signature like this: Click here!


On Mon, Aug 1, 2016 at 10:08 PM, Afkham Azeez  wrote:

> Follow the addStock method in this sample:
> https://github.com/wso2/msf4j/blob/master/samples/stockquote/fatjar/src/main/java/org/wso2/msf4j/example/StockQuoteService.java#L108
>
> Then;
> curl -v -X POST -H "Content-Type:application/json" -d
> '{"symbol":"GOOG","name":"Google Inc.", "high":190.23, "low":187.45}'
> http://localhost:8080/stockquote
>
> On Mon, Aug 1, 2016 at 9:28 PM, Nadeeshaan Gunasinghe  > wrote:
>
>> Hi all,
>>
>> When I try to execute the following sample [1] service's POST operation I
>> could observe the bellow exception.
>>
>> *java.lang.IllegalArgumentException: argument type mismatch*
>> * at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
>> * at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
>> * at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
>> * at java.lang.reflect.Method.invoke(Method.java:497)*
>> * at
>> org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:108)*
>> * at
>> org.wso2.msf4j.internal.MSF4JMessageProcessor.dispatchMethod(MSF4JMessageProcessor.java:129)*
>> * at
>> org.wso2.msf4j.internal.MSF4JMessageProcessor.receive(MSF4JMessageProcessor.java:73)*
>> * at
>> org.wso2.carbon.transport.http.netty.listener.WorkerPoolDispatchingSourceHandler$1.run(WorkerPoolDispatchingSourceHandler.java:127)*
>> * 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)*
>>
>> According to the sample service method I am going to capture the json
>> payload as an object passed to the method as follows.
>>
>> @POST
>> @Path("/test")
>> public Response post(TestPayload testPayloadBody) {
>> // TODO: Implementation for HTTP POST request
>> System.out.println("POST invoked == " +testPayloadBody);
>> return Response.ok().entity(testPayloadBody).build();
>> }
>>
>>
>> After further debugging the code, could find that the arguments list
>> passed at [2] contains a string. But according to the implementation it
>> should be a *TestPayload *object. If we observe at [3] the headers Map's
>> keys are all in lowercase. In order to get the header from the map, we use
>> the constant from* javax.ws.rs.core.Headers, *there the CONTENT_TYPE
>> constant is not in all lowercase and Due to this reason *contentTypeHeaderStr
>> *becomes null and leads to convert the object to a String by the default
>> text formatter, based on the wild card content-type [4].
>>
>> [1]
>> https://drive.google.com/a/wso2.com/folderview?id=0Bx7aKS6MDJqSVDhVSTdWZ1JBVGc=sharing
>> [2]
>> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/router/HttpMethodInfo.java#L108
>> [3]
>> https://github.com/wso2/carbon-messaging/blob/master/components/src/main/java/org/wso2/carbon/messaging/CarbonMessage.java#L162
>> [4]
>> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/router/HttpResourceModelProcessor.java#L158
>>
>> Thanks,
>>
>> *Nadeeshaan Gunasinghe*
>> Software Engineer, WSO2 Inc. http://wso2.com
>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>> <#m_1214838822956125518_m_-746156207640328338_>
>> 
>>   
>> 
>> Get a signature like this: Click here!
>> 
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 

Re: [Dev] [MSF4J] [2.0.0] Illegal argument Exception Thrown when invoking a POST

[Afkham Azeez]

Follow the addStock method in this sample:
https://github.com/wso2/msf4j/blob/master/samples/stockquote/fatjar/src/main/java/org/wso2/msf4j/example/StockQuoteService.java#L108

Then;
curl -v -X POST -H "Content-Type:application/json" -d
'{"symbol":"GOOG","name":"Google Inc.", "high":190.23, "low":187.45}'
http://localhost:8080/stockquote

On Mon, Aug 1, 2016 at 9:28 PM, Nadeeshaan Gunasinghe 
wrote:

> Hi all,
>
> When I try to execute the following sample [1] service's POST operation I
> could observe the bellow exception.
>
> *java.lang.IllegalArgumentException: argument type mismatch*
> * at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
> * at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
> * at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
> * at java.lang.reflect.Method.invoke(Method.java:497)*
> * at
> org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:108)*
> * at
> org.wso2.msf4j.internal.MSF4JMessageProcessor.dispatchMethod(MSF4JMessageProcessor.java:129)*
> * at
> org.wso2.msf4j.internal.MSF4JMessageProcessor.receive(MSF4JMessageProcessor.java:73)*
> * at
> org.wso2.carbon.transport.http.netty.listener.WorkerPoolDispatchingSourceHandler$1.run(WorkerPoolDispatchingSourceHandler.java:127)*
> * 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)*
>
> According to the sample service method I am going to capture the json
> payload as an object passed to the method as follows.
>
> @POST
> @Path("/test")
> public Response post(TestPayload testPayloadBody) {
> // TODO: Implementation for HTTP POST request
> System.out.println("POST invoked == " +testPayloadBody);
> return Response.ok().entity(testPayloadBody).build();
> }
>
>
> After further debugging the code, could find that the arguments list
> passed at [2] contains a string. But according to the implementation it
> should be a *TestPayload *object. If we observe at [3] the headers Map's
> keys are all in lowercase. In order to get the header from the map, we use
> the constant from* javax.ws.rs.core.Headers, *there the CONTENT_TYPE
> constant is not in all lowercase and Due to this reason *contentTypeHeaderStr
> *becomes null and leads to convert the object to a String by the default
> text formatter, based on the wild card content-type [4].
>
> [1]
> https://drive.google.com/a/wso2.com/folderview?id=0Bx7aKS6MDJqSVDhVSTdWZ1JBVGc=sharing
> [2]
> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/router/HttpMethodInfo.java#L108
> [3]
> https://github.com/wso2/carbon-messaging/blob/master/components/src/main/java/org/wso2/carbon/messaging/CarbonMessage.java#L162
> [4]
> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/router/HttpResourceModelProcessor.java#L158
>
> Thanks,
>
> *Nadeeshaan Gunasinghe*
> Software Engineer, WSO2 Inc. http://wso2.com
> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
> <#m_-746156207640328338_>
> 
>   
> 
> Get a signature like this: Click here!
> 
>



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

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

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

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

[Dev] [MSF4J] [2.0.0] Illegal argument Exception Thrown when invoking a POST

[Nadeeshaan Gunasinghe]

Hi all,

When I try to execute the following sample [1] service's POST operation I
could observe the bellow exception.

*java.lang.IllegalArgumentException: argument type mismatch*
* at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
* at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
* at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
* at java.lang.reflect.Method.invoke(Method.java:497)*
* at
org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:108)*
* at
org.wso2.msf4j.internal.MSF4JMessageProcessor.dispatchMethod(MSF4JMessageProcessor.java:129)*
* at
org.wso2.msf4j.internal.MSF4JMessageProcessor.receive(MSF4JMessageProcessor.java:73)*
* at
org.wso2.carbon.transport.http.netty.listener.WorkerPoolDispatchingSourceHandler$1.run(WorkerPoolDispatchingSourceHandler.java:127)*
* 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)*

According to the sample service method I am going to capture the json
payload as an object passed to the method as follows.

@POST
@Path("/test")
public Response post(TestPayload testPayloadBody) {
// TODO: Implementation for HTTP POST request
System.out.println("POST invoked == " +testPayloadBody);
return Response.ok().entity(testPayloadBody).build();
}


After further debugging the code, could find that the arguments list passed
at [2] contains a string. But according to the implementation it should be
a *TestPayload *object. If we observe at [3] the headers Map's keys are all
in lowercase. In order to get the header from the map, we use the constant
from* javax.ws.rs.core.Headers, *there the CONTENT_TYPE constant is not in
all lowercase and Due to this reason *contentTypeHeaderStr *becomes null
and leads to convert the object to a String by the default text formatter,
based on the wild card content-type [4].

[1]
https://drive.google.com/a/wso2.com/folderview?id=0Bx7aKS6MDJqSVDhVSTdWZ1JBVGc=sharing
[2]
https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/router/HttpMethodInfo.java#L108
[3]
https://github.com/wso2/carbon-messaging/blob/master/components/src/main/java/org/wso2/carbon/messaging/CarbonMessage.java#L162
[4]
https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/router/HttpResourceModelProcessor.java#L158

Thanks,

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

  

Get a signature like this: Click here!

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

Re: [Dev] [MSF4J] [2.0.0] Illegal argument Exception Thrown when invoking a POST

[Thusitha Thilina Dayaratne]

Hi Nadeeshan,

Can you share a sample request that you used to invoke the service?
IMHO if the Content-Type header is available in your request this should
work.

Thanks
Thusitha

On Mon, Aug 1, 2016 at 9:28 PM, Nadeeshaan Gunasinghe 
wrote:

> Hi all,
>
> When I try to execute the following sample [1] service's POST operation I
> could observe the bellow exception.
>
> *java.lang.IllegalArgumentException: argument type mismatch*
> * at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
> * at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
> * at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
> * at java.lang.reflect.Method.invoke(Method.java:497)*
> * at
> org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:108)*
> * at
> org.wso2.msf4j.internal.MSF4JMessageProcessor.dispatchMethod(MSF4JMessageProcessor.java:129)*
> * at
> org.wso2.msf4j.internal.MSF4JMessageProcessor.receive(MSF4JMessageProcessor.java:73)*
> * at
> org.wso2.carbon.transport.http.netty.listener.WorkerPoolDispatchingSourceHandler$1.run(WorkerPoolDispatchingSourceHandler.java:127)*
> * 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)*
>
> According to the sample service method I am going to capture the json
> payload as an object passed to the method as follows.
>
> @POST
> @Path("/test")
> public Response post(TestPayload testPayloadBody) {
> // TODO: Implementation for HTTP POST request
> System.out.println("POST invoked == " +testPayloadBody);
> return Response.ok().entity(testPayloadBody).build();
> }
>
>
> After further debugging the code, could find that the arguments list
> passed at [2] contains a string. But according to the implementation it
> should be a *TestPayload *object. If we observe at [3] the headers Map's
> keys are all in lowercase. In order to get the header from the map, we use
> the constant from* javax.ws.rs.core.Headers, *there the CONTENT_TYPE
> constant is not in all lowercase and Due to this reason *contentTypeHeaderStr
> *becomes null and leads to convert the object to a String by the default
> text formatter, based on the wild card content-type [4].
>
> [1]
> https://drive.google.com/a/wso2.com/folderview?id=0Bx7aKS6MDJqSVDhVSTdWZ1JBVGc=sharing
> [2]
> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/router/HttpMethodInfo.java#L108
> [3]
> https://github.com/wso2/carbon-messaging/blob/master/components/src/main/java/org/wso2/carbon/messaging/CarbonMessage.java#L162
> [4]
> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/router/HttpResourceModelProcessor.java#L158
>
> Thanks,
>
> *Nadeeshaan Gunasinghe*
> Software Engineer, WSO2 Inc. http://wso2.com
> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
> <#m_4111866504169707809_>
> 
>   
> 
> Get a signature like this: Click here!
> 
>



-- 
Thusitha Dayaratne
Software Engineer
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

Mobile  +94712756809
Blog  alokayasoya.blogspot.com
Abouthttp://about.me/thusithathilina

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

Re: [Dev] [Architecture] [IS] [Analytics] Improvement to use Siddhi streams to send notifications

[Indunil Upeksha Rathnayake]

Hi Suhothayan,

There was an issue in EventPublisherServiceDS where
setConfigurationContextService() method get invoked after the bundle get
activated. Due to that, when we are trying to invoke
deployEventPublisherConfiguration() of EventPublisherService from the
activate method of an osgi bundle in IS side, it's receiving a null
pointer(Since it refers the ConfigurationContextService object in
EventPublisherServiceValueHolder). I think you can resolve it by changing
the osgi reference cardinality in [1] as "1..1"(Mandatory), if there is no
specific reason for making it optional.
In IS side we were able to get rid of the null pointer by adding an osgi
reference for ConfigurationContextService in the service component and
invoked the deployEventPublisherConfiguration() in activate() method.

And also there was an issue in filling out dynamic properties of an output
adapter from the arbitrary data values, and sent a PR for that. Please
review and merge the PR in [2].

[1]
https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/org.wso2.carbon.event.publisher.core/src/main/java/org/wso2/carbon/event/publisher/core/internal/ds/EventPublisherServiceDS.java#L56
[2] https://github.com/wso2/carbon-analytics-common/pull/306/files

Thanks and Regards

On Mon, Aug 1, 2016 at 3:06 PM, Sriskandarajah Suhothayan 
wrote:

> HI Indunil
>
> Any update on this? Was the provided solution working?
>
> We released CEP 4.2-RC1. If we need new features/improvements for this
> effort, we can incorporate them in the next component release.
>
> Regards
> Suho
>
> On Fri, Jul 22, 2016 at 3:10 PM, Sriskandarajah Suhothayan 
> wrote:
>
>>
>>
>> On Fri, Jul 22, 2016 at 3:00 PM, Johann Nallathamby 
>> wrote:
>>
>>>
>>>
>>> On Fri, Jul 22, 2016 at 8:33 AM, Indunil Upeksha Rathnayake <
>>> indu...@wso2.com> wrote:
>>>
 Hi,

 On Fri, Jul 22, 2016 at 12:28 PM, Sriskandarajah Suhothayan <
 s...@wso2.com> wrote:

>
>
> On Fri, Jul 22, 2016 at 12:00 PM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>>
>> Please find the meeting notes in [1].  I have following
>> considerations regarding the improvements we have discussed.
>>
>> (1) Even though we have configured to load the email template from
>> EventPublisher(analytics side), the placeholder values has to be sent as
>> meta data/correlation data/payload data/arbitrary data, since in 
>> analytics
>> side, the user claim values are not getting from the user store.
>> In order to send the placeholder values from IS side, anyway we have
>> to load the email template and retrieve the placeholders. So as I have
>> understood, for email notifications, it's not needed to use the email
>> template loading part in analytics, since it'll be a redundant task. 
>> (Refer
>> [2])
>>
>
> Here we can set the claim values as arbitrary data, and the
> notification specific details as the meta, correlation & payload data.
> Then we can use the template loading only at the analytics side.
>
 In this case, from IS side, without parsing only the user claims needed
 for a particular email template(i.e.user claim values for the placeholders
 in email template), we have to pass all the user claims as arbitrary data
 values. In that case there's no need for loading the template from the
 registry in IS side. So that in analytics side, all the values needed for
 filling out the template will be there. Will check on that.

>>>
>>> I don't think it will be a good solution. There can be sensitive
>>> information in the claims which we can't send. So for this release it's OK
>>> if we read the template in both sides - security is more important than
>>> performance; or read it only in IS side - but additionally send all those
>>> claims as arbitrary data as well, so if some one wants can use them in CEP
>>> side by their output adaptors.
>>>
>>
>> I think then we can have a common configuration in IS side to specify
>> what are the claims that should be added to notifications.
>>
>> Regards
>> Suho
>>
>>
>>>
>>>
>
>> (2) The email templates has to be changed as follows.
>> i) if the value will be provided in an arbitrary data map, the
>> placeholder should be with a prefix "arbitrary_"
>> (ex:{{arbitrary_givenname}})
>>
> ii) if the value will be provided in an meta data map, the
>> placeholder should be changed as {{...}} (ex:{{givenname}})
>>
>> No we should not use "arbitrary_" for any cases, its internal
> information and the names should not have "arbitrary_" even if its in
> arbitrary data map or otherwise.
>
> (3) Only Text OutputMapping Content can be filled from a value in an
>> arbitrary data map using prefix "arbitrary_" .  It's not possible to use 
>> a
>> value of an arbitrary data 

Re: [Dev] [ESB] Error log continuously printing in the carbon log

[Gayan Gunarathne]

Hi Chanaka,

I used this documentation[1]. For the FileURI only changed to the sftps.
Thing is file moving correctly. But continuously see the above log in the
carbon console.

sftp://:@

[1]https://docs.wso2.com/display/ESB500/File+Inbound+Protocol

Thanks,
Gayan

On Sat, Jul 30, 2016 at 12:00 AM, Chanaka Fernando 
wrote:

> Hi Gayan,
>
> Can you share the configuration you have used?
>
> On Sat, Jul 30, 2016 at 12:52 AM, Gayan Gunarathne 
> wrote:
>
>> We have used the ESB 5.0.0 beta2 release and configured file inbound
>> endpoint with sftp.
>> File moving happen correctly but found following logs print in the carbon
>> log continuously. Why is that happening?
>>
>> TID: [-1234] [] [2016-07-29 15:11:21,977] ERROR
>> {org.wso2.carbon.inbound.endpoint.protocol.file.FilePollingConsumer} -
>>  Unable to close the file system. null
>> {org.wso2.carbon.inbound.endpoint.protocol.file.FilePollingConsumer}
>> TID: [-1234] [] [2016-07-29 15:11:21,977] ERROR
>> {org.wso2.carbon.inbound.endpoint.protocol.file.FilePollingConsumer} -
>>  java.lang.NullPointerException
>> {org.wso2.carbon.inbound.endpoint.protocol.file.FilePollingConsumer}
>>
>> Thanks,
>> Gayan
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead, WSO2 Inc. (http://wso2.com)
>> Committer & PMC Member, Apache Stratos
>> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>>
>>
>>
>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> m: +94 773337238
> https://wso2.com 
>
>
>
>
>
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Synapse-2.1.7-wso2v4 Released

[Nadeeshaan Gunasinghe]

Hi all,

Please note $subject.

org.apache.synapse
Apache-Synapse
2.1.7-wso2v4

Thanks,

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

  

Get a signature like this: Click here!

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

[Dev] Axis2 Transport 1.1.1-wso2v5 Released

[Jagath Sisirakumara Ariyarathne]

Hi All,

Axis2 Transport version 1.1.1-wso2v5 Released.

org.apache.axis2.transport
axis2-transports
1.1.1-wso2v5


Thanks.

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

Re: [Dev] [VOTE] Release WSO2 Machine Learner 1.1.1 RC1

[Supun Sethunga]

[-]  Calling off the vote as we have encountered some issues with the ml ui
jaggery app. url mappings are broken. We will start a new vote soon.

Regards,
Supun

On Sat, Jul 30, 2016 at 8:30 AM, Supun Sethunga  wrote:

> Hi Devs,
>
> This is the 1st Release Candidate of the WSO2 Machine Learner 1.1.1. This
> is a patch release and following main fixes were included:
>
>- ML-DAS integration
>- Security fixes associated with the WSO2 Carbon 4.4.7 platform release
>
>
> Please download, test the product and vote. Vote will be open for 72 hours
> or as needed.
> Refer to github readme for guides.
>
> The distribution is available to download at [1].
>
> Fixed Issue in [2]. Tag to be vote upon [3].
>
> [1]
> https://github.com/wso2/product-ml/releases/download/v1.1.1-rc1/wso2ml-1.1.1-rc1.zip
>
> [2] https://wso2.org/jira/issues/?filter=13175
> [3] *https://github.com/wso2/product-ml/releases/tag/v1.1.1-rc1
> *
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> Thanks,
> WSO2 ML Team
>
> --
> *Supun Sethunga*
> Senior Software Engineer
> WSO2, Inc.
> http://wso2.com/
> lean | enterprise | middleware
> Mobile : +94 716546324
> Blog: http://supunsetunga.blogspot.com
>



-- 
*Supun Sethunga*
Senior Software Engineer
WSO2, Inc.
http://wso2.com/
lean | enterprise | middleware
Mobile : +94 716546324
Blog: http://supunsetunga.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Mesos Artifacts 1.0.0 RC1

[Akila Ravihansa Perera]

Verified the following:

 - License headers using RAT plugin
 - Checked distribution structure
 - Tested wso2bps 3.5.1 distributed deployment
 - Tested wso2am with IS as KM pattern

[x] - Stable, go ahead and release



On Mon, Aug 1, 2016 at 5:03 PM, Isuru Haththotuwa  wrote:

> Verified the following:
>
>1. License headers using RAT plugin
>2. Tested the following on mesos:
>- wso2am 1.10.0 - standalone and distributed deployments
>   - wso2das 3.0.1 - standalone and distributed deployments
>   - wso2cep 4.0.0 - standalone deployment with a smoke test
>
> *[x] - Stable, go ahead and release*
>
> On Tue, Jul 26, 2016 at 11:28 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Devs,
>>
>> This is the first release candidate (RC1) of WSO2 Mesos Artifacts 1.0.0.
>>
>> Please download, test and vote. Please refer the README files under each
>> product for details on testing the artifacts.
>>
>> Source & binary distribution files:
>> https://github.com/wso2/mesos-artifacts/releases/tag/v1.0.0-rc1
>>
>> Maven staging repo:
>>
>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbonmesosartifacts-1000/
>>
>> The tag to be voted upon:
>> https://github.com/wso2/mesos-artifacts/releases/tag/v1.0.0-rc1
>>
>> Mesos Artifacts Documentation:
>> https://docs.wso2.com/display/MA100/Home
>>
>> This vote will be open for 72 hours or as needed.
>>
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>>
>> Regards,
>> WSO2 PaaS team
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

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

Re: [Dev] [VOTE] Release WSO2 Mesos Artifacts 1.0.0 RC1

[Isuru Haththotuwa]

Verified the following:

   1. License headers using RAT plugin
   2. Tested the following on mesos:
   - wso2am 1.10.0 - standalone and distributed deployments
  - wso2das 3.0.1 - standalone and distributed deployments
  - wso2cep 4.0.0 - standalone deployment with a smoke test

*[x] - Stable, go ahead and release*

On Tue, Jul 26, 2016 at 11:28 PM, Pubudu Gunatilaka 
wrote:

> Hi Devs,
>
> This is the first release candidate (RC1) of WSO2 Mesos Artifacts 1.0.0.
>
> Please download, test and vote. Please refer the README files under each
> product for details on testing the artifacts.
>
> Source & binary distribution files:
> https://github.com/wso2/mesos-artifacts/releases/tag/v1.0.0-rc1
>
> Maven staging repo:
>
> https://maven.wso2.org/nexus/content/repositories/orgwso2carbonmesosartifacts-1000/
>
> The tag to be voted upon:
> https://github.com/wso2/mesos-artifacts/releases/tag/v1.0.0-rc1
>
> Mesos Artifacts Documentation:
> https://docs.wso2.com/display/MA100/Home
>
> This vote will be open for 72 hours or as needed.
>
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
>
> Regards,
> WSO2 PaaS team
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks and Regards,

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

Re: [Dev] App manager REST API issue with MySQL

[Dinusha Senanayaka]

Hi Chathura,

Is this happen in latest AppM (master or 1.2.0 release)? Also  could see
space in the path: /mobileapps/admin/android/*Anti Virus 3*/1.2.0
. Can you try without having spaces in the App name.

Regards,
Dinusha.

On Mon, Aug 1, 2016 at 4:31 PM, Chathura Dilan  wrote:

> Hi All,
>
> We are getting following error in EMM after configure it with MySQL 5.5
> when adding a mobile app with REST API.
>
>
>
> TID: [-1234] [] [2016-08-01 10:20:21,492] ERROR
> {org.wso2.carbon.appmgt.rest.api.publisher.AppsApiService} -  Error
> occurred while creating mobile application : Anti Virus 3
> org.wso2.carbon.appmgt.api.AppManagementException: Error occurred while
> creating the mobile application : Anti Virus 3
> at
> org.wso2.carbon.appmgt.impl.AbstractAPIManager.handleException(AbstractAPIManager.java:692)
> at
> org.wso2.carbon.appmgt.impl.APIProviderImpl.createMobileApp(APIProviderImpl.java:470)
> at
> org.wso2.carbon.appmgt.impl.UserAwareAPIProvider.createMobileApp(UserAwareAPIProvider.java:36)
> at
> org.wso2.carbon.appmgt.rest.api.publisher.impl.AppsApiServiceImpl.appsAppTypePost(AppsApiServiceImpl.java:217)
> at
> org.wso2.carbon.appmgt.rest.api.publisher.AppsApi.appsAppTypePost(AppsApi.java:118)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:200)
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:99)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:251)
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)
> at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:180)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:293)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:212)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:268)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
> at
> org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
> at
> org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationValve.invoke(WebappAuthenticationValve.java:45)
> at
> org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
> at
> 

[Dev] Foundation dependency in UI is under samples

[Sajini De Silva]

Hi,

Currently we use org.wso2.carbon.uuf.sample.foundation package to get the
basic layout of MB product UI (header, footer etc. ). Since this is used
for sampling this cannot be used in a production environment. Since this
feature is common to all the products in WSO2 is there any plan on
implementing a new foundation feature for this?

Thanks,
-- 
Sajini De SIlva
Senior Software Engineer; WSO2 Inc.; http://wso2.com ,
Email: saj...@wso2.comp
Blog: http://sajinid.blogspot.com/
Git hub profile: https://github.com/sajinidesilva

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

[Dev] App manager REST API issue with MySQL

[Chathura Dilan]

Hi All,

We are getting following error in EMM after configure it with MySQL 5.5
when adding a mobile app with REST API.



TID: [-1234] [] [2016-08-01 10:20:21,492] ERROR
{org.wso2.carbon.appmgt.rest.api.publisher.AppsApiService} -  Error
occurred while creating mobile application : Anti Virus 3
org.wso2.carbon.appmgt.api.AppManagementException: Error occurred while
creating the mobile application : Anti Virus 3
at
org.wso2.carbon.appmgt.impl.AbstractAPIManager.handleException(AbstractAPIManager.java:692)
at
org.wso2.carbon.appmgt.impl.APIProviderImpl.createMobileApp(APIProviderImpl.java:470)
at
org.wso2.carbon.appmgt.impl.UserAwareAPIProvider.createMobileApp(UserAwareAPIProvider.java:36)
at
org.wso2.carbon.appmgt.rest.api.publisher.impl.AppsApiServiceImpl.appsAppTypePost(AppsApiServiceImpl.java:217)
at
org.wso2.carbon.appmgt.rest.api.publisher.AppsApi.appsAppTypePost(AppsApi.java:118)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
at
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:200)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:99)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:251)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160)
at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:180)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:293)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:212)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:268)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57)
at
org.wso2.carbon.webapp.authenticator.framework.WebappAuthenticationValve.invoke(WebappAuthenticationValve.java:45)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57)
at
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)

Re: [Dev] Passing values to the Xpath 2.0 function - fn:avg

[Sohani Weerasinghe]

According to [1] if I test the distinct-values function,it behaves as
explained below:


1. If I use a rest mock service to get the response and then get the
distinct values :

Rest mock service response:

http://example.org/ACC/;> 
*557
44*
*44*  

Rest API:

http://ws.apache.org/ns/synapse; name="sample123"
context="/test123">   
 http://localhost:8080/getResult"/> 
http://www.w3.org/2005/xpath-functions; xmlns:ns="
http://org.apache.synapse/xsd; xmlns:base="http://test; name="testValue"
*expression="fn:**distinct-values**(//product/*)"/*>
   


Then expected result is : *557, 44*

But I am getting only *557*

Am I missing something here?

2. If I directly use this function as below

http://ws.apache.org/ns/synapse;
   name="testProxy"
   transports="http https"
   startOnLoad="true">
   
   
  
 
http://www.w3.org/2005/xpath-functions;
  xmlns:xs="http://www.w3.org/2001/XMLSchema;
  xmlns:ns="http://org.apache.synapse/xsd;
  name="testValue"
  expression="*fn:**distinct-values**(('a', 'b', 'a'))*
"/>
 
  
  
   


Then I'm getting the exception "invalid XPapth expression" in saving the
proxy

But according to [1] it seems both ways are correct


[1] http://www.xqueryfunctions.com/xq/fn_distinct-values.html

Thanks,
Sohani

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

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

On Mon, Aug 1, 2016 at 3:54 PM, Sohani Weerasinghe  wrote:

>
>
>
> Sohani Weerasinghe
> Senior Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Mon, Aug 1, 2016 at 1:28 PM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> It seems, the " Invalid XPapth expression" comes when we use two
>> brackets in the function as below
>>
>
>
> While I was testing further I found that below function works perfectly
> even it has two brackets, so that means the syntax of the above mentioned
> functions are correct.
>
> So, are these functions not supported in ESB? Appreciate your input on this
>
> fn:dateTime(xs:date('2006-08-15'), xs:time('12:30:45-05:00'))
>
>
>> fn:codepoints-to-string(*(*2309, 2358, 2378, 2325*)*)
>> fn:string-join(('a', 'c'), 'bbb')
>>
>>
>>
>>
>>
>>
>> Sohani Weerasinghe
>> Senior Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> On Mon, Aug 1, 2016 at 12:06 PM, Sohani Weerasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> I am validating the Xpath 2.0 functions support in ESB ( please refer
>>> [1]) and I am using below configuration in defining 'avg' function
>>> (Referred [2]), but it seems I am using the wrong syntax.
>>>
>>>   http://www.w3.org/2005/xpath-functions;
>>>   xmlns:test="http://test;
>>>   xmlns:ns="http://org.apache.synapse/xsd;
>>>   name="testValue"
>>> *  expression="fn:avg((3,4,5))"/>*
>>>
>>> Can someone please point the correct syntax?
>>>
>>> Since avg function requires a single parameter, is there a way to define
>>> the integer values externally ( may be using a property mediator ) and use
>>> it inside the function ?
>>>
>>> If this syntax is correct, is this function not supported in ESB?
>>>
>>> Really appreciate your input on this
>>>
>>> FYI: When saving the proxy, I'm getting below exception:
>>>
>>> [2016-08-01 11:41:11,718] ERROR - ProxyServiceAdmin Unable to save
>>> changes made for the proxy service : testProxy. Restored the existing
>>> proxy... :: Invalid XPapth expression : fn:avg((3,4,5))
>>> org.apache.synapse.SynapseException: Invalid XPapth expression :
>>> fn:avg((3,4,5))
>>> at
>>> org.apache.synapse.config.xml.MediatorPropertyFactory.getMediatorProperties(MediatorPropertyFactory.java:106)
>>> at
>>> org.apache.synapse.config.xml.LogMediatorFactory.createSpecificMediator(LogMediatorFactory.java:111)
>>> ...
>>>
>>>
>>>
>>> [1] Xpath 2.0.0 functions supported by ESB
>>> [2] https://www.w3.org/TR/xpath-functions/#func-avg
>>> Sohani Weerasinghe
>>> Senior Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] WSO2 Application Server 6.0.0-M3 Released !

[Chanaka Cooray]

WSO2 Application Server 6.0.0-M3 Released !

WSO2 Application Server 6.0.0 is the successor of the WSO2 Carbon based
Application Server. It is a complete revamp and is based on vanilla Apache
Tomcat 8. WSO2 provides a number of features by means of extensions to
Apache Tomcat to integrate it with rest of the products of the WSO2 Carbon
middleware platform. It provides first class support for generic web
applications, JAX-RS/JAX-WS web applications and jaggery applications. The
performance of the server and individual application can be monitored by
integrating WSO2 Application Server with WSO2 Data Analytics Server.

WSO2 Application Server is an open source project and it is available under
the Apache Software License (v2.0)
.

Source and product distribution for this release is available here
.
New Features

   -

   [WSAS-2191 ] - SAML 2.0 based
   Single-Sign-On (SSO) Apache Tomcat valve

WSO2 Application Server now supports SSO for web applications with WSO2
Identity Server. We have introduced the SSO Quick Start

script to try out SSO functionality with one go.

   -

   [WSAS-2250 ] - Jaggery runtime
   support

With this release of WSO2 Application Server we have introduced the Jaggery
runtime. Jaggery applications can be deployed with this custom runtime.
Improvements

   -

   [WSAS-2235 ] - Change the names
   of appserver-utils module classes into meaningful names with less confusion
   -

   [WSAS-2237 ] - Change of the
   location of the WSO2 AS web application descriptor, within a web application
   -

   [WSAS-2244 ] - Adding test cases
   for validating security related system properties.
   -

   [WSAS-2251 ] - SSO QuickStart
   Guide

Tasks

   -

   [WSAS-2229 ] - Add a feature to
   test failing test cases in the integration tests
   -

   [WSAS-2230 ] - Merge jacoco
   integration test coverage reports
   -

   [WSAS-2242 ] - Update
   client-truststore.jks with the latest
   -

   [WSAS-2246 ] - Get rid of
   org.wso2.carbon.logging-4.4.3.jar in /lib
   -

   [WSAS-2252 ] - Set https enabled
   by default in server.xml
   -

   [WSAS-2253 ] - Shade
   commons-logging and log4j jars

Key Features

   -

   HTTP Statistics Publishing to WSO2 Data Analytics Server
   -

   SAML based Single Sign On (SSO) for web applications
   -

   Support for Jaggery applications deployment
   -

   Webapp classloading runtimes

Reporting Issues

Issues, documentation errors and feature requests regarding WSO2
Application Server can be reported through the public issue tracking
system. https://wso2.org/jira/browse/WSAS.
Contact us

WSO2 Application Server developers can be contacted via the Development
 and Architecture  mailing lists.

Alternatively, questions can also be raised in the stackoverflow forum :
http://stackoverflow.com/questions/tagged/wso2

Thank you for your interest in WSO2 Application Server.

-The WSO2 Application Server Development Team -


On Mon, Aug 1, 2016 at 11:10 AM, Chanaka Cooray  wrote:

> WSO2 Application Server 6.0.0-M3 Released !
> Welcome to WSO2 Application Server, the successor of WSO2 Carbon based
> Application Server. WSO2 Application Server 6.0.0 is a complete revamp and
> is based on vanilla Apache Tomcat. WSO2 provides a number of features by
> means of extensions to Tomcat to add/enhance the functionality. It provides
> first class support for generic web applications, JAX-RS/JAX-WS web
> applications and jaggery applications. The performance of the server and
> individual application can be monitored by integrating WSO2 Application
> Server with WSO2 Data Analytics Server.
>
> WSO2 Application Server is an open source project and it is available
> under the Apache Software License (v2.0)
> .
>
> Source and product distribution for this release is available here
> .
> Key Features
>
>- HTTP Statistics Monitoring
>- Webapp Classloading Runtimes
>- Jaggery Runtime Support
>- Accessing Applications using Single Sign-On
>
> Fixed Issues
>
>- https://wso2.org/jira/browse/WSAS-2194?filter=13173
>
> Known Issues
>
>- https://wso2.org/jira/browse/WSAS-2248?filter=13174
>
> Reporting Issues
>
> Issues, 

Re: [Dev] Passing values to the Xpath 2.0 function - fn:avg

[Sohani Weerasinghe]

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

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

On Mon, Aug 1, 2016 at 1:28 PM, Sohani Weerasinghe  wrote:

> Hi All,
>
> It seems, the " Invalid XPapth expression" comes when we use two brackets
> in the function as below
>


While I was testing further I found that below function works perfectly
even it has two brackets, so that means the syntax of the above mentioned
functions are correct.

So, are these functions not supported in ESB? Appreciate your input on this

fn:dateTime(xs:date('2006-08-15'), xs:time('12:30:45-05:00'))


> fn:codepoints-to-string(*(*2309, 2358, 2378, 2325*)*)
> fn:string-join(('a', 'c'), 'bbb')
>
>
>
>
>
>
> Sohani Weerasinghe
> Senior Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Mon, Aug 1, 2016 at 12:06 PM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> I am validating the Xpath 2.0 functions support in ESB ( please refer
>> [1]) and I am using below configuration in defining 'avg' function
>> (Referred [2]), but it seems I am using the wrong syntax.
>>
>>   http://www.w3.org/2005/xpath-functions;
>>   xmlns:test="http://test;
>>   xmlns:ns="http://org.apache.synapse/xsd;
>>   name="testValue"
>> *  expression="fn:avg((3,4,5))"/>*
>>
>> Can someone please point the correct syntax?
>>
>> Since avg function requires a single parameter, is there a way to define
>> the integer values externally ( may be using a property mediator ) and use
>> it inside the function ?
>>
>> If this syntax is correct, is this function not supported in ESB?
>>
>> Really appreciate your input on this
>>
>> FYI: When saving the proxy, I'm getting below exception:
>>
>> [2016-08-01 11:41:11,718] ERROR - ProxyServiceAdmin Unable to save
>> changes made for the proxy service : testProxy. Restored the existing
>> proxy... :: Invalid XPapth expression : fn:avg((3,4,5))
>> org.apache.synapse.SynapseException: Invalid XPapth expression :
>> fn:avg((3,4,5))
>> at
>> org.apache.synapse.config.xml.MediatorPropertyFactory.getMediatorProperties(MediatorPropertyFactory.java:106)
>> at
>> org.apache.synapse.config.xml.LogMediatorFactory.createSpecificMediator(LogMediatorFactory.java:111)
>> ...
>>
>>
>>
>> [1] Xpath 2.0.0 functions supported by ESB
>> [2] https://www.w3.org/TR/xpath-functions/#func-avg
>> Sohani Weerasinghe
>> Senior Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Is it possible to define a global response header in a MSF4J service

[Thusitha Thilina Dayaratne]

Hi Sumedha,

You can implement an Interceptor and in the precall you can add the header
that you want.
e.g.

public class TestInterceptor implements Interceptor {
@Override
public boolean preCall(Request request, Response responder,
ServiceMethodInfo serviceMethodInfo) throws Exception {
responder.setHeader("Access-Control-Allow-Origin", "ALL");
return true;
}

.


Thanks

Thusitha


On Mon, Aug 1, 2016 at 2:57 PM, Sumedha Kodithuwakku 
wrote:

> Hi Kasun,
>
> In my case I need to set "Access-Control-Allow-Origin" header to every
> method and it will have a fixed value.
>
> Thanks
> SumedhaS
>
>
> On Mon, Aug 1, 2016 at 2:43 PM, KasunG Gajasinghe  wrote:
>
>> Hi Sumedha,
>>
>> As I see, this is not provided by the JAX-RS 2.0 specification. If this
>> is set at the class-level, then the header names and values will need to be
>> hard-coded. Can you explain the usecase here?
>>
>> On Mon, Aug 1, 2016 at 2:32 PM, Sumedha Kodithuwakku 
>> wrote:
>>
>>> Hi all,
>>>
>>> $subject.?
>>>
>>> I can set a response header within each response as below;
>>>
>>> Response.status(Response.Status.OK).entity(object).header("Header", 
>>> "Value").build();
>>>
>>> However is it possible to define such a header at global level.? For
>>> example like *@Header({ Header", "Value" } public class ClassName(**)* at
>>> class level.
>>>
>>> Appreciate your thoughts on this..
>>>
>>> Thanks
>>> SumedhaS
>>>
>>> --
>>> *Sumedha Kodithuwakku*
>>> Senior Software Engineer
>>> WSO2 Inc. : http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> Mobile: +94 71 808 1124
>>> Blog: http://sumedhask.blogspot.com/
>>>
>>>
>>
>>
>> --
>>
>> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
>> email: kasung AT spamfree wso2.com
>> linked-in: http://lk.linkedin.com/in/gajasinghe
>> blog: http://kasunbg.org
>>
>>
>>
>
>
>
> --
> *Sumedha Kodithuwakku*
> Senior Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> Mobile: +94 71 808 1124
> Blog: http://sumedhask.blogspot.com/
>
>


-- 
Thusitha Dayaratne
Software Engineer
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

Mobile  +94712756809
Blog  alokayasoya.blogspot.com
Abouthttp://about.me/thusithathilina

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

Re: [Dev] [Vote] Release WSO2 Data Analytics Server (DAS) 3.1.0-RC1

[Niranda Perera]

Hi all,

[-] Broken - Do not release (explain why)

We found several issues while doing further testing.

Hence, calling off the vote.


On Mon, Aug 1, 2016 at 12:04 PM, Niranda Perera  wrote:

> Hi Iranga,
>
> ML features are fully integrated to DAS now. So, it is not required to
> install any additional features to use the ML functionality
>
> ESB analytics is still not released. I think @Nirmal should be able to
> give a p2 for APIM analytics.
>
> Best
>
> On Mon, Aug 1, 2016 at 11:54 AM, Iranga Muthuthanthri 
> wrote:
>
>> Would it be possible to have a p2-repo to test the  following
>>
>> [i] Install ML features
>> [ii] Install product analytics [ESB, API-M]
>>
>>
>> Added a doc jira to keep track [1]
>>
>> [1]https://wso2.org/jira/browse/DOCUMENTATION-3699
>>
>>
>> On Sat, Jul 30, 2016 at 3:31 AM, Niranda Perera  wrote:
>>
>>> Hi Devs,
>>>
>>> This is the first release candidate (RC1) of WSO2 Data Analytics Server
>>> 3.1.0 release.
>>>
>>>
>>> New / Improvements In This Release
>>>
>>>- Integrating WSO2 Machine Learner features
>>>- Supporting incremental data processing
>>>- Improved gadget generation wizard
>>>- Cross-tenant support
>>>- Improved CarbonJDBC connector
>>>- Improvements for facet based aggregations
>>>- Supporting index based sorting
>>>- Supporting Spark on YARN for DAS
>>>- Improvements for indexing
>>>
>>>
>>>
>>> Issues Fixed in This Release
>>>
>>>- WSO2 DAS 3.1.0 Fixed Issues
>>>
>>>
>>> Known Issues
>>>
>>>- WSO2 DAS 3.1.0 Known Issues
>>>
>>>
>>> *Source and distribution packages:*
>>>
>>>
>>>- https://github.com/wso2/product-das/releases/tag/v3.1.0-RC1
>>>
>>>
>>>
>>>
>>> Please download, test, and vote. The README file under the distribution
>>> contains guide and instructions on how to try it out locally.
>>>
>>> [+] Stable - Go ahead and release
>>>
>>> [-] Broken - Do not release (explain why)
>>>
>>>
>>> This vote will be open for 72 hours or as needed.
>>>
>>> Regards,
>>> WSO2 DAS Team
>>>
>>> --
>>> *Niranda Perera*
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94-71-554-8430
>>> Twitter: @n1r44 
>>> https://pythagoreanscript.wordpress.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks & Regards
>>
>> Iranga Muthuthanthri
>> (M) -0777-255773
>> Team Product Management
>>
>>
>
>
> --
> *Niranda Perera*
> Software Engineer, WSO2 Inc.
> Mobile: +94-71-554-8430
> Twitter: @n1r44 
> https://pythagoreanscript.wordpress.com/
>



-- 
*Niranda Perera*
Software Engineer, WSO2 Inc.
Mobile: +94-71-554-8430
Twitter: @n1r44 
https://pythagoreanscript.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Governance Registry 5.3.0 RC 1

[Danesh Kuruppu]

Hi all,

We have encountered two issues [1] and [2] which need to be fixed. We will
cancel this vote and call for a RC2.

[1] - https://wso2.org/jira/browse/REGISTRY-3857
[2] - https://wso2.org/jira/browse/REGISTRY-3858

Thanks
Danesh

On Fri, Jul 29, 2016 at 2:54 PM, Rajith Roshan  wrote:

> Hi Devs,
>
> WSO2 Governance Registry 5.3.0 RC1 Release Vote.
>
> This release fixes the following issues:
> https://wso2.org/jira/browse/REGISTRY-3854?filter=13166
>
> Please download, test and vote. Please refer the release verification
> guide for detailed information on verifying this release.
>
> Source & binary distribution files:
> https://svn.wso2.org/repos/wso2/scratch/G-Reg/5.3.0/rc1/
>
> Maven staging repo:
> *https://maven.wso2.org/nexus/content/repositories/orgwso2greg-1007/
> *
>
> The tag to be voted upon:
> https://github.com/wso2/product-greg/tree/v5.3.0-rc1
>
> *Note*: We will upload OWASP zap tool reports for console, publisher and
> store soon.
>
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> Thanks and Regards
> ES/G-Reg team
>
>
> --
> Rajith Roshan
> Software Engineer, WSO2 Inc.
> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Danesh Kuruppu*
Senior Software Engineer | WSO2

Email: dan...@wso2.com
Mobile: +94 (77) 1690552
Web: WSO2 Inc 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Meeting minutes

[Abhishek Tiwari]

Hi Imesh,

Thanks for the feedback. I completely agree with the naming of executable.
Unfortunately, go install builds executable using module name and main()
has to be inside main module name (based on what I have read so far). A
quick search did not provide any solution so I will tackle this later. If
anyone has addressed this in the community, please let me know.

Import statement for common is fully qualified since that is the root level
package. If I try prefixing that with project name, that will not work, as
Go will try to look for the package in the following:
/src/

I have also provided instruction to build the project without Eclipse [1].
It looks like your GOPATH is missing the path of the source directory of
project. My GOPATH has following additional entry for the project:
/Users/abhishektiwari/dev/test-framework

Could you please try adding the source root to GOPATH in your bash_profile.
Please let me know if you still face issues with the build.

[1]. https://github.com/abhishek0198/test-framework#build-without-eclipse

Thanks
Abhishek

On Mon, Aug 1, 2016 at 2:46 PM, Imesh Gunaratne  wrote:

> Hi Abhishek,
>
> On Mon, Aug 1, 2016 at 6:15 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> Hi Imesh,
>>
>> The project is currently structured around standard Golang project
>> created by eclipse, you can add eclipse plugin, create a new project with
>> existing sources and it should compile fine. I will add complete
>> instructions on Github and update this thread.
>>
>
> ​I do not think we should use Eclipse specific build tools. The project
> should be able to build from the shell with standard go build commands.​
> I went through the updated README and still the given instructions seem to
> be not working:
>
> ~/dev/test-framework$ go install -v -gcflags "-N -l" ./...
> src/main/config_parser.go:24:2: cannot find package "common" in any of:
> /usr/local/go/src/common (from $GOROOT)
> /Users/imesh/dev/go/src/common (from $GOPATH)
>
> I see couple of problems in the code:
>
>- ​The executable name should be meaningful. I do not think main is
>much meaningful binary name.
>- Import statements which refer packages from the same project should
>use fully qualified package names [1]. See [2]. This might be the root
>cause of the above error.
>
> ​[1]
>
> https://github.com/abhishek0198/test-framework/blob/master/src/main/config_parser.go#L24
> [2]
> https://github.com/kubernetes/kubernetes/blob/master/pkg/proxy/iptables/proxier.go#L38
>
> Thanks​
> ​
>
>
>> Chamila,
>> The tests I am working on are custom tests which aims at verifying few
>> endpoints using CURL. I tried using existing tests for ESB, and that didn't
>> help either since setup steps of those tests requires a lot of efforts. If
>> developers from specific projects can help out with configuration, then we
>> can run existing full fledged tests.
>>
>> Thanks
>> Abhishek
>>
>> On Thu, Jul 28, 2016 at 9:08 PM, Chamila De Alwis 
>> wrote:
>>
>>>
>>> On Thu, Jul 28, 2016 at 4:19 AM, Abhishek Tiwari <
>>> abhishek.tiwari0...@gmail.com> wrote:
>>>
 2. I am currently working on adding the ability to run smoke tests from
 the framework. The idea is to have the capability of having product
 specific smoke tests, then teams with more product knowledge can add smoke
 tests. I will add smoke tests for ESB at this point.

>>>
>>> Would these be custom tests that are specific to WSO2 Dockerfiles
>>> context or generic tests that aim to test the product code? It would be
>>> better if we can reuse the generic tests, as new tests would not be
>>> attractive to the developers.
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Committer and PMC Member - Apache Stratos
>>> Senior Software Engineer | WSO2
>>> Blog: https://medium.com/@chamilad
>>>
>>>
>>>
>>
>
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Disabling INFO logs per page rendering

[Prabath Abeysekera]

[Looping dev@]

Folks, please refrain from discussing development related stuff in private.

Cheers,
Prabath

On Mon, Aug 1, 2016 at 3:08 PM, Milan Perera  wrote:

> +1.
> We should have to definitely remove them.
> As I remember , this was mistakenly committed by Dilan Aiya for debug
> purpose and Prabath aiya asked to remove them.
>
>
> On Mon, Aug 1, 2016 at 2:55 PM, Rasika Perera  wrote:
>
>> [+Milan]
>>
>> On Mon, Aug 1, 2016 at 2:28 PM, Rasika Perera  wrote:
>>
>>> Can we do $subject as it affects performance of the rendering.
>>>
>>> Most of the seems belongs to DEBUG and TRACE levels.
>>>
>>> [2016-08-01 14:24:12,623]  INFO {JAGGERY.lib.pages:jag} -  ##
>>> Permissions : {"LIST_DEVICES" : true, "LIST_OWN_DEVICES" : true,
>>> "LIST_ALL_GROUPS" : true, "LIST_GROUPS" : true, "LIST_USERS" : true,
>>> "LIST_ROLES" : true, "LIST_ALL_POLICIES" : true, "LIST_POLICIES" : true,
>>> "ADD_DEVICE" : true, "ADD_GROUP" : true, "ADD_USER" : true, "REMOVE_USER" :
>>> true, "ADD_ROLE" : true, "ADD_ADMIN_POLICY" : true, "ADD_POLICY" : true,
>>> "CHANGE_POLICY_PRIORITY" : true, "VIEW_DASHBOARD" : true,
>>> "TENANT_CONFIGURATION" : true}
>>> [2016-08-01 14:24:13,433]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Request : GET
>>> https://10.100.7.31:9443/api/device-mgt/v1.0/roles?offset=0=1
>>> [2016-08-01 14:24:13,435]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Request payload
>>> if any : null
>>> [2016-08-01 14:24:13,433]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Request : GET
>>> https://10.100.7.31:9443/api/device-mgt/v1.0/notifications?status=NEW
>>> [2016-08-01 14:24:13,433]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Request : GET
>>> https://10.100.7.31:9443/api/device-mgt/v1.0/users?offset=0=1
>>> [2016-08-01 14:24:13,437]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Request payload
>>> if any : null
>>> [2016-08-01 14:24:13,436]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Request : GET
>>> https://10.100.7.31:9443/api/device-mgt/v1.0/devices?offset=0=1
>>> [2016-08-01 14:24:13,436]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Response status
>>> : 200
>>> [2016-08-01 14:24:13,440]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Request payload
>>> if any : null
>>> [2016-08-01 14:24:13,438]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Response status
>>> : 200
>>> [2016-08-01 14:24:13,437]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Request payload
>>> if any : null
>>> [2016-08-01 14:24:13,441]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Response status
>>> : 200
>>> [2016-08-01 14:24:13,441]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Response status
>>> : 200
>>> [2016-08-01 14:24:13,440]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Response
>>> payload if any : {"roles":["admin"],"count":1}
>>> [2016-08-01 14:24:13,442]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Response
>>> payload if any : {"users":[{"username":"admin"}],"count":1}
>>> [2016-08-01 14:24:13,442]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Response
>>> payload if any : {"devices":[],"count":0}
>>> [2016-08-01 14:24:13,441]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Response
>>> payload if any : {"notifications":[],"count":0}
>>> [2016-08-01 14:24:13,443]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Request : GET
>>> https://10.100.7.31:9443/api/device-mgt/v1.0/policies?offset=0=1
>>> [2016-08-01 14:24:13,444]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Request payload
>>> if any : null
>>> [2016-08-01 14:24:13,445]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Response status
>>> : 200
>>> [2016-08-01 14:24:13,445]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Response
>>> payload if any : {"policies":[],"count":0}
>>> [2016-08-01 14:24:13,916]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Request : GET
>>> https://10.100.7.31:9443/api/device-mgt/v1.0/notifications?status=NEW
>>> [2016-08-01 14:24:13,916]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Request payload
>>> if any : null
>>> [2016-08-01 14:24:13,916]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Response status
>>> : 200
>>> [2016-08-01 14:24:13,917]  INFO
>>> {/app/modules/oauth/token-protected-service-invokers.js} -  Response
>>> payload if any : {"notifications":[],"count":0}
>>>
>>> --
>>> With Regards,
>>>
>>> *Rasika Perera*
>>> Software Engineer
>>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>>
>>> [image: wso2-signature-general.png] 

Re: [Dev] [VOTE] Release WSO2 Enterprise Store 2.1.0 RC 1

[Chanaka Jayasena]

Hi Devs,

We have identified a security issue which is a blocker for the release. We
are closing the vote now and will provide RC2 with the issues fixed.

thanks,
Chanaka

On Fri, Jul 29, 2016 at 5:04 PM, Sameera Medagammaddegedara <
samee...@wso2.com> wrote:

> Hi Devs,
>
> WSO2 Enterprise Store 2.1.0 RC1 Release Vote
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=13171
>
> Please download, test and vote. Please refer the release verification
> guide for detailed information on verifying this release.
>
> Source & binary distribution files:
> https://svn.wso2.org/repos/wso2/scratch/ES/2.1.0/rc1/
> 
>
> Maven staging repo:
>
> https://maven.wso2.org/nexus/content/repositories/orgwso2es-1005/org/wso2/es/
> 
>
> The tag to be voted upon:
> https://github.com/wso2/product-es/tree/v2.1.0-rc1
>
> *Note*: We will upload OWASP zap tool reports for console, publisher and
> store soon.
>
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> Thanks and Regards
> ES/G-Reg team
> --
> Sameera Medagammaddegedara
> Software Engineer
>
> Contact:
> Email: samee...@wso2.com
> Mobile: + 94 077 255 3005
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Chanaka Jayasena
Associate Tech Lead,
email: chan...@wso2.com; cell: +94 77 4464006
blog: http://chanaka3d.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [IS] [Analytics] Improvement to use Siddhi streams to send notifications

[Sriskandarajah Suhothayan]

HI Indunil

Any update on this? Was the provided solution working?

We released CEP 4.2-RC1. If we need new features/improvements for this
effort, we can incorporate them in the next component release.

Regards
Suho

On Fri, Jul 22, 2016 at 3:10 PM, Sriskandarajah Suhothayan 
wrote:

>
>
> On Fri, Jul 22, 2016 at 3:00 PM, Johann Nallathamby 
> wrote:
>
>>
>>
>> On Fri, Jul 22, 2016 at 8:33 AM, Indunil Upeksha Rathnayake <
>> indu...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> On Fri, Jul 22, 2016 at 12:28 PM, Sriskandarajah Suhothayan <
>>> s...@wso2.com> wrote:
>>>


 On Fri, Jul 22, 2016 at 12:00 PM, Indunil Upeksha Rathnayake <
 indu...@wso2.com> wrote:

> Hi,
>
> Please find the meeting notes in [1].  I have following considerations
> regarding the improvements we have discussed.
>
> (1) Even though we have configured to load the email template from
> EventPublisher(analytics side), the placeholder values has to be sent as
> meta data/correlation data/payload data/arbitrary data, since in analytics
> side, the user claim values are not getting from the user store.
> In order to send the placeholder values from IS side, anyway we have
> to load the email template and retrieve the placeholders. So as I have
> understood, for email notifications, it's not needed to use the email
> template loading part in analytics, since it'll be a redundant task. 
> (Refer
> [2])
>

 Here we can set the claim values as arbitrary data, and the
 notification specific details as the meta, correlation & payload data.
 Then we can use the template loading only at the analytics side.

>>> In this case, from IS side, without parsing only the user claims needed
>>> for a particular email template(i.e.user claim values for the placeholders
>>> in email template), we have to pass all the user claims as arbitrary data
>>> values. In that case there's no need for loading the template from the
>>> registry in IS side. So that in analytics side, all the values needed for
>>> filling out the template will be there. Will check on that.
>>>
>>
>> I don't think it will be a good solution. There can be sensitive
>> information in the claims which we can't send. So for this release it's OK
>> if we read the template in both sides - security is more important than
>> performance; or read it only in IS side - but additionally send all those
>> claims as arbitrary data as well, so if some one wants can use them in CEP
>> side by their output adaptors.
>>
>
> I think then we can have a common configuration in IS side to specify what
> are the claims that should be added to notifications.
>
> Regards
> Suho
>
>
>>
>>

> (2) The email templates has to be changed as follows.
> i) if the value will be provided in an arbitrary data map, the
> placeholder should be with a prefix "arbitrary_"
> (ex:{{arbitrary_givenname}})
>
 ii) if the value will be provided in an meta data map, the
> placeholder should be changed as {{...}} (ex:{{givenname}})
>
> No we should not use "arbitrary_" for any cases, its internal
 information and the names should not have "arbitrary_" even if its in
 arbitrary data map or otherwise.

 (3) Only Text OutputMapping Content can be filled from a value in an
> arbitrary data map using prefix "arbitrary_" .  It's not possible to use a
> value of an arbitrary data map, in a Dynamic adapter properties, only a
> value from a meta data/correlation data/payload data map can be used. I
> think that need to be extended to use even an arbitrary value as a dynamic
> adapter property.(Refer [3])
>

 @Gobi can you please fix this if that's the case.


>
> (4) The default stream definitions and publisher definitions has to be
> deployed on super tenant as well as other tenants as well. And when a new
> tenant is added, those streams and publishers has to be deployed for that
> particular tenant as well.
>
> We can have a tenant creation handler to do this copying during that
 tenant creation time. WDYT?

 Really appreciate your ideas/suggestions regarding the above mentioned
> concerns.
>
> [1] Invitation: [Architecture] [Discussion] Improvement to use Siddhi
> str... @ Wed Jul 20, 2016 4:30pm - 5:30pm (IST) (indu...@wso2.com)
>
> [2]
> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/org.wso2.carbon.event.publisher.core/src/main/java/org/wso2/carbon/event/publisher/core/internal/type/text/TextOutputMapper.java#L108
>
> [3]
> https://github.com/wso2/carbon-analytics-common/blob/master/components/event-publisher/org.wso2.carbon.event.publisher.core/src/main/java/org/wso2/carbon/event/publisher/core/internal/EventPublisher.java#L311
>
> Thanks and Regards
> --
> Indunil Upeksha 

Re: [Dev] Is it possible to define a global response header in a MSF4J service

[Sumedha Kodithuwakku]

Hi Kasun,

In my case I need to set "Access-Control-Allow-Origin" header to every
method and it will have a fixed value.

Thanks
SumedhaS

On Mon, Aug 1, 2016 at 2:43 PM, KasunG Gajasinghe  wrote:

> Hi Sumedha,
>
> As I see, this is not provided by the JAX-RS 2.0 specification. If this is
> set at the class-level, then the header names and values will need to be
> hard-coded. Can you explain the usecase here?
>
> On Mon, Aug 1, 2016 at 2:32 PM, Sumedha Kodithuwakku 
> wrote:
>
>> Hi all,
>>
>> $subject.?
>>
>> I can set a response header within each response as below;
>>
>> Response.status(Response.Status.OK).entity(object).header("Header", 
>> "Value").build();
>>
>> However is it possible to define such a header at global level.? For
>> example like *@Header({ Header", "Value" } public class ClassName(**)* at
>> class level.
>>
>> Appreciate your thoughts on this..
>>
>> Thanks
>> SumedhaS
>>
>> --
>> *Sumedha Kodithuwakku*
>> Senior Software Engineer
>> WSO2 Inc. : http://wso2.com
>> lean . enterprise . middleware
>>
>> Mobile: +94 71 808 1124
>> Blog: http://sumedhask.blogspot.com/
>>
>>
>
>
> --
>
> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
> email: kasung AT spamfree wso2.com
> linked-in: http://lk.linkedin.com/in/gajasinghe
> blog: http://kasunbg.org
>
>
>



-- 
*Sumedha Kodithuwakku*
Senior Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware

Mobile: +94 71 808 1124
Blog: http://sumedhask.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Meeting minutes

[Imesh Gunaratne]

Hi Abhishek,

On Mon, Aug 1, 2016 at 6:15 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> Hi Imesh,
>
> The project is currently structured around standard Golang project created
> by eclipse, you can add eclipse plugin, create a new project with existing
> sources and it should compile fine. I will add complete instructions on
> Github and update this thread.
>

​I do not think we should use Eclipse specific build tools. The project
should be able to build from the shell with standard go build commands.​
I went through the updated README and still the given instructions seem to
be not working:

~/dev/test-framework$ go install -v -gcflags "-N -l" ./...
src/main/config_parser.go:24:2: cannot find package "common" in any of:
/usr/local/go/src/common (from $GOROOT)
/Users/imesh/dev/go/src/common (from $GOPATH)

I see couple of problems in the code:

   - ​The executable name should be meaningful. I do not think main is much
   meaningful binary name.
   - Import statements which refer packages from the same project should
   use fully qualified package names [1]. See [2]. This might be the root
   cause of the above error.

​[1]
https://github.com/abhishek0198/test-framework/blob/master/src/main/config_parser.go#L24
[2]
https://github.com/kubernetes/kubernetes/blob/master/pkg/proxy/iptables/proxier.go#L38

Thanks​
​


> Chamila,
> The tests I am working on are custom tests which aims at verifying few
> endpoints using CURL. I tried using existing tests for ESB, and that didn't
> help either since setup steps of those tests requires a lot of efforts. If
> developers from specific projects can help out with configuration, then we
> can run existing full fledged tests.
>
> Thanks
> Abhishek
>
> On Thu, Jul 28, 2016 at 9:08 PM, Chamila De Alwis 
> wrote:
>
>>
>> On Thu, Jul 28, 2016 at 4:19 AM, Abhishek Tiwari <
>> abhishek.tiwari0...@gmail.com> wrote:
>>
>>> 2. I am currently working on adding the ability to run smoke tests from
>>> the framework. The idea is to have the capability of having product
>>> specific smoke tests, then teams with more product knowledge can add smoke
>>> tests. I will add smoke tests for ESB at this point.
>>>
>>
>> Would these be custom tests that are specific to WSO2 Dockerfiles context
>> or generic tests that aim to test the product code? It would be better if
>> we can reuse the generic tests, as new tests would not be attractive to the
>> developers.
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Senior Software Engineer | WSO2
>> Blog: https://medium.com/@chamilad
>>
>>
>>
>


-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Is it possible to define a global response header in a MSF4J service

[KasunG Gajasinghe]

Hi Sumedha,

As I see, this is not provided by the JAX-RS 2.0 specification. If this is
set at the class-level, then the header names and values will need to be
hard-coded. Can you explain the usecase here?

On Mon, Aug 1, 2016 at 2:32 PM, Sumedha Kodithuwakku 
wrote:

> Hi all,
>
> $subject.?
>
> I can set a response header within each response as below;
>
> Response.status(Response.Status.OK).entity(object).header("Header", 
> "Value").build();
>
> However is it possible to define such a header at global level.? For
> example like *@Header({ Header", "Value" } public class ClassName(**)* at
> class level.
>
> Appreciate your thoughts on this..
>
> Thanks
> SumedhaS
>
> --
> *Sumedha Kodithuwakku*
> Senior Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> Mobile: +94 71 808 1124
> Blog: http://sumedhask.blogspot.com/
>
>


-- 

*Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Is it possible to define a global response header in a MSF4J service

[Sumedha Kodithuwakku]

Hi all,

$subject.?

I can set a response header within each response as below;

Response.status(Response.Status.OK).entity(object).header("Header",
"Value").build();

However is it possible to define such a header at global level.? For
example like *@Header({ Header", "Value" } public class ClassName(**)* at
class level.

Appreciate your thoughts on this..

Thanks
SumedhaS

-- 
*Sumedha Kodithuwakku*
Senior Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware

Mobile: +94 71 808 1124
Blog: http://sumedhask.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][C5] Cannot build product-mb with UUF dependency

[Sajini De Silva]

Hi all,

The reason for this issue was that handlebar artifact ID is changed
to org.wso2.carbon.uuf.renderablecreator.hbs.feature. After changing that,
it worked.

Thanks

On Mon, Aug 1, 2016 at 10:34 AM, Sajini De Silva  wrote:

> Hi,
>
> org.wso2.carbon.andes.rest.service.feature.group 3.5.0.SNAPSHOT
> requires package org.wso2.msf4j [2.0.0,3.0.0). We also have another
> dependency for org.wso2.carbon.uufW. org.wso2.carbon.uuf uses
> org.wso2.msf4j 2.0.0 version only in 1.0.0-SNAPSHOT version.
>
> We have a dependency for org.wso2.uuf.handlebars.feature also. But we UUF
> 1.0.0-SNAPSHOT release org.wso2.uuf.handlebars.feature is not released.
> Therefore we cannot build our product.
>
> This is a blocker for us right now. Can you please look in to this?
>
> Thanks,
>
> --
> Sajini De SIlva
> Senior Software Engineer; WSO2 Inc.; http://wso2.com ,
> Email: saj...@wso2.com
> Blog: http://sajinid.blogspot.com/
> Git hub profile: https://github.com/sajinidesilva
>
> Phone: +94 712797729
>
>


-- 
Sajini De SIlva
Senior Software Engineer; WSO2 Inc.; http://wso2.com ,
Email: saj...@wso2.com
Blog: http://sajinid.blogspot.com/
Git hub profile: https://github.com/sajinidesilva

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

Re: [Dev] Passing values to the Xpath 2.0 function - fn:avg

[Sohani Weerasinghe]

Hi All,

It seems, the " Invalid XPapth expression" comes when we use two brackets
in the function as below

fn:codepoints-to-string(*(*2309, 2358, 2378, 2325*)*)
fn:string-join(('a', 'c'), 'bbb')






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

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

On Mon, Aug 1, 2016 at 12:06 PM, Sohani Weerasinghe  wrote:

> Hi All,
>
> I am validating the Xpath 2.0 functions support in ESB ( please refer [1])
> and I am using below configuration in defining 'avg' function (Referred
> [2]), but it seems I am using the wrong syntax.
>
>   http://www.w3.org/2005/xpath-functions;
>   xmlns:test="http://test;
>   xmlns:ns="http://org.apache.synapse/xsd;
>   name="testValue"
> *  expression="fn:avg((3,4,5))"/>*
>
> Can someone please point the correct syntax?
>
> Since avg function requires a single parameter, is there a way to define
> the integer values externally ( may be using a property mediator ) and use
> it inside the function ?
>
> If this syntax is correct, is this function not supported in ESB?
>
> Really appreciate your input on this
>
> FYI: When saving the proxy, I'm getting below exception:
>
> [2016-08-01 11:41:11,718] ERROR - ProxyServiceAdmin Unable to save changes
> made for the proxy service : testProxy. Restored the existing proxy... ::
> Invalid XPapth expression : fn:avg((3,4,5))
> org.apache.synapse.SynapseException: Invalid XPapth expression :
> fn:avg((3,4,5))
> at
> org.apache.synapse.config.xml.MediatorPropertyFactory.getMediatorProperties(MediatorPropertyFactory.java:106)
> at
> org.apache.synapse.config.xml.LogMediatorFactory.createSpecificMediator(LogMediatorFactory.java:111)
> ...
>
>
>
> [1] Xpath 2.0.0 functions supported by ESB
> [2] https://www.w3.org/TR/xpath-functions/#func-avg
> Sohani Weerasinghe
> Senior Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Imesh Gunaratne]

Hi Osura,

It's good to see the blog posts!
IMO it would be better if you can start writing documentation in parallel
to blog posts, may be using Markdown format in Github.

Thanks

On Fri, Jul 29, 2016 at 10:49 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> I'm researching about automation in Azure. Shall we please have the
> hangout on Monday?
> BTW I will be able to complete the documentation on centralized logging,
> monitoring, auto scaling and load balancing by this weekend and I will
> update my blog with the progress. Your feedback is much appreciated.
>
> Thank you,
>
> On Fri, Jul 29, 2016 at 9:51 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> On Wed, Jul 27, 2016 at 9:17 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi All,
>>>
>>> Following are the meeting notes of the hangout we had on 25th of July,
>>> 2016.
>>>
>>> *Centralized logging*
>>>
>>> Azure Log Analytics provides centralized logging which facilitates the
>>> users to get logs from a given location in a VM, to a centralized location
>>> so that they can analyse and query those logs as they need.
>>> *next task - Documentation in terms of a blog post or webinar
>>>
>>> *Auto scaling*
>>>
>>> Auto scaling is achieved through scale sets in Azure. Scale set is a set
>>> of VMs and auto scaling rules that defines auto scale metrics & actions and
>>> the specification of the VMs.
>>>
>>> *Limitations - Azure portal doesn't support addition of auto scale
>>> rules, it only allows to add a simple scale set with a given number of
>>> instances. Whereas azure CLI, Powershell and REST API supports full
>>> functionality.
>>>
>>> I have added the template to the github repo which I used to create the
>>> auto scale settings which includes the ability to add a custom VM image and
>>> auto scale rules. When you deploy from this template you should give the
>>> URI of the VM image. you can edit auto scale rules using CLI, Power shell
>>> or REST API. Azure Resource Explorer  can
>>> be used if you choose REST API to modify.
>>>
>>> *next tasks - 1) Have to figure out a way to pass application and user
>>> data such as usernames and passwords of database, to the VM image through
>>> the template. 2) Documentaion
>>>
>>>
>>> *Load balancing*
>>>
>>> Following are some key terms you need to know.
>>>
>>> · Backend pool: This is a pool of virtual machines that share
>>> the traffic
>>>
>>> · Probe: The load balancer can probe the health of the various
>>> server instances. When a probe fails to respond, the load balancer stops
>>> sending new connections to the unhealthy instances. Existing connections
>>> are not impacted.
>>>
>>> · Availability set: when you have a set of virtual machines for
>>> the same purpose, azure recommends to add them to an availability set.
>>>
>>> We can add load balancing rules such that requests coming from a given
>>> URL  are shared among the VMs in backend pool. if we configure the load
>>> balancer with auto scaling, VMs in the scale set can be added to the
>>> backend pool so if the auto scale rules are met, it can scale in or out.
>>>
>>> *next tasks - 1)  research more about Probe and service health checking.
>>> 2)  documentation 3) How to automate the whole deployment process.
>>>
>> Thanks for the notes.
>>
>> From the next steps you have mentioned here, deployment automation part
>> is very vital for the project completion. Basically we would need to use
>> either the CLI or the Rest API and create a few of scripts to do a complete
>> deployment on Azure. We can have a hangout today/Monday to discuss the
>> progress on the next tasks and the automation aspects.
>>
>>>
>>> [1] https://github.com/osuran/Azure-templates
>>>
>>> Thank you,
>>>
>>>
>>> On Mon, Jul 25, 2016 at 11:46 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 Thank you. That will solve the issue.

 On Mon, Jul 25, 2016 at 11:44 AM, Isuru Haththotuwa 
 wrote:

> Hi Osura,
>
> If you need any customizations/configurations done at the VM startup,
> you can use /etc/rc.local script to do it. Also, if you define the
> JAVA_HOME in a system wide bashrc file at /etc/bash.bashrc it won't get
> deleted when the user home is removed.
>
>
> On Mon, Jul 25, 2016 at 11:31 AM, Osura Rathnayake  > wrote:
>
>> Hi Imesh,
>>
>> You can only capture a generalized VM image, so when it's being
>> generalized, all of the data in '/home' is erased. Since .bashrc is also 
>> in
>> '/home/', it's also erased. Only the data that are 
>> not
>> in '/home' is preserved.
>>
>> Okay I will try out these steps.
>>
>> Thanks,
>>
>> On Mon, Jul 25, 2016 at 10:14 AM, Imesh Gunaratne 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> On Sun, Jul 24, 2016 at 6:30 PM, 

Re: [Dev] [CARBON] Error after installing web app run time features

[Lakshman Udayakantha]

Thanks Bhathiya. I will check with that version.

On Sun, Jul 31, 2016 at 1:36 AM, Bhathiya Jayasekara 
wrote:

> Hi Lakshman,
>
> I also faced the same issue, and could resolve after upgrading
> carbon-deployment version to 4.6.2.
>
> Thanks,
> Bhathiya
>
> On Thu, Jul 28, 2016 at 8:59 PM, Lakshman Udayakantha 
> wrote:
>
>> Hi,
>>
>> I got error [1] after doing $subject on carbon 4.4.7 kernel. I installed
>> web app hosting feature and web app runtime features. It seems it could not
>> upload web apps. This error getting continuously. How do I prevent this
>> issue and upload web apps?
>>
>> [1]
>>
>> java.lang.NoSuchMethodError: org.apache.coyote.Request.getBytesRead()I
>>
>> at org.apache.coyote.RequestInfo.updateCounters(RequestInfo.java:143)
>>
>> at org.apache.coyote.Request.updateCounters(Request.java:533)
>>
>> at
>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1140)
>>
>> at
>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
>>
>> at
>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1749)
>>
>> at
>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1708)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>
>> at
>> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>>
>> at java.lang.Thread.run(Thread.java:745)
>>
>>
>> Thanks
>> --
>> Lakshman Udayakantha
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>> Mobile: *0717429601 <0717429601>*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Bhathiya Jayasekara*
> *Senior Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <%2B94715478185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
> *Blog: http://movingaheadblog.blogspot.com
> *
>



-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0717429601*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Passing values to the Xpath 2.0 function - fn:avg

[Sohani Weerasinghe]

Hi All,

I am validating the Xpath 2.0 functions support in ESB ( please refer [1])
and I am using below configuration in defining 'avg' function (Referred
[2]), but it seems I am using the wrong syntax.

  http://www.w3.org/2005/xpath-functions;
  xmlns:test="http://test;
  xmlns:ns="http://org.apache.synapse/xsd;
  name="testValue"
*  expression="fn:avg((3,4,5))"/>*

Can someone please point the correct syntax?

Since avg function requires a single parameter, is there a way to define
the integer values externally ( may be using a property mediator ) and use
it inside the function ?

If this syntax is correct, is this function not supported in ESB?

Really appreciate your input on this

FYI: When saving the proxy, I'm getting below exception:

[2016-08-01 11:41:11,718] ERROR - ProxyServiceAdmin Unable to save changes
made for the proxy service : testProxy. Restored the existing proxy... ::
Invalid XPapth expression : fn:avg((3,4,5))
org.apache.synapse.SynapseException: Invalid XPapth expression :
fn:avg((3,4,5))
at
org.apache.synapse.config.xml.MediatorPropertyFactory.getMediatorProperties(MediatorPropertyFactory.java:106)
at
org.apache.synapse.config.xml.LogMediatorFactory.createSpecificMediator(LogMediatorFactory.java:111)
...



[1] Xpath 2.0.0 functions supported by ESB
[2] https://www.w3.org/TR/xpath-functions/#func-avg
Sohani Weerasinghe
Senior Software Engineer
WSO2, Inc: http://wso2.com

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

Re: [Dev] [Vote] Release WSO2 Data Analytics Server (DAS) 3.1.0-RC1

[Niranda Perera]

Hi Iranga,

ML features are fully integrated to DAS now. So, it is not required to
install any additional features to use the ML functionality

ESB analytics is still not released. I think @Nirmal should be able to give
a p2 for APIM analytics.

Best

On Mon, Aug 1, 2016 at 11:54 AM, Iranga Muthuthanthri 
wrote:

> Would it be possible to have a p2-repo to test the  following
>
> [i] Install ML features
> [ii] Install product analytics [ESB, API-M]
>
>
> Added a doc jira to keep track [1]
>
> [1]https://wso2.org/jira/browse/DOCUMENTATION-3699
>
>
> On Sat, Jul 30, 2016 at 3:31 AM, Niranda Perera  wrote:
>
>> Hi Devs,
>>
>> This is the first release candidate (RC1) of WSO2 Data Analytics Server
>> 3.1.0 release.
>>
>>
>> New / Improvements In This Release
>>
>>- Integrating WSO2 Machine Learner features
>>- Supporting incremental data processing
>>- Improved gadget generation wizard
>>- Cross-tenant support
>>- Improved CarbonJDBC connector
>>- Improvements for facet based aggregations
>>- Supporting index based sorting
>>- Supporting Spark on YARN for DAS
>>- Improvements for indexing
>>
>>
>>
>> Issues Fixed in This Release
>>
>>- WSO2 DAS 3.1.0 Fixed Issues
>>
>>
>> Known Issues
>>
>>- WSO2 DAS 3.1.0 Known Issues
>>
>>
>> *Source and distribution packages:*
>>
>>
>>- https://github.com/wso2/product-das/releases/tag/v3.1.0-RC1
>>
>>
>>
>>
>> Please download, test, and vote. The README file under the distribution
>> contains guide and instructions on how to try it out locally.
>>
>> [+] Stable - Go ahead and release
>>
>> [-] Broken - Do not release (explain why)
>>
>>
>> This vote will be open for 72 hours or as needed.
>>
>> Regards,
>> WSO2 DAS Team
>>
>> --
>> *Niranda Perera*
>> Software Engineer, WSO2 Inc.
>> Mobile: +94-71-554-8430
>> Twitter: @n1r44 
>> https://pythagoreanscript.wordpress.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards
>
> Iranga Muthuthanthri
> (M) -0777-255773
> Team Product Management
>
>


-- 
*Niranda Perera*
Software Engineer, WSO2 Inc.
Mobile: +94-71-554-8430
Twitter: @n1r44 
https://pythagoreanscript.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Data Analytics Server (DAS) 3.1.0-RC1

[Iranga Muthuthanthri]

Would it be possible to have a p2-repo to test the  following

[i] Install ML features
[ii] Install product analytics [ESB, API-M]


Added a doc jira to keep track [1]

[1]https://wso2.org/jira/browse/DOCUMENTATION-3699


On Sat, Jul 30, 2016 at 3:31 AM, Niranda Perera  wrote:

> Hi Devs,
>
> This is the first release candidate (RC1) of WSO2 Data Analytics Server
> 3.1.0 release.
>
>
> New / Improvements In This Release
>
>- Integrating WSO2 Machine Learner features
>- Supporting incremental data processing
>- Improved gadget generation wizard
>- Cross-tenant support
>- Improved CarbonJDBC connector
>- Improvements for facet based aggregations
>- Supporting index based sorting
>- Supporting Spark on YARN for DAS
>- Improvements for indexing
>
>
>
> Issues Fixed in This Release
>
>- WSO2 DAS 3.1.0 Fixed Issues
>
>
> Known Issues
>
>- WSO2 DAS 3.1.0 Known Issues
>
>
> *Source and distribution packages:*
>
>
>- https://github.com/wso2/product-das/releases/tag/v3.1.0-RC1
>
>
>
>
> Please download, test, and vote. The README file under the distribution
> contains guide and instructions on how to try it out locally.
>
> [+] Stable - Go ahead and release
>
> [-] Broken - Do not release (explain why)
>
>
> This vote will be open for 72 hours or as needed.
>
> Regards,
> WSO2 DAS Team
>
> --
> *Niranda Perera*
> Software Engineer, WSO2 Inc.
> Mobile: +94-71-554-8430
> Twitter: @n1r44 
> https://pythagoreanscript.wordpress.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards

Iranga Muthuthanthri
(M) -0777-255773
Team Product Management
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PC]Unable to change states in lifecycle

[Yasima Dewmini]

Hi Thilini,


I got the idea.
Thank you.

Regards,
Yasima.

On Mon, Aug 1, 2016 at 11:26 AM, Thilini Cooray  wrote:

> Hi,
>
> On Mon, Aug 1, 2016 at 11:19 AM, Yasima Dewmini  wrote:
>
>> Hi Thilini,
>>
>> Only thing I'm doing is changing the permission of the user roles to deny
>> the write permission.
>> When trying to change state following error comes.
>>
>>
>
> As I mentioned above, the lifecycle executor which gets fired in your
> scenario tries to update a resource. Since the "user1" doesn't have the
> write access to the resource "/_system/governance/processes/process1/
> 1.0.0. ", you are unable to update.
>
> Please check on the executor why this resource needs to be updated on the
> lifecycle change.
> As per now, user1 needs to have write access.
>
>
>
>> [2016-08-01 11:17:01,378] ERROR {rxt.asset} -  Failed to invoke action:
>> Submit for the asset of id: "02cbe9d0-5482-4d68-b507-c76b4ede6310".The
>> following exception was thrown: JavaException:
>> org.wso2.carbon.registry.core.secure.AuthorizationFailedException: Resource
>> update failed. User user1 is not authorized to update the resource
>> /_system/governance/processes/process1/1.0.0.
>> [2016-08-01 11:17:01,379] ERROR
>> {JAGGERY.extensions.assets.default.apis.asset:jag} -
>> org.wso2.carbon.registry.core.secure.AuthorizationFailedException: Resource
>> update failed. User user1 is not authorized to update the resource
>> /_system/governance/processes/process1/1.0.0.
>>
>> Regards,
>> Yasima.
>>
>
>
> Thanks.
>
>
>
>>
>>
>> On Mon, Aug 1, 2016 at 11:06 AM, Thilini Cooray 
>> wrote:
>>
>>> Hi,
>>>
>>> Unless the executor itself doesn't try to update any resources, the
>>> process owner does not require write access.
>>> Do you observe any server side errors mentioning user not authorized to
>>> access the resource etc.?
>>>
>>> Thanks.
>>>
>>> On Mon, Aug 1, 2016 at 10:57 AM, Yasima Dewmini  wrote:
>>>
 Hi,

 I'm creating a new life cycle for PC. I want to remove write permission
 of the process owner when the process is in In-Review state. So, I wrote an
 executor to be executed at Development state to remove that permission.
 When write permission is removed, the process owner is not allowed to
 change the states of life cycle. But the process owner has life cycle
 permission.

 Does any user need write permission to change life cycle states? Isn't
 life cycle permission enough to change states?

 Any clarification on this issue is appreciated.

 Regards,
 Yasima.

 --
 http://wso2.com/signatureYasima Dewmini
 Software Engineer, WSO2, Inc.
 Email: yas...@wso2.com
 Mobile: +94713117081

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


>>>
>>>
>>> --
>>> Best Regards,
>>>
>>> *Thilini Cooray*
>>> Software Engineer
>>> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
>>> E-mail : thili...@wso2.com
>>>
>>> WSO2 Inc. www.wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>> http://wso2.com/signatureYasima Dewmini
>> Software Engineer, WSO2, Inc.
>> Email: yas...@wso2.com
>> Mobile: +94713117081
>>
>
>
>
> --
> Best Regards,
>
> *Thilini Cooray*
> Software Engineer
> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
> E-mail : thili...@wso2.com
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 
http://wso2.com/signatureYasima Dewmini
Software Engineer, WSO2, Inc.
Email: yas...@wso2.com
Mobile: +94713117081
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev