;>>>>
>>>>>> false
>>>>>>
>>>>>> PMode.Responder.Party
>>>>>>
>>>>>> true
>>>>>>
>>>>>> PMode.Responder.Role
>>>>>>
>>>>>>
t;
>>>>
>>>
>>>
>>> --
>>>
>>> *Sanjeewa Malalgoda*
>>> WSO2 Inc.
>>> Mobile : +94713068779 <+94%2071%20306%208779>
>>>
>>> <http://sanjeewamalalgoda.blogspot.com/>blog
>>>
| middleware
>> Mobile | +94752833834|+94777226874
>> Email | raj...@wso2.com
>> LinkedIn <https://lk.linkedin.com/in/hmohammedrajjaz> | Blogger
>> <http://rajjazhm.blogspot.com/> | WSO2 Profile
>> <http://wso2.com/about/team/mohammer-rajjaz/>
>>
gt;>>>>>>>
>>>>>>>>>>>>> *Sanjeewa Malalgoda*
>>>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>>>> Mobile : +94713068779
>>>>>>>>>>>&g
es.
>>
>> The initial source code of this effort can be found in WSO2 Incubator
>> [1]. Please feel free to try this out and share your thoughts.
>>
>> [1]
>> https://github.com/wso2-incubator/js-tooling-framework
>>
>> Thanks
>>
>>
Shall we finalize the things that are going to deprecate in ESB 5?
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
ntioned other
> possible functionalities that can be included as well in the document.
> Please update the document for further requirements.
>
> [1].
> https://docs.google.com/a/wso2.com/spreadsheets/d/1uDLkH-_Ce2YJUSL6QoP_i_PU7jzMBJzF2mCrhSo8q-A/edit?usp=sharing
>
> Thanks,
>
>
e more efficient scoped-style
>>> efficient implementation? This would prevent the registry performance hit,
>>> and prevent the necessity for customers to modify all their xml code.
>>>
>>>
>>>
>>> Thanks,
>>> Colin Roy-Ehri
>&g
ord=[wso2carbon]
>>>>>
>>>>>
>>>>> *New design decisions taken compared to C4 SecureVault implementation:*
>>>>>
>>>>>1. We have removed the usage of cipher-tool.properties file. (This
>>>>>file was u
gt;
>>
>>>
>>> --Srinath
>>>
>>> On Tue, May 17, 2016 at 10:33 AM, Artur Reaboi <artur.rea...@egov.md>
>>> wrote:
>>>
>>>> +1
>>>>
>>>>
>>>>
>>>> Are there any worka
(CPU )
>>>>>>>
>>>>>>> Header based routing , send messages to Echo service and respond
>>>>>>> back to client.
>>>>>>>
>>>>>>> TPS
>>>>>>>
>>>>>>>
n.blogspot.com/>twitter:
> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in:
> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
>
> ___
> Architecture mailing list
> A
ire logs for mediators
>> (for example if there is a send mediator in the flow, we can see the
>> wirelog sent to back end from the send mediator and the response for it,
>> faced some difficulties when relating those information with the
>> corresponding mediator when the mess
and error handling happens in the fault sequence.
Therefore we need to carefully evaluate the possible places that the errors
can occur and handle them at an unified layer.
Thanks,
Kasun
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Hi,
We need to make sure that all the possible mediation stats are exposed via
JMX too. We had JMX support in previous impl. Hence we can't lose that in
the new impl.
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http
to make it a part of the message context as we don't
>>> have access to any context at the Wire level (Not even the http core level
>>> context).
>>>
>>>
>>> On Tue, Apr 5, 2016 at 9:11 AM, Kasun Indrasiri <ka...@wso2.com> wrote:
>>&g
--
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email *nuw...@wso2.com <nuw...@wso2.com>*
> Mobile *+947190797
t;isu...@wso2.com> wrote:
>
>> Hi Kasun,
>>
>> It is not possible to make it a part of the message context as we don't
>> have access to any context at the Wire level (Not even the http core level
>> context).
>>
>>
>> On Tue, Apr 5, 2016 at 9:11 AM, Kasu
the above use case too. WDYT?
On Tue, Apr 5, 2016 at 9:11 AM, Kasun Indrasiri <ka...@wso2.com> wrote:
> Can we have wire level message information as part of the message context
> (Of course we have to do this only if debugging is enabled or something),
> so that we can correlate
wire.
> WDYT?
>
> Thanks,
>
> On Thu, Mar 31, 2016 at 10:54 AM, Kasun Indrasiri <ka...@wso2.com> wrote:
>
>> Hi,
>>
>> We came across a sort of a mandatory requirement for debugger : debugging
>> wire
>> level message from the visual editor. We
).
With this feature, the debugger can be used to design/debug complete end to
end message flows in ESB.
Thanks,
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com
>>>>>>>
>>>>>>>> I tried implementing the same MockEngine Example
>>>>>>>> <http://shafreenanfar.blogspot.in/2016/03/write-your-own-engine-for-wso2-gw.html>,
>>>>>>>> but I'm getting this Error <http://
re; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * <http://www.apache.org/>*
>>> *email: **az...@wso2.com* <az...@wso2.com>
>>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>>> *htt
gt; is unacceptable.
> On Mar 11, 2016 9:45 AM, "Isuru Ranawaka" <isu...@wso2.com> wrote:
>
>> Hi ,
>>
>> We have already added native worker pool for Disruptor and Samiyuru is
>> doing testing on that. We will make disruptor optional as well.
>>
>&
http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>
> _______
> Architecture mailing list
> Architecture@wso2.org
> https://mail.ws
> >>
> >
>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 777542851
> ___
e: ESB Analytics Mediation Event Publishing Mechanism
To: Anjana Fernando <anj...@wso2.com>
Cc: "engineering-gr...@wso2.com" <engineering-gr...@wso2.com>, Srinath
Perera <srin...@wso2.com>, Sanjiva Weerawarana <sanj...@wso2.com>, Kasun
Indrasiri <ka...@wso2.com>
apability.
>> Once DevS team build the visual debugging interface users can use DevS to
>> test and debug the implementations on the fly for any product.
>>
>> Thanks and Regards,
>> Harshana
>>
>> On Tuesday, 19 January 2016, Kasun Indrasiri <ka...@wso2.co
custom
>> gateway as we need.
>> Store do not need direct service access of gateway.
>>
>> Thanks
>> sanjeewa.
>>
>> sent from my phone
>> On Jan 18, 2016 10:59 PM, "Kasun Indrasiri" <ka...@wso2.com> wrote:
>>
>>> Hi,
&
ssary.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog :
.
So that means we have to use a dedicated HTTP port with WebSocket support.
Kevin can you please share the main WebSockets use cases that we came up
with.
Thanks,
Kasun.
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http
ediation other
>> for the backend to client mediation.
>>
>> 3. Support different content types for Websocket frames dynamic way. This
>> is handled using Websocket Sub protocol.
>>
>> Regards
>> Kevin
>>
>> On Tue, Dec 22, 2015 at 10:22 AM, Kasun Indr
le to return a single row of data,
>>>>> DB Report mediator is still quite useful in writing to a database,
>>>>> especially when we use a DB as part of the mediation sequences.
>>>>>
>>>>> I also feel it is worth continuing with POJOCommand
gt; *- Router* : Same as filter mediator, so no use of having this.
>>> *- In, Out * : Rarely used and often not required with the new
>>> call/respond mediator approach.
>>>
>>> +1 for deprecating these mediators.
>>>
>>> With the new DAS
this.
*- In, Out * : Rarely used and often not required with the new call/respond
mediator approach.
Any comments on these or any other features that we should deprecate from
4.10 release?
Thanks,
Kasun.
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
, Malaka Silva <mal...@wso2.com> wrote:
> Resolved the jira. Check the functionality on pre release pack and seems
> to be working.
>
> On Wed, Dec 2, 2015 at 10:14 AM, Kasun Indrasiri <ka...@wso2.com> wrote:
>
>> I think all the required changes are already merg
Down/index.html
>
> Thanks,
> Dunith
>
>
>
> On Thu, Dec 3, 2015 at 6:49 PM, Kasun Indrasiri <ka...@wso2.com> wrote:
>
>> Are we planning to support this at framework/DAS level itself. I think
>> this will be a common requirement for ESB, CEP and BPS etc. So,
sharing
>
> [5]
> https://drive.google.com/a/wso2.com/file/d/0Byt7F9S8tb-DWnNDZk5xZGtTRHc/view?usp=sharing
>
> [6]
> https://drive.google.com/a/wso2.com/file/d/0Byt7F9S8tb-DRlFKa2FpMG5fd00/view?usp=sharing
>
> [7] http://jsfiddle.net/virajsen/pofy6c7t/embedded/result/
>
>
/team/malaka-silva/>
>> https://store.wso2.com/store/
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>> _______
>> Ar
additions to support tracing and stats.
Thanks,
Kasun.
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Architecture mailing list
Architecture
zeez
>> <http://lk.linkedin.com/in/afkhamazeez>*
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> *Kishanthan Thangarajah*
> Associate Technical Lead,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94
later in the day we need to upgrade all
>> products and it’s less complex in deployment. And also in the worst case if
>> we can’t patch with the logging feature then log download function won’t be
>> available immediately to ESB application types.
>>
>> T
Hi,
I think we need to rethink the connector versioning approach. As we have
many connectors in the connector store, we should cater the needs to using
two different version of the same connector in the same ESB runtime.
Any thoughts?
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http
Hi,
Is it possible to add this as a new feature at carbon level? I think when a
CApp deployment initially fails due to intermittent resources/databases
unavailability etc., it may be required to have a re-try mechanism for
re-deploying artifacts without user intervention.
Thanks.
--
Kasun
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo
list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell
What's the current status of the project? There are no updates for weeks
:(.
On Tue, Jul 7, 2015 at 4:39 PM, Kasun Indrasiri ka...@wso2.com wrote:
Hi Achintha,
As we are behind the schedule, we need to complete the end to end message
flow for content aware scenarios. We expect you to finish
Hi Chanka,
Can you please provide a status update on the project?
On Tue, Jun 30, 2015 at 1:06 PM, Chanaka Sampath Cooray
chanakasampat...@gmail.com wrote:
Hi Kasun,
Added to the doc.
Thanks,
On Tue, Jun 30, 2015 at 12:44 PM, Kasun Indrasiri ka...@wso2.com wrote:
Hi Chanaka,
I think
.
On Tue, Jul 7, 2015 at 4:22 PM, Kasun Indrasiri ka...@wso2.com
wrote:
Any progress on this task?
On Thu, Jul 2, 2015 at 11:09 PM, Malaka Silva mal...@wso2.com
wrote:
Hi All,
Shakila will be starting to implement this functionality from ESB
side.
@Shakila - Any blockers user this mail thread
|** rimmythepaperclip.blogspot.com
http://rimmythepaperclip.blogspot.com*
*Twitter|* @rimmynuts(A.Reemal)
*LinkedIn|* lk.linkedin.com/in/achinthareemal/
*Mobile| *0715471301
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http
.
Thanks and Regards
/Jasintha
On Tue, Jun 30, 2015 at 5:11 PM, Kasun Indrasiri ka...@wso2.com wrote:
Hi,
AFAIR, this was discussed several times. But in the context of ESB as a
service, I think this will be quite useful. I don't think we have any
technical difficulty in doing this.
Use
as part of the cApp, then the connector
deployment is completely transparent to the users.
WDYT?
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com
at Inbound EP level, so that we can specify the
allowed services and APIs (as a pattern matching expression) when we define
an inbound EP.
Any thoughts?
Thanks,
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http
perspective)
How about using the following config, so that the UI and engine is using
the same semantics.
parameter name=transport.vfs.FileURI*$registry:*
conf:/repository/esb/esb-configurations/test/parameter
On Tue, Jun 16, 2015 at 10:50 AM, Kasun Indrasiri ka...@wso2.com wrote:
Great. Must
required property values from the context.
@Nadeeshan : we need to include $registry: as well.
Any other use cases that we need to cover?
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/
http://wso2.com/about/team/malaka-silva/
Save a tree -Conserve nature Save the world for your future. Print this
email only if it is absolutely necessary.
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
AM, Kasun Indrasiri ka...@wso2.com wrote:
Hi Malaka,
Do we support this capability in the current inbound implementation?
On Mon, May 11, 2015 at 8:34 PM, Malaka Silva mal...@wso2.com wrote:
Hi,
This will cover the following requirement.
*Use Case:*
User should be able to use the same
://buddhimawijeweera.wordpress.com
GitHub Profile: https://github.com/Buddhima
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
');
On Tue, May 26, 2015 at 9:51 AM, Kasun Indrasiri ka...@wso2.com wrote:
Hi,
It is often required to persist content into the underlying registry
impl during message mediation (in stateful mediation scenarios). For
example, with connector we need to keep the access token/refresh token
persisted
using its scope concept.
property name=conf:/Resource/bar value=xx | expression=yy
scope=registry/
Please share your thoughts.
@Nadeeshan/Buddhima : Will this design fits into solving access
token/refresh token handling limitations with Connectors?
--
Kasun Indrasiri
Software Architect
WSO2, Inc
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com
|* lk.linkedin.com/in/achinthareemal/
*Mobile| *0715471301
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Architecture mailing list
Architecture
.
WDYT?
--Srinath
--
Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
Site: http://people.apache.org/~hemapani/
Photos: http://www.flickr.com/photos/hemapani/
Phone: 0772360902
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
.org/cgi-bin/mailman/listinfo/architecture
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org
team (again, there are exceptions, but team has to
justify that). For example, ESB can't depend on corbon-governance
SNAPSHOT.
On Tue, Mar 10, 2015 at 8:10 AM, Sagara Gunathunga sag...@wso2.com
wrote:
On Tue, Mar 10, 2015 at 12:34 AM, Kasun Indrasiri ka...@wso2.com
wrote:
How about
Blog ; http://ssagara.blogspot.com
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org
https
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com
/chanakaudaya
Wordpress:http://chanakaudaya.wordpress.com
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Architecture mailing list
Architecture
use Callout mediator at the moment). However, having 'Call' and 'Callout'
mediators is very confusing for the users and we need to have a single
mediator with both capabilities. Hence we can add the blocking support as
part of the Call mediator and deprecate Callout mediator.
Thanks,
--
Kasun
to be working fine with
inbound eps.
On Mon, Jul 14, 2014 at 4:35 PM, Kasun Indrasiri ka...@wso2.com wrote:
+1. Basic UI should be sufficient.
On Mon, Jul 14, 2014 at 8:58 PM, Malaka Silva mal...@wso2.com wrote:
Shall we also do a simple UI for inbound Endpoints?
On Thu, Jul 10, 2014 at 1:32 PM
:-).
Sanjiva.
On Mon, Jul 21, 2014 at 8:31 AM, Kasun Indrasiri ka...@wso2.com
wrote:
Hi Sanjiva,
I think the problem we have with inbound HTTP and existing
HTTP transport is that, they are completely isolated. So, even
if we implement the new InboundEP
.
-
Thanks.
Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com
-- Forwarded message --
From: Ishara Cooray isha...@wso2.com
Date: Sun, Jul 6, 2014 at 12:39 PM
Subject: [Architecture] Kafka transport for WSO2 ESB
To:
Cc: Kasun Indrasiri ka...@wso2.com, Srinath Perera srin...@wso2.com,
Samisa Abeysinghe sam...@wso2.com, Kathees Rajendram
kath
://twitter.com/kishanthan*
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org
https
/Ishan : Any thoughts on the complexities involved with this.
Thanks,
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Architecture mailing
We need to test the coordination behavior of inbound endpoints and make
sure it executes only on manager and an elected worker node.
@Ishan : Please update the thread once we are done with the
implementation/verification.
On Mon, Apr 28, 2014 at 8:01 AM, Kasun Indrasiri ka...@wso2.com wrote
, 2014 at 11:22 AM, Kasun Indrasiri ka...@wso2.com wrote:
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
and output will always be same. We
can specific this in init method of the connector definition.
On Tue, May 13, 2014 at 5:07 PM, Kasun Indrasiri ka...@wso2.com wrote:
Hi,
We been working on the initial design of the type-aware mediator concept
for ESB. The main objective
generating
the required ESB configuration.
Thanks,
Viraj.
On Tue, May 20, 2014 at 10:53 PM, Kasun Indrasiri ka...@wso2.com wrote:
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
and please
share your thoughts too.
Thanks.
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org
,
Malaka
On Fri, Apr 25, 2014 at 5:44 PM, Sriskandarajah Suhothayan
s...@wso2.com wrote:
Thanks, This code reuse is very useful.
CEP team will start integrating when this its ready.
Regards
Suho
On Fri, Apr 25, 2014 at 4:24 PM, Kasun Indrasiri ka...@wso2.comwrote:
Hi Suho,
As per
like what axis2 JMS transport was doing etc.
We'll work with you on the integration
Thanks
Suho
On Mon, Apr 21, 2014 at 9:56 AM, Kasun Indrasiri ka...@wso2.com wrote:
Hi Suho,
We are not dependent on any axis2 related transport. The generic
functionalities related to protocols such as JMS
, Apr 16, 2014 at 2:08 PM, Kasun Indrasiri ka...@wso2.com wrote:
We need to finalize the tooling aspect of this too. Ideally this is
another entry point to ESB, which is very similar to a proxy service or a
REST api. Any thoughts on how we should proceed with the tooling aspect of
this?
On Wed
We need to finalize the tooling aspect of this too. Ideally this is another
entry point to ESB, which is very similar to a proxy service or a REST api.
Any thoughts on how we should proceed with the tooling aspect of this?
On Wed, Apr 9, 2014 at 3:01 PM, Kasun Indrasiri ka...@wso2.com wrote
or NTaskManager).
@Kasun/Anjana: are we missing something here?
Thanks,
Chanaka
On Sat, Apr 5, 2014 at 9:32 AM, Kasun Indrasiri ka...@wso2.comwrote:
On Sat, Apr 5, 2014 at 9:22 AM, Anjana Fernando anj...@wso2.comwrote:
Hi Ishan,
On Sat, Apr 5, 2014 at 7:33 AM, Ishan Jayawardena is...@wso2
the functionality in super tenant
and tenant mode as well.
Ravi is working on getting the end to end scenario working for JMS Inbound
EP.
Please review the design and share your thoughts.
Thanks,
Kasun
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94
are planning to do a poc around the above mentioned design and then we
can do a review.
Please correct me if I miss any thing related to this topic and please
share your thoughts on this too.
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94
or omissions.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http
Wheeler jac...@wso2.com wrote:
Please summarize the changes so I can update the docs. I'm not sure we
came to a final conclusion on naming.
Thanks,
Jackie
On Mon, Nov 18, 2013 at 12:02 AM, Kasun Indrasiri ka...@wso2.com wrote:
Hi Shafreen,
Lets get these changes in to the next build
...@wso2.com isabe...@wso2.com - mobile: +34 616050684
On Thu, Nov 7, 2013 at 7:57 PM, Jackie Wheeler jac...@wso2.com wrote:
Can we rename the configKey attribute to initKey to make it clearer?
On Thu, Nov 7, 2013 at 7:14 AM, Kasun Indrasiri ka...@wso2.com wrote:
Let me try to write
@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
--
S.Uthaiyashankar
VP Engineering
WSO2 Inc.
http
://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Architecture mailing list
Architecture
We need to do the $subject as part of the cloud connector tooling. We
already have a maven archetype for creating custom connectors and DevS can
directly use that for the new wizard.
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http
/in/ssagara
Blog ; http://ssagara.blogspot.com
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Architecture mailing list
Architecture@wso2
, Oct 8, 2013 at 5:31 PM, Kasun Indrasiri ka...@wso2.com wrote:
Hi,
We have been using PF for JSON based RESTful integration and there seems
to have several areas to improve.
- JSON-JSON - This works fine with JSON Path[1].. but we have to use
JSON streaming builders/formatters.
- XML- JSON
-path functionality as an extension to
expression (we have done this for Payload Factory).
[1] https://code.google.com/p/json-path/
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com
/in/rumeshbandara*
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 71 536 4128
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 71 536 4128
Blog : http://kasunpanorama.blogspot.com/
___
Architecture mailing list
1 - 100 of 117 matches
Mail list logo
