Re: [Architecture] [Dev] Working With VFS Sender in ESB

Yep Malaka. I have implemented this feature. Best Regards, Yashothara.S Software Engineer WSO2 On Wed, May 18, 2016 at 9:24 AM, Malaka Silva wrote: > Hi Yashothara, > > Have we implemented this feature? > > On Wed, May 4, 2016 at 12:54 PM, Yashothara Shanmugarajah < >

Re: [Architecture] [Dev] Working With VFS Sender in ESB

Hi Yashothara, Have we implemented this feature? On Wed, May 4, 2016 at 12:54 PM, Yashothara Shanmugarajah < yashoth...@wso2.com> wrote: > Hi all, > > I have herewith attached the link [1] to my milestone plan for the File > Connector project. Please be kind enough to provide necessary

Re: [Architecture] Improving error handling at different layers in ESB

Hi Kasun, In the axis2 level, we can see "sendStacktraceDetailsWithFaults" and "DrillDownToRootCauseForFaultReason" parameters. Can't we use those parameters to propagate the errors happens in the transport layer? Thanks. /Susankha. On Tue, May 17, 2016 at 11:47 AM, Kasun Indrasiri

Re: [Architecture] Improving error handling at different layers in ESB

For most of E3 type errors (such as timeout, connection closing etc.) we do invoke fault sequence (if not specified default fault sequence) of the associated mediation logic. However, the current design doesn't not guarantee that all possible errors are handled in that way. That's why we need a

Re: [Architecture] Product Integration Server thread model and implementation

Hi Ranawaka, I think we should finalize the decision on the default thread model of the transport and the engine. How does the poc implementation with multiple disruptors (dedicated disruptors for IO and CPU bound work) perform? Thanks, Kasun On Sun, Apr 24, 2016 at 9:19 PM, Isuru Ranawaka

Re: [Architecture] [Siddhi] Making Disruptor configurable

Hi Suho, We have observed similar behavior with recent Gateway framework development in which the heavy resource consumption overrules the performance gain that the Disruptor brings in. Also for IO bound scenarios we tried using dedicated Disruptors for CPU and IO bound scenarios but that again

[Architecture] Fwd: Solution for Gadgets Responsive Issue

Hi Jerad, How this is normally handled in gadget world is by all ways write the gadget to take the full width. It's bit odd that you have a scenario where the gadget needs to know the size of the external container. We also have the full-screen view VS normal view feature. Can you give an explain

Re: [Architecture] [C5] [OSGi] Pax Exam Container for Carbon 5 - In-Container Testing

Hi all, I'm trying to implement the pax exam container for C5. I'm going to implement the container like the existing Karaf container in pax exam[1]. So initially there has to be two implementations of "TestContainer" and "TestContainerFactory" interfaces in pax exam. Currently I'm working on

Re: [Architecture] Comments about IoTS Docs

agreed, I think challenge it making it clear that power of a full blown analytics platform is behind the IoT product. I think from the doc, and site, it is not apparent. Also, in future version, IoT tooling can carry Analytics tooling intergated . --Srinath On Tue, May 17, 2016 at 3:47 PM,

Re: [Architecture] Adding arbitrary mapping in siddhi / execution plan validation

Yes.. +1.. On Tue, May 17, 2016 at 2:48 PM, Sajith Perera wrote: > +1,Yes this can be done, as we can read the annotation keys and values. > > On Tue, May 17, 2016 at 2:42 PM, Sriskandarajah Suhothayan > wrote: > >> How about >> >> @Import('loganalyzer:1.0.0',

Re: [Architecture] Comments about IoTS Docs

Srinath, We are already doing this. For device type analytics, you can include those queries as part of device plugin. We deploy them as CAR files into DAS. For example https://docs.wso2.com/display/IoTS100/Device+Manufacturer#DeviceManufacturer-WritingbatchanalyticsforConnectedCup For anything

Re: [Architecture] ESB Debugger - Representing wire message debugging at the visual editor

Hi Kasun, On Tue, May 17, 2016 at 4:05 AM, Kasun Indrasiri wrote: > Looks good. > > How do we handle the use cases in which we have multiple requests going > out from ESB (i.e. such as service chaining scenario). In that case can we > clearly identify and correlate wirelogs

Re: [Architecture] Comments about IoTS Docs

Thanks Sumedha. Suho, are we going to support users to write queries CEP, Spark on top of this data IoTS captured? ( or is it for future releases?) IMO that will add lot of values to the story. --Srinath On Tue, May 17, 2016 at 10:59 AM, Sumedha Rubasinghe wrote: > > > On

Re: [Architecture] Introducing Secure-Vault support to C5

Manu, I prefer the approach Sameera mentioned as it is independent of the config file and will work with any future config file as well. --Srinath On Fri, May 13, 2016 at 7:26 PM, Manuranga Perera wrote: > 1) > >> Now we don't maintain passwords or any sensitive data in the >>

Re: [Architecture] Improving error handling at different layers in ESB

On Tue, May 17, 2016 at 11:28 AM, Isuru Udana wrote: > Hi Srinath, > > On Tue, May 17, 2016 at 11:13 AM, Srinath Perera wrote: > >> Kasun, what is the answer? >> >> Problem is that client does not know when the result will come back. >> >> >>1. If client