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
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
On 20 May 2014 20:42, Rajith Vitharana raji...@wso2.com 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
I propose triggers as the name for the things that kick off sequences.
On Mon, Apr 7, 2014 at 8:02 PM, Srinath Perera srin...@wso2.com 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
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
