Re: [Dev] [MSF4J] Clarification on debugging a micro service

[Sabra Ossen]

Hi,

I am using IntelliJ idea Ultimate 2016.1

On Tue, May 24, 2016 at 11:05 AM, Isuru Perera  wrote:

> Hi,
>
> All HTTP events are published via HTTPMonitoringDataPublisher
> .
> So, the IDE should stop at that debug point. So, there must be something
> wrong. Which IDE are you using?
>
> On Mon, May 23, 2016 at 5:53 PM, Afkham Azeez  wrote:
>
>> +isuru
>>
>> On Fri, May 20, 2016 at 2:01 PM, Sabra Ossen  wrote:
>>
>>> Hi All,
>>>
>>> I am trying the example in [1] and trying to debug the micro service and
>>> identify details of events being published to WSO2 DAS. I set a debug point
>>> in [2] and I could see that the HTTPMonitoringInterceptor is initialized
>>> and then the HTTPMonitoringDataPublisher is initialized.
>>>
>>> The data has been published to the DAS. But during debugging the code
>>> doesn't reach debug point [3] when I invoke the micro service.
>>>
>>> Am I debugging the micro service correctly. Any clarification on the
>>> issue is appreciated.
>>>
>>> [1]
>>> https://github.com/wso2/msf4j/tree/master/samples/metrics-httpmon/metrics-httpmon-fatjar
>>> [2]
>>> https://github.com/wso2/msf4j/blob/master/samples/metrics-httpmon/metrics-httpmon-fatjar/src/main/java/org/wso2/msf4j/example/Application.java#L36
>>> [3]
>>> https://github.com/wso2/msf4j/blob/master/analytics/msf4j-analytics/src/main/java/org/wso2/msf4j/analytics/httpmonitoring/HTTPMonitoringDataPublisher.java#L182
>>>
>>> Thanks and Regards.
>>>
>>> --
>>> *Sabra Ossen*
>>> *Software Engineer*
>>> Email: sa...@wso2.com
>>> Mobile: +94 767 837356
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *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 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> Isuru Perera
> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>



-- 
*Sabra Ossen*
*Software Engineer*
Email: sa...@wso2.com
Mobile: +94 767 837356
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fwd: GSOC2016: [ML][CEP] Predictive analytic with online data for WSO2 Machine Learner

[Maheshakya Wijewardena]

Also note that there is a calculation interval in the siddhi time series
regression function[1]. You maybe able get some insight for this from that
as well.

[1] https://docs.wso2.com/display/CEP400/Regression

On Tue, May 24, 2016 at 11:03 AM, Maheshakya Wijewardena <
mahesha...@wso2.com> wrote:

> Hi Mahesh,
>
> As we discussed offline, we can use similar mechanism to train linear
> regression models, logistic regression models and k-means clustering models.
>
> It is very interesting that i have found that somethings that can make use
>> of our work. In the cep 4.0 documentation there is a Custom Stream
>> Processor Extention program [1]. There is a example of
>> LinearRegressionStreamProcessor [1].
>>
>
> As we have to train predictive models with Spark, you can write wrappers
> around regression/clustering models of Spark. Refer to Siddhi time series
> regression source codes[1][2]. You can write a streaming linear regression
> class for ML in a similar fashion by wrapping Spark mllib implementations.
> You can use the methods "addEvent", "removeEvent", etc. (may have to be
> changed according to requirements) for the similar purpose. You can
> introduce trainLinearRegression/LogisticRegression/Kmeans which does a
> similar thing as in createLinearRegression in those time series functions.
> In the processData method you can use Spark mllib classes to actually train
> models and return the model weights, evaluation metrics. So, converting
> streams into RDDs and retrieving information from the trained models shall
> happen in this method.
>
> In the stream processor extension example, you can retrieve those values
> then use them to train new models with new batches. Weights/cluster centers
> maybe passed as initialization parameters for the wrappers.
>
> Please note that we have to figure out the best siddhi extension type for
> this process. In the siddhi query, we define batch size, type of algorithm
> and number of features (there can be more). After batch size number of
> events received, train a model and save parameters, return evaluation
> metric. With the next batch, retrain the model initialized with previously
> learned parameters.
>
> We also may need to test the same scenario with a moving window, but I
> suspect that that approach may become so slow as a model is trained each
> time an event is received. So, we may have to change the number of slots
> the moving window moves at a time (eg: not one by one, but ten by ten).
>
> Once this is resolved, majority of the research part will be finished and
> all we will be left to do is implementing wrappers around the 3 learning
> algorithms we consider.
>
> Best regards.
>
> [1]
> https://github.com/wso2/siddhi/blob/master/modules/siddhi-extensions/timeseries/src/main/java/org/wso2/siddhi/extension/timeseries/linreg/RegressionCalculator.java
> [2]
> https://github.com/wso2/siddhi/blob/master/modules/siddhi-extensions/timeseries/src/main/java/org/wso2/siddhi/extension/timeseries/linreg/SimpleLinearRegressionCalculator.java
>
>
> On Sat, May 21, 2016 at 2:55 PM, Mahesh Dananjaya <
> dananjayamah...@gmail.com> wrote:
>
>> Hi Maheshkya,
>> shall we use [1] for our work? i am checking the possibility.
>> BR,
>> Mahesh.
>> [1]
>> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Stream+Processor+Extension
>> [2]
>> https://docs.wso2.com/display/CEP400/Inbuilt+Windows#InbuiltWindows-lengthlength
>> [3]
>> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Aggregate+Function
>>
>> On Sat, May 21, 2016 at 2:44 PM, Mahesh Dananjaya <
>> dananjayamah...@gmail.com> wrote:
>>
>>> Hi Maheshakya,
>>> It is very interesting that i have found that somethings that can make
>>> use of our work. In the cep 4.0 documentation there is a Custom Stream
>>> Processor Extention program [1]. There is a example of
>>> LinearRegressionStreamProcessor [1] and also i saw
>>>  private int batchSize = 10; i am going through this one.
>>> Please check whether we can use. WIll there be any compatibility or
>>> support issue?
>>> regards,
>>> Mahesh.
>>>
>>>
>>> [1]
>>> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Stream+Processor+Extension
>>>
>>> On Sat, May 21, 2016 at 11:52 AM, Mahesh Dananjaya <
>>> dananjayamah...@gmail.com> wrote:
>>>
 Hi maheshakya,
 anyway how can test any siddhi extention after write it without
 integrating it to cep.can you please explain me the procedure. i am
 referring to [1] [2] [3] [4].  thank you.
 BR,
 Mahesh.

 [1] https://docs.wso2.com/display/CEP310/Writing+Extensions+to+Siddhi
 [2] https://docs.wso2.com/display/CEP310/Writing+a+Custom+Function
 [3] https://docs.wso2.com/display/CEP310/Writing+a+Custom+Window
 [4] https://docs.wso2.com/display/CEP400/Writing+Extensions+to+Siddhi

 On Thu, May 19, 2016 at 12:08 PM, Mahesh Dananjaya <
 dananjayamah...@gmail.com> wrote:

> Hi Maheshakya,
> thank you for the feedback. I have add data-sets into repo.

Re: [Dev] [MSF4J] Clarification on debugging a micro service

[Isuru Perera]

Hi,

All HTTP events are published via HTTPMonitoringDataPublisher
.
So, the IDE should stop at that debug point. So, there must be something
wrong. Which IDE are you using?

On Mon, May 23, 2016 at 5:53 PM, Afkham Azeez  wrote:

> +isuru
>
> On Fri, May 20, 2016 at 2:01 PM, Sabra Ossen  wrote:
>
>> Hi All,
>>
>> I am trying the example in [1] and trying to debug the micro service and
>> identify details of events being published to WSO2 DAS. I set a debug point
>> in [2] and I could see that the HTTPMonitoringInterceptor is initialized
>> and then the HTTPMonitoringDataPublisher is initialized.
>>
>> The data has been published to the DAS. But during debugging the code
>> doesn't reach debug point [3] when I invoke the micro service.
>>
>> Am I debugging the micro service correctly. Any clarification on the
>> issue is appreciated.
>>
>> [1]
>> https://github.com/wso2/msf4j/tree/master/samples/metrics-httpmon/metrics-httpmon-fatjar
>> [2]
>> https://github.com/wso2/msf4j/blob/master/samples/metrics-httpmon/metrics-httpmon-fatjar/src/main/java/org/wso2/msf4j/example/Application.java#L36
>> [3]
>> https://github.com/wso2/msf4j/blob/master/analytics/msf4j-analytics/src/main/java/org/wso2/msf4j/analytics/httpmonitoring/HTTPMonitoringDataPublisher.java#L182
>>
>> Thanks and Regards.
>>
>> --
>> *Sabra Ossen*
>> *Software Engineer*
>> Email: sa...@wso2.com
>> Mobile: +94 767 837356
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *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 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 
Isuru Perera
Associate Technical Lead | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
Contact: +IsuruPereraWSO2 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fwd: GSOC2016: [ML][CEP] Predictive analytic with online data for WSO2 Machine Learner

[Maheshakya Wijewardena]

Hi Mahesh,

As we discussed offline, we can use similar mechanism to train linear
regression models, logistic regression models and k-means clustering models.

It is very interesting that i have found that somethings that can make use
> of our work. In the cep 4.0 documentation there is a Custom Stream
> Processor Extention program [1]. There is a example of
> LinearRegressionStreamProcessor [1].
>

As we have to train predictive models with Spark, you can write wrappers
around regression/clustering models of Spark. Refer to Siddhi time series
regression source codes[1][2]. You can write a streaming linear regression
class for ML in a similar fashion by wrapping Spark mllib implementations.
You can use the methods "addEvent", "removeEvent", etc. (may have to be
changed according to requirements) for the similar purpose. You can
introduce trainLinearRegression/LogisticRegression/Kmeans which does a
similar thing as in createLinearRegression in those time series functions.
In the processData method you can use Spark mllib classes to actually train
models and return the model weights, evaluation metrics. So, converting
streams into RDDs and retrieving information from the trained models shall
happen in this method.

In the stream processor extension example, you can retrieve those values
then use them to train new models with new batches. Weights/cluster centers
maybe passed as initialization parameters for the wrappers.

Please note that we have to figure out the best siddhi extension type for
this process. In the siddhi query, we define batch size, type of algorithm
and number of features (there can be more). After batch size number of
events received, train a model and save parameters, return evaluation
metric. With the next batch, retrain the model initialized with previously
learned parameters.

We also may need to test the same scenario with a moving window, but I
suspect that that approach may become so slow as a model is trained each
time an event is received. So, we may have to change the number of slots
the moving window moves at a time (eg: not one by one, but ten by ten).

Once this is resolved, majority of the research part will be finished and
all we will be left to do is implementing wrappers around the 3 learning
algorithms we consider.

Best regards.

[1]
https://github.com/wso2/siddhi/blob/master/modules/siddhi-extensions/timeseries/src/main/java/org/wso2/siddhi/extension/timeseries/linreg/RegressionCalculator.java
[2]
https://github.com/wso2/siddhi/blob/master/modules/siddhi-extensions/timeseries/src/main/java/org/wso2/siddhi/extension/timeseries/linreg/SimpleLinearRegressionCalculator.java


On Sat, May 21, 2016 at 2:55 PM, Mahesh Dananjaya  wrote:

> Hi Maheshkya,
> shall we use [1] for our work? i am checking the possibility.
> BR,
> Mahesh.
> [1]
> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Stream+Processor+Extension
> [2]
> https://docs.wso2.com/display/CEP400/Inbuilt+Windows#InbuiltWindows-lengthlength
> [3]
> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Aggregate+Function
>
> On Sat, May 21, 2016 at 2:44 PM, Mahesh Dananjaya <
> dananjayamah...@gmail.com> wrote:
>
>> Hi Maheshakya,
>> It is very interesting that i have found that somethings that can make
>> use of our work. In the cep 4.0 documentation there is a Custom Stream
>> Processor Extention program [1]. There is a example of
>> LinearRegressionStreamProcessor [1] and also i saw
>>  private int batchSize = 10; i am going through this one.
>> Please check whether we can use. WIll there be any compatibility or
>> support issue?
>> regards,
>> Mahesh.
>>
>>
>> [1]
>> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Stream+Processor+Extension
>>
>> On Sat, May 21, 2016 at 11:52 AM, Mahesh Dananjaya <
>> dananjayamah...@gmail.com> wrote:
>>
>>> Hi maheshakya,
>>> anyway how can test any siddhi extention after write it without
>>> integrating it to cep.can you please explain me the procedure. i am
>>> referring to [1] [2] [3] [4].  thank you.
>>> BR,
>>> Mahesh.
>>>
>>> [1] https://docs.wso2.com/display/CEP310/Writing+Extensions+to+Siddhi
>>> [2] https://docs.wso2.com/display/CEP310/Writing+a+Custom+Function
>>> [3] https://docs.wso2.com/display/CEP310/Writing+a+Custom+Window
>>> [4] https://docs.wso2.com/display/CEP400/Writing+Extensions+to+Siddhi
>>>
>>> On Thu, May 19, 2016 at 12:08 PM, Mahesh Dananjaya <
>>> dananjayamah...@gmail.com> wrote:
>>>
 Hi Maheshakya,
 thank you for the feedback. I have add data-sets into repo.
 data-sets/lr. I am all right with next week.Now i am writing some examples
 to collect samples and build mini batches and run the algorithms on those
 mini-batches. thank you. will add those into repo soon.I am still working
 on that siddhi extention.i will let you know the progress.
 BR,
 mahesh.

 On Thu, May 19, 2016 at 11:10 AM, Maheshakya Wijewardena <
 mahesha...@wso2.com> wrote:

> Hi 

Re: [Dev] [DEV][Vote] Release WSO2 Puppet Modules 2.0.0

[Thushara Ranawaka]

Hi Everyone,

Tested the default deployment for G-Reg 5.1.0 and went through
configuration and found no blocking issues.

[X] Stable - Go ahead and release

Thanks,
Thushara.


On Tue, May 24, 2016 at 9:48 AM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi
>
> *[X] Stable* - go ahead and release
>
> verified the following.
>
>- README Files
>- License Headers
>
> Tested the default and kubernetes deployment for the following products
> puppet modules.
>
>- WSO2 BPS
>- WSO2 ESB
>- WSO2 AS
>
>
> On Wed, May 18, 2016 at 10:24 PM, Chamila De Alwis 
> wrote:
>
>> Hi,
>>
>>
>> This is the first release candidate (RC1) for WSO2 Puppet Modules 2.0.0.
>> Please download, verify, and vote. Voting will be open for 72 hours.
>>
>> [ ] Broken - Do not release (explain why)
>>
>> [ ] Stable - Go ahead and release
>>
>> Main features and fixes released with this release:
>>
>>-
>>
>>Updated Hiera data hierarchy to include deployment Platform
>>-
>>
>>Kubernetes based workflow supported, based on
>>wso2/kubernetes-artifacts
>>-
>>
>>system_file_list to copy files with scope outside of CARBON_HOME
>>-
>>
>>Platform specific configuration data sets for Kubernetes
>>-
>>
>>   Kubernetes deployment-ready Puppet modules
>>   -
>>
>>   Data sources matching a distributed set of Kubernetes MySQL
>>   Services
>>   -
>>
>>Streamlined Default platform YAML configuration data
>>-
>>
>>Optional update flags to control product pack and JDK cleanup
>>-
>>
>>Minor fixes on the Hiera data
>>-
>>
>>   Issues in YAML file formatting
>>   -
>>
>>   Puppet templates for identity.xml added to relevant products
>>   -
>>
>>   Proxy Port values assigned to different products are streamlined
>>   -
>>
>>   Hostname entries streamlined in default deployment platform data
>>   set
>>   -
>>
>>   Pass Through Port Mapping for WSO2 ESB
>>   -
>>
>>   Fixing Thrift Server IP configuration for WSO2 MB
>>   -
>>
>>   SecureVault parameters made optional
>>   -
>>
>>   Reusing Data Source related fields in YAML by inheriting from
>>   wso2/common.yaml
>>   -
>>
>>   Fix Symbolic Link creation in WSO2 DAS
>>   -
>>
>>   Fixed installation directory creation failure when parent
>>   directory doesn’t exist
>>   -
>>
>>   Removed use of Kubernetes Master details in Clustering templates
>>   -
>>
>>   Streamlined use of hiera, hiera_array, and hiera_hash lookup
>>   -
>>
>>WSO2 API Manager Gateway Manager-Worker separate profiles in Hieradata
>>-
>>
>>WSO2 PPaaS Puppet module and Hiera data removed
>>-
>>
>>Deprecated older product versions
>>-
>>
>>   WSO2 AM 1.9.1
>>   -
>>
>>   WSO2 BRS 2.1.0
>>   -
>>
>>   WSO2 GREG 4.6.0
>>   -
>>
>>   WSO2 IS 5.0.0
>>   -
>>
>>   WSO2 MB 3.0.0
>>   -
>>
>>Improve Puppet Vagrant setup to use PUPPET_HOME environment variable
>>-
>>
>>Included sample config.yaml files in the Puppet Vagrant setup to
>>quickly test standalone and distributed deployments
>>-
>>
>>Fixed Java System Prefs location issue
>>-
>>
>>Included YAML Style Guide for Hiera data files
>>
>>
>>
>> This release is based on the following tag:
>>
>> https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1
>>
>> Release verification guide can be found at:
>>
>> https://docs.wso2.com/display/PM200/Setting+up+the+Development+Environment
>>
>> Source and distribution packages can be downloaded at:
>>
>> https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel  : +94 112 145 345
> a nurudd...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks,
Thushara Kasun Ranawaka
Software Engineer
WSO2 Inc.; 
lean.enterprise.middleware
Mobile : *+94 (0) 773438949*
*thusha...@wso2.com *
___
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

[Supun Sethunga]

Hi Lakini,

Yes you can use any of them, with open source licence. But I would prefer
JQueryUI, as its a well known library, and is already been used by some of
the wso2 products.

Regards,
Supun

On Tue, May 24, 2016 at 9:29 AM, Lakini Senanayaka <
lakinisenanayak...@gmail.com> wrote:

> Hi,
>
> I have found some libraries to build drag and drop UI for our front end
> .They are JQury UI[1],Dragula[2],Draggablily[3].
> I hope I can do the developments using these libraries.
>
> [1]jqueryui 
> [2]dragula 
> [3]draggabilly 
>
> Could you please tell me if you have any other suggestions?
>
> On Sat, May 21, 2016 at 11:05 PM, Lakini Senanayaka <
> lakinisenanayak...@gmail.com> wrote:
>
>> Hi ,
>>
>> This is my weekly progress update of my project.
>>
>> I have solved all the problems I have mentioned  in the last email.I
>> could find a class BaseDatasetIterator which is in DL4J where we can find
>> inbuilt iterators for CurvesDataSetIterator, IrisDataSetIterator,
>> MnistDataSetIterator, MovingWindowBaseDataSetIterator,
>> RawMnistDataSetIterator .There is no iterator for CIFAR dataset yet.
>>
>> I have gone through the whole documentation except Deeplearning4j on
>> Spark.The latest documentation is very understandable than the earlier
>> one.I have studied neural networks-  Restricted Boltzmann Machines,
>> Convolutional Nets (ConvNets),
>> Long Short-Term Memory Units (LSTMs),
>> Denoising Autoencoders,
>> Recurrent Nets and LSTMs,
>> Multilayer Neural Nets,
>> Deep-Belief Network,
>> Deep AutoEncoder,
>> Stacked Denoising Autoencoders
>>
>> I have run the example codes[1] and I have understood the
>> implementations.I have rerun the codes with modifying different parameter
>> values like number and size of the hidden layers,  learning rate, momentum,
>> weight distribution and various types of regularization and checked the
>> performance.
>>
>> I have implemented a convolution net[3] and trained it using LFW
>> dataset[2] and a Recurrent net[4].Still I have a problem in vectorizing
>> CIFRA-10 data set.
>>
>> Currently  I am researching about  libraries to build drag & drop UI for
>> front end.
>>
>> [1]dl4j-0.4-examples
>> 
>> [2]LFW Face Dataset 
>> [3]ConvolutionNetLFW
>> 
>> [4]RecurrentNetworkExample
>> 
>>
>>
>> Could you please guide me to do the next step of my project .
>>
>> Thank you.
>>
>> Sincerely,
>> *Lakini Senanayaka.*
>>
>>
>
>
> --
> Thank you.
>
> Sincerely,
> *Lakini Senanayaka.*
>
>


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

Re: [Dev] Too much noise during MSF4J startup (master branch)

[Senduran Balasubramaniyam]

Hi Azeez,

All the above logs (the verbose ones) are in debug level. Also the log4j
properties rootLogger level is set to INFO. So it is unclear why does those
logs are appears at the start up.
I will try to find the cause.

Regards
Senduran



On Tue, May 24, 2016 at 12:24 AM, Afkham Azeez  wrote:

> [org.wso2.carbon.transport.http.netty.listener.NettyListener] : Starting
> Netty Http Transport Listener
>
> [io.netty.util.internal.logging.InternalLoggerFactory] : Using SLF4J as
> the default logging framework
>
> [io.netty.channel.MultithreadEventLoopGroup] :
> -Dio.netty.eventLoopThreads: 16
>
> [io.netty.util.internal.PlatformDependent0] : java.nio.Buffer.address:
> available
>
> [io.netty.util.internal.PlatformDependent0] : sun.misc.Unsafe.theUnsafe:
> available
>
> [io.netty.util.internal.PlatformDependent0] : sun.misc.Unsafe.copyMemory:
> available
>
> [io.netty.util.internal.PlatformDependent0] : java.nio.Bits.unaligned: true
>
> [io.netty.util.internal.PlatformDependent] : Java version: 8
>
> [io.netty.util.internal.PlatformDependent] : -Dio.netty.noUnsafe: false
>
> [io.netty.util.internal.PlatformDependent] : sun.misc.Unsafe: available
>
> [io.netty.util.internal.PlatformDependent] : -Dio.netty.noJavassist: false
>
> [io.netty.util.internal.PlatformDependent] : Javassist: available
>
> [io.netty.util.internal.PlatformDependent] : -Dio.netty.tmpdir:
> /var/folders/9c/f5j0x_mx6xsgx06x63sl6410gn/T (java.io.tmpdir)
>
> [io.netty.util.internal.PlatformDependent] : -Dio.netty.bitMode: 64
> (sun.arch.data.model)
>
> [io.netty.util.internal.PlatformDependent] : -Dio.netty.noPreferDirect:
> false
>
> [io.netty.channel.nio.NioEventLoop] : -Dio.netty.noKeySetOptimization:
> false
>
> [io.netty.channel.nio.NioEventLoop] :
> -Dio.netty.selectorAutoRebuildThreshold: 512
>
> [org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty Boss
> group size io.netty.channel.nio.NioEventLoopGroup@396a51ab
>
> [org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
> Worker group Sizeio.netty.channel.nio.NioEventLoopGroup@51081592
>
> [org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
> Server Socket BACKLOG 100
>
> [org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
> Server Socket TCP_NODELAY true
>
> [org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
> Server Socket SO_KEEPALIVE true
>
> [org.wso2.carbon.transport.http.netty.listener.NettyListener] :  Netty
> Server Socket CONNECT_TIMEOUT_MILLIS 15000
>
> [org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
> Server Socket SO_SNDBUF 1048576
>
> [org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
> Server Socket SO_RCVBUF 1048576
>
> [org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
> Server Socket SO_RCVBUF 1048576
>
> [org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
> Server Socket SO_SNDBUF 1048576
>
> [org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
> : connection.pool.count: 0
>
> [org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
> : max.active.connections.per.pool:-1
>
> [org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
> : min.idle.connections.per.pool:100
>
> [org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
> : max.idle.connections.per.pool:100
>
> [org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
> : min.eviction.idle.time:30
>
> [org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
> : sender.thread.count:20
>
> [org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
> : Time between Evictions Runs:3
>
> [org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
> : Pool exhausted action:2
>
> [org.wso2.carbon.transport.http.netty.listener.CarbonNettyServerInitializer]
> : Disruptor is disabled and using executor thread pool with size of 1024
>
> [io.netty.util.internal.ThreadLocalRandom] :
> -Dio.netty.initialSeedUniquifier: 0x8fc366dfb69a63b3 (took 27 ms)
>
> [io.netty.buffer.ByteBufUtil] : -Dio.netty.allocator.type: unpooled
>
> [io.netty.buffer.ByteBufUtil] : -Dio.netty.threadLocalDirectBufferSize:
> 65536
>
> [io.netty.util.NetUtil] : Loopback interface: lo0 (lo0, 0:0:0:0:0:0:0:1)
>
> [io.netty.util.NetUtil] : /proc/sys/net/core/somaxconn: 128 (non-existent)
>
> --
> *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 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . 

Re: [Dev] [APIM] Loading different configurations with different profiles

[Niranjan Karunanandham]

Hi Amila,

On Tue, May 24, 2016 at 10:03 AM, Amila De Silva  wrote:

> Hi All,
>
> Need to know if $subject is possible with kernel 4.4.6.
>
> For API Manager 2.0.0 we are creating a new profile which will only have
> CEP and MB features. This profile doesn't need to have all the transports
> (PT) message builders/formatters and axis2 handlers needed by the standard
> APIM components. But if we are going to use the same axis2.xml (which is
> shipped with the product by default) with the new profile, we'd have to add
> unnecessary features with the new profile, just to start up the server
> without any problems. If it's possible to load a config file specific to a
> profile, then we can make the profile more lean.
>
AFAIK this is not possible. Using the carbon-p2-plugin, it only defines the
components in the Bundles.info for that profile, but inorder to read
different configuration files based on the profile requires to come from
the component.


>
>
> --
> *Amila De Silva*
>
> WSO2 Inc.
> mobile :(+94) 775119302
>
>
Regards,
Nira

-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM] Loading different configurations with different profiles

[Amila De Silva]

Hi All,

Need to know if $subject is possible with kernel 4.4.6.

For API Manager 2.0.0 we are creating a new profile which will only have
CEP and MB features. This profile doesn't need to have all the transports
(PT) message builders/formatters and axis2 handlers needed by the standard
APIM components. But if we are going to use the same axis2.xml (which is
shipped with the product by default) with the new profile, we'd have to add
unnecessary features with the new profile, just to start up the server
without any problems. If it's possible to load a config file specific to a
profile, then we can make the profile more lean.

-- 
*Amila De Silva*

WSO2 Inc.
mobile :(+94) 775119302
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AppCloud] [APPCLOUD-24] Streaming logs in application log page

[Danushka Fernando]

Currently we have a page to load all logs. With Streaming I guess we need
to go for tailing certain amount of time could be preconfigured and later
we can let the user configure the time he wants to tail.
There are two options
Keep current full log option and stream last no of lines of the log in a
separate page (That means have two log watching places one for full log and
other for tailing last 5 mins)
or
Keep only tailing logs option.
IMO we need both options. WDYT?

Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729

On Fri, May 20, 2016 at 9:53 PM, Kasun De Silva  wrote:

> Hi Danushka,
>
> Streaming log option is similar to tailf in unix systems. I guess you
> application is not actively producing any logs. That might be the reason
> you don't get any output or experiencing this.
>
> First I would try following kube command in k8s console against my
> respective pod.
>
> # Begin streaming the logs of a pod
> ./kubectl logs -f 
>
> Go to 249 or 251 and try that. You can try more options as mentioned in
> [3]. but make sure you have the "*-f "* option.
>
> Also you can try [1] from you browser against 249 or 251, that is the
> direct api call to the k8s to get streaming of the logs. This is the same
> call that is generated by the fabric8 when we are invoking streamRuntimeLogs()
> method.
>
> Also I would have a web app that actively generate logs to test this
> option. Something like [2]. You can just download the war file from [2] and
> deploy it in AppCloud setup you are testing. Then just hit "
> */logme*" from the browser and the application will start
> generate logs continuously. This kind of application will help you test
> this feature.
>
>
> Finally I would try to see whether if we can pass tailing lines or 
> .sinceSeconds()
> or .tailingLines() options to streamRuntimeLogs() builder pattern, better
> if something like .tailingLines(10) then streaming will always starts
> with last 10 lines. In that case we need to modify the back end code
> similar to "getRuntimeLogs(LogQuery query)" method.
>
> This is something I would try at the very end, if everything goes smoothly
> above.
>
> Hope this information is helpful to you regarding this JIRA. Let me know
> if you have any concerns.
>
>
> [1] http://*:*/api/v1/namespaces/**/pods/
> **/log?container=tomcat-server&*follow=true*
> =false=false
>
> [2]
> https://github.com/kasundsilva/jsp-loggin/tree/master/sample.log.app.one/target
>
> [3] http://kubernetes.io/docs/user-guide/kubectl/kubectl_logs/
>
>
> Thanks
> Kasun
>
> *Kasun de Silva*
> Software Engineer
>
> WSO2 Inc *. *|* E*mail : kas...@wso2.com | Mobile: +94
> 77 794 4260
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][Vote] Release WSO2 Puppet Modules 2.0.0

[Anuruddha Liyanarachchi]

Hi

*[X] Stable* - go ahead and release

verified the following.

   - README Files
   - License Headers

Tested the default and kubernetes deployment for the following products
puppet modules.

   - WSO2 BPS
   - WSO2 ESB
   - WSO2 AS


On Wed, May 18, 2016 at 10:24 PM, Chamila De Alwis 
wrote:

> Hi,
>
>
> This is the first release candidate (RC1) for WSO2 Puppet Modules 2.0.0.
> Please download, verify, and vote. Voting will be open for 72 hours.
>
> [ ] Broken - Do not release (explain why)
>
> [ ] Stable - Go ahead and release
>
> Main features and fixes released with this release:
>
>-
>
>Updated Hiera data hierarchy to include deployment Platform
>-
>
>Kubernetes based workflow supported, based on wso2/kubernetes-artifacts
>-
>
>system_file_list to copy files with scope outside of CARBON_HOME
>-
>
>Platform specific configuration data sets for Kubernetes
>-
>
>   Kubernetes deployment-ready Puppet modules
>   -
>
>   Data sources matching a distributed set of Kubernetes MySQL Services
>   -
>
>Streamlined Default platform YAML configuration data
>-
>
>Optional update flags to control product pack and JDK cleanup
>-
>
>Minor fixes on the Hiera data
>-
>
>   Issues in YAML file formatting
>   -
>
>   Puppet templates for identity.xml added to relevant products
>   -
>
>   Proxy Port values assigned to different products are streamlined
>   -
>
>   Hostname entries streamlined in default deployment platform data set
>   -
>
>   Pass Through Port Mapping for WSO2 ESB
>   -
>
>   Fixing Thrift Server IP configuration for WSO2 MB
>   -
>
>   SecureVault parameters made optional
>   -
>
>   Reusing Data Source related fields in YAML by inheriting from
>   wso2/common.yaml
>   -
>
>   Fix Symbolic Link creation in WSO2 DAS
>   -
>
>   Fixed installation directory creation failure when parent directory
>   doesn’t exist
>   -
>
>   Removed use of Kubernetes Master details in Clustering templates
>   -
>
>   Streamlined use of hiera, hiera_array, and hiera_hash lookup
>   -
>
>WSO2 API Manager Gateway Manager-Worker separate profiles in Hieradata
>-
>
>WSO2 PPaaS Puppet module and Hiera data removed
>-
>
>Deprecated older product versions
>-
>
>   WSO2 AM 1.9.1
>   -
>
>   WSO2 BRS 2.1.0
>   -
>
>   WSO2 GREG 4.6.0
>   -
>
>   WSO2 IS 5.0.0
>   -
>
>   WSO2 MB 3.0.0
>   -
>
>Improve Puppet Vagrant setup to use PUPPET_HOME environment variable
>-
>
>Included sample config.yaml files in the Puppet Vagrant setup to
>quickly test standalone and distributed deployments
>-
>
>Fixed Java System Prefs location issue
>-
>
>Included YAML Style Guide for Hiera data files
>
>
>
> This release is based on the following tag:
>
> https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1
>
> Release verification guide can be found at:
>
> https://docs.wso2.com/display/PM200/Setting+up+the+Development+Environment
>
> Source and distribution packages can be downloaded at:
>
> https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel  : +94 112 145 345
a nurudd...@wso2.com
___
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

[Lakini Senanayaka]

Hi,

I have found some libraries to build drag and drop UI for our front end
.They are JQury UI[1],Dragula[2],Draggablily[3].
I hope I can do the developments using these libraries.

[1]jqueryui 
[2]dragula 
[3]draggabilly 

Could you please tell me if you have any other suggestions?

On Sat, May 21, 2016 at 11:05 PM, Lakini Senanayaka <
lakinisenanayak...@gmail.com> wrote:

> Hi ,
>
> This is my weekly progress update of my project.
>
> I have solved all the problems I have mentioned  in the last email.I could
> find a class BaseDatasetIterator which is in DL4J where we can find inbuilt
> iterators for CurvesDataSetIterator, IrisDataSetIterator,
> MnistDataSetIterator, MovingWindowBaseDataSetIterator,
> RawMnistDataSetIterator .There is no iterator for CIFAR dataset yet.
>
> I have gone through the whole documentation except Deeplearning4j on
> Spark.The latest documentation is very understandable than the earlier
> one.I have studied neural networks-  Restricted Boltzmann Machines,
> Convolutional Nets (ConvNets),
> Long Short-Term Memory Units (LSTMs),
> Denoising Autoencoders,
> Recurrent Nets and LSTMs,
> Multilayer Neural Nets,
> Deep-Belief Network,
> Deep AutoEncoder,
> Stacked Denoising Autoencoders
>
> I have run the example codes[1] and I have understood the
> implementations.I have rerun the codes with modifying different parameter
> values like number and size of the hidden layers,  learning rate, momentum,
> weight distribution and various types of regularization and checked the
> performance.
>
> I have implemented a convolution net[3] and trained it using LFW
> dataset[2] and a Recurrent net[4].Still I have a problem in vectorizing
> CIFRA-10 data set.
>
> Currently  I am researching about  libraries to build drag & drop UI for
> front end.
>
> [1]dl4j-0.4-examples 
> [2]LFW Face Dataset 
> [3]ConvolutionNetLFW
> 
> [4]RecurrentNetworkExample
> 
>
>
> Could you please guide me to do the next step of my project .
>
> Thank you.
>
> Sincerely,
> *Lakini Senanayaka.*
>
>


-- 
Thank you.

Sincerely,
*Lakini Senanayaka.*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][Vote] Release WSO2 Puppet Modules 2.0.0

[Isuru Haththotuwa]

Verified the following:

   1. License verification using the release tag
   2. Testing of the following products on default and K8s platforms:
  - APIM 1.10.0
  - ES 2.0.0
  - CEP 4.0.0

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

On Tue, May 24, 2016 at 6:23 AM, Chamila Wijayarathna 
wrote:

> Tested APIM 1.10.0 installation in different profiles in default platform,
> No blocking issues found.
>
> *[X ] Stable* - go ahead and release
>
> On Mon, May 23, 2016 at 4:14 PM, Vishanth Balasubramaniam <
> vishan...@wso2.com> wrote:
>
>> *[X ] Stable* - go ahead and release
>>
>> I have verified the following.
>>
>>- READMEs
>>- License
>>- Packaging
>>
>> Tested the Default and Kubenetes platform for the following products
>>
>>- WSO2 AS
>>- WSO2 BPS
>>- WSO2 BRS
>>- WSO2 ESB
>>- WSO2 GREG
>>- WSO2 IS
>>
>> Regards,
>> Vishanth
>>
>>
>> On Mon, May 23, 2016 at 10:24 PM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> [x] Stable - Go ahead and release
>>>
>>> Tested following on both default and K8S platforms;
>>>  - WSO2 APIM 1.10.0
>>>  - WSO2 DAS 3.0.1
>>>  - WSO2 CEP 4.0.0
>>>
>>> On Mon, May 23, 2016 at 9:28 PM, Thanuja Uruththirakodeeswaran <
>>> thanu...@wso2.com> wrote:
>>>
 [x] Stable - Go ahead and release

 Verified the following:

 1. License header
 2. Packaging
 3. Tested below wso2 products default and distributed deployments in
 default and kubernetes 1.2.0 platform and verified the basic
 functionalities:


- WSO2 BPS 3.5.0
- WSO2 ES 2.0.0
- WSO2 GREG 5.1.0


 Thanks.

 On Mon, May 23, 2016 at 9:14 PM, Imesh Gunaratne 
 wrote:

> +1 for the release, I verified following:
>
>- README files
>- Distributed deployments of following products on K8S using
>Docker images built using Puppet:
>
>
>- Application Server 5.3.0
>   - API Manager 1.10.0
>   - Enterprise Service Bus 4.9.0
>   - Business Process Server 3.5.0
>   - Business Rules Server 2.2.0
>   - Data Services Server 3.5.0
>   - Enterprise Store 2.0.0
>   - Governance Registry 5.1.0
>   - Data Analytics Server 3.0.1
>   - Complex Event Processor 4.0.0
>
> Thanks
>
> On Wed, May 18, 2016 at 10:24 PM, Chamila De Alwis 
> wrote:
>
>> Hi,
>>
>>
>> This is the first release candidate (RC1) for WSO2 Puppet Modules
>> 2.0.0. Please download, verify, and vote. Voting will be open for 72 
>> hours.
>>
>> [ ] Broken - Do not release (explain why)
>>
>> [ ] Stable - Go ahead and release
>>
>> Main features and fixes released with this release:
>>
>>-
>>
>>Updated Hiera data hierarchy to include deployment Platform
>>-
>>
>>Kubernetes based workflow supported, based on
>>wso2/kubernetes-artifacts
>>-
>>
>>system_file_list to copy files with scope outside of CARBON_HOME
>>-
>>
>>Platform specific configuration data sets for Kubernetes
>>-
>>
>>   Kubernetes deployment-ready Puppet modules
>>   -
>>
>>   Data sources matching a distributed set of Kubernetes MySQL
>>   Services
>>   -
>>
>>Streamlined Default platform YAML configuration data
>>-
>>
>>Optional update flags to control product pack and JDK cleanup
>>-
>>
>>Minor fixes on the Hiera data
>>-
>>
>>   Issues in YAML file formatting
>>   -
>>
>>   Puppet templates for identity.xml added to relevant products
>>   -
>>
>>   Proxy Port values assigned to different products are
>>   streamlined
>>   -
>>
>>   Hostname entries streamlined in default deployment platform
>>   data set
>>   -
>>
>>   Pass Through Port Mapping for WSO2 ESB
>>   -
>>
>>   Fixing Thrift Server IP configuration for WSO2 MB
>>   -
>>
>>   SecureVault parameters made optional
>>   -
>>
>>   Reusing Data Source related fields in YAML by inheriting from
>>   wso2/common.yaml
>>   -
>>
>>   Fix Symbolic Link creation in WSO2 DAS
>>   -
>>
>>   Fixed installation directory creation failure when parent
>>   directory doesn’t exist
>>   -
>>
>>   Removed use of Kubernetes Master details in Clustering
>>   templates
>>   -
>>
>>   Streamlined use of hiera, hiera_array, and hiera_hash lookup
>>   -
>>
>>WSO2 API Manager Gateway Manager-Worker separate profiles in
>>Hieradata
>>-
>>
>>WSO2 PPaaS Puppet module and Hiera data 

Re: [Dev] [DEV][Vote] Release WSO2 Puppet Modules 2.0.0

[Chamila Wijayarathna]

Tested APIM 1.10.0 installation in different profiles in default platform,
No blocking issues found.

*[X ] Stable* - go ahead and release

On Mon, May 23, 2016 at 4:14 PM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:

> *[X ] Stable* - go ahead and release
>
> I have verified the following.
>
>- READMEs
>- License
>- Packaging
>
> Tested the Default and Kubenetes platform for the following products
>
>- WSO2 AS
>- WSO2 BPS
>- WSO2 BRS
>- WSO2 ESB
>- WSO2 GREG
>- WSO2 IS
>
> Regards,
> Vishanth
>
>
> On Mon, May 23, 2016 at 10:24 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> [x] Stable - Go ahead and release
>>
>> Tested following on both default and K8S platforms;
>>  - WSO2 APIM 1.10.0
>>  - WSO2 DAS 3.0.1
>>  - WSO2 CEP 4.0.0
>>
>> On Mon, May 23, 2016 at 9:28 PM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>> [x] Stable - Go ahead and release
>>>
>>> Verified the following:
>>>
>>> 1. License header
>>> 2. Packaging
>>> 3. Tested below wso2 products default and distributed deployments in
>>> default and kubernetes 1.2.0 platform and verified the basic
>>> functionalities:
>>>
>>>
>>>- WSO2 BPS 3.5.0
>>>- WSO2 ES 2.0.0
>>>- WSO2 GREG 5.1.0
>>>
>>>
>>> Thanks.
>>>
>>> On Mon, May 23, 2016 at 9:14 PM, Imesh Gunaratne  wrote:
>>>
 +1 for the release, I verified following:

- README files
- Distributed deployments of following products on K8S using Docker
images built using Puppet:


- Application Server 5.3.0
   - API Manager 1.10.0
   - Enterprise Service Bus 4.9.0
   - Business Process Server 3.5.0
   - Business Rules Server 2.2.0
   - Data Services Server 3.5.0
   - Enterprise Store 2.0.0
   - Governance Registry 5.1.0
   - Data Analytics Server 3.0.1
   - Complex Event Processor 4.0.0

 Thanks

 On Wed, May 18, 2016 at 10:24 PM, Chamila De Alwis 
 wrote:

> Hi,
>
>
> This is the first release candidate (RC1) for WSO2 Puppet Modules
> 2.0.0. Please download, verify, and vote. Voting will be open for 72 
> hours.
>
> [ ] Broken - Do not release (explain why)
>
> [ ] Stable - Go ahead and release
>
> Main features and fixes released with this release:
>
>-
>
>Updated Hiera data hierarchy to include deployment Platform
>-
>
>Kubernetes based workflow supported, based on
>wso2/kubernetes-artifacts
>-
>
>system_file_list to copy files with scope outside of CARBON_HOME
>-
>
>Platform specific configuration data sets for Kubernetes
>-
>
>   Kubernetes deployment-ready Puppet modules
>   -
>
>   Data sources matching a distributed set of Kubernetes MySQL
>   Services
>   -
>
>Streamlined Default platform YAML configuration data
>-
>
>Optional update flags to control product pack and JDK cleanup
>-
>
>Minor fixes on the Hiera data
>-
>
>   Issues in YAML file formatting
>   -
>
>   Puppet templates for identity.xml added to relevant products
>   -
>
>   Proxy Port values assigned to different products are streamlined
>   -
>
>   Hostname entries streamlined in default deployment platform
>   data set
>   -
>
>   Pass Through Port Mapping for WSO2 ESB
>   -
>
>   Fixing Thrift Server IP configuration for WSO2 MB
>   -
>
>   SecureVault parameters made optional
>   -
>
>   Reusing Data Source related fields in YAML by inheriting from
>   wso2/common.yaml
>   -
>
>   Fix Symbolic Link creation in WSO2 DAS
>   -
>
>   Fixed installation directory creation failure when parent
>   directory doesn’t exist
>   -
>
>   Removed use of Kubernetes Master details in Clustering templates
>   -
>
>   Streamlined use of hiera, hiera_array, and hiera_hash lookup
>   -
>
>WSO2 API Manager Gateway Manager-Worker separate profiles in
>Hieradata
>-
>
>WSO2 PPaaS Puppet module and Hiera data removed
>-
>
>Deprecated older product versions
>-
>
>   WSO2 AM 1.9.1
>   -
>
>   WSO2 BRS 2.1.0
>   -
>
>   WSO2 GREG 4.6.0
>   -
>
>   WSO2 IS 5.0.0
>   -
>
>   WSO2 MB 3.0.0
>   -
>
>Improve Puppet Vagrant setup to use PUPPET_HOME environment
>variable
>-
>
>Included sample config.yaml files in the Puppet Vagrant setup to
>quickly test standalone and 

Re: [Dev] [DEV][Vote] Release WSO2 Puppet Modules 2.0.0

[Vishanth Balasubramaniam]

*[X ] Stable* - go ahead and release

I have verified the following.

   - READMEs
   - License
   - Packaging

Tested the Default and Kubenetes platform for the following products

   - WSO2 AS
   - WSO2 BPS
   - WSO2 BRS
   - WSO2 ESB
   - WSO2 GREG
   - WSO2 IS

Regards,
Vishanth


On Mon, May 23, 2016 at 10:24 PM, Akila Ravihansa Perera  wrote:

> [x] Stable - Go ahead and release
>
> Tested following on both default and K8S platforms;
>  - WSO2 APIM 1.10.0
>  - WSO2 DAS 3.0.1
>  - WSO2 CEP 4.0.0
>
> On Mon, May 23, 2016 at 9:28 PM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> [x] Stable - Go ahead and release
>>
>> Verified the following:
>>
>> 1. License header
>> 2. Packaging
>> 3. Tested below wso2 products default and distributed deployments in
>> default and kubernetes 1.2.0 platform and verified the basic
>> functionalities:
>>
>>
>>- WSO2 BPS 3.5.0
>>- WSO2 ES 2.0.0
>>- WSO2 GREG 5.1.0
>>
>>
>> Thanks.
>>
>> On Mon, May 23, 2016 at 9:14 PM, Imesh Gunaratne  wrote:
>>
>>> +1 for the release, I verified following:
>>>
>>>- README files
>>>- Distributed deployments of following products on K8S using Docker
>>>images built using Puppet:
>>>
>>>
>>>- Application Server 5.3.0
>>>   - API Manager 1.10.0
>>>   - Enterprise Service Bus 4.9.0
>>>   - Business Process Server 3.5.0
>>>   - Business Rules Server 2.2.0
>>>   - Data Services Server 3.5.0
>>>   - Enterprise Store 2.0.0
>>>   - Governance Registry 5.1.0
>>>   - Data Analytics Server 3.0.1
>>>   - Complex Event Processor 4.0.0
>>>
>>> Thanks
>>>
>>> On Wed, May 18, 2016 at 10:24 PM, Chamila De Alwis 
>>> wrote:
>>>
 Hi,


 This is the first release candidate (RC1) for WSO2 Puppet Modules
 2.0.0. Please download, verify, and vote. Voting will be open for 72 hours.

 [ ] Broken - Do not release (explain why)

 [ ] Stable - Go ahead and release

 Main features and fixes released with this release:

-

Updated Hiera data hierarchy to include deployment Platform
-

Kubernetes based workflow supported, based on
wso2/kubernetes-artifacts
-

system_file_list to copy files with scope outside of CARBON_HOME
-

Platform specific configuration data sets for Kubernetes
-

   Kubernetes deployment-ready Puppet modules
   -

   Data sources matching a distributed set of Kubernetes MySQL
   Services
   -

Streamlined Default platform YAML configuration data
-

Optional update flags to control product pack and JDK cleanup
-

Minor fixes on the Hiera data
-

   Issues in YAML file formatting
   -

   Puppet templates for identity.xml added to relevant products
   -

   Proxy Port values assigned to different products are streamlined
   -

   Hostname entries streamlined in default deployment platform data
   set
   -

   Pass Through Port Mapping for WSO2 ESB
   -

   Fixing Thrift Server IP configuration for WSO2 MB
   -

   SecureVault parameters made optional
   -

   Reusing Data Source related fields in YAML by inheriting from
   wso2/common.yaml
   -

   Fix Symbolic Link creation in WSO2 DAS
   -

   Fixed installation directory creation failure when parent
   directory doesn’t exist
   -

   Removed use of Kubernetes Master details in Clustering templates
   -

   Streamlined use of hiera, hiera_array, and hiera_hash lookup
   -

WSO2 API Manager Gateway Manager-Worker separate profiles in
Hieradata
-

WSO2 PPaaS Puppet module and Hiera data removed
-

Deprecated older product versions
-

   WSO2 AM 1.9.1
   -

   WSO2 BRS 2.1.0
   -

   WSO2 GREG 4.6.0
   -

   WSO2 IS 5.0.0
   -

   WSO2 MB 3.0.0
   -

Improve Puppet Vagrant setup to use PUPPET_HOME environment
variable
-

Included sample config.yaml files in the Puppet Vagrant setup to
quickly test standalone and distributed deployments
-

Fixed Java System Prefs location issue
-

Included YAML Style Guide for Hiera data files



 This release is based on the following tag:

 https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1

 Release verification guide can be found at:


 https://docs.wso2.com/display/PM200/Setting+up+the+Development+Environment

[Dev] Too much noise during MSF4J startup (master branch)

[Afkham Azeez]

[org.wso2.carbon.transport.http.netty.listener.NettyListener] : Starting
Netty Http Transport Listener

[io.netty.util.internal.logging.InternalLoggerFactory] : Using SLF4J as the
default logging framework

[io.netty.channel.MultithreadEventLoopGroup] : -Dio.netty.eventLoopThreads:
16

[io.netty.util.internal.PlatformDependent0] : java.nio.Buffer.address:
available

[io.netty.util.internal.PlatformDependent0] : sun.misc.Unsafe.theUnsafe:
available

[io.netty.util.internal.PlatformDependent0] : sun.misc.Unsafe.copyMemory:
available

[io.netty.util.internal.PlatformDependent0] : java.nio.Bits.unaligned: true

[io.netty.util.internal.PlatformDependent] : Java version: 8

[io.netty.util.internal.PlatformDependent] : -Dio.netty.noUnsafe: false

[io.netty.util.internal.PlatformDependent] : sun.misc.Unsafe: available

[io.netty.util.internal.PlatformDependent] : -Dio.netty.noJavassist: false

[io.netty.util.internal.PlatformDependent] : Javassist: available

[io.netty.util.internal.PlatformDependent] : -Dio.netty.tmpdir:
/var/folders/9c/f5j0x_mx6xsgx06x63sl6410gn/T (java.io.tmpdir)

[io.netty.util.internal.PlatformDependent] : -Dio.netty.bitMode: 64
(sun.arch.data.model)

[io.netty.util.internal.PlatformDependent] : -Dio.netty.noPreferDirect:
false

[io.netty.channel.nio.NioEventLoop] : -Dio.netty.noKeySetOptimization: false

[io.netty.channel.nio.NioEventLoop] :
-Dio.netty.selectorAutoRebuildThreshold: 512

[org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty Boss
group size io.netty.channel.nio.NioEventLoopGroup@396a51ab

[org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
Worker group Sizeio.netty.channel.nio.NioEventLoopGroup@51081592

[org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
Server Socket BACKLOG 100

[org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
Server Socket TCP_NODELAY true

[org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
Server Socket SO_KEEPALIVE true

[org.wso2.carbon.transport.http.netty.listener.NettyListener] :  Netty
Server Socket CONNECT_TIMEOUT_MILLIS 15000

[org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
Server Socket SO_SNDBUF 1048576

[org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
Server Socket SO_RCVBUF 1048576

[org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
Server Socket SO_RCVBUF 1048576

[org.wso2.carbon.transport.http.netty.listener.NettyListener] : Netty
Server Socket SO_SNDBUF 1048576

[org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
: connection.pool.count: 0

[org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
: max.active.connections.per.pool:-1

[org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
: min.idle.connections.per.pool:100

[org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
: max.idle.connections.per.pool:100

[org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
: min.eviction.idle.time:30

[org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
: sender.thread.count:20

[org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
: Time between Evictions Runs:3

[org.wso2.carbon.transport.http.netty.sender.channel.pool.PoolConfiguration]
: Pool exhausted action:2

[org.wso2.carbon.transport.http.netty.listener.CarbonNettyServerInitializer]
: Disruptor is disabled and using executor thread pool with size of 1024

[io.netty.util.internal.ThreadLocalRandom] :
-Dio.netty.initialSeedUniquifier: 0x8fc366dfb69a63b3 (took 27 ms)

[io.netty.buffer.ByteBufUtil] : -Dio.netty.allocator.type: unpooled

[io.netty.buffer.ByteBufUtil] : -Dio.netty.threadLocalDirectBufferSize:
65536

[io.netty.util.NetUtil] : Loopback interface: lo0 (lo0, 0:0:0:0:0:0:0:1)

[io.netty.util.NetUtil] : /proc/sys/net/core/somaxconn: 128 (non-existent)

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

Re: [Dev] [DEV][Vote] Release WSO2 Puppet Modules 2.0.0

[Akila Ravihansa Perera]

[x] Stable - Go ahead and release

Tested following on both default and K8S platforms;
 - WSO2 APIM 1.10.0
 - WSO2 DAS 3.0.1
 - WSO2 CEP 4.0.0

On Mon, May 23, 2016 at 9:28 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> [x] Stable - Go ahead and release
>
> Verified the following:
>
> 1. License header
> 2. Packaging
> 3. Tested below wso2 products default and distributed deployments in
> default and kubernetes 1.2.0 platform and verified the basic
> functionalities:
>
>
>- WSO2 BPS 3.5.0
>- WSO2 ES 2.0.0
>- WSO2 GREG 5.1.0
>
>
> Thanks.
>
> On Mon, May 23, 2016 at 9:14 PM, Imesh Gunaratne  wrote:
>
>> +1 for the release, I verified following:
>>
>>- README files
>>- Distributed deployments of following products on K8S using Docker
>>images built using Puppet:
>>
>>
>>- Application Server 5.3.0
>>   - API Manager 1.10.0
>>   - Enterprise Service Bus 4.9.0
>>   - Business Process Server 3.5.0
>>   - Business Rules Server 2.2.0
>>   - Data Services Server 3.5.0
>>   - Enterprise Store 2.0.0
>>   - Governance Registry 5.1.0
>>   - Data Analytics Server 3.0.1
>>   - Complex Event Processor 4.0.0
>>
>> Thanks
>>
>> On Wed, May 18, 2016 at 10:24 PM, Chamila De Alwis 
>> wrote:
>>
>>> Hi,
>>>
>>>
>>> This is the first release candidate (RC1) for WSO2 Puppet Modules 2.0.0.
>>> Please download, verify, and vote. Voting will be open for 72 hours.
>>>
>>> [ ] Broken - Do not release (explain why)
>>>
>>> [ ] Stable - Go ahead and release
>>>
>>> Main features and fixes released with this release:
>>>
>>>-
>>>
>>>Updated Hiera data hierarchy to include deployment Platform
>>>-
>>>
>>>Kubernetes based workflow supported, based on
>>>wso2/kubernetes-artifacts
>>>-
>>>
>>>system_file_list to copy files with scope outside of CARBON_HOME
>>>-
>>>
>>>Platform specific configuration data sets for Kubernetes
>>>-
>>>
>>>   Kubernetes deployment-ready Puppet modules
>>>   -
>>>
>>>   Data sources matching a distributed set of Kubernetes MySQL
>>>   Services
>>>   -
>>>
>>>Streamlined Default platform YAML configuration data
>>>-
>>>
>>>Optional update flags to control product pack and JDK cleanup
>>>-
>>>
>>>Minor fixes on the Hiera data
>>>-
>>>
>>>   Issues in YAML file formatting
>>>   -
>>>
>>>   Puppet templates for identity.xml added to relevant products
>>>   -
>>>
>>>   Proxy Port values assigned to different products are streamlined
>>>   -
>>>
>>>   Hostname entries streamlined in default deployment platform data
>>>   set
>>>   -
>>>
>>>   Pass Through Port Mapping for WSO2 ESB
>>>   -
>>>
>>>   Fixing Thrift Server IP configuration for WSO2 MB
>>>   -
>>>
>>>   SecureVault parameters made optional
>>>   -
>>>
>>>   Reusing Data Source related fields in YAML by inheriting from
>>>   wso2/common.yaml
>>>   -
>>>
>>>   Fix Symbolic Link creation in WSO2 DAS
>>>   -
>>>
>>>   Fixed installation directory creation failure when parent
>>>   directory doesn’t exist
>>>   -
>>>
>>>   Removed use of Kubernetes Master details in Clustering templates
>>>   -
>>>
>>>   Streamlined use of hiera, hiera_array, and hiera_hash lookup
>>>   -
>>>
>>>WSO2 API Manager Gateway Manager-Worker separate profiles in
>>>Hieradata
>>>-
>>>
>>>WSO2 PPaaS Puppet module and Hiera data removed
>>>-
>>>
>>>Deprecated older product versions
>>>-
>>>
>>>   WSO2 AM 1.9.1
>>>   -
>>>
>>>   WSO2 BRS 2.1.0
>>>   -
>>>
>>>   WSO2 GREG 4.6.0
>>>   -
>>>
>>>   WSO2 IS 5.0.0
>>>   -
>>>
>>>   WSO2 MB 3.0.0
>>>   -
>>>
>>>Improve Puppet Vagrant setup to use PUPPET_HOME environment variable
>>>-
>>>
>>>Included sample config.yaml files in the Puppet Vagrant setup to
>>>quickly test standalone and distributed deployments
>>>-
>>>
>>>Fixed Java System Prefs location issue
>>>-
>>>
>>>Included YAML Style Guide for Hiera data files
>>>
>>>
>>>
>>> This release is based on the following tag:
>>>
>>> https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1
>>>
>>> Release verification guide can be found at:
>>>
>>>
>>> https://docs.wso2.com/display/PM200/Setting+up+the+Development+Environment
>>>
>>> Source and distribution packages can be downloaded at:
>>>
>>> https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Committer and PMC Member - Apache Stratos
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Senior Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 

Re: [Dev] [APIM] Throttling Applicability Levels With New Throttling Implementation

[Harsha Kumara]

Yeah that information we can't currently get from the handler and CEP side.
Basically we need some kind of tracing capability in our throttling
implementation. We can have CEP extension to generate more resourceful
event(i.e event including throttled out tier, user, throttling level, token
and etc) when the throttled out happen. So we can go through those data and
trace what was happen to particular request to be throttled out. Also when
user customize the throttle out message, end user won't get this error code
sometimes. If that case we won't have much information. This is a area
which we will need to improve.

On Mon, May 23, 2016 at 6:08 PM, Uvindra Dias Jayasinha 
wrote:

> Im not so much interested in the response that is returned to the invoker,
> what I meant is can APIM/CEP tell us effectively that this is what caused
> the throttling to take place for the given API when it was invoked by
> access token X for example?
>
> What will happen is the user will get throttled out and they will come and
> ask why was I throttled out. With a so many combinations of policies
> available we need to be able to say this was your usage(Or some one else
> used up the shared quota available to you) and this tripped off the
> following policy. Can we do that?
>
> We cant turn on tracing/debug logs after this has taken place because then
> its too late. This needs to work like auditing, its always available to
> refer to if required.
>
> On 23 May 2016 at 17:47, Harsha Kumara  wrote:
>
>> @Isabelle, @Uvindra You can  identify which level  you will be throttle
>> out from the code that returned in the response. So no need of debug logs
>> to identify which level particular request has throttled out. With the code
>> you can customized the throttled out message according to your
>> requirements. If you need more information, you can enable debug logs.
>>
>> Also CEP has message tracing capabilities which we can use to identify
>> what happen in CEP side. @Mohan should be able to give more information on
>> CEP side.
>>
>> *Api Level Throttled Out Response*
>>
>> { "fault": { "code": 900800, "message": "Message throttled out", "
>> description": "You have exceeded your quota", "nextAccessTime": "2016-May-21
>> 15:41:00+ UTC" } }
>>
>> *Hard Limit Throttled Out Response*
>>
>> { "fault": { "code": 900801, "message": "API Limit Reached", "description":
>> "API not accepting requests" } }
>>
>> *Resource Level** Throttled Out Response*
>> {
>> "fault": { "code": 900802, "message": "Message throttled out", "
>> description": "You have exceeded your quota", "nextAccessTime": "2016-May-21
>> 15:05:00+ UTC" } }
>>
>> *Application Level Throttled Out Response*
>>
>> { "fault": { "code": 900803, "message": "Message throttled out", "
>> description": "You have exceeded your quota", "nextAccessTime": "2016-May-21
>> 15:36:00+ UTC" } }
>>
>> *Subscription Level Throttled Out Response*
>>
>> {
>> "fault": { "code": 900804, "message": "Message throttled out", "
>> description": "You have exceeded your quota", "nextAccessTime": "2016-May-21
>> 15:36:00+ UTC" } }
>>
>> *Blocked Response*
>>
>> {
>> "fault": { "code": 900805, "message": "Message blocked", "description": "You
>> have been blocked from accessing the resource" } }
>>
>> *Throttle Out by Custom Policy Response*
>>
>> { "fault": { "code": 900806, "message": "Message throttled out", "
>> description": "You have exceeded your quota", "nextAccessTime": "2016-May-21
>> 17:05:10+ UTC" } }
>>
>> On Mon, May 23, 2016 at 5:20 PM, Isabelle Mauny 
>> wrote:
>>
>>> +1 !! No debug logs allowed here. All the tracking of what’s happening
>>> must be easily available - Using don’t have to debug this, they need to
>>> understand that is happening based on the information they have set ( and
>>> no that does not mean debugging CEP either, which just happens to be the
>>> engine we are relying on)
>>>
>>> Isabelle.
>>> __
>>>
>>> Isabelle Mauny
>>> VP, Product Management; WSO2, Inc.;  http://wso2.com/
>>>
>>>
>>> On May 23, 2016, at 1:45 PM, Uvindra Dias Jayasinha 
>>> wrote:
>>>
>>> Debug logging might not always be a feasible option for this. CEP engine
>>> should be able to tell what events triggered a given rule right(for
>>> auditing purposes)?
>>>
>>> On 23 May 2016 at 15:09, Harsha Kumara  wrote:
>>>
 Yes, we are returning different codes for each level of throttle. Also
 enabling debug logs should give more information as well. So you can
 identify which level you have been throttle out from codes. I agree with
 you that we need to clearly mentioned the use of each level of throttling.
 Users will need throttle on few levels depend on their requirements. Since
 we are providing the flexibility to apply throttling at different levels,
 with proper details they can apply required throttling levels 

[Dev] [DEV] WSO2 App Manager 1.2.0 Milestone 5 Released

[Lahiru Cooray]

Hi All,

WSO2 App Manager team pleased to announce
the WSO2 APP Manager 1.2.0 - Milestone 5 release. It contains following new
features and bug fixes.

You can download this distribution from below link.
http://builder1.us1.wso2.org/~appm/release-1.2.0/M5/wso2appm-1.2.0-M5.zip


*New Feature(s) *
1. Oauth secured Rest API's (Web apps)

   - Store API's
   - Publisher API's

2. Business Owner concept implementation

*Bug Fixes*
WSO2 App Manager 1.2.0-M5 resolved issues



Regards,
App Manager Team.


-- 
*Lahiru Cooray*
Software Engineer
WSO2, Inc.;http://wso2.com/
lean.enterprise.middleware

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

Re: [Dev] [DEV][Vote] Release WSO2 Puppet Modules 2.0.0

[Thanuja Uruththirakodeeswaran]

[x] Stable - Go ahead and release

Verified the following:

1. License header
2. Packaging
3. Tested below wso2 products default and distributed deployments in
default and kubernetes 1.2.0 platform and verified the basic
functionalities:


   - WSO2 BPS 3.5.0
   - WSO2 ES 2.0.0
   - WSO2 GREG 5.1.0


Thanks.

On Mon, May 23, 2016 at 9:14 PM, Imesh Gunaratne  wrote:

> +1 for the release, I verified following:
>
>- README files
>- Distributed deployments of following products on K8S using Docker
>images built using Puppet:
>
>
>- Application Server 5.3.0
>   - API Manager 1.10.0
>   - Enterprise Service Bus 4.9.0
>   - Business Process Server 3.5.0
>   - Business Rules Server 2.2.0
>   - Data Services Server 3.5.0
>   - Enterprise Store 2.0.0
>   - Governance Registry 5.1.0
>   - Data Analytics Server 3.0.1
>   - Complex Event Processor 4.0.0
>
> Thanks
>
> On Wed, May 18, 2016 at 10:24 PM, Chamila De Alwis 
> wrote:
>
>> Hi,
>>
>>
>> This is the first release candidate (RC1) for WSO2 Puppet Modules 2.0.0.
>> Please download, verify, and vote. Voting will be open for 72 hours.
>>
>> [ ] Broken - Do not release (explain why)
>>
>> [ ] Stable - Go ahead and release
>>
>> Main features and fixes released with this release:
>>
>>-
>>
>>Updated Hiera data hierarchy to include deployment Platform
>>-
>>
>>Kubernetes based workflow supported, based on
>>wso2/kubernetes-artifacts
>>-
>>
>>system_file_list to copy files with scope outside of CARBON_HOME
>>-
>>
>>Platform specific configuration data sets for Kubernetes
>>-
>>
>>   Kubernetes deployment-ready Puppet modules
>>   -
>>
>>   Data sources matching a distributed set of Kubernetes MySQL
>>   Services
>>   -
>>
>>Streamlined Default platform YAML configuration data
>>-
>>
>>Optional update flags to control product pack and JDK cleanup
>>-
>>
>>Minor fixes on the Hiera data
>>-
>>
>>   Issues in YAML file formatting
>>   -
>>
>>   Puppet templates for identity.xml added to relevant products
>>   -
>>
>>   Proxy Port values assigned to different products are streamlined
>>   -
>>
>>   Hostname entries streamlined in default deployment platform data
>>   set
>>   -
>>
>>   Pass Through Port Mapping for WSO2 ESB
>>   -
>>
>>   Fixing Thrift Server IP configuration for WSO2 MB
>>   -
>>
>>   SecureVault parameters made optional
>>   -
>>
>>   Reusing Data Source related fields in YAML by inheriting from
>>   wso2/common.yaml
>>   -
>>
>>   Fix Symbolic Link creation in WSO2 DAS
>>   -
>>
>>   Fixed installation directory creation failure when parent
>>   directory doesn’t exist
>>   -
>>
>>   Removed use of Kubernetes Master details in Clustering templates
>>   -
>>
>>   Streamlined use of hiera, hiera_array, and hiera_hash lookup
>>   -
>>
>>WSO2 API Manager Gateway Manager-Worker separate profiles in Hieradata
>>-
>>
>>WSO2 PPaaS Puppet module and Hiera data removed
>>-
>>
>>Deprecated older product versions
>>-
>>
>>   WSO2 AM 1.9.1
>>   -
>>
>>   WSO2 BRS 2.1.0
>>   -
>>
>>   WSO2 GREG 4.6.0
>>   -
>>
>>   WSO2 IS 5.0.0
>>   -
>>
>>   WSO2 MB 3.0.0
>>   -
>>
>>Improve Puppet Vagrant setup to use PUPPET_HOME environment variable
>>-
>>
>>Included sample config.yaml files in the Puppet Vagrant setup to
>>quickly test standalone and distributed deployments
>>-
>>
>>Fixed Java System Prefs location issue
>>-
>>
>>Included YAML Style Guide for Hiera data files
>>
>>
>>
>> This release is based on the following tag:
>>
>> https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1
>>
>> Release verification guide can be found at:
>>
>> https://docs.wso2.com/display/PM200/Setting+up+the+Development+Environment
>>
>> Source and distribution packages can be downloaded at:
>>
>> https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.io TW: @imesh
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanuja Uruththirakodeeswaran
Software Engineer
WSO2 Inc.;http://wso2.com
lean.enterprise.middleware

mobile: +94 774363167
___
Dev mailing list
Dev@wso2.org

Re: [Dev] [DEV][Vote] Release WSO2 Puppet Modules 2.0.0

[Imesh Gunaratne]

+1 for the release, I verified following:

   - README files
   - Distributed deployments of following products on K8S using Docker
   images built using Puppet:


   - Application Server 5.3.0
  - API Manager 1.10.0
  - Enterprise Service Bus 4.9.0
  - Business Process Server 3.5.0
  - Business Rules Server 2.2.0
  - Data Services Server 3.5.0
  - Enterprise Store 2.0.0
  - Governance Registry 5.1.0
  - Data Analytics Server 3.0.1
  - Complex Event Processor 4.0.0

Thanks

On Wed, May 18, 2016 at 10:24 PM, Chamila De Alwis 
wrote:

> Hi,
>
>
> This is the first release candidate (RC1) for WSO2 Puppet Modules 2.0.0.
> Please download, verify, and vote. Voting will be open for 72 hours.
>
> [ ] Broken - Do not release (explain why)
>
> [ ] Stable - Go ahead and release
>
> Main features and fixes released with this release:
>
>-
>
>Updated Hiera data hierarchy to include deployment Platform
>-
>
>Kubernetes based workflow supported, based on wso2/kubernetes-artifacts
>-
>
>system_file_list to copy files with scope outside of CARBON_HOME
>-
>
>Platform specific configuration data sets for Kubernetes
>-
>
>   Kubernetes deployment-ready Puppet modules
>   -
>
>   Data sources matching a distributed set of Kubernetes MySQL Services
>   -
>
>Streamlined Default platform YAML configuration data
>-
>
>Optional update flags to control product pack and JDK cleanup
>-
>
>Minor fixes on the Hiera data
>-
>
>   Issues in YAML file formatting
>   -
>
>   Puppet templates for identity.xml added to relevant products
>   -
>
>   Proxy Port values assigned to different products are streamlined
>   -
>
>   Hostname entries streamlined in default deployment platform data set
>   -
>
>   Pass Through Port Mapping for WSO2 ESB
>   -
>
>   Fixing Thrift Server IP configuration for WSO2 MB
>   -
>
>   SecureVault parameters made optional
>   -
>
>   Reusing Data Source related fields in YAML by inheriting from
>   wso2/common.yaml
>   -
>
>   Fix Symbolic Link creation in WSO2 DAS
>   -
>
>   Fixed installation directory creation failure when parent directory
>   doesn’t exist
>   -
>
>   Removed use of Kubernetes Master details in Clustering templates
>   -
>
>   Streamlined use of hiera, hiera_array, and hiera_hash lookup
>   -
>
>WSO2 API Manager Gateway Manager-Worker separate profiles in Hieradata
>-
>
>WSO2 PPaaS Puppet module and Hiera data removed
>-
>
>Deprecated older product versions
>-
>
>   WSO2 AM 1.9.1
>   -
>
>   WSO2 BRS 2.1.0
>   -
>
>   WSO2 GREG 4.6.0
>   -
>
>   WSO2 IS 5.0.0
>   -
>
>   WSO2 MB 3.0.0
>   -
>
>Improve Puppet Vagrant setup to use PUPPET_HOME environment variable
>-
>
>Included sample config.yaml files in the Puppet Vagrant setup to
>quickly test standalone and distributed deployments
>-
>
>Fixed Java System Prefs location issue
>-
>
>Included YAML Style Guide for Hiera data files
>
>
>
> This release is based on the following tag:
>
> https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1
>
> Release verification guide can be found at:
>
> https://docs.wso2.com/display/PM200/Setting+up+the+Development+Environment
>
> Source and distribution packages can be downloaded at:
>
> https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.io TW: @imesh
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ESB Enrich Mediator Issue with JSON array

[Godwin Shrimal]

Hi All,

I used Enrich Mediator to copy the original payload as follows.









Incoming JSON payload has multi-value attribute, But when multi-value
attribute has only one value, Enrich mediator convert the JSON payload it
as a single value attribute. Is this a known issue or do we have any work
around for this ?


Thanks
Godwin



-- 
*Godwin Amila Shrimal*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: *+94772264165*
linkedin: *http://lnkd.in/KUum6D *
twitter: https://twitter.com/godwinamila
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Identity Server 5.0.0 as API-M Key Manager

[rohit]

hi Pushpalanka,
  Thanks. I have the Identity Server running on port 9443 and API Manager
running on 9447. So when i try to access //authorize/ endpoint of API
Manager to generate an authorization code, the request gets forwarded to
//authenticationendpoint/oauth2_authz.do/ endpoint of Identity
Server(Identity Server login page where I am supposed to enter my
credentials), however the ip is localhost, so everytime i got to replace
localhost with the actual ip.

Moreover Once I enter my credentials, the request goes forward to
//commonauth/?sessionDataKey=<>=oauth2/ endpoint(where i either need to
grant or deny accesss) but here again ip is localhost, so i got to again
replace the localhost with actual ip. Im just guessing this is some
configuration issue. And I'm following this  link

  



--
View this message in context: 
http://wso2-oxygen-tank.10903.n7.nabble.com/Identity-Server-5-0-0-as-API-M-Key-Manager-tp136062p136926.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Identity Server 5.0.0 as API-M Key Manager

[Pushpalanka Jayawardhana]

On Mon, May 23, 2016 at 5:43 PM, rohit  wrote:

> Havent had much progress since then. Im still stuck. Hoping to find some
> help
> here
>

Hi Rohit,

What is the server that runs on port 9443 in your setup?
Also it would be a good idea to verify and confirm the step 5 again for API
Manager.

Thanks,

>
>
>
> --
> View this message in context:
> http://wso2-oxygen-tank.10903.n7.nabble.com/Identity-Server-5-0-0-as-API-M-Key-Manager-tp136062p136924.html
> Sent from the WSO2 Development mailing list archive at Nabble.com.
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
Pushpalanka.
-- 
Pushpalanka Jayawardhana, B.Sc.Eng.(Hons).
Senior Software Engineer, WSO2 Lanka (pvt) Ltd;  wso2.com/
Mobile: +94779716248
Blog: pushpalankajaya.blogspot.com/ | LinkedIn:
lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Identity Server 5.0.0 as API-M Key Manager

[rohit]

Havent had much progress since then. Im still stuck. Hoping to find some help
here



--
View this message in context: 
http://wso2-oxygen-tank.10903.n7.nabble.com/Identity-Server-5-0-0-as-API-M-Key-Manager-tp136062p136924.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] G-Reg extension for integration with API-M

[Shazni Nazir]

yeah Nuwan. That's what the token regeneration part does.

Shazni Nazeer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com

On Mon, May 23, 2016 at 6:13 PM, Nuwan Bandara  wrote:

> ah got it, thanks. So I assume when a person is logged into the publisher
> the API-M token is refreshed automatically if expired correct ?
>
> On Mon, May 23, 2016 at 8:38 AM, Shazni Nazir  wrote:
>
>> Hi NuwanB,
>>
>> ​We only need publisher integration right, so why are we doing token
>>> generation as thats a store function ?​
>>
>>
>> To use the new API-M REST API, you need token generation. Refer following
>> documentation [1]
>>
>> [1]
>> https://docs.wso2.com/display/AM1100/apidocs/publisher/index.html#guide
>>
>> Shazni Nazeer
>> Mob : +94 37331
>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>> Blog : http://shazninazeer.blogspot.com
>>
>> On Mon, May 23, 2016 at 6:06 PM, Nuwan Bandara  wrote:
>>
>>> Hi Guys,
>>>
>>> On Mon, May 23, 2016 at 8:27 AM, Shazni Nazir  wrote:
>>>
 Last week had a meeting with G-Reg team (participants - Sagara,
 Chandana and SameeraM) and SanjeewaM from API-M to see the current work and
 to get few thing clarified. Notes of the meeting can be found in the
 following [1]

 [1] Invitation: G-Reg extension for API-M integration design/current
 prog... @ Wed May 18, 2016 2pm - 3pm (sha...@wso2.com)

 Apart from that following are the the finished work and TODOs left

- Handler is almost complete. Have to add copy and delete handler
methods and do the consequent API-M operations
- Add more fields like, in, out and fault sequence.
- Request json payload creation for API creation - done. I
identified an issue in the API-M REST API where the scopes and
uri-templates are specified, those do not get added. The reason is
explained in the email [2] and the PR also sent to the git repo.
- Get the access and the refresh token using the API-M REST API
- Access token regeneration when token expires

 ​We only need publisher integration right, so why are we doing token
>>> generation as thats a store function ?​
>>>

-
- Artifact attribute reading
- Provide rxt fields to read API Definition and populate the
payload according to that
- life-cycle configuration for the API lifecycle - Using the same
lifecycle as what API-M already have

 [2] [API-M] API Definition and scopes do not get added and updated
 when using new REST API

 TODO's

- Reading the api manager related configuration from a
configuration file
- Adding the thumbnail of the API. Currently having an issue when
adding a thumnail in the G-Reg publisher. I'm looking into it. In the
meeting we discussed a way to send the thumbnail URL in the API-M REST 
 API.
See the meeting notes on the decision.
- Develop the executor for the lifecycle state change
- Add docs section to the rxt
- Persist the consumer key and consumer secret obtained for G-Reg in
registry
- Do some G-Reg publisher level customization like avoiding
additions of the same context and adding placeholders


 Shazni Nazeer
 Mob : +94 37331
 LinkedIn : http://lk.linkedin.com/in/shazninazeer
 Blog : http://shazninazeer.blogspot.com

 On Tue, May 17, 2016 at 10:45 AM, Shazni Nazir  wrote:

> Since this component is developed as an extension, it can be deployed
> as a jar to the repository/components/lib as a library. And other 
> artifacts
> like rxts can be added to G-Reg in runtime. With this setup I can test 
> with
> a standalone G-Reg 5.2.0 with a standalone API-M 1.10.0 without any 
> hassle.
> Currently as I develop this implementation, I do testing as it goes.
>
> Shazni Nazeer
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
> Blog : http://shazninazeer.blogspot.com
>
> On Tue, May 17, 2016 at 6:33 AM, Samisa Abeysinghe 
> wrote:
>
>> Great!
>>
>> How are we planning to test this implementation?
>>
>> Thanks,
>> Samisa...
>>
>>
>> Samisa Abeysinghe
>>
>> Vice President Delivery
>>
>> WSO2 Inc.
>> http://wso2.com
>>
>>
>> On Mon, May 16, 2016 at 7:31 PM, Shazni Nazir 
>> wrote:
>>
>>> Yes Samisa, so far so good.
>>>
>>> I'll also be having a review with NuwanB and G-Reg team by Thursday
>>> to see if things are aligned.
>>> On 16 May 2016 6:33 p.m., "Samisa Abeysinghe" 
>>> wrote:
>>>
>>> Are we on track in terms of the time schedule to deliver this?

Re: [Dev] G-Reg extension for integration with API-M

[Nuwan Bandara]

ah got it, thanks. So I assume when a person is logged into the publisher
the API-M token is refreshed automatically if expired correct ?

On Mon, May 23, 2016 at 8:38 AM, Shazni Nazir  wrote:

> Hi NuwanB,
>
> ​We only need publisher integration right, so why are we doing token
>> generation as thats a store function ?​
>
>
> To use the new API-M REST API, you need token generation. Refer following
> documentation [1]
>
> [1]
> https://docs.wso2.com/display/AM1100/apidocs/publisher/index.html#guide
>
> Shazni Nazeer
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
> Blog : http://shazninazeer.blogspot.com
>
> On Mon, May 23, 2016 at 6:06 PM, Nuwan Bandara  wrote:
>
>> Hi Guys,
>>
>> On Mon, May 23, 2016 at 8:27 AM, Shazni Nazir  wrote:
>>
>>> Last week had a meeting with G-Reg team (participants - Sagara, Chandana
>>> and SameeraM) and SanjeewaM from API-M to see the current work and to get
>>> few thing clarified. Notes of the meeting can be found in the following [1]
>>>
>>> [1] Invitation: G-Reg extension for API-M integration design/current
>>> prog... @ Wed May 18, 2016 2pm - 3pm (sha...@wso2.com)
>>>
>>> Apart from that following are the the finished work and TODOs left
>>>
>>>- Handler is almost complete. Have to add copy and delete handler
>>>methods and do the consequent API-M operations
>>>- Add more fields like, in, out and fault sequence.
>>>- Request json payload creation for API creation - done. I
>>>identified an issue in the API-M REST API where the scopes and
>>>uri-templates are specified, those do not get added. The reason is
>>>explained in the email [2] and the PR also sent to the git repo.
>>>- Get the access and the refresh token using the API-M REST API
>>>- Access token regeneration when token expires
>>>
>>> ​We only need publisher integration right, so why are we doing token
>> generation as thats a store function ?​
>>
>>>
>>>-
>>>- Artifact attribute reading
>>>- Provide rxt fields to read API Definition and populate the payload
>>>according to that
>>>- life-cycle configuration for the API lifecycle - Using the same
>>>lifecycle as what API-M already have
>>>
>>> [2] [API-M] API Definition and scopes do not get added and updated when
>>> using new REST API
>>>
>>> TODO's
>>>
>>>- Reading the api manager related configuration from a configuration
>>>file
>>>- Adding the thumbnail of the API. Currently having an issue when
>>>adding a thumnail in the G-Reg publisher. I'm looking into it. In the
>>>meeting we discussed a way to send the thumbnail URL in the API-M REST 
>>> API.
>>>See the meeting notes on the decision.
>>>- Develop the executor for the lifecycle state change
>>>- Add docs section to the rxt
>>>- Persist the consumer key and consumer secret obtained for G-Reg in
>>>registry
>>>- Do some G-Reg publisher level customization like avoiding
>>>additions of the same context and adding placeholders
>>>
>>>
>>> Shazni Nazeer
>>> Mob : +94 37331
>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>>> Blog : http://shazninazeer.blogspot.com
>>>
>>> On Tue, May 17, 2016 at 10:45 AM, Shazni Nazir  wrote:
>>>
 Since this component is developed as an extension, it can be deployed
 as a jar to the repository/components/lib as a library. And other artifacts
 like rxts can be added to G-Reg in runtime. With this setup I can test with
 a standalone G-Reg 5.2.0 with a standalone API-M 1.10.0 without any hassle.
 Currently as I develop this implementation, I do testing as it goes.

 Shazni Nazeer
 Mob : +94 37331
 LinkedIn : http://lk.linkedin.com/in/shazninazeer
 Blog : http://shazninazeer.blogspot.com

 On Tue, May 17, 2016 at 6:33 AM, Samisa Abeysinghe 
 wrote:

> Great!
>
> How are we planning to test this implementation?
>
> Thanks,
> Samisa...
>
>
> Samisa Abeysinghe
>
> Vice President Delivery
>
> WSO2 Inc.
> http://wso2.com
>
>
> On Mon, May 16, 2016 at 7:31 PM, Shazni Nazir  wrote:
>
>> Yes Samisa, so far so good.
>>
>> I'll also be having a review with NuwanB and G-Reg team by Thursday
>> to see if things are aligned.
>> On 16 May 2016 6:33 p.m., "Samisa Abeysinghe" 
>> wrote:
>>
>> Are we on track in terms of the time schedule to deliver this?
>>
>> Thanks,
>> Samisa...
>>
>>
>> Samisa Abeysinghe
>>
>> Vice President Delivery
>>
>> WSO2 Inc.
>> http://wso2.com
>>
>>
>> On Mon, May 16, 2016 at 4:45 PM, Shazni Nazir 
>> wrote:
>>
>>> Hi all,
>>>
>>> Following is the current update of the G-Reg extension for API-M
>>> integration.
>>>
>>>- API rxt - 

Re: [Dev] G-Reg extension for integration with API-M

[Shazni Nazir]

Hi NuwanB,

​We only need publisher integration right, so why are we doing token
> generation as thats a store function ?​


To use the new API-M REST API, you need token generation. Refer following
documentation [1]

[1] https://docs.wso2.com/display/AM1100/apidocs/publisher/index.html#guide

Shazni Nazeer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com

On Mon, May 23, 2016 at 6:06 PM, Nuwan Bandara  wrote:

> Hi Guys,
>
> On Mon, May 23, 2016 at 8:27 AM, Shazni Nazir  wrote:
>
>> Last week had a meeting with G-Reg team (participants - Sagara, Chandana
>> and SameeraM) and SanjeewaM from API-M to see the current work and to get
>> few thing clarified. Notes of the meeting can be found in the following [1]
>>
>> [1] Invitation: G-Reg extension for API-M integration design/current
>> prog... @ Wed May 18, 2016 2pm - 3pm (sha...@wso2.com)
>>
>> Apart from that following are the the finished work and TODOs left
>>
>>- Handler is almost complete. Have to add copy and delete handler
>>methods and do the consequent API-M operations
>>- Add more fields like, in, out and fault sequence.
>>- Request json payload creation for API creation - done. I identified
>>an issue in the API-M REST API where the scopes and uri-templates are
>>specified, those do not get added. The reason is explained in the email 
>> [2]
>>and the PR also sent to the git repo.
>>- Get the access and the refresh token using the API-M REST API
>>- Access token regeneration when token expires
>>
>> ​We only need publisher integration right, so why are we doing token
> generation as thats a store function ?​
>
>>
>>-
>>- Artifact attribute reading
>>- Provide rxt fields to read API Definition and populate the payload
>>according to that
>>- life-cycle configuration for the API lifecycle - Using the same
>>lifecycle as what API-M already have
>>
>> [2] [API-M] API Definition and scopes do not get added and updated when
>> using new REST API
>>
>> TODO's
>>
>>- Reading the api manager related configuration from a configuration
>>file
>>- Adding the thumbnail of the API. Currently having an issue when
>>adding a thumnail in the G-Reg publisher. I'm looking into it. In the
>>meeting we discussed a way to send the thumbnail URL in the API-M REST 
>> API.
>>See the meeting notes on the decision.
>>- Develop the executor for the lifecycle state change
>>- Add docs section to the rxt
>>- Persist the consumer key and consumer secret obtained for G-Reg in
>>registry
>>- Do some G-Reg publisher level customization like avoiding additions
>>of the same context and adding placeholders
>>
>>
>> Shazni Nazeer
>> Mob : +94 37331
>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>> Blog : http://shazninazeer.blogspot.com
>>
>> On Tue, May 17, 2016 at 10:45 AM, Shazni Nazir  wrote:
>>
>>> Since this component is developed as an extension, it can be deployed as
>>> a jar to the repository/components/lib as a library. And other artifacts
>>> like rxts can be added to G-Reg in runtime. With this setup I can test with
>>> a standalone G-Reg 5.2.0 with a standalone API-M 1.10.0 without any hassle.
>>> Currently as I develop this implementation, I do testing as it goes.
>>>
>>> Shazni Nazeer
>>> Mob : +94 37331
>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>>> Blog : http://shazninazeer.blogspot.com
>>>
>>> On Tue, May 17, 2016 at 6:33 AM, Samisa Abeysinghe 
>>> wrote:
>>>
 Great!

 How are we planning to test this implementation?

 Thanks,
 Samisa...


 Samisa Abeysinghe

 Vice President Delivery

 WSO2 Inc.
 http://wso2.com


 On Mon, May 16, 2016 at 7:31 PM, Shazni Nazir  wrote:

> Yes Samisa, so far so good.
>
> I'll also be having a review with NuwanB and G-Reg team by Thursday to
> see if things are aligned.
> On 16 May 2016 6:33 p.m., "Samisa Abeysinghe"  wrote:
>
> Are we on track in terms of the time schedule to deliver this?
>
> Thanks,
> Samisa...
>
>
> Samisa Abeysinghe
>
> Vice President Delivery
>
> WSO2 Inc.
> http://wso2.com
>
>
> On Mon, May 16, 2016 at 4:45 PM, Shazni Nazir  wrote:
>
>> Hi all,
>>
>> Following is the current update of the G-Reg extension for API-M
>> integration.
>>
>>- API rxt - created, but additional fields needs to be added.
>>
>> Some fields like thumbnail, sequences for in, out, fault have few
>> limitations on the rxt end. Pure rxt's doesn't support for file system
>> browse. I'm also looking into publisher extension to see if this could be
>> added in publisher app end.
>>
>> Further, the API-M REST API [1] does 

Re: [Dev] G-Reg extension for integration with API-M

[Nuwan Bandara]

Hi Guys,

On Mon, May 23, 2016 at 8:27 AM, Shazni Nazir  wrote:

> Last week had a meeting with G-Reg team (participants - Sagara, Chandana
> and SameeraM) and SanjeewaM from API-M to see the current work and to get
> few thing clarified. Notes of the meeting can be found in the following [1]
>
> [1] Invitation: G-Reg extension for API-M integration design/current
> prog... @ Wed May 18, 2016 2pm - 3pm (sha...@wso2.com)
>
> Apart from that following are the the finished work and TODOs left
>
>- Handler is almost complete. Have to add copy and delete handler
>methods and do the consequent API-M operations
>- Add more fields like, in, out and fault sequence.
>- Request json payload creation for API creation - done. I identified
>an issue in the API-M REST API where the scopes and uri-templates are
>specified, those do not get added. The reason is explained in the email [2]
>and the PR also sent to the git repo.
>- Get the access and the refresh token using the API-M REST API
>- Access token regeneration when token expires
>
> ​We only need publisher integration right, so why are we doing token
generation as thats a store function ?​

>
>-
>- Artifact attribute reading
>- Provide rxt fields to read API Definition and populate the payload
>according to that
>- life-cycle configuration for the API lifecycle - Using the same
>lifecycle as what API-M already have
>
> [2] [API-M] API Definition and scopes do not get added and updated when
> using new REST API
>
> TODO's
>
>- Reading the api manager related configuration from a configuration
>file
>- Adding the thumbnail of the API. Currently having an issue when
>adding a thumnail in the G-Reg publisher. I'm looking into it. In the
>meeting we discussed a way to send the thumbnail URL in the API-M REST API.
>See the meeting notes on the decision.
>- Develop the executor for the lifecycle state change
>- Add docs section to the rxt
>- Persist the consumer key and consumer secret obtained for G-Reg in
>registry
>- Do some G-Reg publisher level customization like avoiding additions
>of the same context and adding placeholders
>
>
> Shazni Nazeer
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
> Blog : http://shazninazeer.blogspot.com
>
> On Tue, May 17, 2016 at 10:45 AM, Shazni Nazir  wrote:
>
>> Since this component is developed as an extension, it can be deployed as
>> a jar to the repository/components/lib as a library. And other artifacts
>> like rxts can be added to G-Reg in runtime. With this setup I can test with
>> a standalone G-Reg 5.2.0 with a standalone API-M 1.10.0 without any hassle.
>> Currently as I develop this implementation, I do testing as it goes.
>>
>> Shazni Nazeer
>> Mob : +94 37331
>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>> Blog : http://shazninazeer.blogspot.com
>>
>> On Tue, May 17, 2016 at 6:33 AM, Samisa Abeysinghe 
>> wrote:
>>
>>> Great!
>>>
>>> How are we planning to test this implementation?
>>>
>>> Thanks,
>>> Samisa...
>>>
>>>
>>> Samisa Abeysinghe
>>>
>>> Vice President Delivery
>>>
>>> WSO2 Inc.
>>> http://wso2.com
>>>
>>>
>>> On Mon, May 16, 2016 at 7:31 PM, Shazni Nazir  wrote:
>>>
 Yes Samisa, so far so good.

 I'll also be having a review with NuwanB and G-Reg team by Thursday to
 see if things are aligned.
 On 16 May 2016 6:33 p.m., "Samisa Abeysinghe"  wrote:

 Are we on track in terms of the time schedule to deliver this?

 Thanks,
 Samisa...


 Samisa Abeysinghe

 Vice President Delivery

 WSO2 Inc.
 http://wso2.com


 On Mon, May 16, 2016 at 4:45 PM, Shazni Nazir  wrote:

> Hi all,
>
> Following is the current update of the G-Reg extension for API-M
> integration.
>
>- API rxt - created, but additional fields needs to be added.
>
> Some fields like thumbnail, sequences for in, out, fault have few
> limitations on the rxt end. Pure rxt's doesn't support for file system
> browse. I'm also looking into publisher extension to see if this could be
> added in publisher app end.
>
> Further, the API-M REST API [1] does provide the thumbnailUrl and
> sequence. Need to verify if this supports file based urls.
>
>- Developed the skeleton handler code
>- Developed the code to get consumer key and secret using the
>API-M REST API
>- Developed the code to get the access and the refresh token using
>the API-M REST API
>- Developing the artifact attribute reading logic - in progress
>
> TODO's
>
>- Add missing fields to ext
>- Reading the api manager related configuration from a
>configuration file
>- Provide rxt fields to read API Definition and 

Re: [Dev] G-Reg extension for integration with API-M

[Shazni Nazir]

Last week had a meeting with G-Reg team (participants - Sagara, Chandana
and SameeraM) and SanjeewaM from API-M to see the current work and to get
few thing clarified. Notes of the meeting can be found in the following [1]

[1] Invitation: G-Reg extension for API-M integration design/current
prog... @ Wed May 18, 2016 2pm - 3pm (sha...@wso2.com)

Apart from that following are the the finished work and TODOs left

   - Handler is almost complete. Have to add copy and delete handler
   methods and do the consequent API-M operations
   - Add more fields like, in, out and fault sequence.
   - Request json payload creation for API creation - done. I identified an
   issue in the API-M REST API where the scopes and uri-templates are
   specified, those do not get added. The reason is explained in the email [2]
   and the PR also sent to the git repo.
   - Get the access and the refresh token using the API-M REST API
   - Access token regeneration when token expires
   - Artifact attribute reading
   - Provide rxt fields to read API Definition and populate the payload
   according to that
   - life-cycle configuration for the API lifecycle - Using the same
   lifecycle as what API-M already have

[2] [API-M] API Definition and scopes do not get added and updated when
using new REST API

TODO's

   - Reading the api manager related configuration from a configuration file
   - Adding the thumbnail of the API. Currently having an issue when adding
   a thumnail in the G-Reg publisher. I'm looking into it. In the meeting we
   discussed a way to send the thumbnail URL in the API-M REST API. See the
   meeting notes on the decision.
   - Develop the executor for the lifecycle state change
   - Add docs section to the rxt
   - Persist the consumer key and consumer secret obtained for G-Reg in
   registry
   - Do some G-Reg publisher level customization like avoiding additions of
   the same context and adding placeholders


Shazni Nazeer
Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com

On Tue, May 17, 2016 at 10:45 AM, Shazni Nazir  wrote:

> Since this component is developed as an extension, it can be deployed as a
> jar to the repository/components/lib as a library. And other artifacts like
> rxts can be added to G-Reg in runtime. With this setup I can test with a
> standalone G-Reg 5.2.0 with a standalone API-M 1.10.0 without any hassle.
> Currently as I develop this implementation, I do testing as it goes.
>
> Shazni Nazeer
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
> Blog : http://shazninazeer.blogspot.com
>
> On Tue, May 17, 2016 at 6:33 AM, Samisa Abeysinghe 
> wrote:
>
>> Great!
>>
>> How are we planning to test this implementation?
>>
>> Thanks,
>> Samisa...
>>
>>
>> Samisa Abeysinghe
>>
>> Vice President Delivery
>>
>> WSO2 Inc.
>> http://wso2.com
>>
>>
>> On Mon, May 16, 2016 at 7:31 PM, Shazni Nazir  wrote:
>>
>>> Yes Samisa, so far so good.
>>>
>>> I'll also be having a review with NuwanB and G-Reg team by Thursday to
>>> see if things are aligned.
>>> On 16 May 2016 6:33 p.m., "Samisa Abeysinghe"  wrote:
>>>
>>> Are we on track in terms of the time schedule to deliver this?
>>>
>>> Thanks,
>>> Samisa...
>>>
>>>
>>> Samisa Abeysinghe
>>>
>>> Vice President Delivery
>>>
>>> WSO2 Inc.
>>> http://wso2.com
>>>
>>>
>>> On Mon, May 16, 2016 at 4:45 PM, Shazni Nazir  wrote:
>>>
 Hi all,

 Following is the current update of the G-Reg extension for API-M
 integration.

- API rxt - created, but additional fields needs to be added.

 Some fields like thumbnail, sequences for in, out, fault have few
 limitations on the rxt end. Pure rxt's doesn't support for file system
 browse. I'm also looking into publisher extension to see if this could be
 added in publisher app end.

 Further, the API-M REST API [1] does provide the thumbnailUrl and
 sequence. Need to verify if this supports file based urls.

- Developed the skeleton handler code
- Developed the code to get consumer key and secret using the API-M
REST API
- Developed the code to get the access and the refresh token using
the API-M REST API
- Developing the artifact attribute reading logic - in progress

 TODO's

- Add missing fields to ext
- Reading the api manager related configuration from a
configuration file
- Provide rxt fields to read API Definition and populate the
payload according to that
- Develop the request json payload creation for API creation - in
progress
- Develop the access token regeneration when token expires
- Develop the life-cycle configuration for the API lifecycle
- Develop the executor for the lifecycle state change


 [1]
 

Re: [Dev] [APIM] Throttling Applicability Levels With New Throttling Implementation

[Harsha Kumara]

@Isabelle, @Uvindra You can  identify which level  you will be throttle out
from the code that returned in the response. So no need of debug logs to
identify which level particular request has throttled out. With the code
you can customized the throttled out message according to your
requirements. If you need more information, you can enable debug logs.

Also CEP has message tracing capabilities which we can use to identify what
happen in CEP side. @Mohan should be able to give more information on CEP
side.

*Api Level Throttled Out Response*

{ "fault": { "code": 900800, "message": "Message throttled out", "
description": "You have exceeded your quota", "nextAccessTime": "2016-May-21
15:41:00+ UTC" } }

*Hard Limit Throttled Out Response*

{ "fault": { "code": 900801, "message": "API Limit Reached",
"description": "API
not accepting requests" } }

*Resource Level** Throttled Out Response*
{
"fault": { "code": 900802, "message": "Message throttled out", "description":
"You have exceeded your quota", "nextAccessTime": "2016-May-21
15:05:00+ UTC" } }

*Application Level Throttled Out Response*

{ "fault": { "code": 900803, "message": "Message throttled out", "
description": "You have exceeded your quota", "nextAccessTime": "2016-May-21
15:36:00+ UTC" } }

*Subscription Level Throttled Out Response*

{
"fault": { "code": 900804, "message": "Message throttled out", "description":
"You have exceeded your quota", "nextAccessTime": "2016-May-21
15:36:00+ UTC" } }

*Blocked Response*

{
"fault": { "code": 900805, "message": "Message blocked", "description": "You
have been blocked from accessing the resource" } }

*Throttle Out by Custom Policy Response*

{ "fault": { "code": 900806, "message": "Message throttled out", "
description": "You have exceeded your quota", "nextAccessTime": "2016-May-21
17:05:10+ UTC" } }

On Mon, May 23, 2016 at 5:20 PM, Isabelle Mauny  wrote:

> +1 !! No debug logs allowed here. All the tracking of what’s happening
> must be easily available - Using don’t have to debug this, they need to
> understand that is happening based on the information they have set ( and
> no that does not mean debugging CEP either, which just happens to be the
> engine we are relying on)
>
> Isabelle.
> __
>
> Isabelle Mauny
> VP, Product Management; WSO2, Inc.;  http://wso2.com/
>
>
> On May 23, 2016, at 1:45 PM, Uvindra Dias Jayasinha 
> wrote:
>
> Debug logging might not always be a feasible option for this. CEP engine
> should be able to tell what events triggered a given rule right(for
> auditing purposes)?
>
> On 23 May 2016 at 15:09, Harsha Kumara  wrote:
>
>> Yes, we are returning different codes for each level of throttle. Also
>> enabling debug logs should give more information as well. So you can
>> identify which level you have been throttle out from codes. I agree with
>> you that we need to clearly mentioned the use of each level of throttling.
>> Users will need throttle on few levels depend on their requirements. Since
>> we are providing the flexibility to apply throttling at different levels,
>> with proper details they can apply required throttling levels based on what
>> they really need for the protect their APIs. I have mentioned all the
>> responses return by APIM for each level of throttling in[1] mail thread.
>>
>> [1] - CEP Based Throttling Implementation - Changes in Quota calculations
>>
>>
>> On Mon, May 23, 2016 at 3:00 PM, Uvindra Dias Jayasinha > > wrote:
>>
>>> Thanks for clearing that up Harsha, with all these different
>>> combinations its going to be tricky to know what a users or applications
>>> effective quota is going to be. Its going to be just as hard to debug
>>> throttling related scenarios. Do we have a way of diagnosing(getting some
>>> feedback) regarding the effective quota that is being enforced? This is
>>> extremely important or we wont be able to explain why throttling is
>>> happening in a certain way.
>>>
>>> On 23 May 2016 at 14:24, Harsha Kumara  wrote:
>>>
 I also missed one more types of throttle policy. We have added
 capability define custom policies for super tenant. Those policies will be
 applied across all APIs globally. With custom policies, user can write a
 siddhi query with stream data and define a throtttleKey based on their
  requirement and it will deploy to  CEP. Then those custom policies will
 apply for all the APIs.



 On Mon, May 23, 2016 at 2:20 PM, Harsha Kumara 
 wrote:

>
>
> On Mon, May 23, 2016 at 10:57 AM, Uvindra Dias Jayasinha <
> uvin...@wso2.com> wrote:
>
>> Can we simplify the definition a bit more? Seems that the main thing
>> we have done here is having a differentiation between individual user/app
>> quotas and shared quotas across all users/apps. I think we need to 

Re: [Dev] [MSF4J] Clarification on debugging a micro service

[Afkham Azeez]

+isuru

On Fri, May 20, 2016 at 2:01 PM, Sabra Ossen  wrote:

> Hi All,
>
> I am trying the example in [1] and trying to debug the micro service and
> identify details of events being published to WSO2 DAS. I set a debug point
> in [2] and I could see that the HTTPMonitoringInterceptor is initialized
> and then the HTTPMonitoringDataPublisher is initialized.
>
> The data has been published to the DAS. But during debugging the code
> doesn't reach debug point [3] when I invoke the micro service.
>
> Am I debugging the micro service correctly. Any clarification on the issue
> is appreciated.
>
> [1]
> https://github.com/wso2/msf4j/tree/master/samples/metrics-httpmon/metrics-httpmon-fatjar
> [2]
> https://github.com/wso2/msf4j/blob/master/samples/metrics-httpmon/metrics-httpmon-fatjar/src/main/java/org/wso2/msf4j/example/Application.java#L36
> [3]
> https://github.com/wso2/msf4j/blob/master/analytics/msf4j-analytics/src/main/java/org/wso2/msf4j/analytics/httpmonitoring/HTTPMonitoringDataPublisher.java#L182
>
> Thanks and Regards.
>
> --
> *Sabra Ossen*
> *Software Engineer*
> Email: sa...@wso2.com
> Mobile: +94 767 837356
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] Why there is a TestNG version 6.9.11 in WSO2 Maven Repo??

[Dharshana Warusavitharana]

Yes we have to remove that.

On Mon, May 23, 2016 at 5:04 PM, Isuru Perera  wrote:

> Hi,
>
> On Mon, May 23, 2016 at 4:57 PM, Dharshana Warusavitharana <
> dharsha...@wso2.com> wrote:
>
>> Hi Isuru,
>>
>> This seems a cached dependency on wso2 repository. the correct version is
>> 6.9.10.  I have no idea how 6.9.11 was cashed.
>>
> There is no 6.9.11 version yet. So, how it can be a cached one? If that's
> not a correct version, can we remove it from WSO2 Maven Repo?
>
> Carbon Team, do you have any idea on $subject?
>
>>
>> Thank you,
>> Dharshana.
>>
>> On Mon, May 23, 2016 at 4:50 PM, Isuru Perera  wrote:
>>
>>> ping!
>>>
>>> On Thu, May 19, 2016 at 2:49 PM, Isuru Perera  wrote:
>>>
 Hi,

 I noticed that there is a TestNG version 6.9.11 in WSO2 Maven Repo.

 The latest TestNG version is 6.9.10 [2, 3].

 I usually use "mvn versions:display-dependency-updates" to update my
 dependencies and I thought TestNG 6.9.11 is the latest version.

 I had an issue with Pax Exam OSGi tests and the build was not failing
 if there is an assertion error in TestNG 6.9.11.

 However that issue is solved when using the TestNG 6.9.10.

 I was checking on this issue for few days because of the this unknown
 TestNG version in WSO2 Maven Repo! :(

 [1]
 http://maven.wso2.org/nexus/content/groups/wso2-public/org/testng/testng/6.9.11/
 [2] http://search.maven.org/#search|ga|1|testng
 [3] http://mvnrepository.com/artifact/org.testng/testng

 --
 Isuru Perera
 Associate Technical Lead | WSO2, Inc. | http://wso2.com/
 Lean . Enterprise . Middleware

 about.me/chrishantha
 Contact: +IsuruPereraWSO2
 

>>>
>>>
>>>
>>> --
>>> Isuru Perera
>>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> about.me/chrishantha
>>> Contact: +IsuruPereraWSO2
>>> 
>>>
>>
>>
>>
>> --
>>
>> Dharshana Warusavitharana
>> Senior Software Engineer , Test Automation
>> WSO2 Inc. http://wso2.com
>> email : dharsha...@wso2.com 
>> Tel  : +94 11 214 5345
>> Fax :+94 11 2145300
>> cell : +94770342233
>> blog : http://dharshanaw.blogspot.com
>>
>> lean . enterprise . middleware
>>
>
>
>
> --
> Isuru Perera
> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>



-- 

Dharshana Warusavitharana
Senior Software Engineer , Test Automation
WSO2 Inc. http://wso2.com
email : dharsha...@wso2.com 
Tel  : +94 11 214 5345
Fax :+94 11 2145300
cell : +94770342233
blog : http://dharshanaw.blogspot.com

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

Re: [Dev] Can we use Snakeyaml 1.17 in Carbon 5.1.0?

[Isuru Perera]

No, not a blocker. I just checked.

On Mon, May 23, 2016 at 4:53 PM, Niranjan Karunanandham 
wrote:

> Hi Isuru,
>
> Currently we are working on the Beta release for Carbon 5.1.0. Is this a
> blocker for the release?
>
> Regards,
> Nira
>
> On Mon, May 23, 2016 at 4:50 PM, Isuru Perera  wrote:
>
>> Hi Nira,
>>
>> Will you upgrade the snakeyaml version?
>>
>> On Thu, May 19, 2016 at 1:32 PM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Isuru,
>>>
>>> +1 to upgrade the snakeyaml version. IMO it would be better to upgrade
>>> the version, but before that we need to verify if there has been any API
>>> changes (since it is a minor release).
>>>
>>> Regards,
>>> Nira
>>>
>>> On Thu, May 19, 2016 at 1:27 PM, Isuru Perera  wrote:
>>>
 Hi Carbon Team,

 I noticed that there is a new version for snakeyaml [1]. Do you usually
 check your dependencies before releasing a new Carbon Kernel version?

 [1] http://mvnrepository.com/artifact/org.yaml/snakeyaml

 --
 Isuru Perera
 Associate Technical Lead | WSO2, Inc. | http://wso2.com/
 Lean . Enterprise . Middleware

 about.me/chrishantha
 Contact: +IsuruPereraWSO2
 

>>>
>>>
>>>
>>> --
>>>
>>> *Niranjan Karunanandham*
>>> Senior Software Engineer - WSO2 Inc.
>>> WSO2 Inc.: http://www.wso2.com
>>>
>>
>>
>>
>> --
>> Isuru Perera
>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>> Contact: +IsuruPereraWSO2 
>>
>
>
>
> --
>
> *Niranjan Karunanandham*
> Senior Software Engineer - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>



-- 
Isuru Perera
Associate Technical Lead | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
Contact: +IsuruPereraWSO2 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Why there is a TestNG version 6.9.11 in WSO2 Maven Repo??

[Isuru Perera]

Hi,

On Mon, May 23, 2016 at 4:57 PM, Dharshana Warusavitharana <
dharsha...@wso2.com> wrote:

> Hi Isuru,
>
> This seems a cached dependency on wso2 repository. the correct version is
> 6.9.10.  I have no idea how 6.9.11 was cashed.
>
There is no 6.9.11 version yet. So, how it can be a cached one? If that's
not a correct version, can we remove it from WSO2 Maven Repo?

Carbon Team, do you have any idea on $subject?

>
> Thank you,
> Dharshana.
>
> On Mon, May 23, 2016 at 4:50 PM, Isuru Perera  wrote:
>
>> ping!
>>
>> On Thu, May 19, 2016 at 2:49 PM, Isuru Perera  wrote:
>>
>>> Hi,
>>>
>>> I noticed that there is a TestNG version 6.9.11 in WSO2 Maven Repo.
>>>
>>> The latest TestNG version is 6.9.10 [2, 3].
>>>
>>> I usually use "mvn versions:display-dependency-updates" to update my
>>> dependencies and I thought TestNG 6.9.11 is the latest version.
>>>
>>> I had an issue with Pax Exam OSGi tests and the build was not failing if
>>> there is an assertion error in TestNG 6.9.11.
>>>
>>> However that issue is solved when using the TestNG 6.9.10.
>>>
>>> I was checking on this issue for few days because of the this unknown
>>> TestNG version in WSO2 Maven Repo! :(
>>>
>>> [1]
>>> http://maven.wso2.org/nexus/content/groups/wso2-public/org/testng/testng/6.9.11/
>>> [2] http://search.maven.org/#search|ga|1|testng
>>> [3] http://mvnrepository.com/artifact/org.testng/testng
>>>
>>> --
>>> Isuru Perera
>>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> about.me/chrishantha
>>> Contact: +IsuruPereraWSO2
>>> 
>>>
>>
>>
>>
>> --
>> Isuru Perera
>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>> Contact: +IsuruPereraWSO2 
>>
>
>
>
> --
>
> Dharshana Warusavitharana
> Senior Software Engineer , Test Automation
> WSO2 Inc. http://wso2.com
> email : dharsha...@wso2.com 
> Tel  : +94 11 214 5345
> Fax :+94 11 2145300
> cell : +94770342233
> blog : http://dharshanaw.blogspot.com
>
> lean . enterprise . middleware
>



-- 
Isuru Perera
Associate Technical Lead | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
Contact: +IsuruPereraWSO2 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Why there is a TestNG version 6.9.11 in WSO2 Maven Repo??

[Dharshana Warusavitharana]

Hi Isuru,

This seems a cached dependency on wso2 repository. the correct version is
6.9.10.  I have no idea how 6.9.11 was cashed.

Thank you,
Dharshana.

On Mon, May 23, 2016 at 4:50 PM, Isuru Perera  wrote:

> ping!
>
> On Thu, May 19, 2016 at 2:49 PM, Isuru Perera  wrote:
>
>> Hi,
>>
>> I noticed that there is a TestNG version 6.9.11 in WSO2 Maven Repo.
>>
>> The latest TestNG version is 6.9.10 [2, 3].
>>
>> I usually use "mvn versions:display-dependency-updates" to update my
>> dependencies and I thought TestNG 6.9.11 is the latest version.
>>
>> I had an issue with Pax Exam OSGi tests and the build was not failing if
>> there is an assertion error in TestNG 6.9.11.
>>
>> However that issue is solved when using the TestNG 6.9.10.
>>
>> I was checking on this issue for few days because of the this unknown
>> TestNG version in WSO2 Maven Repo! :(
>>
>> [1]
>> http://maven.wso2.org/nexus/content/groups/wso2-public/org/testng/testng/6.9.11/
>> [2] http://search.maven.org/#search|ga|1|testng
>> [3] http://mvnrepository.com/artifact/org.testng/testng
>>
>> --
>> Isuru Perera
>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>> Contact: +IsuruPereraWSO2 
>>
>
>
>
> --
> Isuru Perera
> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>



-- 

Dharshana Warusavitharana
Senior Software Engineer , Test Automation
WSO2 Inc. http://wso2.com
email : dharsha...@wso2.com 
Tel  : +94 11 214 5345
Fax :+94 11 2145300
cell : +94770342233
blog : http://dharshanaw.blogspot.com

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

Re: [Dev] Can we use Snakeyaml 1.17 in Carbon 5.1.0?

[Niranjan Karunanandham]

Hi Isuru,

Currently we are working on the Beta release for Carbon 5.1.0. Is this a
blocker for the release?

Regards,
Nira

On Mon, May 23, 2016 at 4:50 PM, Isuru Perera  wrote:

> Hi Nira,
>
> Will you upgrade the snakeyaml version?
>
> On Thu, May 19, 2016 at 1:32 PM, Niranjan Karunanandham  > wrote:
>
>> Hi Isuru,
>>
>> +1 to upgrade the snakeyaml version. IMO it would be better to upgrade
>> the version, but before that we need to verify if there has been any API
>> changes (since it is a minor release).
>>
>> Regards,
>> Nira
>>
>> On Thu, May 19, 2016 at 1:27 PM, Isuru Perera  wrote:
>>
>>> Hi Carbon Team,
>>>
>>> I noticed that there is a new version for snakeyaml [1]. Do you usually
>>> check your dependencies before releasing a new Carbon Kernel version?
>>>
>>> [1] http://mvnrepository.com/artifact/org.yaml/snakeyaml
>>>
>>> --
>>> Isuru Perera
>>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> about.me/chrishantha
>>> Contact: +IsuruPereraWSO2
>>> 
>>>
>>
>>
>>
>> --
>>
>> *Niranjan Karunanandham*
>> Senior Software Engineer - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>
>
>
> --
> Isuru Perera
> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>



-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Why there is a TestNG version 6.9.11 in WSO2 Maven Repo??

[Isuru Perera]

ping!

On Thu, May 19, 2016 at 2:49 PM, Isuru Perera  wrote:

> Hi,
>
> I noticed that there is a TestNG version 6.9.11 in WSO2 Maven Repo.
>
> The latest TestNG version is 6.9.10 [2, 3].
>
> I usually use "mvn versions:display-dependency-updates" to update my
> dependencies and I thought TestNG 6.9.11 is the latest version.
>
> I had an issue with Pax Exam OSGi tests and the build was not failing if
> there is an assertion error in TestNG 6.9.11.
>
> However that issue is solved when using the TestNG 6.9.10.
>
> I was checking on this issue for few days because of the this unknown
> TestNG version in WSO2 Maven Repo! :(
>
> [1]
> http://maven.wso2.org/nexus/content/groups/wso2-public/org/testng/testng/6.9.11/
> [2] http://search.maven.org/#search|ga|1|testng
> [3] http://mvnrepository.com/artifact/org.testng/testng
>
> --
> Isuru Perera
> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>



-- 
Isuru Perera
Associate Technical Lead | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
Contact: +IsuruPereraWSO2 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Can we use Snakeyaml 1.17 in Carbon 5.1.0?

[Isuru Perera]

Hi Nira,

Will you upgrade the snakeyaml version?

On Thu, May 19, 2016 at 1:32 PM, Niranjan Karunanandham 
wrote:

> Hi Isuru,
>
> +1 to upgrade the snakeyaml version. IMO it would be better to upgrade the
> version, but before that we need to verify if there has been any API
> changes (since it is a minor release).
>
> Regards,
> Nira
>
> On Thu, May 19, 2016 at 1:27 PM, Isuru Perera  wrote:
>
>> Hi Carbon Team,
>>
>> I noticed that there is a new version for snakeyaml [1]. Do you usually
>> check your dependencies before releasing a new Carbon Kernel version?
>>
>> [1] http://mvnrepository.com/artifact/org.yaml/snakeyaml
>>
>> --
>> Isuru Perera
>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>> Contact: +IsuruPereraWSO2 
>>
>
>
>
> --
>
> *Niranjan Karunanandham*
> Senior Software Engineer - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>



-- 
Isuru Perera
Associate Technical Lead | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
Contact: +IsuruPereraWSO2 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IoTS]Error when downloading virtual fire alarm on IoT Server in Windows

[Ayyoob Hamza]

Hi Dakshitha,
In our sample implementation we delete the sketch from the temporary folder
once the device agent zip is created. In windows it does not allow todo
when the pack is in the C Drive since it requires admin permission. Could
it be possible to try this out in another drive.

Thanks
Ayyoob

*Ayyoob Hamza*
*Software Engineer*
WSO2 Inc.; http://wso2.com
email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [cep][ml][gsoc-6]Capturing event stream with a specified window size for ml

[Mahesh Dananjaya]

Hi Maheshkya,
Ok.then we have a output data too. I thought those data wont be sending
back to cep. In that case we can easily send those info back.thank you for
correcting.
regards,
Mahesh.

On Mon, May 23, 2016 at 3:09 PM, Maheshakya Wijewardena  wrote:

> Hi Mahesh,
>
> Actually, IMO, there should be an output for trained model, which is the
> evaluation metric; for linear regression, MSE and for logistic regression,
> accuracy. For clustering, it could be cluster centers.
> That way, it's possible to examine how model behaves with data.
>
> Best regards.
>
> On Mon, May 23, 2016 at 3:06 PM, Mahesh Dananjaya <
> dananjayamah...@gmail.com> wrote:
>
>> Hi suho,
>> in my project machine learning models are incrementally being trained.
>> Therefore real time data is taken into my design as mini batches of data
>> sample points. Since we are developing this models for cep siddhi
>> processor,we want to get the mini batch of data points into my algorithms
>> from siddhi processor. In my case there is a input stream of K-size
>> (Batch/Window Size) of sample points bundles together. In linear regrassion
>> case all the independent and dependent data, In K-mean case whole feature
>> vector (data sample). Not only as single sample points (Window size=1), but
>> also as mini-batch (Window size=N)of sample points (Stream data). In my
>> case there wont be an output stream. The modeled will be there so even
>> predict can be used with that models.I looked into the [1] also.thank you.
>> regards,
>> Mahesh.
>> [1]
>> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Stream+Processor+Extension
>>
>> On Mon, May 23, 2016 at 2:48 PM, Sriskandarajah Suhothayan > > wrote:
>>
>>> Hi Mahesh
>>>
>>> Can you explain the expected input to your extension and the expected
>>> output. Then we can help you to find the proper Siddhi extension to use.
>>>
>>> Regards
>>> Suho
>>>
>>> On Sat, May 21, 2016 at 11:44 AM, Mahesh Dananjaya <
>>> dananjayamah...@gmail.com> wrote:
>>>
 Hi all,
 i am currenl working on the gsoc project "Predictive analytics with
 online data for WSO2 Machine Learner
 "
 with wso2 ML and cep extention for acquiring stream of events (sample data
 points interms of ml) from cep siddhi porocessor. I am trying to write a
 cep extention to get the stream of events as windows with a "Specified
 window size". Then i am using those data sets to incrementally and
 periodically learn the ML model which store the specific ml model
 information to use with the current window of event data samples. I am
 facing problem of writing a siddhi extention for my purpose to get stream
 of data windows from cep siddhi rpocessor. Please help me with followings.
 1. I have been referring to [1] [2] [3] for writing siddhi extention.
 In my case,what can be the most suitable option for this among the set
 of siddhi extensions given?

 2. I am currently working on carbon-ml and product-ml and ml cep
 extentions currently built [6]. In case what is the best way to write
 simple cep extention to check the functionality.?

 3. I have gone through the [5] [4] for cep inbuilt windows. How can i
 effectivey aggregate those features into my case?

 In case, if i need to look into other areas of cep for this purpose
 please let me know. Thank you very much.
 regards,
 Mahesh.
 [1]https://docs.wso2.com/display/CEP310/Writing+Extensions+to+Siddhi
 https://docs.wso2.com/display/CEP310/Writing+Extensions+to+Siddhi
 [2]https://docs.wso2.com/display/CEP400/Writing+Extensions+to+Siddhi
 https://docs.wso2.com/display/CEP400/Writing+Extensions+to+Siddhi
 [3]https://docs.wso2.com/display/CEP310/Writing+a+Custom+Function
 https://docs.wso2.com/display/CEP310/Writing+a+Custom+Function
 [4]
 https://docs.wso2.com/display/CEP400/Inbuilt+Windows#InbuiltWindows-lengthlength
 https://docs.wso2.com/display/CEP400/Inbuilt+Windows#InbuiltWindows-lengthlength
 [5]
 https://docs.wso2.com/display/CEP400/Writing+a+Custom+Aggregate+Function
 https://docs.wso2.com/display/CEP400/Writing+a+Custom+Aggregate+Function
 [6]
 https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions#WSO2CEPExtensionforMLPredictions-Siddhisyntaxfortheextension
 https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions#WSO2CEPExtensionforMLPredictions-Siddhisyntaxfortheextension

>>>
>>>
>>>
>>> --
>>>
>>> *S. Suhothayan*
>>> Technical Lead & Team Lead of WSO2 Complex Event Processor
>>> *WSO2 Inc. *http://wso2.com
>>> * *
>>> lean . enterprise . middleware
>>>
>>>
>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
>>> http://suhothayan.blogspot.com/ 

Re: [Dev] [cep][ml][gsoc-6]Capturing event stream with a specified window size for ml

[Maheshakya Wijewardena]

Hi Mahesh,

Actually, IMO, there should be an output for trained model, which is the
evaluation metric; for linear regression, MSE and for logistic regression,
accuracy. For clustering, it could be cluster centers.
That way, it's possible to examine how model behaves with data.

Best regards.

On Mon, May 23, 2016 at 3:06 PM, Mahesh Dananjaya  wrote:

> Hi suho,
> in my project machine learning models are incrementally being trained.
> Therefore real time data is taken into my design as mini batches of data
> sample points. Since we are developing this models for cep siddhi
> processor,we want to get the mini batch of data points into my algorithms
> from siddhi processor. In my case there is a input stream of K-size
> (Batch/Window Size) of sample points bundles together. In linear regrassion
> case all the independent and dependent data, In K-mean case whole feature
> vector (data sample). Not only as single sample points (Window size=1), but
> also as mini-batch (Window size=N)of sample points (Stream data). In my
> case there wont be an output stream. The modeled will be there so even
> predict can be used with that models.I looked into the [1] also.thank you.
> regards,
> Mahesh.
> [1]
> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Stream+Processor+Extension
>
> On Mon, May 23, 2016 at 2:48 PM, Sriskandarajah Suhothayan 
> wrote:
>
>> Hi Mahesh
>>
>> Can you explain the expected input to your extension and the expected
>> output. Then we can help you to find the proper Siddhi extension to use.
>>
>> Regards
>> Suho
>>
>> On Sat, May 21, 2016 at 11:44 AM, Mahesh Dananjaya <
>> dananjayamah...@gmail.com> wrote:
>>
>>> Hi all,
>>> i am currenl working on the gsoc project "Predictive analytics with
>>> online data for WSO2 Machine Learner
>>> "
>>> with wso2 ML and cep extention for acquiring stream of events (sample data
>>> points interms of ml) from cep siddhi porocessor. I am trying to write a
>>> cep extention to get the stream of events as windows with a "Specified
>>> window size". Then i am using those data sets to incrementally and
>>> periodically learn the ML model which store the specific ml model
>>> information to use with the current window of event data samples. I am
>>> facing problem of writing a siddhi extention for my purpose to get stream
>>> of data windows from cep siddhi rpocessor. Please help me with followings.
>>> 1. I have been referring to [1] [2] [3] for writing siddhi extention. In
>>> my case,what can be the most suitable option for this among the set of
>>> siddhi extensions given?
>>>
>>> 2. I am currently working on carbon-ml and product-ml and ml cep
>>> extentions currently built [6]. In case what is the best way to write
>>> simple cep extention to check the functionality.?
>>>
>>> 3. I have gone through the [5] [4] for cep inbuilt windows. How can i
>>> effectivey aggregate those features into my case?
>>>
>>> In case, if i need to look into other areas of cep for this purpose
>>> please let me know. Thank you very much.
>>> regards,
>>> Mahesh.
>>> [1]https://docs.wso2.com/display/CEP310/Writing+Extensions+to+Siddhi
>>> https://docs.wso2.com/display/CEP310/Writing+Extensions+to+Siddhi
>>> [2]https://docs.wso2.com/display/CEP400/Writing+Extensions+to+Siddhi
>>> https://docs.wso2.com/display/CEP400/Writing+Extensions+to+Siddhi
>>> [3]https://docs.wso2.com/display/CEP310/Writing+a+Custom+Function
>>> https://docs.wso2.com/display/CEP310/Writing+a+Custom+Function
>>> [4]
>>> https://docs.wso2.com/display/CEP400/Inbuilt+Windows#InbuiltWindows-lengthlength
>>> https://docs.wso2.com/display/CEP400/Inbuilt+Windows#InbuiltWindows-lengthlength
>>> [5]
>>> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Aggregate+Function
>>> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Aggregate+Function
>>> [6]
>>> https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions#WSO2CEPExtensionforMLPredictions-Siddhisyntaxfortheextension
>>> https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions#WSO2CEPExtensionforMLPredictions-Siddhisyntaxfortheextension
>>>
>>
>>
>>
>> --
>>
>> *S. Suhothayan*
>> Technical Lead & Team Lead of WSO2 Complex Event Processor
>> *WSO2 Inc. *http://wso2.com
>> * *
>> lean . enterprise . middleware
>>
>>
>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
>> http://suhothayan.blogspot.com/ twitter:
>> http://twitter.com/suhothayan  | linked-in:
>> http://lk.linkedin.com/in/suhothayan *
>>
>
>


-- 
Pruthuvi Maheshakya Wijewardena
mahesha...@wso2.com
+94711228855
___
Dev mailing list
Dev@wso2.org

[Dev] [APIM-Anlytics]Classifying severity of alert types

[Fazlan Nazeem]

Hi,

We need to classify the alert types into different severity levels as
discussed in the previous APIM analytics demo meeting. We have planned to
have 3 severity levels as follows.

   - Severe
   - Moderate
   - Mild


The initial classification of alerts in in [1]. Please suggest any if any
changes need to be done.

[1]
https://docs.google.com/a/wso2.com/spreadsheets/d/13By0F8IwQBPsdTa7BjWUq9ebryNfItGpkuJY5JHAyrc/edit?usp=sharing


Thanks & Regards,

Fazlan Nazeem

*Software Engineer*

*WSO2 Inc*
Mobile : +94772338839
<%2B94%20%280%29%20773%20451194>
fazl...@wso2.com


Alert Severity Categroization.xlsx
Description: MS-Excel 2007 spreadsheet
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [cep][ml][gsoc-6]Capturing event stream with a specified window size for ml

[Mahesh Dananjaya]

Hi suho,
in my project machine learning models are incrementally being trained.
Therefore real time data is taken into my design as mini batches of data
sample points. Since we are developing this models for cep siddhi
processor,we want to get the mini batch of data points into my algorithms
from siddhi processor. In my case there is a input stream of K-size
(Batch/Window Size) of sample points bundles together. In linear regrassion
case all the independent and dependent data, In K-mean case whole feature
vector (data sample). Not only as single sample points (Window size=1), but
also as mini-batch (Window size=N)of sample points (Stream data). In my
case there wont be an output stream. The modeled will be there so even
predict can be used with that models.I looked into the [1] also.thank you.
regards,
Mahesh.
[1]
https://docs.wso2.com/display/CEP400/Writing+a+Custom+Stream+Processor+Extension

On Mon, May 23, 2016 at 2:48 PM, Sriskandarajah Suhothayan 
wrote:

> Hi Mahesh
>
> Can you explain the expected input to your extension and the expected
> output. Then we can help you to find the proper Siddhi extension to use.
>
> Regards
> Suho
>
> On Sat, May 21, 2016 at 11:44 AM, Mahesh Dananjaya <
> dananjayamah...@gmail.com> wrote:
>
>> Hi all,
>> i am currenl working on the gsoc project "Predictive analytics with
>> online data for WSO2 Machine Learner
>> "
>> with wso2 ML and cep extention for acquiring stream of events (sample data
>> points interms of ml) from cep siddhi porocessor. I am trying to write a
>> cep extention to get the stream of events as windows with a "Specified
>> window size". Then i am using those data sets to incrementally and
>> periodically learn the ML model which store the specific ml model
>> information to use with the current window of event data samples. I am
>> facing problem of writing a siddhi extention for my purpose to get stream
>> of data windows from cep siddhi rpocessor. Please help me with followings.
>> 1. I have been referring to [1] [2] [3] for writing siddhi extention. In
>> my case,what can be the most suitable option for this among the set of
>> siddhi extensions given?
>>
>> 2. I am currently working on carbon-ml and product-ml and ml cep
>> extentions currently built [6]. In case what is the best way to write
>> simple cep extention to check the functionality.?
>>
>> 3. I have gone through the [5] [4] for cep inbuilt windows. How can i
>> effectivey aggregate those features into my case?
>>
>> In case, if i need to look into other areas of cep for this purpose
>> please let me know. Thank you very much.
>> regards,
>> Mahesh.
>> [1]https://docs.wso2.com/display/CEP310/Writing+Extensions+to+Siddhi
>> https://docs.wso2.com/display/CEP310/Writing+Extensions+to+Siddhi
>> [2]https://docs.wso2.com/display/CEP400/Writing+Extensions+to+Siddhi
>> https://docs.wso2.com/display/CEP400/Writing+Extensions+to+Siddhi
>> [3]https://docs.wso2.com/display/CEP310/Writing+a+Custom+Function
>> https://docs.wso2.com/display/CEP310/Writing+a+Custom+Function
>> [4]
>> https://docs.wso2.com/display/CEP400/Inbuilt+Windows#InbuiltWindows-lengthlength
>> https://docs.wso2.com/display/CEP400/Inbuilt+Windows#InbuiltWindows-lengthlength
>> [5]
>> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Aggregate+Function
>> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Aggregate+Function
>> [6]
>> https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions#WSO2CEPExtensionforMLPredictions-Siddhisyntaxfortheextension
>> https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions#WSO2CEPExtensionforMLPredictions-Siddhisyntaxfortheextension
>>
>
>
>
> --
>
> *S. Suhothayan*
> Technical Lead & Team Lead of WSO2 Complex Event Processor
> *WSO2 Inc. *http://wso2.com
> * *
> lean . enterprise . middleware
>
>
> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
> http://suhothayan.blogspot.com/ twitter:
> http://twitter.com/suhothayan  | linked-in:
> http://lk.linkedin.com/in/suhothayan *
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [cep][ml][gsoc-6]Capturing event stream with a specified window size for ml

[Sriskandarajah Suhothayan]

Hi Mahesh

Can you explain the expected input to your extension and the expected
output. Then we can help you to find the proper Siddhi extension to use.

Regards
Suho

On Sat, May 21, 2016 at 11:44 AM, Mahesh Dananjaya <
dananjayamah...@gmail.com> wrote:

> Hi all,
> i am currenl working on the gsoc project "Predictive analytics with
> online data for WSO2 Machine Learner
> "
> with wso2 ML and cep extention for acquiring stream of events (sample data
> points interms of ml) from cep siddhi porocessor. I am trying to write a
> cep extention to get the stream of events as windows with a "Specified
> window size". Then i am using those data sets to incrementally and
> periodically learn the ML model which store the specific ml model
> information to use with the current window of event data samples. I am
> facing problem of writing a siddhi extention for my purpose to get stream
> of data windows from cep siddhi rpocessor. Please help me with followings.
> 1. I have been referring to [1] [2] [3] for writing siddhi extention. In
> my case,what can be the most suitable option for this among the set of
> siddhi extensions given?
>
> 2. I am currently working on carbon-ml and product-ml and ml cep
> extentions currently built [6]. In case what is the best way to write
> simple cep extention to check the functionality.?
>
> 3. I have gone through the [5] [4] for cep inbuilt windows. How can i
> effectivey aggregate those features into my case?
>
> In case, if i need to look into other areas of cep for this purpose please
> let me know. Thank you very much.
> regards,
> Mahesh.
> [1]https://docs.wso2.com/display/CEP310/Writing+Extensions+to+Siddhi
> https://docs.wso2.com/display/CEP310/Writing+Extensions+to+Siddhi
> [2]https://docs.wso2.com/display/CEP400/Writing+Extensions+to+Siddhi
> https://docs.wso2.com/display/CEP400/Writing+Extensions+to+Siddhi
> [3]https://docs.wso2.com/display/CEP310/Writing+a+Custom+Function
> https://docs.wso2.com/display/CEP310/Writing+a+Custom+Function
> [4]
> https://docs.wso2.com/display/CEP400/Inbuilt+Windows#InbuiltWindows-lengthlength
> https://docs.wso2.com/display/CEP400/Inbuilt+Windows#InbuiltWindows-lengthlength
> [5]
> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Aggregate+Function
> https://docs.wso2.com/display/CEP400/Writing+a+Custom+Aggregate+Function
> [6]
> https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions#WSO2CEPExtensionforMLPredictions-Siddhisyntaxfortheextension
> https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions#WSO2CEPExtensionforMLPredictions-Siddhisyntaxfortheextension
>



-- 

*S. Suhothayan*
Technical Lead & Team Lead of WSO2 Complex Event Processor
*WSO2 Inc. *http://wso2.com
* *
lean . enterprise . middleware


*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: http://twitter.com/suhothayan
 | linked-in:
http://lk.linkedin.com/in/suhothayan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Getting org.osgi.framework.ServiceException with PaxExam tests.

[Hasitha Aravinda]

Hi Dharshana,

I am writing a PAX Exam test cases [1] ( You can check out and build) and
getting following error [2]. Even I get this error, it is not affecting to
test scenarios. Any thoughts on this. ?

[1] - https://github.com/hasithaa/carbon-business-process

[2] -
14:30:14.222 [Framework Event Dispatcher: Equinox Container:
400bc2c0-c420-0016-1f8b-9c0e9399ab0f] ERROR org.wso2.carbon.bpmn -
FrameworkEvent ERROR - org.wso2.carbon.bpmn
org.osgi.framework.ServiceException:
org.eclipse.equinox.internal.ds.ServiceReg.getService() returned a service
object that is not an instance of the service class
org.wso2.carbon.bpmn.core.BPMNEngineService
at
org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.factoryGetService(ServiceFactoryUse.java:243)
~[?:?]
at
org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.getService(ServiceFactoryUse.java:111)
~[?:?]
at
org.eclipse.osgi.internal.serviceregistry.ServiceConsumer$2.getService(ServiceConsumer.java:45)
~[?:?]
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:496)
~[?:?]
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.getService(ServiceRegistry.java:461)
~[?:?]
at
org.eclipse.osgi.internal.framework.BundleContextImpl.getService(BundleContextImpl.java:619)
~[?:?]
at
org.osgi.util.tracker.ServiceTracker.addingService(ServiceTracker.java:414)
~[?:?]
at
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
~[?:?]
at
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
~[?:?]
at
org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
~[?:?]
at
org.osgi.util.tracker.AbstractTracked.trackInitial(AbstractTracked.java:183)
~[?:?]
at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:318) ~[?:?]
at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:261) ~[?:?]
at
org.ops4j.pax.swissbox.tracker.ServiceLookup.getService(ServiceLookup.java:195)
~[?:?]
at
org.ops4j.pax.swissbox.tracker.ServiceLookup.getService(ServiceLookup.java:136)
~[?:?]
at
org.ops4j.pax.exam.inject.internal.ServiceInjector.injectField(ServiceInjector.java:89)
~[?:?]
at
org.ops4j.pax.exam.inject.internal.ServiceInjector.injectDeclaredFields(ServiceInjector.java:69)
~[?:?]
at
org.ops4j.pax.exam.inject.internal.ServiceInjector.injectFields(ServiceInjector.java:61)
~[?:?]
at
org.ops4j.pax.exam.raw.extender.intern.ProbeInvokerImpl.injectContextAndInvoke(ProbeInvokerImpl.java:121)
~[?:?]
at
org.ops4j.pax.exam.raw.extender.intern.ProbeInvokerImpl.findAndInvoke(ProbeInvokerImpl.java:85)
~[?:?]
at
org.ops4j.pax.exam.raw.extender.intern.ProbeInvokerImpl.call(ProbeInvokerImpl.java:73)
~[?:?]
at
org.ops4j.pax.exam.nat.internal.NativeTestContainer.call(NativeTestContainer.java:109)
~[?:?]
at
org.ops4j.pax.exam.spi.reactors.EagerSingleStagedReactor.invoke(EagerSingleStagedReactor.java:109)
~[?:?]
at org.ops4j.pax.exam.testng.listener.PaxExam.runByDriver(PaxExam.java:458)
~[?:?]
at org.ops4j.pax.exam.testng.listener.PaxExam.run(PaxExam.java:308) ~[?:?]
at
org.testng.internal.MethodInvocationHelper.invokeHookable(MethodInvocationHelper.java:212)
~[?:?]
at org.testng.internal.Invoker.invokeMethod(Invoker.java:652) ~[?:?]
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:845) ~[?:?]
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1153) ~[?:?]
at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
~[?:?]
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
~[?:?]
at org.testng.TestRunner.privateRun(TestRunner.java:771) ~[?:?]
at org.testng.TestRunner.run(TestRunner.java:621) ~[?:?]
at org.testng.SuiteRunner.runTest(SuiteRunner.java:357) ~[?:?]
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352) ~[?:?]
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:310) ~[?:?]
at org.testng.SuiteRunner.run(SuiteRunner.java:259) ~[?:?]
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) ~[?:?]
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) ~[?:?]
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1199) ~[?:?]
at org.testng.TestNG.runSuitesLocally(TestNG.java:1124) ~[?:?]
at org.testng.TestNG.run(TestNG.java:1032) ~[?:?]
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:281)
~[?:?]
at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:75)
~[?:?]
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:121)
~[?:?]
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
~[?:?]
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
~[?:?]
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
~[?:?]

Thanks,
Hasitha.

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

[Dev] [IoTS]Error when downloading virtual fire alarm on IoT Server in Windows

[Dakshitha Ratnayake]

Please see error below -

Caused by: java.io.IOException: Unable to delete file:
C:\CLIENT~1\2016\IOT_SE~1\WSO2IO~1.0-A\bin\..\repository\resources\sketches\archives\1h8226aoqvo11\start-device.sh
at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2279)
at
org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1653)
at
org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1535)
at
org.wso2.carbon.device.mgt.iot.util.Utils.getSketchArchive(Utils.java:107)
at
org.wso2.carbon.device.mgt.iot.virtualfirealarm.service.impl.util.ZipUtil.createZipFile(ZipUtil.java:85)
... 53 more
[2016-05-23 14:18:06,740] ERROR - jag {}

-- 
Dakshitha Ratnayake | Lead Solutions Engineer | WSO2 
+94 772 962 552 | http://dakshithar.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)

[Manujith Pallewatte]

Hi all,

To update on the progress so far, after having a chat with Pushpalanka, I
started with the project code. Basic setups are done.
Necessary entry points for the service was identified and now I'm familiar
with the process of deploying the REST service as a Web app to the IS.

Right now, the getDecision method is implemented in a RESTful manner, using
Apache cxf (following the guidelines of SCIM implementation as suggested by
Pushpalanka and Omindu). The implementation works, yet it's only a test
implementation.

We are expecting to consult the community on the actual implementation of
the service, focusing on points like
1) End point URLs
2) Resource identification
3) Service method definitions

At the moment I'm struggling with implementations of some methods using the
current CXF version, hoping to resolve it ASAP.

Thanks,
Manujith

On Mon, May 16, 2016 at 11:18 AM, Pushpalanka Jayawardhana 
wrote:

> Hi Manujith,
>
> Good progress in getting familiar with the environment.
> So let's try to start with the scope of the project too.
>
> Since we are to work on implementing REST service, it is better to go
> through WSO2 guidelines for REST service implementation. Please find the
> white paper at[1] and the relevant discussion can be found at architecture
> mailing list under "REST API Guidelines". Then we can work on defining the
> API definition for the endpoint.
>
> You can also have a look at the existing WSO2 REST implementation to
> capture the followed patterns referring the SCIM[2] and OAuth endpoints[3].
>
>
> [1] - http://wso2.com/whitepapers/wso2-rest-apis-design-guidelines/
> [2] -
> https://github.com/wso2-extensions/identity-inbound-provisioning-scim/tree/master/components/org.wso2.carbon.identity.scim.provider
> [3] -
> https://github.com/wso2-extensions/identity-inbound-auth-oauth/tree/master/components/org.wso2.carbon.identity.oauth.endpoint
>
> Thanks,
> Pushpalanka
>
> On Wed, May 11, 2016 at 3:23 PM, Manujith Pallewatte <
> manujith...@gmail.com> wrote:
>
>> Hi Pushpalanka,
>>
>> I managed to setup the development environment and build all the sources
>> (thanks to Omindu :))
>> Then I made the PEP client using the entitlement stubs as you have
>> mentioned in a previous thread. It's working in an accepted state. But I
>> encountered some questions during the process, so I'm currently building a
>> doc with all the questions so I can document them and their answers for
>> future reference.
>> Other than that I'm trying to write different policies using XACML
>>
>> Also please let me know of any other steps i can follow to get familiar
>> with the components, specially the code since I'm only focusing on
>> Entitlement service right now
>>
>> Thank You
>> Manujith
>> --
>>
>>
>>
>> [image: Manujith Pallewatte on about.me]
>>
>> Manujith Pallewatte
>> about.me/manzzup
>>   
>>
>
>
>
> --
> Pushpalanka.
> --
> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons).
> Senior Software Engineer, WSO2 Lanka (pvt) Ltd;  wso2.com/
> Mobile: +94779716248
> Blog: pushpalankajaya.blogspot.com/ | LinkedIn:
> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka
>
>


-- 



[image: Manujith Pallewatte on about.me]

Manujith Pallewatte
about.me/manzzup
  
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MSF4J] Swagger documentation not working when using OSGi components.

[Afkham Azeez]

Yes, we have an issue with getting the libraries working in OSGi. I will
look into it.

On Mon, May 23, 2016 at 12:26 PM, Hemika Kodikara  wrote:

> Hi All,
>
> I have added the swagger documentation to my microservice. But I am unable
> to get the documentation generated through the browser.
>
> It seems the swagger definition service is only being added through the
> MicroserviceRunner class[1].
>
> [1] -
> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/MicroservicesRunner.java#L151
>
> Regards,
> Hemika
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>



-- 
*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] [API-M] API Definition and scopes do not get added and updated when using new REST API

[Shazni Nazir]

Hi Nuwan/API-M team,

When adding an API to API-M through the new REST API, with api defintion
and scopes together, the resources and scopes doesn't get added and the
exception [2] gets thrown. For example use the payload [3].

I debugged the carbon-apimgt and found the issue. The PR is sent to the git
repo [1]. Please review the change and merge it.

[1] https://github.com/wso2/carbon-apimgt/pull/2312

The issue however doesn't happen when adding through the publisher. The
reason is, the issue happens only when adding the API with scopes and api
Definitions at the same time. In publisher however, it normally doesn't
happen, since in the first page, the user add resources (uri-templates),
and then add scopes and attach to it. But when using REST API, when both
are used together, the scopes get added separately and subsequently the url
templates get added without scope id's just generated without getting set
in the uri-template objects, hence throwing a constraint violation at the
DB level. Without the fix, the scope id in the template always get set as
0.

Also when the API is updated with the REST API, the newly added uri-temples
and scopes do not get updated as well. The PR contains the fix for that as
well. This is due to not saving the swagger definitions in registry in
the apisApiIdPut method.

[2]

Caused by: org.wso2.carbon.apimgt.api.APIManagementException: Error while
adding URL template(s) to the database for API : admin-MyTest-1.1.1
at
org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO.handleException(ApiMgtDAO.java:7259)
at
org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO.addURLTemplates(ApiMgtDAO.java:6611)
at
org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO.addAPI(ApiMgtDAO.java:6269)
at
org.wso2.carbon.apimgt.impl.APIProviderImpl.addAPI(APIProviderImpl.java:589)
... 52 more
Caused by: java.sql.BatchUpdateException: Cannot add or update a child row:
a foreign key constraint fails (`apimdb`.`idn_oauth2_resource_scope`,
CONSTRAINT `idn_oauth2_resource_scope_ibfk_1` FOREIGN KEY (`SCOPE_ID`)
REFERENCES `idn_oauth2_scope` (`SCOPE_ID`) ON DELETE CASCADE ON UPDATE
CASCADE)
at
com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2056)
at
com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1467)
at
org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO.addURLTemplates(ApiMgtDAO.java:6607)
... 54 more
Caused by:
com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
Cannot add or update a child row: a foreign key constraint fails
(`apimdb`.`idn_oauth2_resource_scope`, CONSTRAINT
`idn_oauth2_resource_scope_ibfk_1` FOREIGN KEY (`SCOPE_ID`) REFERENCES
`idn_oauth2_scope` (`SCOPE_ID`) ON DELETE CASCADE ON UPDATE CASCADE)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1041)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4190)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4122)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2570)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2731)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2818)
at
com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2157)
at
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2460)
at
com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2008)
... 56 more


[3]

{
  "name": "TestAPI",
  "provider": "admin",
  "version": "2.2.3",
  "description": "This is a test API",
  "context": "testing",
  "cacheTimeout": 300,
  "subscriptionAvailability": null,
  "isDefaultVersion": false,
  "responseCaching": "Enabled",
  "visibility": "PUBLIC",
  "sequences": [
{
  "name": "json_to_xml_in_message",
  "config": null,
  "type": "in"
},
{
  "name": "xml_to_json_out_message",
  "config": null,
  "type": "out"
},
{
  "name": "json_fault",
  "config": null,
  "type": "fault"
}
  ],
  "businessInformation": {
"businessOwner": "sample",
"businessOwnerEmail": "sam...@gmail.com",
"technicalOwner": "check",
"technicalOwnerEmail": "ch...@wso2.com"
  },
  "tiers": [
"Bronze"
  ],
  "transport": [
"https",
"http"
  ],
  "visibleRoles": [
"test",
"good"
  ],
  "visibleTenants": [],
  "endpointConfig":

[Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

[Awanthika Senarath]

Hello Devs,


We are pleased to announce the vote for RC-2 of *WSO2 Developer Studio Tooling
for Platform 4.1.0.*

P2 repository of WSO2 developer Studio  Tooling for Platform 4.1.0 is
available here
.
Source
and Tag Location to be voted upon is available here

.

Developer Studio 4.1.0  Tooling for Platform is released on Developer
Studio kernel 4.1.0
Developer Studio Kernel contains a single feature which has the bundles
that are required to implement WSO2 specific product tooling on Eclipse.

   - This release contains Developer Studio migration to Eclipse mars
   - Improvements in the Developer Studio Updater tool for automatic updates



   1. [+] Stable - go ahead and release
   2. [-]  Broken - do not release (please explain why)


The platform could to be tested on top of Developer Studio Kernel with
compatible tooling SNAPSHOT versions available at [1].


[1]
http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/


Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] APIM 2.0.0-SNAPSHOT Nightly build - 22/05/2016

[Nuwan Dias]

These are UM tables, coming from the carbon kernel. These tables haven't
changed since carbon 4.2.x. Surprising to see this issue now.

On Mon, May 23, 2016 at 1:01 PM, Shavantha Weerasinghe 
wrote:

> Hi Bhathiya
>
> Attempt to create/list a subscriber user role failed with MSSQL2012 DB.
> The jira id is https://wso2.org/jira/browse/APIMANAGER-4876
>
> regards,
>
> Shavantha Weerasinghe
> Senior Software Engineer QA
> WSO2, Inc.
> lean.enterprise.middleware.
> http://wso2.com
> http://wso2.org
> Tel : 94 11 214 5345
> Fax :94 11 2145300
>
>
> On Sun, May 22, 2016 at 11:34 PM, Bhathiya Jayasekara 
> wrote:
>
>> Hi all,
>>
>> Please find APIM 2.0.0 SNAPSHOT nightly build here[1].
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/scratch/2016/apim-2.0.0/wso2am-2.0.0-SNAPSHOT-22-05-2016.zip
>>
>> Thanks,
>>
>>
>> --
>> *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
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nuwan Dias

Technical Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Axis fault while trying to publish API runtime statistics using rest client

[Fathima Dilhasha]

Thanks Thilini for the offline help.
The doc instructs to set the offset to 1. But when it comes to configuring
the analytics the port values correspond to an offset of 3.
I will create a doc jira on this.

Thanks.

On Mon, May 23, 2016 at 1:21 PM, Fathima Dilhasha  wrote:

> Hi,
>
> I am trying to follow [1]
> 
> to publish API runtime statistics using rest client. I have used fresh
> installations of APIM and DAS.
> Following is the axis fault I'm getting. Have I missed any configrations?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *TID: [-1234] [] [2016-05-23 13:13:49,741]  INFO
> {org.apache.axis2.transport.http.HTTPSender} -  Unable to sendViaPost to
> url[https://localhost:9446/services/CarbonAppUploader
> ]
> {org.apache.axis2.transport.http.HTTPSender}java.net.ConnectException:
> Connection refusedat java.net.PlainSocketImpl.socketConnect(Native
> Method)at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)at
> java.net.Socket.connect(Socket.java:579)at
> sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:625)at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)at
> org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:140)
> at
> org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:130)
> at
> org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
> at
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> at
> org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:630)
> at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:195)
> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.carbon.application.mgt.stub.upload.CarbonAppUploaderStub.uploadApp(CarbonAppUploaderStub.java:184)
> at
> org.wso2.carbon.apimgt.usage.client.impl.APIUsageStatisticsRestClientImpl.deployArtifacts(APIUsageStatisticsRestClientImpl.java:2276)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)at
> org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)at
> org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
> at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
> at
> org.jaggeryjs.rhino.admin_dashboard.modules.analytics.c2._c_anonymous_4(/admin-dashboard/modules/analytics/add.jag:221)
> at
> org.jaggeryjs.rhino.admin_dashboard.modules.analytics.c2.call(/admin-dashboard/modules/analytics/add.jag)
> at
> org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
> at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
> at
> org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
> at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
> at
> org.jaggeryjs.rhino.admin_dashboard.modules.analytics.c0._c_anonymous_6(/admin-dashboard/modules/analytics/module.jag:25)
> at
> 

[Dev] Axis fault while trying to publish API runtime statistics using rest client

[Fathima Dilhasha]

Hi,

I am trying to follow [1]

to publish API runtime statistics using rest client. I have used fresh
installations of APIM and DAS.
Following is the axis fault I'm getting. Have I missed any configrations?

































































































*TID: [-1234] [] [2016-05-23 13:13:49,741]  INFO
{org.apache.axis2.transport.http.HTTPSender} -  Unable to sendViaPost to
url[https://localhost:9446/services/CarbonAppUploader
]
{org.apache.axis2.transport.http.HTTPSender}java.net.ConnectException:
Connection refusedat java.net.PlainSocketImpl.socketConnect(Native
Method)at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)at
java.net.Socket.connect(Socket.java:579)at
sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:625)at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)at
org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:140)
at
org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:130)
at
org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:630)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:195)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.wso2.carbon.application.mgt.stub.upload.CarbonAppUploaderStub.uploadApp(CarbonAppUploaderStub.java:184)
at
org.wso2.carbon.apimgt.usage.client.impl.APIUsageStatisticsRestClientImpl.deployArtifacts(APIUsageStatisticsRestClientImpl.java:2276)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)at
org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)at
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
at
org.jaggeryjs.rhino.admin_dashboard.modules.analytics.c2._c_anonymous_4(/admin-dashboard/modules/analytics/add.jag:221)
at
org.jaggeryjs.rhino.admin_dashboard.modules.analytics.c2.call(/admin-dashboard/modules/analytics/add.jag)
at
org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
at org.mozilla.javascript.BaseFunction.execIdCall(BaseFunction.java:269)
at
org.mozilla.javascript.IdFunctionObject.call(IdFunctionObject.java:97)
at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.admin_dashboard.modules.analytics.c0._c_anonymous_6(/admin-dashboard/modules/analytics/module.jag:25)
at
org.jaggeryjs.rhino.admin_dashboard.modules.analytics.c0.call(/admin-dashboard/modules/analytics/module.jag)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.admin_dashboard.site.blocks.analytics_task.ajax.c1._c_anonymous_1(/admin-dashboard/site/blocks/analytics-task/ajax/add.jag:76)
at
org.jaggeryjs.rhino.admin_dashboard.site.blocks.analytics_task.ajax.c1.call(/admin-dashboard/site/blocks/analytics-task/ajax/add.jag)
at org.mozilla.javascript.optimizer.OptRuntime.call0(OptRuntime.java:23)
at

Re: [Dev] APIM 2.0.0-SNAPSHOT Nightly build - 22/05/2016

[Shavantha Weerasinghe]

Hi Bhathiya

Attempt to create/list a subscriber user role failed with MSSQL2012 DB. The
jira id is https://wso2.org/jira/browse/APIMANAGER-4876

regards,

Shavantha Weerasinghe
Senior Software Engineer QA
WSO2, Inc.
lean.enterprise.middleware.
http://wso2.com
http://wso2.org
Tel : 94 11 214 5345
Fax :94 11 2145300


On Sun, May 22, 2016 at 11:34 PM, Bhathiya Jayasekara 
wrote:

> Hi all,
>
> Please find APIM 2.0.0 SNAPSHOT nightly build here[1].
>
> [1]
> https://svn.wso2.org/repos/wso2/scratch/2016/apim-2.0.0/wso2am-2.0.0-SNAPSHOT-22-05-2016.zip
>
> Thanks,
>
>
> --
> *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
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [MSF4J] Swagger documentation not working when using OSGi components.

[Hemika Kodikara]

Hi All,

I have added the swagger documentation to my microservice. But I am unable
to get the documentation generated through the browser.

It seems the swagger definition service is only being added through the
MicroserviceRunner class[1].

[1] -
https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/MicroservicesRunner.java#L151

Regards,
Hemika

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

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

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

[Niranjan Karunanandham]

As a general practice, PR (with all the product's required features) to the
carbon-feature-repository is sent only after the product is released. In
order for testing, we can clone the carbon-feature-repository and add your
product's features. This can be tested by locally building it and obtaining
the p2-repo.

Regards,
Nira

On Mon, May 23, 2016 at 12:04 PM, Gihan Anuruddha  wrote:

> We didn't include to P2-repo yet. Will provide a repo soon.
>
> On Mon, May 23, 2016 at 11:57 AM, Isuru Udana  wrote:
>
>> [+Anjana, Gihan, Gokul]
>>
>> On Mon, May 23, 2016 at 11:52 AM, Iranga Muthuthanthri 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> The requirement would be to install ESB Analytics features to DAS from a
>>> p2-repo,
>>>
>>> On Mon, May 23, 2016 at 11:45 AM, Isuru Udana  wrote:
>>>
 Hi Iranga,

 On Mon, May 23, 2016 at 11:38 AM, Iranga Muthuthanthri  wrote:

> Would it be possible to get the p2-repo (with the analytics features
> included?)
>
  Analytics features related to ESB core side is included within the ESB
 pack itself. And as mentioned above ESB Analytics pack can be found from
 following.
 https://github.com/wso2/analytics-esb/releases/tag/v1.0.0-beta

 Any other need for a p2-repo ?

 Thanks.



>
>
> On Sat, May 21, 2016 at 2:17 AM, Buddhima Wijeweera  > wrote:
>
>> *WSO2 ESB 5.0.0-BETA Released*
>>
>> ESB Team is pleased to announce the WSO2 ESB 5.0.0 - BETA release.
>>
>> The distribution is available to download at [1].
>>
>> [1] https://github.com/wso2/product-esb/releases/tag/v5.0.0-BETA
>>
>>
>> *WSO2 **ESB Tooling 5.0.0**-BETA Released*
>>
>> The distribution is available to download at [3].
>>
>> [3] 
>> *https://github.com/wso2/devstudio-tooling-esb/releases/tag/v5.0.0-beta
>> *
>>
>>
>> *WSO2 **ESB Analytics 1.0.0**-BETA Released*
>>
>> The distribution is available to download at [2].
>>
>> [2] https://github.com/wso2/analytics-esb/releases/tag/v1.0.0-beta
>>
>>
>> WSO2 ESB 5.0.0-BETA contains following improvement and bug fixes.
>>
>> Bug
>>
>>- [ESBJAVA-3117 ] -
>>The bind-address feature was not implemented for Pass-through 
>> transport
>>- [ESBJAVA-3801 ] -
>>java.lang.IllegalStateException: Trying to set the domain from 8 to 6 
>> when
>>invoking the same service from two tenant domains
>>- [ESBJAVA-4014 ] -
>>Proxy services can be invoked using invalid URL in super tenant mode.
>>- [ESBJAVA-4137 ] -
>>Empty POST body with application/json content-type throws an Error
>>- [ESBJAVA-4225 ] -
>>Endpoint re-deployment issue via a CAR while invoking the same 
>> endpoint
>>- [ESBJAVA-4244 ] -
>>JsonUtil #newJsonPayload. Could not save JSON payload. Invalid input 
>> stream
>>found.
>>- [ESBJAVA-4297 ] -
>>[ESB 4.9.0]Sample 57: Error when updating from admin UI.
>>- [ESBJAVA-4319 ] -
>>WSO2 ESB Problems
>>- [ESBJAVA-4326 ] -
>>Overriding the Host Header in an HTTP Call from the ESB does not work 
>> with
>>service chaining scenario
>>- [ESBJAVA-4345 ] -
>>Possibilities of two or more proxies trying to lock and read the same 
>> file
>>at the same time.
>>- [ESBJAVA-4356 ] -
>>Inbound endpoint interval shows null in editInbound.jsp although 
>> source
>>configuration have interval specified
>>- [ESBJAVA-4384 ] -
>>Unable to use multiple mailto senders
>>- [ESBJAVA-4387 ] -
>>Mediation debugger failed to set breakpoints for Aggragete mediator 
>> inlined
>>sequence.
>>- [ESBJAVA-4397 ] -
>>The display name get disorted when a description is added to the 
>> endpoint
>>- [ESBJAVA-4398 ] -
>>When seperate listener is used in endpoint, the request is not sent 
>> to the
>>endpoint
>>- [ESBJAVA-4399 ] 

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

[Gihan Anuruddha]

We didn't include to P2-repo yet. Will provide a repo soon.

On Mon, May 23, 2016 at 11:57 AM, Isuru Udana  wrote:

> [+Anjana, Gihan, Gokul]
>
> On Mon, May 23, 2016 at 11:52 AM, Iranga Muthuthanthri 
> wrote:
>
>> Hi Isuru,
>>
>> The requirement would be to install ESB Analytics features to DAS from a
>> p2-repo,
>>
>> On Mon, May 23, 2016 at 11:45 AM, Isuru Udana  wrote:
>>
>>> Hi Iranga,
>>>
>>> On Mon, May 23, 2016 at 11:38 AM, Iranga Muthuthanthri 
>>> wrote:
>>>
 Would it be possible to get the p2-repo (with the analytics features
 included?)

>>>  Analytics features related to ESB core side is included within the ESB
>>> pack itself. And as mentioned above ESB Analytics pack can be found from
>>> following.
>>> https://github.com/wso2/analytics-esb/releases/tag/v1.0.0-beta
>>>
>>> Any other need for a p2-repo ?
>>>
>>> Thanks.
>>>
>>>
>>>


 On Sat, May 21, 2016 at 2:17 AM, Buddhima Wijeweera 
 wrote:

> *WSO2 ESB 5.0.0-BETA Released*
>
> ESB Team is pleased to announce the WSO2 ESB 5.0.0 - BETA release.
>
> The distribution is available to download at [1].
>
> [1] https://github.com/wso2/product-esb/releases/tag/v5.0.0-BETA
>
>
> *WSO2 **ESB Tooling 5.0.0**-BETA Released*
>
> The distribution is available to download at [3].
>
> [3] 
> *https://github.com/wso2/devstudio-tooling-esb/releases/tag/v5.0.0-beta
> *
>
>
> *WSO2 **ESB Analytics 1.0.0**-BETA Released*
>
> The distribution is available to download at [2].
>
> [2] https://github.com/wso2/analytics-esb/releases/tag/v1.0.0-beta
>
>
> WSO2 ESB 5.0.0-BETA contains following improvement and bug fixes.
>
> Bug
>
>- [ESBJAVA-3117 ] - The
>bind-address feature was not implemented for Pass-through transport
>- [ESBJAVA-3801 ] -
>java.lang.IllegalStateException: Trying to set the domain from 8 to 6 
> when
>invoking the same service from two tenant domains
>- [ESBJAVA-4014 ] -
>Proxy services can be invoked using invalid URL in super tenant mode.
>- [ESBJAVA-4137 ] -
>Empty POST body with application/json content-type throws an Error
>- [ESBJAVA-4225 ] -
>Endpoint re-deployment issue via a CAR while invoking the same endpoint
>- [ESBJAVA-4244 ] -
>JsonUtil #newJsonPayload. Could not save JSON payload. Invalid input 
> stream
>found.
>- [ESBJAVA-4297 ] -
>[ESB 4.9.0]Sample 57: Error when updating from admin UI.
>- [ESBJAVA-4319 ] -
>WSO2 ESB Problems
>- [ESBJAVA-4326 ] -
>Overriding the Host Header in an HTTP Call from the ESB does not work 
> with
>service chaining scenario
>- [ESBJAVA-4345 ] -
>Possibilities of two or more proxies trying to lock and read the same 
> file
>at the same time.
>- [ESBJAVA-4356 ] -
>Inbound endpoint interval shows null in editInbound.jsp although source
>configuration have interval specified
>- [ESBJAVA-4384 ] -
>Unable to use multiple mailto senders
>- [ESBJAVA-4387 ] -
>Mediation debugger failed to set breakpoints for Aggragete mediator 
> inlined
>sequence.
>- [ESBJAVA-4397 ] - The
>display name get disorted when a description is added to the endpoint
>- [ESBJAVA-4398 ] -
>When seperate listener is used in endpoint, the request is not sent to 
> the
>endpoint
>- [ESBJAVA-4399 ] -
>WS-Security is not executable when associated with a WSDL endpoint
>- [ESBJAVA-4400 ] -
>Default endpoint does not work as expected
>- [ESBJAVA-4401 ] -
>Product version and relevant details should be updated on distribution
>files for ESB 4.10 release
>- [ESBJAVA-4442 ] -
>[ESB500]Error in Clustering Mode - JMS 2.0 Feature:Shared Topic 
> 

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC1

[Awanthika Senarath]

Hi all,


We are withdrawing this vote due to [1].

We will be starting the vote for platform 4.1.0 RC 2 with the fix.

[1] https://wso2.org/jira/browse/TOOLS-3413

Regards
Awanthika

Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Thu, May 19, 2016 at 3:11 PM, Awanthika Senarath 
wrote:

> Hello Devs,
>
>
> We are pleased to announce the vote for RC-3 of *WSO2 Developer Studio Tooling
> for Platform 4.1.0.*
>
> P2 repository of WSO2 developer Studio  Tooling for Platform 4.1.0 is
> available here
> .
>  Source
> and Tag Location to be voted upon is available here
> 
> .
>
> Developer Studio 4.1.0  Tooling for Platform is released on Developer
> Studio kernel 4.1.0
> Developer Studio Kernel contains a single feature which has the bundles
> that are required to implement WSO2 specific product tooling on Eclipse.
>
>- This release contains Developer Studio migration to Eclipse mars
>- Improvements in the Developer Studio Updater tool for automatic
>updates
>
>
>
>1. [+] Stable - go ahead and release
>2. [-]  Broken - do not release (please explain why)
>
>
> The platform could to be tested on top of Developer Studio Kernel with
> compatible tooling SNAPSHOT versions available at [1].
>
>
> [1]
> http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Isuru Udana]

[+Anjana, Gihan, Gokul]

On Mon, May 23, 2016 at 11:52 AM, Iranga Muthuthanthri 
wrote:

> Hi Isuru,
>
> The requirement would be to install ESB Analytics features to DAS from a
> p2-repo,
>
> On Mon, May 23, 2016 at 11:45 AM, Isuru Udana  wrote:
>
>> Hi Iranga,
>>
>> On Mon, May 23, 2016 at 11:38 AM, Iranga Muthuthanthri 
>> wrote:
>>
>>> Would it be possible to get the p2-repo (with the analytics features
>>> included?)
>>>
>>  Analytics features related to ESB core side is included within the ESB
>> pack itself. And as mentioned above ESB Analytics pack can be found from
>> following.
>> https://github.com/wso2/analytics-esb/releases/tag/v1.0.0-beta
>>
>> Any other need for a p2-repo ?
>>
>> Thanks.
>>
>>
>>
>>>
>>>
>>> On Sat, May 21, 2016 at 2:17 AM, Buddhima Wijeweera 
>>> wrote:
>>>
 *WSO2 ESB 5.0.0-BETA Released*

 ESB Team is pleased to announce the WSO2 ESB 5.0.0 - BETA release.

 The distribution is available to download at [1].

 [1] https://github.com/wso2/product-esb/releases/tag/v5.0.0-BETA


 *WSO2 **ESB Tooling 5.0.0**-BETA Released*

 The distribution is available to download at [3].

 [3] *https://github.com/wso2/devstudio-tooling-esb/releases/tag/v5.0.0-beta
 *


 *WSO2 **ESB Analytics 1.0.0**-BETA Released*

 The distribution is available to download at [2].

 [2] https://github.com/wso2/analytics-esb/releases/tag/v1.0.0-beta


 WSO2 ESB 5.0.0-BETA contains following improvement and bug fixes.

 Bug

- [ESBJAVA-3117 ] - The
bind-address feature was not implemented for Pass-through transport
- [ESBJAVA-3801 ] -
java.lang.IllegalStateException: Trying to set the domain from 8 to 6 
 when
invoking the same service from two tenant domains
- [ESBJAVA-4014 ] -
Proxy services can be invoked using invalid URL in super tenant mode.
- [ESBJAVA-4137 ] -
Empty POST body with application/json content-type throws an Error
- [ESBJAVA-4225 ] -
Endpoint re-deployment issue via a CAR while invoking the same endpoint
- [ESBJAVA-4244 ] -
JsonUtil #newJsonPayload. Could not save JSON payload. Invalid input 
 stream
found.
- [ESBJAVA-4297 ] - [ESB
4.9.0]Sample 57: Error when updating from admin UI.
- [ESBJAVA-4319 ] - WSO2
ESB Problems
- [ESBJAVA-4326 ] -
Overriding the Host Header in an HTTP Call from the ESB does not work 
 with
service chaining scenario
- [ESBJAVA-4345 ] -
Possibilities of two or more proxies trying to lock and read the same 
 file
at the same time.
- [ESBJAVA-4356 ] -
Inbound endpoint interval shows null in editInbound.jsp although source
configuration have interval specified
- [ESBJAVA-4384 ] -
Unable to use multiple mailto senders
- [ESBJAVA-4387 ] -
Mediation debugger failed to set breakpoints for Aggragete mediator 
 inlined
sequence.
- [ESBJAVA-4397 ] - The
display name get disorted when a description is added to the endpoint
- [ESBJAVA-4398 ] - When
seperate listener is used in endpoint, the request is not sent to the
endpoint
- [ESBJAVA-4399 ] -
WS-Security is not executable when associated with a WSDL endpoint
- [ESBJAVA-4400 ] -
Default endpoint does not work as expected
- [ESBJAVA-4401 ] -
Product version and relevant details should be updated on distribution
files for ESB 4.10 release
- [ESBJAVA-4442 ] -
[ESB500]Error in Clustering Mode - JMS 2.0 Feature:Shared Topic 
 Subscription
- [ESBJAVA-4446 ] -
[ESB500][JMS 2.0 Feature : JMSXDeliveryCount]Could not reconnect to JMS
broker after loosing connection.
- [ESBJAVA-4459 ] -

Re: [Dev] Which feature has org.wso2.carbon.jaxws.webapp.mgt jar?

[KasunG Gajasinghe]

Xfer and Mex has also been deprecated and removed in Carbon 4.4.x.

On Mon, May 23, 2016 at 10:22 AM, Bhathiya Jayasekara 
wrote:

> Can you please comment on this too?
>
> org.wso2.carbon.xfer:${carbon.kernel.version}
>
>
> Thanks,
> Bhathiya
>
> On Mon, May 23, 2016 at 8:10 AM, Bhathiya Jayasekara 
> wrote:
>
>> Thanks Kasun.
>>
>> On Mon, May 23, 2016 at 7:52 AM, KasunG Gajasinghe 
>> wrote:
>>
>>>
>>> This component is no longer used since the functionality is merged to
>>> org.wso2.carbon.webapp.mgt.
>>>
>>> On Mon, May 23, 2016 at 12:02 AM, Bhathiya Jayasekara >> > wrote:
>>>
 Hi Carbon team,

 Could you please tell me the $subject [1]?

 [1]
 https://github.com/wso2/carbon-deployment/tree/4.6.x/components/webapp-mgt/org.wso2.carbon.jaxws.webapp.mgt


 Thanks,

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

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



-- 

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

Re: [Dev] [APIM-Analytics] API availability status page improvements

[Fazlan Nazeem]

[Looping Jerad]

On Mon, May 23, 2016 at 11:51 AM, Fazlan Nazeem  wrote:

> Hi,
>
> Currently we have an 'Availability of APIs' page in the API-M admin
> dashboard(Image attached) which shows the availability of APIs. In here we
> have listed each *api_version* with it's availability *status*. Currently
> the "status" can take values as follows.
>
>
>1. Available
>2. Server error occurred
>3. Response count is too low
>4. Response time is too high
>
> In a discussion with Issabelle it was suggested we should avoid using
> 2,3,4 as statuses, since they are not actually statuses, but the reason
> behind the status. We cannot use "unavailable" instead of 2,3,4 since they
> do not mean the API is unavailable, but those APIs are not behaving normal.
> There are two points need to be figured out.
>
>
>- The correct wording to use
>
> Healthy/Unhealthy
>
> Normal/Abnormal
>
>
>
>- How to show the reason behind the status
>
> The initial suggestion was that we could give the user a drill down option
> to see the real reason behind the status. The UI folks suggested to list
> the reason(2,3,4) within brackets.
>
>
>
> We could also change the column name from 'status' to a more sensible name
> if we could come up with one.
>
> Any suggestions?
>
> --
> Thanks & Regards,
>
> Fazlan Nazeem
>
> *Software Engineer*
>
> *WSO2 Inc*
> Mobile : +94772338839
> <%2B94%20%280%29%20773%20451194>
> fazl...@wso2.com
>



-- 
Thanks & Regards,

Fazlan Nazeem

*Software Engineer*

*WSO2 Inc*
Mobile : +94772338839
<%2B94%20%280%29%20773%20451194>
fazl...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Iranga Muthuthanthri]

Hi Isuru,

The requirement would be to install ESB Analytics features to DAS from a
p2-repo,

On Mon, May 23, 2016 at 11:45 AM, Isuru Udana  wrote:

> Hi Iranga,
>
> On Mon, May 23, 2016 at 11:38 AM, Iranga Muthuthanthri 
> wrote:
>
>> Would it be possible to get the p2-repo (with the analytics features
>> included?)
>>
>  Analytics features related to ESB core side is included within the ESB
> pack itself. And as mentioned above ESB Analytics pack can be found from
> following.
> https://github.com/wso2/analytics-esb/releases/tag/v1.0.0-beta
>
> Any other need for a p2-repo ?
>
> Thanks.
>
>
>
>>
>>
>> On Sat, May 21, 2016 at 2:17 AM, Buddhima Wijeweera 
>> wrote:
>>
>>> *WSO2 ESB 5.0.0-BETA Released*
>>>
>>> ESB Team is pleased to announce the WSO2 ESB 5.0.0 - BETA release.
>>>
>>> The distribution is available to download at [1].
>>>
>>> [1] https://github.com/wso2/product-esb/releases/tag/v5.0.0-BETA
>>>
>>>
>>> *WSO2 **ESB Tooling 5.0.0**-BETA Released*
>>>
>>> The distribution is available to download at [3].
>>>
>>> [3] *https://github.com/wso2/devstudio-tooling-esb/releases/tag/v5.0.0-beta
>>> *
>>>
>>>
>>> *WSO2 **ESB Analytics 1.0.0**-BETA Released*
>>>
>>> The distribution is available to download at [2].
>>>
>>> [2] https://github.com/wso2/analytics-esb/releases/tag/v1.0.0-beta
>>>
>>>
>>> WSO2 ESB 5.0.0-BETA contains following improvement and bug fixes.
>>>
>>> Bug
>>>
>>>- [ESBJAVA-3117 ] - The
>>>bind-address feature was not implemented for Pass-through transport
>>>- [ESBJAVA-3801 ] -
>>>java.lang.IllegalStateException: Trying to set the domain from 8 to 6 
>>> when
>>>invoking the same service from two tenant domains
>>>- [ESBJAVA-4014 ] - Proxy
>>>services can be invoked using invalid URL in super tenant mode.
>>>- [ESBJAVA-4137 ] - Empty
>>>POST body with application/json content-type throws an Error
>>>- [ESBJAVA-4225 ] -
>>>Endpoint re-deployment issue via a CAR while invoking the same endpoint
>>>- [ESBJAVA-4244 ] -
>>>JsonUtil #newJsonPayload. Could not save JSON payload. Invalid input 
>>> stream
>>>found.
>>>- [ESBJAVA-4297 ] - [ESB
>>>4.9.0]Sample 57: Error when updating from admin UI.
>>>- [ESBJAVA-4319 ] - WSO2
>>>ESB Problems
>>>- [ESBJAVA-4326 ] -
>>>Overriding the Host Header in an HTTP Call from the ESB does not work 
>>> with
>>>service chaining scenario
>>>- [ESBJAVA-4345 ] -
>>>Possibilities of two or more proxies trying to lock and read the same 
>>> file
>>>at the same time.
>>>- [ESBJAVA-4356 ] -
>>>Inbound endpoint interval shows null in editInbound.jsp although source
>>>configuration have interval specified
>>>- [ESBJAVA-4384 ] -
>>>Unable to use multiple mailto senders
>>>- [ESBJAVA-4387 ] -
>>>Mediation debugger failed to set breakpoints for Aggragete mediator 
>>> inlined
>>>sequence.
>>>- [ESBJAVA-4397 ] - The
>>>display name get disorted when a description is added to the endpoint
>>>- [ESBJAVA-4398 ] - When
>>>seperate listener is used in endpoint, the request is not sent to the
>>>endpoint
>>>- [ESBJAVA-4399 ] -
>>>WS-Security is not executable when associated with a WSDL endpoint
>>>- [ESBJAVA-4400 ] -
>>>Default endpoint does not work as expected
>>>- [ESBJAVA-4401 ] -
>>>Product version and relevant details should be updated on distribution
>>>files for ESB 4.10 release
>>>- [ESBJAVA-4442 ] -
>>>[ESB500]Error in Clustering Mode - JMS 2.0 Feature:Shared Topic 
>>> Subscription
>>>- [ESBJAVA-4446 ] -
>>>[ESB500][JMS 2.0 Feature : JMSXDeliveryCount]Could not reconnect to JMS
>>>broker after loosing connection.
>>>- [ESBJAVA-4459 ] -
>>>[ESB500M2] Removing "enableSec" element, but keeping the "policy" element
>>>from a UT secured proxy
>>>- [ESBJAVA-4472 ] -
>>>[ESB500M2][LongRun][Intermittent] 

[Dev] [APIM-Analytics] API availability status page improvements

[Fazlan Nazeem]

Hi,

Currently we have an 'Availability of APIs' page in the API-M admin
dashboard(Image attached) which shows the availability of APIs. In here we
have listed each *api_version* with it's availability *status*. Currently
the "status" can take values as follows.


   1. Available
   2. Server error occurred
   3. Response count is too low
   4. Response time is too high

In a discussion with Issabelle it was suggested we should avoid using 2,3,4
as statuses, since they are not actually statuses, but the reason behind
the status. We cannot use "unavailable" instead of 2,3,4 since they do not
mean the API is unavailable, but those APIs are not behaving normal. There
are two points need to be figured out.


   - The correct wording to use

Healthy/Unhealthy

Normal/Abnormal



   - How to show the reason behind the status

The initial suggestion was that we could give the user a drill down option
to see the real reason behind the status. The UI folks suggested to list
the reason(2,3,4) within brackets.



We could also change the column name from 'status' to a more sensible name
if we could come up with one.

Any suggestions?

-- 
Thanks & Regards,

Fazlan Nazeem

*Software Engineer*

*WSO2 Inc*
Mobile : +94772338839
<%2B94%20%280%29%20773%20451194>
fazl...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Isuru Udana]

Hi Iranga,

On Mon, May 23, 2016 at 11:38 AM, Iranga Muthuthanthri 
wrote:

> Would it be possible to get the p2-repo (with the analytics features
> included?)
>
 Analytics features related to ESB core side is included within the ESB
pack itself. And as mentioned above ESB Analytics pack can be found from
following.
https://github.com/wso2/analytics-esb/releases/tag/v1.0.0-beta

Any other need for a p2-repo ?

Thanks.



>
>
> On Sat, May 21, 2016 at 2:17 AM, Buddhima Wijeweera 
> wrote:
>
>> *WSO2 ESB 5.0.0-BETA Released*
>>
>> ESB Team is pleased to announce the WSO2 ESB 5.0.0 - BETA release.
>>
>> The distribution is available to download at [1].
>>
>> [1] https://github.com/wso2/product-esb/releases/tag/v5.0.0-BETA
>>
>>
>> *WSO2 **ESB Tooling 5.0.0**-BETA Released*
>>
>> The distribution is available to download at [3].
>>
>> [3] *https://github.com/wso2/devstudio-tooling-esb/releases/tag/v5.0.0-beta
>> *
>>
>>
>> *WSO2 **ESB Analytics 1.0.0**-BETA Released*
>>
>> The distribution is available to download at [2].
>>
>> [2] https://github.com/wso2/analytics-esb/releases/tag/v1.0.0-beta
>>
>>
>> WSO2 ESB 5.0.0-BETA contains following improvement and bug fixes.
>>
>> Bug
>>
>>- [ESBJAVA-3117 ] - The
>>bind-address feature was not implemented for Pass-through transport
>>- [ESBJAVA-3801 ] -
>>java.lang.IllegalStateException: Trying to set the domain from 8 to 6 when
>>invoking the same service from two tenant domains
>>- [ESBJAVA-4014 ] - Proxy
>>services can be invoked using invalid URL in super tenant mode.
>>- [ESBJAVA-4137 ] - Empty
>>POST body with application/json content-type throws an Error
>>- [ESBJAVA-4225 ] -
>>Endpoint re-deployment issue via a CAR while invoking the same endpoint
>>- [ESBJAVA-4244 ] -
>>JsonUtil #newJsonPayload. Could not save JSON payload. Invalid input 
>> stream
>>found.
>>- [ESBJAVA-4297 ] - [ESB
>>4.9.0]Sample 57: Error when updating from admin UI.
>>- [ESBJAVA-4319 ] - WSO2
>>ESB Problems
>>- [ESBJAVA-4326 ] -
>>Overriding the Host Header in an HTTP Call from the ESB does not work with
>>service chaining scenario
>>- [ESBJAVA-4345 ] -
>>Possibilities of two or more proxies trying to lock and read the same file
>>at the same time.
>>- [ESBJAVA-4356 ] -
>>Inbound endpoint interval shows null in editInbound.jsp although source
>>configuration have interval specified
>>- [ESBJAVA-4384 ] - Unable
>>to use multiple mailto senders
>>- [ESBJAVA-4387 ] -
>>Mediation debugger failed to set breakpoints for Aggragete mediator 
>> inlined
>>sequence.
>>- [ESBJAVA-4397 ] - The
>>display name get disorted when a description is added to the endpoint
>>- [ESBJAVA-4398 ] - When
>>seperate listener is used in endpoint, the request is not sent to the
>>endpoint
>>- [ESBJAVA-4399 ] -
>>WS-Security is not executable when associated with a WSDL endpoint
>>- [ESBJAVA-4400 ] -
>>Default endpoint does not work as expected
>>- [ESBJAVA-4401 ] -
>>Product version and relevant details should be updated on distribution
>>files for ESB 4.10 release
>>- [ESBJAVA-4442 ] -
>>[ESB500]Error in Clustering Mode - JMS 2.0 Feature:Shared Topic 
>> Subscription
>>- [ESBJAVA-4446 ] -
>>[ESB500][JMS 2.0 Feature : JMSXDeliveryCount]Could not reconnect to JMS
>>broker after loosing connection.
>>- [ESBJAVA-4459 ] -
>>[ESB500M2] Removing "enableSec" element, but keeping the "policy" element
>>from a UT secured proxy
>>- [ESBJAVA-4472 ] -
>>[ESB500M2][LongRun][Intermittent] WSSecurityException occurred when
>>invoking WS Secured Proxy with correct Credentials
>>- [ESBJAVA-4485 ] -
>>[ESB500][Store Mediator]- When there is no messages to send to message
>>store, giving an unhandled error
>>- [ESBJAVA-4492 

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

[Iranga Muthuthanthri]

Would it be possible to get the p2-repo (with the analytics features
included?)


On Sat, May 21, 2016 at 2:17 AM, Buddhima Wijeweera 
wrote:

> *WSO2 ESB 5.0.0-BETA Released*
>
> ESB Team is pleased to announce the WSO2 ESB 5.0.0 - BETA release.
>
> The distribution is available to download at [1].
>
> [1] https://github.com/wso2/product-esb/releases/tag/v5.0.0-BETA
>
>
> *WSO2 **ESB Tooling 5.0.0**-BETA Released*
>
> The distribution is available to download at [3].
>
> [3] *https://github.com/wso2/devstudio-tooling-esb/releases/tag/v5.0.0-beta
> *
>
>
> *WSO2 **ESB Analytics 1.0.0**-BETA Released*
>
> The distribution is available to download at [2].
>
> [2] https://github.com/wso2/analytics-esb/releases/tag/v1.0.0-beta
>
>
> WSO2 ESB 5.0.0-BETA contains following improvement and bug fixes.
>
> Bug
>
>- [ESBJAVA-3117 ] - The
>bind-address feature was not implemented for Pass-through transport
>- [ESBJAVA-3801 ] -
>java.lang.IllegalStateException: Trying to set the domain from 8 to 6 when
>invoking the same service from two tenant domains
>- [ESBJAVA-4014 ] - Proxy
>services can be invoked using invalid URL in super tenant mode.
>- [ESBJAVA-4137 ] - Empty
>POST body with application/json content-type throws an Error
>- [ESBJAVA-4225 ] -
>Endpoint re-deployment issue via a CAR while invoking the same endpoint
>- [ESBJAVA-4244 ] -
>JsonUtil #newJsonPayload. Could not save JSON payload. Invalid input stream
>found.
>- [ESBJAVA-4297 ] - [ESB
>4.9.0]Sample 57: Error when updating from admin UI.
>- [ESBJAVA-4319 ] - WSO2
>ESB Problems
>- [ESBJAVA-4326 ] -
>Overriding the Host Header in an HTTP Call from the ESB does not work with
>service chaining scenario
>- [ESBJAVA-4345 ] -
>Possibilities of two or more proxies trying to lock and read the same file
>at the same time.
>- [ESBJAVA-4356 ] - Inbound
>endpoint interval shows null in editInbound.jsp although source
>configuration have interval specified
>- [ESBJAVA-4384 ] - Unable
>to use multiple mailto senders
>- [ESBJAVA-4387 ] -
>Mediation debugger failed to set breakpoints for Aggragete mediator inlined
>sequence.
>- [ESBJAVA-4397 ] - The
>display name get disorted when a description is added to the endpoint
>- [ESBJAVA-4398 ] - When
>seperate listener is used in endpoint, the request is not sent to the
>endpoint
>- [ESBJAVA-4399 ] -
>WS-Security is not executable when associated with a WSDL endpoint
>- [ESBJAVA-4400 ] - Default
>endpoint does not work as expected
>- [ESBJAVA-4401 ] - Product
>version and relevant details should be updated on distribution files for
>ESB 4.10 release
>- [ESBJAVA-4442 ] -
>[ESB500]Error in Clustering Mode - JMS 2.0 Feature:Shared Topic 
> Subscription
>- [ESBJAVA-4446 ] -
>[ESB500][JMS 2.0 Feature : JMSXDeliveryCount]Could not reconnect to JMS
>broker after loosing connection.
>- [ESBJAVA-4459 ] -
>[ESB500M2] Removing "enableSec" element, but keeping the "policy" element
>from a UT secured proxy
>- [ESBJAVA-4472 ] -
>[ESB500M2][LongRun][Intermittent] WSSecurityException occurred when
>invoking WS Secured Proxy with correct Credentials
>- [ESBJAVA-4485 ] -
>[ESB500][Store Mediator]- When there is no messages to send to message
>store, giving an unhandled error
>- [ESBJAVA-4492 ] - Json to
>XML conversion is wrong when json attribute name has spaces
>- [ESBJAVA-4516 ] -
>publishing to DAS from scheduled task in ESB fails
>- [ESBJAVA-4529 ] - Make
>sure ESB is using the latest drool engine
>- [ESBJAVA-4531 ] - Support
>to map tree nodes which