Noted
On Wed, May 21, 2014 at 11:57 AM, Rasika Hettige wrote:
> Hi Malaka,
>
> As suggested by you, following will be the final list of methods that will
> develop in this connector.
>
> createDomain - Creates a new domain
> deleteAttributes - Deletes one or more attributes associated with the
Hi Malaka,
As suggested by you, following will be the final list of methods that will
develop in this connector.
createDomain - Creates a new domain
deleteAttributes - Deletes one or more attributes associated with the item.
deleteDomain - The DeleteDomain operation deletes a domain.
getAttribute
Hi Kevin
As we agreed in the first meeting, you should come up with your own
milestone plan, So can you please share that before EOD
/Jasintha
On Wed, May 21, 2014 at 11:33 AM, Kasun Indrasiri wrote:
> Hi Kevin,
>
> Do we have a milestone plan and the deliverables that we expect deliver. I
>
Hi Kevin,
Do we have a milestone plan and the deliverables that we expect deliver. I
would like to see a demo on the things that are completed.
On Sat, May 17, 2014 at 1:56 PM, Kevin Ratnasekera
wrote:
> Simplified and Solved some Issues had in provided links in last email.
>
> [1]
> https://g
Hi Viraj,
When generating a connector invoke mediator out of a connector, we can
extract the supported data format from the connector and set that as the
input and output type of that mediator. The idea is to use single api to
extract the input and output type across all mediators. Lets have a rev
I propose "triggers" as the name for the things that kick off sequences.
On Mon, Apr 7, 2014 at 8:02 PM, Srinath Perera wrote:
> Hi Paul,
>
>
> Its a good question. I think the basic idea here is that you cannot rely
>> on which thread you are on. i.e. there is no guarantee of threads being the
Hi,
When we consider putting Data mapper mediator in between two connector
operations in Developer Studio, we can use following steps to deduce input
and output types for Data mapper mediator without asking user to provide
them.
1. Since we are going to include the supported message type or me
On 20 May 2014 20:42, Rajith Vitharana wrote:
> Hi Lasantha, Kasun,
>
> Here we are trying to achieve is giving a http endpoint so that a
> javascript could be able to invoke that endpoint with usage statistic of
> specific client web application. It doesn't matter where the web
> application is
DM between Connector invocations is the prime candidate for the application
of this concept. As we are quite certain on what needs to be done from ESB
level, we have to work closely with the DevS to get the story right.
On Tue, May 20, 2014 at 5:18 PM, Jeewantha Dharmaparakrama <
jeewan...@wso2.c
Hi Lasantha, Kasun,
Here we are trying to achieve is giving a http endpoint so that a
javascript could be able to invoke that endpoint with usage statistic of
specific client web application. It doesn't matter where the web
application is hosted. It could be any Server. The point is that, the web
Hi,
Just a reminder for chunk 11 release
We hope to get org.wso2.carbon.apimgt.interceptor.feature bug fixed version
as 1.2.2 and start up publisher
org.wso2.carbon.apimgt.startup.publisher.feature as version 1.2.2 for EMM
release.
Also org.wso2.carbon.apimgt.core can we continue with version 1.
We already have a data publisher and a toolbox in place to publish web
application statistics to BAM. [1] What are you trying achieve here
specifically?
[1]
https://docs.wso2.org/display/AS521/Web+Application+Statistics+Monitoring+with+BAM
On Tue, May 20, 2014 at 6:23 PM, Lasantha Fernando wrote
Hi Rajith,
Since this seems to be an adaptor for HTTP which uses servlets, I was
wondering whether it is similar to HTTP input/output adaptors in CEP. You
can find more info at [1,3] and the servlet implementation at [2].
[1]
http://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/componen
We have implemented the $subject and it is available in the ESB's git repo.
As we initially planned we will be releasing this new task manager with our
next release.
Thanks,
Ishan.
On Mon, Apr 21, 2014 at 5:27 PM, Ishan Jayawardena wrote:
> Today we had a discussion to review the current imple
As we discussed we will be adding getInputType() getOutputType() methods in
the AbstractMediator which can be overridden by the Type aware mediators.
Type aware mediators can be
* All connectors
* All transformation mediators
* Enrich
* Property (When xpath, json path is used)
etc
There are non-t
15 matches
Mail list logo
