On Thu, Nov 20, 2014 at 1:19 PM, Lasantha Fernando lasan...@wso2.com
wrote:
Hi Jo,
Metadata related to the API is retrieved from registry RXT which stores it
in XML format. Can't we put that metadata as XML as well to the archive and
simply push it back to the registry when importing? For
Hi,
Is the documentation done for this?
On Mon, Oct 27, 2014 at 4:47 PM, Elilmatha Sivanesan elilma...@wso2.com
wrote:
I'm refactoring the code as vanji suggested in the code review,I will give
the pull request by tomorrow.
Thank you.
On Mon, Oct 27, 2014 at 1:12 PM, Malaka Silva
please refer the document
https://docs.google.com/a/wso2.com/document/d/1soTciSmkufgx7ch-iV7sOOkBGpxP-0wARlZ4kkFCigQ/edit
On Thu, Nov 20, 2014 at 1:50 PM, Malaka Silva mal...@wso2.com wrote:
Hi,
Is the documentation done for this?
On Mon, Oct 27, 2014 at 4:47 PM, Elilmatha Sivanesan
Hi,
On 20 November 2014 13:36, Ajith Vitharana aji...@wso2.com wrote:
On Thu, Nov 20, 2014 at 1:19 PM, Lasantha Fernando lasan...@wso2.com
wrote:
Hi Jo,
Metadata related to the API is retrieved from registry RXT which stores
it in XML format. Can't we put that metadata as XML as well to
Hi Lasantha
Currently the add-api accepts swagger doc to create an API. So If we are
using the existing services to import it is just a matter of posting the
swagger to the add API.
As Ajith pointed out the other issue is with API related meta data stored
in DB Ex: scopes. If we use swagger we
Hi Shashika,
We have done the necessary changes to Kernel 4.3.0. There are some changes
to be done for tenant.mgt code and the listerners who has implemented the
TenantMgtListener interface. Lets have a chat on how to complete all these
tasks in order to implement a successful tenant deletion.
Hi Elimantha,
Could you please change this documentation so that it complies with our
existing documentation[1]. We need to include all the configurations and
sample scenarios in the documentation in a way such that an end user can
follow very easily.
[1]
Hi,
*Please refer the mail thread : [Architecture] [AF] Capturing BAM events
with an objective of understanding user activity*
Currently I'm working on implementing a common JS library modifying the
above mentioned JS to make it more generic.
User can give the below inputs to this Javascript as
Hi all,
I'm in the process of designing the architecture of Database Snapshot
feature for Storage Server. I had a research on how each RDBMS servers
support creating database snapshots. Here are my findings.
*H2: *In H2, we can create a snapshot through a JDBC call. *SCRIP TO
'{FILE_NAME}'*
Ruchira/Sameera/Manu,
AFAIK we do not have a specific folder to keep JS libraries related to BE
functionality in the current Jaggery App Structure. Only libraries I have
seen (could be wrong) are in themes/{theme name}/lib.
But these libraries are mostly related to UI presentation.
If I am
Is this library a client-side JavaScript file or a *.js file with server
side JavaScript(Jaggery)?
If it is a Jaggery code, then best option would be to make it a Jaggery
module[1]. So, you can version it, share it etc.
If it is a clientside static *.js file, in the current caramel model, we
Useful to have in competition with Storm. Performance is the concern.
One ida is to get extensions as scala function and running is using
https://code.google.com/p/scalascriptengine/
WDYT?
--Srinath
--
Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
12 matches
Mail list logo