On Tue, Sep 22, 2015 at 11:53 AM, Malaka Silva wrote:
> Hi Ajith,
>
> It seems the change was not merge for some reason. [1]
>
> [1] https://github.com/wso2/wso2-synapse/pull/214
>
Thanks Malaka. Created a JIRA to track
https://wso2.org/jira/browse/ESBJAVA-4232
-Ajith
>
> On Tue, Sep 22, 2015
Hi Ajith,
It seems the change was not merge for some reason. [1]
[1] https://github.com/wso2/wso2-synapse/pull/214
On Tue, Sep 22, 2015 at 9:12 PM, Ajith Vitharana wrote:
> Hi Buddhima
>
> On Tue, Sep 22, 2015 at 11:36 AM, Buddhima Wijeweera
> wrote:
>
>> Hi Ajith,
>> Example2 shows that:
>>
Hi Buddhima
On Tue, Sep 22, 2015 at 11:36 AM, Buddhima Wijeweera
wrote:
> Hi Ajith,
> Example2 shows that:
> https://docs.wso2.com/display/ESB490/Property+Mediator
>
I'm getting following exception when I try to save the synapse config in
ESB 4.9.0.
[2015-09-22 11:41:35,940] INFO - Deploymen
Hi Ajith,
Example2 shows that: https://docs.wso2.com/display/ESB490/Property+Mediator
Thanks,
On Tue, Sep 22, 2015 at 9:03 PM, Ajith Vitharana wrote:
> Hi All,
>
> Do we support this in ESB 4.9.0 ? if so please point me the doc.
>
> -Ajith
>
> On Wed, Jun 3, 2015 at 2:21 AM, Susinda Perera wro
Hi All,
Do we support this in ESB 4.9.0 ? if so please point me the doc.
-Ajith
On Wed, Jun 3, 2015 at 2:21 AM, Susinda Perera wrote:
> Don't we need to restrict this to a particular space in registry? So that
> this would not overwrite the wanted data.
>
> On Tue, Jun 2, 2015 at 11:02 PM, Kas
Don't we need to restrict this to a particular space in registry? So that
this would not overwrite the wanted data.
On Tue, Jun 2, 2015 at 11:02 PM, Kasun Indrasiri wrote:
> Looks good. Please proceed with the fix and update the documentation.
>
> On Mon, Jun 1, 2015 at 10:44 AM, Nadeeshaan Guna
Looks good. Please proceed with the fix and update the documentation.
On Mon, Jun 1, 2015 at 10:44 AM, Nadeeshaan Gunasinghe
wrote:
> Hi all,
> In order to persist content in to mediation layer I added an initial
> implementation and via that we can use the following mediation logic to
> store n
Hi all,
In order to persist content in to mediation layer I added an initial
implementation and via that we can use the following mediation logic to
store new persistent content in the registry,
and
In this implementation it uses scope to determine whether the content need
to be stored persiste
Hi,
Yes this make sense if the provider does not support password grant type.
But my concern is security. If we save the access tokens and refresh token
it's visible to all parties.
Can we do the same with secure-vault instead. WDYT?
eg:-
wso2:vault-lookup('UserManager.AdminUser.Password')
ws
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.
Therefore a generic mechanism of persisting content from mediation flow
wi
10 matches
Mail list logo