Hi all,
We have implemented self signup feature for tenanted App Stores in
multi-tenanted environment. In App Manager 1.0.0, we did not have isolated
tenanted App Store view support along with the tenanted user signup
feature. It only facilitates the anonymous App Store view and self signup
Hi all,
At the moment I am involved in implementing this feature. As the first step
I am going to capture the raw metrics related data which we need to have in
order to calculate the various latency values such as *Average throughput,
Average Latency, Average Jitter of the connections, etc. *All
We have implemented exact same thing for API Manager and you may use same
code.
And you cannot use file "'/_system/governance/*apimgt*/
applicationdata/sign-up-config.xml" as APIM component already using it.
You can create new file in '/_system/governance/*appmgt*/
[Adding IsuruP]
Can't we use existing metrics feature for this?
Thanks
*Dinesh J. Weerakkody*
Software Engineer
WSO2 Inc.
lean | enterprise | middleware
M : +94 727 868676 | E : dine...@wso2.com | W : www.wso2.com
On Thu, Dec 17, 2015 at 2:18 PM, Nadeeshaan Gunasinghe
Yes, in the case of kernel, you have used PAX exam to install all the
kernel bundles and then test the relevant features. Ideally, you would add
mock bundles and then test just one or a few real bundles. So this is a
unit test for OSGi bundles. That should have been the correct approach.
Also,
Hi Sanjeewa,
We referred the code in API Manager while implementing this feature since
we need the same user signup functionality available in API Store.
The correct registry location of the signup-config in App Manager is "
/_system/governance/appmgt/ap uplicationdata/sign-up-config.xml" and
This file should be in the config registry since its a config file and
since it only makes sense to APP Manager.
On Thu, Dec 17, 2015 at 3:08 PM, Thilini Shanika wrote:
> Hi Sanjeewa,
>
> We referred the code in API Manager while implementing this feature since
> we need the
WSO2 Business Process Server 3.5.1 - Beta Released !
Date : 17th December 2015
WSO2 BPS team is pleased to announce the Beta release of WSO2 BPS 3.5.1
Beta. You can download the distribution from [1].
WSO2 Business Process Server (BPS) is an easy-to-use Open Source Business
Process Server that
Hi Malmee,
Great work on the migration tool. AFAIU this is as far as we can go to ease
the migration process for a Stratos user.
Some improvements that can be implemented, IMO, are,
1. Rename bin/run.sh to bin/stratos.sh to conform with the existing pattern
where each separate Stratos component
Hi Amila,
On Fri, Dec 18, 2015 at 11:12 AM, Amila Maha Arachchi
wrote:
> Have you seen *Enqueue* and *RMSequence* mediators being used when
> implementing mediation logics?
>
We have already removed RMSequence mediator in 4.9.0.
I haven't seen anyone using Enqueue Mediator in a
Hi all,
I'm trying to refactor code and move the initialization logic out from the
interceptors we have. i.e. MetricsInterceptor [1] and
HTTPMonitoringInterceptor [2]. With current lifecycle method support, we
can write some initialization code within the service only [3].
I understand that it's
On Wed, Dec 16, 2015 at 2:28 PM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:
> Hi all,
>
> I have done this use case, for that I used read operation from the file
> connector and send the mail operation from Gmail connector.
>
> Get the content of the file and send that content to
Yes. It's better if GW can use Carbon Metrics [1]. If there are missing
features, we may be able to implement in Metrics. I had a discussion with
ESB team before and there were some requirements, which could not be done
with [1]. As I remember, they wanted per request metrics. Shall we have a
Hi Gayan ,
No, We are going to read only the body to send mail from the file. We have
to give manually other things such as address , subject etc.
*Thank youVivekananthan Sivanayagam*
*Associate Software Engineer | WSO2*
*E:vivekanant...@wso2.com *
On Fri, Dec 18, 2015 at 11:33 AM, Isuru Perera wrote:
> Hi all,
>
> I'm trying to refactor code and move the initialization logic out from the
> interceptors we have. i.e. MetricsInterceptor [1] and
> HTTPMonitoringInterceptor [2]. With current lifecycle method support, we
> can
Have you seen *Enqueue* and *RMSequence* mediators being used when
implementing mediation logics?
On Wed, Dec 9, 2015 at 12:11 PM, Kasun Indrasiri wrote:
> Shall we deprecate following mediators in 4.10 release.
>
> *- Callout mediator :*
> All the callout functionality is
16 matches
Mail list logo