Hi Amila,
Noted with thanks!
On Wed, Sep 24, 2014 at 10:34 AM, Amila Maha Arachchi ami...@wso2.com
wrote:
+1 with few suggestions.
Always use meaningful names.
tenantDataTables - tenantDataDeleter.xml
deleteTenantTableData - delete ProductSpecificTenantData
On Wed, Sep 24, 2014 at 12:06
+1 from me as discussed offline.
Azeez
On Tue, Sep 23, 2014 at 7:51 PM, Sagara Gunathunga sag...@wso2.com wrote:
According to Axis2 architecture it calls all registered deployers during
the ConfigurationContext creation process, this is perfectly ok for both
Axis2 standalone server and
-- Forwarded message --
From: Sriashalya Srivathsan asha...@wso2.com
Date: Wed, Sep 24, 2014 at 2:19 PM
Subject: 500,Internal server error
To: architecture-requ...@wso2.org
We are doing meetup conector.we got the error ,while doing Every where
seed.we have reported this problem
Hi All,
Currently I am working on the Front end. These were developed keeping
Kibana as the reference. Currently the UI supports the following tasks.
1. Setting the refresh rate ( Refresh the logging graph and the log
table / Log view )*
2. Setting the Time range ( custom time range or
Is there any specific reason for using jqplot?
AFAIK platform wide, we are using flotchart lib[1] due to advance
customization capabilities.
1. http://www.flotcharts.org/
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Wed, Sep 24, 2014 at 2:48 PM,
Hi,
WSO2 ESB connectors provides the capability to connect to publicly
available APIs using simple xml configurations. This makes the life easier
for the users who are using WSO2 ESB.We have come across a new requirement
for WSO2 ESB connectors for the ongoing IPAAS implementation. In this, we
[Resending with the images]
WSO2 ESB connectors provides the capability to connect to publicly
available APIs using simple xml configurations. This makes the life easier
for the users who are using WSO2 ESB.We have come across a new requirement
for WSO2 ESB connectors for the ongoing IPAAS
Images have not been added due to some limitation in google docs. I am
attaching the images separately and resending.
WSO2 ESB connectors provides the capability to connect to publicly
available APIs using simple xml configurations. This makes the life easier
for the users who are using WSO2
Hi Dakshika,
There is no specific reason. It seems like both jqplot and Flot have the
same customization capabilities.
It will not be hard to change the graph libraries, if it is needed.
Thanks,
On Wed, Sep 24, 2014 at 3:28 PM, Dakshika Jayathilaka daksh...@wso2.com
wrote:
Is there any
Hi all,
Based on an offline discussion we had with EMM team on the where to pick
the data in order to publish, we decided it would be best, not to write a
custom valve and handle it, instead collect all the data at EMM level. This
is because, some data doesn't go through API manager valve
would love to see you move to log4j2 asap.
please take note, that TenantAwarePatternLayout currently is buggy. i filed
https://wso2.org/jira/browse/CARBON-14920 for it, some weeks ago.
regards,
thomas
Am Dienstag, 23. September 2014 schrieb Isuru Perera :
This is not critical, but I think
Yes we should use the same library everywhere .. no need to be different
just to be different :-).
On Wed, Sep 24, 2014 at 5:36 PM, Gimantha Bandara giman...@wso2.com wrote:
Hi Dakshika,
There is no specific reason. It seems like both jqplot and Flot have the
same customization capabilities.
Gimantha,
The important pieces of functionality from my perspective (also, including
Amila, Dimuthu, and Majula - they are using current non-BAM workaround so
might have a lot of feedback as well) are:
1. Like you mentioned, ability to set time/date period with custom values
and presets like
Thanks for the patch Thomas. Sameera, please note. We need to get this into
4.3.
On Wed, Sep 24, 2014 at 11:10 PM, Thomas Wieger developer.wie...@gmail.com
wrote:
would love to see you move to log4j2 asap.
please take note, that TenantAwarePatternLayout currently is buggy. i
filed
+1 to externalize the authorization logic. It will also help evolve the
connectors when OAuth goes out of fashion and another authorization
standard rules over it. What kind of difficulties did you come across? As
long as it is following OAuth 1.0a or 2.0 standard you should be able to be
able to
Hi Gimantha,
If we can correlate log event based on timestamp range from all
services(AS,BPS,AF,etc) that is really useful when identifying issues.
However there are workarounds as well, like opening multiple tabs for each
service and search for same timestamp range.
Apart from that, I think
On Thu, Sep 25, 2014 at 9:24 AM, Ravindra Ranwala ravin...@wso2.com wrote:
The constraints we encountered are listed below.
Different OAuth Providers use different OAuth versions.
Yes. There are two versions 1.0a and 2.0. You don't have any way around
this because some providers still use
I think its true to some extent that some OAuth authorization servers (AS)
use their own configuration parameters and also some what deviate from the
OAuth specification.
What you can do is - keep a basic OAuth 1.0 and 2.0 modules and if you see
a given AS has changed the behavior - extend from
According to the OAuth 2.0 Bearer Token Profile, when accessing a resource
protected with OAuth 2.0, the bearer token can go in the HTTP Authorization
header or be a form-encoded body parameter or a query parameter. If it’s a
query parameter, its value must be access_token. But here, LinkedIn
19 matches
Mail list logo
